This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 10%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
We're seeing the following error in the Event Viewer logs:
"SQL database login for 'SharePoint_Config' on instance 'dbserver' failed. Additional error information from SQL Server is included below. Login failed for user 'domain\machinename$'."
The error stops when we turn off the Microsoft Monitoring Service. We are certain that this is caused by this service as it runs with "Local System" user, and it does not have permission on that database.
Are there any configurations that can be changed in Microsoft Monitoring Agent using SCOM Console or any articles or something would address this issue.
Would be really helpful.
Thank in advance.
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
If monitoring the SharePoint_Config Database is necessary, please configure the Run As Account. If SharePoint monitoring is not required, you may uninstall the SharePoint Management Pack.
The account must be in the Local Administrator group.
Must be Farm Administrators
Must have DBO role on the database side
After completing these steps, we log in to the account.
Thank you :), Issue is resolved using this post and article we were able to convince respective team to change this run as account from SCOM Console.
Along with this also provided Microsoft document as a reference.
https://download.microsoft.com/download/4/1/d/41d7d3f2-ce2d-4082-888f-185dca42474c/system_center_monitoring_pack_guide_for_microsoft_sharepoint_server.docx
