I've recently added multiple downstream servers to a WSUS environment for a client. All the servers are running WSUS version 3 SP2 (3.2.7600.226). All of them seem to be working well, with one exception.
The location in question is operational, and clients have registered and are receiving updates. However, every synchronization since the initial one has failed. The WSUS management console shows the following error for each failed sync:
SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ReadOneRow() at Microsoft.UpdateServices.Internal.DataAccess.HideUpdatesForReplicaSync(String xmlUpdateIds) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessHiddenUpdates(Guid hiddenUpdates) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
This happens at the end of a sync, after the server has already received the new updates from the upstream server. The changes seem to be getting saved properly, as the new, revised, and expired counts aren't climbing constantly.
I also see Event IDs
10032 in the Application log in Event Viewer at the time of each failure.
I've attempted to run the Server Cleanup Wizard on both the upstream & downstream servers, but it's hanging on both when it gets to the stage of deleting unused updates. I ran it on the upstream a week or so ago, just before configuring all the downstream servers, and it worked fine then.
I've also successfully run the reindexing script from this Microsoft forum discussion on both servers. (The cleanup wizard still hangs up after this.)
I've done quite a bit of searching online for this issue, and I've not been able to find anything that works for this situation. I have to think the issue is specific to the downstream server that's failing, since the others are all working fine.
Is there any way to determine exactly what it's doing when it times out?