We help IT Professionals succeed at work.

WSUS Console loosed connectivity to the database.

wheelgunr
wheelgunr asked
on
405 Views
Last Modified: 2017-04-10
Until recently, my WSUS 3.0 SP2 on a 2008R2 server was working fine. In the past few days, the MMC Console has been losing connectivity with the database.

The error that gets pasted to the clipboard is:

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 -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.

Source
.Net SqlClient Data Provider

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetSummariesPerUpdate(String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetSummariesPerUpdate(UpdateScope updatesToInclude, ComputerTargetScope computersToInclude)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetUpdateSummaries(UpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()

I normally just let the WSUS run and do it's thing, occasionally do the server cleanup utility. I'm not a DBA,

Any suggestions or help would be greatly appreciated.
wsus-error.docx
Comment
Watch Question

Vitor MontalvãoIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
How's the SQL Server box? Check the resources (CPU, Memory and Storage).

Author

Commented:
The SQL server and the WSUS server are one and the same. The original physical server was converted P to V over 2 years ago, and was working just fine until earlier this week. I don't believe its a virtual issue, or a hardware issue. I'm thinking it's some I/O connection, but I don't know what to check.
Vitor MontalvãoIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
The SQL server and the WSUS server are one and the same.
Not really good solution but if you have enough resources it should work.
Can you check the server resources?
How's the SQL Server memory's configuration? I'm talking about min_server_memory and max_server_memory values.
What version and edition of SQL Server do you have?

Author

Commented:
It's on a server 2008 R2, and It's using WSUS 3.0 R2.

Nothing physical has changed in the past year, it's only this week that the console started getting errors. That was after the SQL database was reset and the files and database were shrunk.

it's not a physical or resource issue, since it was working earlier this week. It's an issue between the DB and the console.
Vitor MontalvãoIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
It's on a server 2008 R2, and It's using WSUS 3.0 R2.
It's not what I asked. I want to know the SQL Server version and edition.

That was after the SQL database was reset and the files and database were shrunk.
If you shrunk the data files then I'm afraid you got the data pages fragmented. You should run immediately a rebuild. FYI, do not shrink a database.

Author

Commented:
SQL 2005 Express

How do you run a rebuild?
Vitor MontalvãoIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
I'm passing this on to a co-worker to take try. Like I said, I'm not a DBA, I just do the simple stuff.
DonNetwork Administrator
CERTIFIED EXPERT

Commented:
Looks to me that your WSUS cleanup is still running, Take a look here:

http://wininfra.net/2016/05/13/workaround-for-wsus-sql-timeout-errors/
DonNetwork Administrator
CERTIFIED EXPERT

Commented:
BTW, unless you are handling 10,000+ clients, the internal WID is more than capable(no need for SQL Express) There are no size limitations on the WID for the usage of WSUS.
Network Administrator
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
I never knew about the size limit. Like I said, I'm nor a DBA at all.
 But yep, that was it. We've exceeded to limit of the database.

OK, so now I'll create a virtual Server 2016 Data center server, and utilize the built in WSUS.

Thanks to everyone who helped!
Vitor MontalvãoIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
wheelgunr, if this issue has been solved please close this question by accepting the comment or comments that helped you out.
Cheers
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.