Hi,

We are running SCCM 2012 SP1 with Software Update Point on Windows 2012. Since the beginning of the week we are unable to synchronize our Software Update and we receive this error message in the Site Status logs:

Error 7001 from WSUS_Control_Manager

Failures were reported on WSUS Server "servername" for WSUS components "WSUSService,".Solution: Verify that the failed WSUS components are installed and running. WSUS

Error 6703 from WSUS_SYNC_Manager

 

 

Synchronization failed.
Message: The operation has timed out.
Source: .

Here's the content of the wsyncmgr.log:

SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 4296 (0x10C8). SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:12 PM 4440 (0x1158)
Log level 2 SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:17 PM 4296 (0x10C8)
Next scheduled sync is a retry sync at 2013-02-20 2:37:30 PM SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:17 PM 4296 (0x10C8)
Starting Sync SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:53 PM 4296 (0x10C8)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Read SUPs from SCF for servername SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Found active SUP servername from SCF File. SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:33:55.734 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Synchronizing WSUS server servername SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:56 PM 4296 (0x10C8)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:33:56.872 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:56 PM 4296 (0x10C8)
Synchronizing WSUS server servername ... SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:59 PM 4612 (0x1204)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:59 PM 4612 (0x1204)
Sync failed: The operation has timed out SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:49:03.157 2013 ISTR0="" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Setting sync alert to active state on site GPP SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Sync time: 0d00h15m07s SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)

We were able to sync before, but since a couple days we are receiving these errors.

We have a scheduled job on our remote SQL server that re-index the database (http://gallery.technet.microsoft.com/ScriptCenter/6f8cde49-5c52-4abd-9820-f1d270ddea61/) but even after it runs, we still have the problem.

I know that some Windows updates were applied to this server on Sunday night, here's the list:

- KB2803676

- KB2799494

- KB2797052

- KB2795944

- KB2792100

- KB2790655

- KB2789650

- KB2789649

- KB2778344

Maybe it's not related to our problem, but I wanted to give more information than less.

Thank you!

Hi,

Are you running the WSUS server as a Replica Server?

Hi,

No we are not running WSUS as a Replica.

Yes, I know this is an old post, Just cleaning up un-answer posts. Did you figure this out?

Since there have been no other people attempting to answer this question, At this point I would suggest contact Microsoft Support (CSS) directly for support.

Did you ever get this figured out? We are having the exact same issue.

Did you ever get this figured out? We are having the exact same issue.

I had to first remove the SUP role, then uninstall the WSUS server role. I then deleted the WSUS content file share and recreated it, and also made sure the old SUSDB database was gone. I rebooted the server, installed WSUS again and then added the SUP role back. This solved our issues.