WSUS Clients receiving internal server error in ClientWebService RRS feed

  • Question

  • Hi,

    I have spent some time trying to recover a failed instance of WSUS and have it to the point where it is back running but clients cannot connect. Running Windows Server 2012 R2 with built in WSUS 3.

    The error in the IIS logs show a 500 response

    2015-02-18 16:03:51 POST /ClientWebService/client.asmx - 8530 - Windows-Update-Agent - 500 0 64 113530

    I have enabled Failed Request Tracing in IIS and the error I can see in the log indicates a problem with a module, ManagedPipelineHandler:

      <Data Name="ContextId">{00000000-0000-0000-9B03-0080020000DB}</Data>
      <Data Name="ModuleName">ManagedPipelineHandler</Data>
      <Data Name="Notification">128</Data>
      <Data Name="HttpStatus">500</Data>
      <Data Name="HttpReason">Internal Server Error</Data>
      <Data Name="HttpSubStatus">0</Data>
      <Data Name="ErrorCode">0</Data>
      <Data Name="ConfigExceptionInfo"></Data>

    Do I need to reregister ASP.NET as indicated in some forums? All other sites/services appear to be operating normally using the same app pool and configuration.

    The event immediatedly preceeding this in the request log is:

    <RenderingInfo Culture="en-IE">
     <ExtendedTracingInfo xmlns="http://schemas.microsoft.com/win/2004/08/events/trace">
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <Provider Name="ASPNET" Guid="{AFF081FE-0247-4275-9C4E-021F3DC1DA35}"/>
      <TimeCreated SystemTime="2015-02-18T15:13:03.982Z"/>
      <Correlation ActivityID="{00000000-0000-0000-9B03-0080020000DB}"/>
      <Execution ProcessID="27160" ThreadID="26752"/>
      <Data Name="ConnID">0</Data>
      <Data Name="Context ID">{00000000-0000-0000-9B03-0080020000DB}</Data>
     <RenderingInfo Culture="en-IE">

    At this point I am at a loss having spent numerous hours trawling forums for inspiration.

    • Edited by WillDunne Wednesday, February 18, 2015 7:20 PM
    Wednesday, February 18, 2015 4:33 PM

All replies

  • What else is running on that server, and what versions of OS/WSUS are you running? 
    Wednesday, February 18, 2015 4:57 PM
  • Sorry, should have placed that in my original post. Running Windows Server 2012 R2 with built in WSUS 3.

    It had been functioning perfectly for 6 months and 2 weeks ago it stopped. Numerous reinstalls later I managed to get it up by running procmon and identifying permission errors.

    All services now start and I can access the console however the clients cannot report back due to the error detailed above.

    There are a small number of .NET sites running and it also hosts our AV management suite.
    • Edited by WillDunne Wednesday, February 18, 2015 8:12 PM
    Wednesday, February 18, 2015 7:19 PM