I am trying to add WSUS role on a server 2012 r2 server, but wsus installation failed with message:

The request to add or remove features on the specified server failed.

The operation cannot be completed, because the server that you specified requires a restart.

restart the server and do it again, same failure.

Found in system log, there is a service control manager error 7041 which says:

The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:

Logon failure: the user has not been granted the requested logon type at this computer.

 

Service: MSSQL$MICROSOFT##WID

Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID

 

This service account does not have the required user right "Log on as a service."

 

User Action

 

Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

 

If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.

It seems the WID causes the trouble.

I checked in GPO, "NETWORK Service" has logon as service rights and when trying to add NT SERVICE\MSSQL$MICROSOFT##WID it says the account cannot be validated.

The strange thing is in the wizard I removed "WID database" and selected "Database" but in the "confirm installation selections" I can still see "Windows Internal Database" listed.

I am not sure whether some other people encountered this issue and what is the solution.

Thanks for help.

Issue resolved. The WID is automatically selected in the features list in the wizard and need to be manually removed.

Untick the WID database box does not remove it from the features list. Not sure whether this is a bug.

• Marked as answer by TreeLeafs Tuesday, January 07, 2014 4:47 AM
• Unmarked as answer by TreeLeafs Tuesday, January 07, 2014 9:45 PM

Well, it seems the problem has not been really resolved.

WSUS installation was successful, however, WSUS DB has not been created in the SQL server (on local host), and the WSUS service won't start - terminated unexpectedly.

There is a .NET runtime error:

Application: WsusService.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.Security.SecurityException

Stack:

   at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(System.Type, System.Object[])

   at Microsoft.UpdateServices.EventSystem.SusService.SusServiceStartUpThreadProc()

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   at System.Threading.ThreadHelper.ThreadStart()

And an application error:

Faulting application name: WsusService.exe, version: 6.3.9600.16384, time stamp: 0x5215cd75

Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d557d

Exception code: 0xe0434352

Fault offset: 0x000000000000ab78

Faulting process id: 0x1b38

Faulting application start time: 0x01cf0bee3dd6c479

Faulting application path: C:\Program Files\Update Services\Services\WsusService.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 7bb7dd75-77e1-11e3-80d3-0050569271e1

Faulting package full name:

Faulting package-relative application ID:

Any clue?

Thanks for help.

Yes, I know this is an old, post, Just trying to clean them up. Did you figure this out, if so how?