We had to do a restore of our SCCM2012 Db (not in production yet) due to some errors. Everything seems straightened out now except that WSUS synching keeping failing. I removed the SUP and added it back but I keep getting the same errors. Below is a snippet of the wsyncmgr.log:
Synchronizing update 5500ec2c-3f0d-4e77-a236-a944c35a6ad0 - Update for Windows 7 for x64-based Systems (KB976972) $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:09.640+300><thread=4316 (0x10DC)> *** exec sp_SetupCIDocuments 16782235 $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.010+300><thread=4316 (0x10DC)> *** *** Unknown SQL Error! $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.010+300><thread=4316 (0x10DC)> ~Failed to generate documents for Configuration Item 16782235. $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.013+300><thread=4316 (0x10DC)> Failed to sync update 5500ec2c-3f0d-4e77-a236-a944c35a6ad0. Error: Failed to save update 633db0da-be4d-4355-8f23-529ace063c68. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.015+300><thread=4316 (0x10DC)> Synchronizing update ac8734c3-0254-4c7e-9be2-1ff2d8db0eae - Update for Windows 7 (KB977074) $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.100+300><thread=4316 (0x10DC)> *** exec sp_SetupCIDocuments 16782266 $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.468+300><thread=4316 (0x10DC)> *** *** Unknown SQL Error! $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.469+300><thread=4316 (0x10DC)> ~Failed to generate documents for Configuration Item 16782266. $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.472+300><thread=4316 (0x10DC)> Failed to sync update ac8734c3-0254-4c7e-9be2-1ff2d8db0eae. Error: Failed to save update e22312e2-def9-49b1-8be7-de0e1bce46c2. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<SMS_WSUS_SYNC_MANAGER><11-19-2013 09:43:10.475+300><thread=4316 (0x10DC)> I get a number of these and then it stops synching stating that there were too many failures. There is also an error that appears in the SMS Provider log, not sure if it is related or not: ERROR>: CSspQueryForObject::ConvertWBEMTimeToDBTime invalid wbemtime [2013/11/18 15:14:44.000] SMS_POLICY_PROVIDER also logs this: Microsoft SQL Server reported SQL message 50000, severity 16: *** Unknown SQL Error! I have made sure that Trustworthy is TRUE for the SCCM Db and corrected the Db owner as well. Any thoughts of where to go from here? Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State
