Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Our SCCM setup stopped downloading updates 3 days ago.

The error shown on the wsyncmgr.log is this:

Sync failed: The subscription cannot be run at this time. Please wait a few minutes and try again. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER   11/03/2014 02:53:05 p.m.    308 (0x0134)

Everything was running smoothly. I have tried to solve the issue but I'm stuck here.

EDIT: I have rebooted both DB and SCCM servers.

share|improve this question
    
What does google say about the error? Minus this question of course. –  BigHomie Mar 11 at 22:15
    
@MDMoore313 nothing, actually. Other than this question (and one posted by the same author elsewhere), this error message and source don't show up on the Googles. Might be a case for MS support. –  HopelessN00b Mar 12 at 1:30
    
@hopelessN00b your google fu is weak grasshopper lipsync lipsync lipsync.. social.technet.microsoft.com/Forums/windowsserver/en-US/… try rebooting the sql server. –  BigHomie Mar 12 at 3:35
    
@MDMoore313 Different source (System.Web.Services), and a DB reboot fixed the issue in that thread.... which has already been tried here. –  HopelessN00b Mar 12 at 5:10
    
Thanks for the input. I will schedule of both DB and SCCM servers again tonight. Otherwise, I'll have to open the case with MS. If the reboot works, I will update the question. –  er_tomas Mar 12 at 15:42

1 Answer 1

up vote 0 down vote accepted

As stated on the question, I had rebooted the SQL server without success.

I opened a case with MS support and the analyst recommended rebooting both SQL server and SCCM server.

I tried this and the server is now syncing correctly with Windows Update.

The original cause of the issue was that the SQL server ran out of space. I did not have this information before. The space issue was fixed and the server rebooted, however, a reboot of both servers was necessary in this case.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.