WSUS Help

[ITGURU]

Hi

I've had a WSUS server in place for a long time providing updates to clients.

I have just gone to try and connect to the console and i'm getting the following error below. I am using the WIndows Internal Database and NOT sql, so wondering if anyone knows the fix for this.

 

As it's the internal database, how do i add permissions? The service is running. I believe it may only be since I did the last windows update batch on the server.

 

if anyone can help before I crash and burn, please let me know.

Thanks.

 

 

The WSUS administration console was unable to connect to the WSUS Server Database.

 

Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.

 

 

System.Data.SqlClient.SqlException -- Cannot open database "SUSDB" requested by the login. The login failed.

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

 

Source

.Net SqlClient Data Provider

 

Stack Trace:

at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)

at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetTargetGroupById(Guid id)

at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetById(Guid id, UpdateServer updateServer)

at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetComputerTargetGroup(Guid id)

at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

[ITGURU]

For any one else who experiences the issue, it is now solved - It is to do with a windows update and I found the article below. Uninstalling the KB returns it to normal working. kb3159706 is the culprit

 

https://community.spiceworks.com/topic/1629616-wsus-sql-issues

[Cazale]

Thanks for that. Looked on the Microsoft pages for an hour and tried 20 different things, none of them any use. First post I look at on here (yours) and I find the right answer

[KevinH]

If you never plan to have WSUS handle Win10 updates ever again, then killing the update is fine.

 

The problem with the update is that it does require manual configuration after the install, and like all MS documentation, the instructions are in Martian.

 

The human version is here:

https://community.spiceworks.com/topic/1567653-heads-up-kb3148812-for-wsus-servers?page=5#entry-5795194

 

If you aren't running 10 now, fine - but if you add it later - you will be revisiting this update soon enough.

[datar_]

If you want to run Windows 10 updates however, you just need to do a couple of things to fix WSUS.

 

First thing - Re-run the Post install for WSUS by running the command:

 

"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing

 

Then go into Server Manager and install the feature, .Net Framework 4.5 Features > WCF Services > HTTP Activation; If not already installed it will install another feature, Windows Activation Process Model

 

If WSUS doesn't fix itself after that, give the service a reboot.

 

Let me know how you get on