SCM - MS SQL Server Essentials Connection Error - No Permissions

I am using a domain account in SCM to monitor elements in the database. After I added Trusted_Connection=yes to the connection string it worked for all but 10 elements. I kept getting a permissions error for the objects. I changed all sorts of security settings for the account whose credentials I had assigned to the element. I then went into SQL Management Studio and configured logging for success and failed logins. I executed the test on the element and to my surprise the account being used was the polling engines machine account and not the domain user account. Emanon\poller-1$ instead of Emanon\user. Granting the machine account permissions to view the master and msdb. Now all the elements run just fine. Don't understand exactly why the different account is used from the Poller. I have to assume there is a service running as the local machine that isn't using the connection string to connect.

Parm699 2 months ago

The issue you're describing involves a complex interaction between domain authentication, SQL Server permissions, and the behavior of your monitoring system (SCM). Here's an analysis of what's happening:

1. Adding "Trusted_Connection=yes" to the connection string enabled Windows authentication for most elements, but 10 remained problematic.

2. Despite adjusting permissions for the domain user account, errors persisted for these elements.

3. SQL Server logging revealed that the polling engine's machine account (Emanon\poller-1$) was being used instead of the expected domain user account (Emanon\user).

4. Granting the machine account permissions to view the master and msdb databases resolved the remaining issues.

The unexpected use of the machine account suggests that a local service on the polling machine is making the connection, bypassing the specified connection string. This could be due to how the polling engine or a related service is configured to run.

There are a few possible explanations:

1. The polling service might be running under the Local System account, which uses the machine account when accessing network resources.

2. There could be a configuration setting in SCM that's causing it to use the machine account for certain operations.

3. The connection string might not be applied consistently across all elements, causing some to fall back to default authentication methods.

To resolve this permanently, you might want to:

1. Check the service account settings for the SCM polling service.
2. Review SCM configuration for any settings related to authentication or connection methods.
3. Ensure the connection string is applied consistently across all elements.
4. Consider explicitly specifying the domain account in the connection string instead of relying on "Trusted_Connection=yes".

Understanding these intricacies is crucial for effectively managing and troubleshooting database monitoring systems in Windows environments.

For information about server jobs near you, you can check out server jobs near me
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel