February 24, 2011 at 12:05 am
Well after my previous problems, http://www.sqlservercentral.com/Forums/Topic1062029-146-1.aspx
I thought I was ready to go ahead and change the SQL services account on the other servers. One change is that I installed Windows security updates first. Now, Trying to change SQL Services account on another SQL 2005 SP3 server, I get the error:
"WMI Provider Error [call to WMI Provider returned error code 0x800742a2]
And the services won't start. I rebooted and tried again.
I'm setting the services back to old account which seems to works for now, then get some sleep.
Why is changing SQL Services account so troublesome :angry:
Any ideas ?
February 24, 2011 at 10:33 am
And on yet another server, MSSQLSERVER will start with the new account, but SQLSERVERAGENT will not ... ?!?! How can changing an account go wrong in so many different ways ?
February 25, 2011 at 2:03 am
Could you try to add the SQL Server servcie account to local administrator group and try again. I susepct it is permission issue.
February 25, 2011 at 3:03 am
Try this http://support.microsoft.com/kb/955496%5B/url%5D
If you want change the SQL Server service account, use "SQL Server Configuration Manager".
February 25, 2011 at 11:44 am
DBA328 (2/25/2011)
Could you try to add the SQL Server servcie account to local administrator group and try again. I susepct it is permission issue.
I was going to try that next, but I shouldn't have to, should I ? Isn't it a good practice for the SQL Service account to NOT be a local admin ?
nekonecny (2/25/2011)
Try this http://support.microsoft.com/kb/955496%5B/url%5DIf you want change the SQL Server service account, use "SQL Server Configuration Manager".
Yes, I've been using Configuration Manager. Thanks, but I don't think that link applies to my situation.
February 25, 2011 at 6:08 pm
I know it is not recommened to add SQL Server servcie account as local administratror. This is only to validate whether you got permission issue. If you could restart the servcie after that, you could know it is really permission issue.
June 22, 2011 at 5:35 am
I had the same issue. I tried adding the id to local administrator and it worked well.
Thanks All 🙂
November 24, 2011 at 9:32 am
I also had the WMI error after changing the SQL Server service account, but it disappeared when I added the new account to the SQLServerMSSQLServerADHelperUser$ComputerName group.
Maybe this also works for you?
December 3, 2011 at 4:51 am
hi,
Please check in services.msc and click on sql server to check it has been given permissions of network service or local
July 6, 2012 at 7:14 am
Homebrew - did you find the answer to your issue? I'm facing the same thing now myself.
July 6, 2012 at 10:47 am
Can you try giving "Log on as a service" permission?
Administrative Tools -> Local Security Policy -> Local Policies -> User Rights Assignment.
Edit the item "Log on as a service" and add your SQL Service account
October 24, 2013 at 11:35 pm
I had the same issue.
Do it from the step 9. It worked by me.
(I added the SQL user to the SQLServerMSSQLUsers$<Machine>$<SQLInstance> group and it helped)
Bye,
Moha
June 12, 2021 at 12:31 am
Check your certificate in the registry. If there is an error there or for some reason it hasn't access to the certificate, the WMI service won't start.
Jamie
July 29, 2021 at 8:32 am
This was removed by the editor as SPAM
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply