none
Synchronisations not appearing in console, WSUS email alerts not being delivered

    Question

  • Hi

    WSUS 3 SP2 installed on a Windows 2012 member server in an Active Directory domain.

    WSUS was only recently installed on the Win 2012 server. Issues arose during installation and were resolved here and here.

    I have configured WSUS to send notifications via email when scheduled synchronisations download updates and for the delivery of update status summary reports. Neither have been delivered since Oct 10. When I select the Synchronisation node in the WSUS console the last entry is from Oct 10.

    I manually started a synchronisation this morning and the console displays its status as Running, but the console does not update. It has shown Running for over 2hrs:
    http://img59.imageshack.us/img59/7799/h0md.jpg

    When I looked at windowsupdate.log the synchronisation has been successful (I think), as the exit code seems to be OK:
    2013-10-21 07:59:39:458  888 8fc Service **  END  **  Service: Service exit [Exit code = 0x240001]

    ... but there are several warnings. The synchronisation took 11mins. The log for this session can be viewed here: http://sdrv.ms/1azirO0 (4k) or, the entire windowsupdate.log can be viewed here http://sdrv.ms/1aziUji (2MB).

    The Application log contains Errors for Windows Update: 507 and for Windows Error Reporting: 1001 on Oct 10th. 507 has appeared in the past so may not be significant but there are a few 1001's present.
    http://img132.imageshack.us/img132/8472/mwyd.jpg

    The only coincidence I have noticed is that the server was rebooted after the last scheduled synchronisation was completed. This was to install the last round of Windows Updates.

    Anyone know why this is happening and how I can get WSUS to update the Synchronisation node and to start sending email notifications again, please?

    Thanks!

     

    ***********************************************************************

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          10/10/2013 19:21:54
    Event ID:      507
    Task Category: 1
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Janus.htlincs.local
    Description:
    Update Services failed its initialization and stopped.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">507</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-10-10T18:21:54.000000000Z" />
        <EventRecordID>5105</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Janus.htlincs.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Update Services failed its initialization and stopped.</Data>
      </EventData>
    </Event>

    ***********************************************************************

    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          11/10/2013 00:31:47
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      Janus.htlincs.local
    Description:
    Fault bucket , type 0
    Event Name: WindowsUpdateFailure2
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 7.8.9200.16715
    P2: 8024401c
    P3: 00000000-0000-0000-0000-000000000000
    P4: Scan
    P5: 101
    P6: Managed
    P7: 0
    P8:
    P9:
    P10:

    Attached files:

    These files may be available here:


    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 210d22f0-3204-11e3-9401-d4ae52c8bc97
    Report Status: 262144
    Hashed bucket:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-10-10T23:31:47.000000000Z" />
        <EventRecordID>5130</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Janus.htlincs.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>WindowsUpdateFailure2</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>7.8.9200.16715</Data>
        <Data>8024401c</Data>
        <Data>00000000-0000-0000-0000-000000000000</Data>
        <Data>Scan</Data>
        <Data>101</Data>
        <Data>Managed</Data>
        <Data>0</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>210d22f0-3204-11e3-9401-d4ae52c8bc97</Data>
        <Data>262144</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Monday, October 21, 2013 11:28 AM

Answers

All replies

  • Hi,

    For event 507, we may try below resolutions:

    • The Update Services service has been manually stopped. Start the service.
        • Open a command window.
        • Type sc start wsusservice
    • The Update Services service is set to manual and is stopped.
      1. Open a command window.
      2. Type sc config wsusservice start= auto
      3. Type sc start wsusservice
    • The Update Services service failed to start. Review the NT event log for issues that occurred before this event (for example, the SQL database or IIS) and resolve them. Then start the service.
      1. Open a command window.
      2. Type sc start wsusservice

    Please refer to the below link for more details:

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET+Framework&ProdVer=2.0.50727&EvtID=507&EvtSrc=Windows+Server+Update+Services&LCID=1033

    Regards,

    Yan Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Tuesday, October 22, 2013 2:58 AM
    Moderator
  • Thanks a lot for your reply.

    I checked the wsusservice (called WSUS Service in the Services console), and the start up was set to automatic but the service status was stopped. I started the service then ran the wsusutil checkhealth command (In case anyone else needs to run this it was not located where described in the article but was in the following folder on our 2012 member server: C:\Windows\WinSxS\amd64_updateservices-common_31bf3856ad364e35_6.2.9200.16384_none_76cfa995247b9f35)
    C:\Windows\WinSxS\amd64_updateservices-common_31bf3856ad364e35_6.2.9200.16384_no
    ne_76cfa995247b9f35>wsusutil checkhealth
    Done. Please check event log for events with source "Windows Server Update Servi
    ces".
    C:\Windows\WinSxS\amd64_updateservices-common_31bf3856ad364e35_6.2.9200.16384_no
    ne_76cfa995247b9f35>


    Information event 1000 from WSUS was logged in the Application log with 'WSUS is working correctly.'

    I started the WSUS Console and the synchronisation node showed two synchronisation events for today. The first occurred after the service was started and 13 updates were downloaded. The second took place at about the same time that I ran the wsusutil command. An email alert was also delivered when the first synchronisation had succeeded.

    Thanks a lot for the help. Starting the service solved both issues.

    I have tried to mark your esponse as the answer but nothing happens.

    Tuesday, October 22, 2013 8:36 AM