Fatal Error: Cannot start service MSSQL$MICROSOFT##WID on computer '.'.
The specified account has not been given login as a service right.
Now, I'm assuming they create that goofy named account to run the instance of the internal db, but they have apparently forgot to add automation to set the right to logon as a service. This is a bug, I have the same results on two different server 2012 R2 installs. Is there a manual fix for this somewhere I can try? Very irritating.
- Moved by Frank Shen5Microsoft contingent staff, Moderator Friday, June 27, 2014 5:20 AM
>>Fatal Error: Cannot start service MSSQL$MICROSOFT##WID on computer '.'.
>>The specified account has not been given login as a service right.
Regarding this error, we can refer to the following article to troubleshoot.
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
Besides, the following thread focused on the similar issue and can be referred to for more information.
WSUS roles install on Server 2012 Fails
> they have apparently forgot to add automation to set the right to logon> as a serviceAre these servers member of a domain? In this case, the logon as serviceprivilege might get overridden within a domain GPO...
Mal ein GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))
I fixed the problem by installing the windows internal database feature only. Let it fail then reboot and the NT SERVICE\MSSQL$MICROSOFT##WID account is apparently created. Now go into default domain policy and setup computer rights for this user to logon as a service. Once you do this, reboot, then install the windows internal database and it will complete. NOW, you can install wsus without a problem.
Ridiculous. By default all virtual accounts should be able to logon as a service. Since the account is virtual I don't understand why this would be a security problem. Please fix that.