locked
Upstream Wsus server is showing No status for clients connected to a replica Wsus RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have a Wsus environment with one Upstream server and 5 downstream servers, all in replica mode.

    Upstream Wsus server is showing No Status for clients connected to one of the downstream servers.

    On the downstream server the computer objects have correct information of installed, needed and failed updates.

    Clients connected to the other 4 downstream servers are showing correct data.

    Upstream server: Windows Server 2012 R2 with Wsus version 6.3.9600.18228.

    Downstream Wsus server: Windows Server 2008 R2 with Wsus version 3.2.7600.274. 

    I have reinstalled Wsus on the download server concerned.

    I have removed downstream server from upstream server, and made a new synchronization

    Time is ok on both servers.

    Any good ideas to solve this problem.

    Thanks in advanced.

    /Keith

    [changed error description 2017-03-31, mixed together 2 different problems, sorry]


    Thursday, March 30, 2017 8:37 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    I have now found a solution to my problem, this forum thread did it :)
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/77c0602f-ead7-49a2-8486-50920824a237/wsus-patch-status-information-not-rolling-up-from-downstream-to-upstream?forum=winserverwsus

    Close the WSUS console and stop the services in the following order
    Stop ‘Update Services’
    Stop ‘WSusCertServer’
    Stop ‘World Wide Web Publishing Service’
    Stop ‘Windows Internal Database’
    Stop ‘IIS’
    Change the ownership of the following folders from TrustedInstaller to Administrators and add Full Control to Administrators.   You can change the ownership back to NT SERVICE\TrustedInstaller when the   change is done.
    C:\Program Files\Update Services\WebServices\reportingwebservice\Web.Config
    C:\Program Files\Update Services\WebServices\serversyncwebservice\Web.Config
    Search for the key word “Runtime maxRequestLength” from   web.config file and change the value to 10000
    Eg., <httpRuntime maxRequestLength="10000"   /> 
    Start ‘Windows Internal Database’
    Start ‘World Wide Web Publishing Service’
    Start ‘Update Services’
    Start ‘IIS’
    Friday, March 31, 2017 9:38 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Keith Bengtsson,

    Please click "Synchronize Now" on the downstream WSUS servers, then refresh upstream WSUS server, check if after sync, the upstream WSUS server will update the status and reports of the clients.

    Best Regards,

    Anne

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 31, 2017 7:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi and thanks for your answer Anne,

    The downstream server has been running for a year and are synchronizing 24 times/day.

    All computer objects are reported back to upstream server, all their information except their Update status.

    No Status Count says 19316 for all clients, 0 on failed, needed, installed and not applicable.

    On downstream server is the correct Update status shown. 

    Friday, March 31, 2017 7:44 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I have now found a solution to my problem, this forum thread did it :)
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/77c0602f-ead7-49a2-8486-50920824a237/wsus-patch-status-information-not-rolling-up-from-downstream-to-upstream?forum=winserverwsus

    Close the WSUS console and stop the services in the following order
    Stop ‘Update Services’
    Stop ‘WSusCertServer’
    Stop ‘World Wide Web Publishing Service’
    Stop ‘Windows Internal Database’
    Stop ‘IIS’
    Change the ownership of the following folders from TrustedInstaller to Administrators and add Full Control to Administrators.   You can change the ownership back to NT SERVICE\TrustedInstaller when the   change is done.
    C:\Program Files\Update Services\WebServices\reportingwebservice\Web.Config
    C:\Program Files\Update Services\WebServices\serversyncwebservice\Web.Config
    Search for the key word “Runtime maxRequestLength” from   web.config file and change the value to 10000
    Eg., <httpRuntime maxRequestLength="10000"   /> 
    Start ‘Windows Internal Database’
    Start ‘World Wide Web Publishing Service’
    Start ‘Update Services’
    Start ‘IIS’
    Friday, March 31, 2017 9:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I can confirm that it solved my problem too.

    Note that you have to change parameters on both files. I had previously changed only reportingwebservice config, and it was not enough.

    The default value C:\Program Files\Update Services\WebServices\serversyncwebservice\Web.Config file was quite small (100 kb), so I increased it only to 5000 kb, just to be on a safe side.

    Monday, February 25, 2019 11:26 AM