Hope you can follow this and if you need any more information I'll try my best. However despite this the errors still occur, however if I look at running processes on the SQL servers I can see one of the monitoringhost.exe running as the SQL2012 account, so am I missing something with regards to it being a SQL cluster as opposed to Were then edited and the new run as account applied as individual lines one for each node of the clusters. This account is then distributed to all the nodes of the clusters SO I'll just briefly highlight the changes made so far and see if anyone can see what I have missed, or make a suggestion of what to do.Ī user account, lets call it SQL2012, has been created in AD, this account has been given sysadmin access to both clustersĪ run as account has then been created in SCOM 2007 R2 with the credentials SQL2012 applied to it. The problem started when I then rolled out the same fix to the 2 SQL clusters, the errors do not stop. In SQL 2012 so following the following link, I tested it out on a single SQL test server we had and the errors stopped. After a bit of digging I came to the conclusion that this was an error caused by SCOM because the local system account no longer has sysadmin access I am seeing this error message on clusters we have, both contain multiple instances of SQL. Check with any internal users who may have or had access to your SQL to make sure. It is still necessary to have a secure windows account with appropriate permissions to access SQL and change the ‘sa’ password. Hi, I'm hoping someone can help with the above error message. A restart of the SQL, PDM Archive & PDM Database server services are recommended when resetting the ‘sa’ password.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |