none
WSUS 2016 Server - No Data Listed for Update Details RRS feed

  • Question

  • I am seeing the following on my upstream WSUS Server when trying to look at a computer report for any update (doesn't matter if it failed, succeeded, or is downloaded and waiting, I get the same data): "No events are available. This may be because the client has not yet sent the event or the events have been purged from the server. ".

    The steps I am using:

    1. WSUS Console  -> <Server> -> Computers -> All Computers -> Select any computer -> In the lower half of window -> Select: Updates installed/not applicable 

    2. Once the report opens -> Next page -> On the next page click the status for any update.

    On my Upstream Server it returns: "No events are available. This may be because the client has not yet sent the event or the events have been purged from the server. Please refer to %WINDIR%\WindowsUpdate.log on <computer-name> for details."

    The downstream servers are properly reporting, detailed reports, so it seems limited to the upstream server.

    All of my WSUS Servers are the same version: 10.0.14393.2969 on Windows Server Datacenter:  1607 (14393.3274)

    I haven't found a fix for this yet, anyone have any ideas on a fix?

    Please let me know if you need any other information.

    Thanks in advance!


    Portland Public Schools / Systems Administrator II








    • Edited by Adam Seitz Tuesday, November 5, 2019 9:44 PM
    Tuesday, November 5, 2019 8:09 PM

All replies

  • Hi Adam,
      

    Please consider first checking the settings of the Reporting rollup on the upstream server:
         

           
    Then, verify that these clients have been reported to the downstream server normally, and you can check them on the WSUS console > Computers on the downstream server.
        

            

    Hope the above can help you.
             

    Regards,
    Yic

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

    Wednesday, November 6, 2019 1:55 AM
  • Hi Adam,
      

    Please consider first checking the settings of the Reporting rollup on the upstream server:
         

           
    Then, verify that these clients have been reported to the downstream server normally, and you can check them on the WSUS console > Computers on the downstream server.
        

            

    Hope the above can help you.
             

    Regards,
    Yic

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

    Good Morning,

    Thanks for taking the time to reply, I have my Reporting Roll up set to on the upstream server "Roll up status from replica downstream servers".
    Each of the downstream servers are inheriting that the upstream, I just double checked that make sure on every WSUS Server.

    I have 1 Upstream Server and 9 Downstream Servers, the Upstream is defiantly a problem for every system I have checked.
    The Downstream Servers are not working now that I am really digging in, they have the same problem. The systems I spot checked the first time are very old records,
    they have the data, the newer ones do not seems like the records that are less than 2 years old have no data.

    I just connected to every Downstream server and saw the same errors for each device I spot cecked, the problem is larger than I realized.

    Any ideas where to try to fix this?

    Thanks again for your help!



    Portland Public Schools / Systems Administrator II

    Wednesday, November 6, 2019 4:09 PM
  • Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Wednesday, November 6, 2019 4:38 PM
  • Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    I am declining old updates as I approve the new ones  I have a Power Shell script that uses Invoke-WsusCleanupWizard - But I still run the Wizard manually once a week per server, I Have a DB Maintenance script that runs weekly, from time to time I disapprove all unneeded updates.

    At the Moment the Master Upstream has 1,640 unapproved, 1,540 approved, 5,527 declined.

    Thanks for the reply, your script is awesome but we can't afford it at the moment, unfortunately, so I had to use some other free scripts to try replace the functionality of yours, which is no where near as good. ;)

    I know you weren't talking about it, but I really have been trying to get it purchased, but the money keeps getting moved to other purchases.


    Portland Public Schools / Systems Administrator II





    • Edited by Adam Seitz Wednesday, November 6, 2019 7:44 PM
    Wednesday, November 6, 2019 5:46 PM
  • It wasn't a plug for WAM, it was generally asking if you're doing the maintenance which it seems like you're doing some/most, although manually.

    Have you tried deleting all of the offending systems from the WSUS MMC Console and running the client side script on each affected system?

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Thursday, November 7, 2019 1:22 AM
  • I just connected to every Downstream server and saw the same errors for each device I spot cecked, the problem is larger than I realized.

    Hi Adam,
      

    Do you mean that there is no data in the Update status report for browsing the client on the downstream server? If so, consider starting with the following checks:
       

    1. Make sure that the agent services are up and running in downstream WSUS server.
      - WSUS Server
      - Background Intelligent Transfer Service (BITS)
          
    2. Did clients with no status information mentioned above apply the correct group policy and the network connection to the downstream WSUS server is normal?
      - The application of Group Policy can be checked by running the RSOP on the client using the elevated CMD.
      - Determine the connection between the client and the server by accessing "HTTP://WSUSserverFQDN:8530/selfupdate/iuident.cab".
         
    3. Does the client report any errors when detecting updates?
      Fix it by referring to "Fix Windows Update errors".
        

    If this is not the problem you are currently experiencing, please keep communicating.
    Reply back with the results would be happy to help.
        

    Regards,
    Yic

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

    Thursday, November 7, 2019 2:35 AM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation.
     

    Regards,
    Yic

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

    Monday, November 11, 2019 6:57 AM
  • It wasn't a plug for WAM, it was generally asking if you're doing the maintenance which it seems like you're doing some/most, although manually.

    Have you tried deleting all of the offending systems from the WSUS MMC Console and running the client side script on each affected system?

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    I will try that right now, that's a really good idea.

    Thanks Adam!:)


    Portland Public Schools / Systems Administrator II

    Tuesday, November 12, 2019 7:57 PM
  • I just connected to every Downstream server and saw the same errors for each device I spot cecked, the problem is larger than I realized.

    Hi Adam,
      

    Do you mean that there is no data in the Update status report for browsing the client on the downstream server? If so, consider starting with the following checks:
       

    1. Make sure that the agent services are up and running in downstream WSUS server.
      - WSUS Server
      - Background Intelligent Transfer Service (BITS)
          
    2. Did clients with no status information mentioned above apply the correct group policy and the network connection to the downstream WSUS server is normal?
      - The application of Group Policy can be checked by running the RSOP on the client using the elevated CMD.
      - Determine the connection between the client and the server by accessing "HTTP://WSUSserverFQDN:8530/selfupdate/iuident.cab".
         
    3. Does the client report any errors when detecting updates?
      Fix it by referring to "Fix Windows Update errors".
        

    If this is not the problem you are currently experiencing, please keep communicating.
    Reply back with the results would be happy to help.
        

    Regards,
    Yic

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

    Hello Yic,

    I appreciate the help, I just checked everything you suggested: and

    1. WSUS Service is running but the Bits Service is set to manual, should I make that Automatic? I used my Windows Client I am debugging with and got the iudent.cab file.

    2. All the clients have the WSUS Policy listed that I just spot checked. I am looking at a client at my 1st downstream site and that has the the correct WSUS Downstream Server and The Reporting Point set to the same Downstream Server. All the servers are rolling up reporting to the master WSUS Server.

    3. My windows 10 client has the following error (but is clean otherwise):

    2019/11/12 11:40:14.9343601 19196 16744 SLS             Get response for service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 - forceExpire[False] asyncRefreshOnExpiry[False]
    2019/11/12 11:40:16.7602646 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
    2019/11/12 11:40:16.7602685 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
    2019/11/12 11:40:16.7603233 19196 16744 EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 13C58A2B-3F6D-4186-9217-172B2D38FD6D.1, idExpr=57
    2019/11/12 11:40:16.7603274 19196 16744 Agent           *FAILED* [80070032] Evaluate Installed rule, updateId = {{13C58A2B-3F6D-4186-9217-172B2D38FD6D}.1}
    2019/11/12 11:40:16.7622324 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
    2019/11/12 11:40:16.7622360 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
    2019/11/12 11:40:16.7622885 19196 16744 EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 13C58A2B-3F6D-4186-9217-172B2D38FD6D.1, idExpr=56
    2019/11/12 11:40:16.7622932 19196 16744 Agent           *FAILED* [80070032] Evaluate Installable rule, updateId = {{13C58A2B-3F6D-4186-9217-172B2D38FD6D}.1}
    2019/11/12 11:40:16.7640984 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
    2019/11/12 11:40:16.7641016 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
    2019/11/12 11:40:16.7641477 19196 16744 EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 4172C992-9A52-424A-BD20-5CE510E85BCF.1, idExpr=57
    2019/11/12 11:40:16.7641512 19196 16744 Agent           *FAILED* [80070032] Evaluate Installed rule, updateId = {{4172C992-9A52-424A-BD20-5CE510E85BCF}.1}
    2019/11/12 11:40:16.7658815 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
    2019/11/12 11:40:16.7658848 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
    2019/11/12 11:40:16.7659307 19196 16744 EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 4172C992-9A52-424A-BD20-5CE510E85BCF.1, idExpr=56
    2019/11/12 11:40:16.7659343 19196 16744 Agent           *FAILED* [80070032] Evaluate Installable rule, updateId = {{4172C992-9A52-424A-BD20-5CE510E85BCF}.1}
    2019/11/12 11:40:17.0256059 19196 16744 Agent           Added update 6EBF2E46-DACC-41A6-BEEE-96C37E39CD93.1 to search result
    2019/11/12 11:40:17.0256107 19196 16744 Agent           Added update FBBE96EE-267F-488D-8528-BA7D0E7E21D4.1 to search result

    Thank you!! Any ideas on what I might try next?


    Portland Public Schools / Systems Administrator II



    • Edited by Adam Seitz Tuesday, November 12, 2019 9:05 PM
    Tuesday, November 12, 2019 8:18 PM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation.
     

    Regards,
    Yic

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

    I will absolutely do that. :)

    Portland Public Schools / Systems Administrator II

    Tuesday, November 12, 2019 9:08 PM
  • It wasn't a plug for WAM, it was generally asking if you're doing the maintenance which it seems like you're doing some/most, although manually.

    Have you tried deleting all of the offending systems from the WSUS MMC Console and running the client side script on each affected system?

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    I will try that right now, that's a really good idea.

    Thanks Adam!:)


    Portland Public Schools / Systems Administrator II

    I deleted a few systems and they still have the same issue after they reported back in.

    As for my maintenance scripts actually I don't run those manually at all, I have scheduled tasks that run them, WSUS-Cleanup - daily at 7 am, and WSUS-DB weekly on Sunday night at 11:00 PM.

    The only thing I run manually is the actual WSUS Cleanup Wizard in the console for each server, I just try to run that once a week or so. I saw you suggest that a few times in the past for people asking for help with things.

    Any other ideas?

    Thanks a lot, Adam!!!


    Portland Public Schools / Systems Administrator II



    • Edited by Adam Seitz Thursday, November 14, 2019 5:36 PM
    Tuesday, November 12, 2019 10:19 PM
  • 1. WSUS Service is running but the Bits Service is set to manual, should I make that Automatic? I used my Windows Client I am debugging with and got the iudent.cab file.

    Please keep the current "manual" status, this is ok.
         

    2. All the clients have the WSUS Policy listed that I just spot checked. I am looking at a client at my 1st downstream site and that has the the correct WSUS Downstream Server and The Reporting Point set to the same Downstream Server. All the servers are rolling up reporting to the master WSUS Server.

    At this point, will you view the status reports of these clients on the downstream server, will you record the relevant installed and not installed update information? As you initially want to see, check if these reports exist on the downstream server.
       

    3. My windows 10 client has the following error (but is clean otherwise):

    2019/11/12 11:40:14.9343601 19196 16744 SLS             Get response for service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 - forceExpire[False] asyncRefreshOnExpiry[False]
    2019/11/12 11:40:16.7602646 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]

    Sorry, this part of the log does not clearly express the reason for any Windows Update error. Error code 0x80070032 means that the request is not supported, but this may not be the most direct reason.
    From a simple point of view, on those clients connected to the downstream server, is there any error in Windows Update after checking for updates?
       

    Reply back with the results would be happy to help.
       

    Regards,
    Yic

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

    Friday, November 15, 2019 6:25 AM
  • 1. WSUS Service is running but the Bits Service is set to manual, should I make that Automatic? I used my Windows Client I am debugging with and got the iudent.cab file.

    Please keep the current "manual" status, this is ok.
         

    2. All the clients have the WSUS Policy listed that I just spot checked. I am looking at a client at my 1st downstream site and that has the the correct WSUS Downstream Server and The Reporting Point set to the same Downstream Server. All the servers are rolling up reporting to the master WSUS Server.

    At this point, will you view the status reports of these clients on the downstream server, will you record the relevant installed and not installed update information? As you initially want to see, check if these reports exist on the downstream server.
       

    3. My windows 10 client has the following error (but is clean otherwise):

    2019/11/12 11:40:14.9343601 19196 16744 SLS             Get response for service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 - forceExpire[False] asyncRefreshOnExpiry[False]
    2019/11/12 11:40:16.7602646 19196 16744 Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]

    Sorry, this part of the log does not clearly express the reason for any Windows Update error. Error code 0x80070032 means that the request is not supported, but this may not be the most direct reason.
    From a simple point of view, on those clients connected to the downstream server, is there any error in Windows Update after checking for updates?
       

    Reply back with the results would be happy to help.
       

    Regards,
    Yic

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

    Good morning Yic,

    I will leave the manual service setting alone on the BITS service.

    The status reports are also broken on the downstream servers, I just spot checked a few to make sure.

    Once I checked for updates and then re-generated the log, i see a lot of errors. I couldn't paste the whole log, but I got all of the errors and some info around them.

    2019/11/15 08:39:14.6755063 6408  15412 DataStore       Failed to find update with  global id of B5C6EFE4-96A0-47C3-AA45-3E27335F9911.200 (sessiondata = (null))

    2019/11/15 08:39:14.7651174 6408  6684  DataStore       Failed to find update with  global id of 82F0E17A-5A2F-487B-863C-C1CA804DA875.200 (sessiondata = (null))
    2019/11/15 08:39:14.7651234 6408  6684  DownloadManager No locked revisions found for update 82F0E17A-5A2F-487B-863C-C1CA804DA875.200 (SessionData = (null)); locking the user-specified revision.
    2019/11/15 08:39:14.7651333 6408  6684  DataStore       Failed to find update with  global id of 82F0E17A-5A2F-487B-863C-C1CA804DA875.200 (sessiondata = (null))
    2019/11/15 08:39:14.7654161 6408  6684  DataStore       Failed to find update with  global id of 6599CA12-AC4B-4A3C-B53B-FB2FD6478AA5.200 (sessiondata = (null))
    2019/11/15 08:39:14.7654220 6408  6684  DownloadManager No locked revisions found for update 6599CA12-AC4B-4A3C-B53B-FB2FD6478AA5.200 (SessionData = (null)); locking the user-specified revision.
    2019/11/15 08:39:14.7654301 6408  6684  DataStore       Failed to find update with  global id of 6599CA12-AC4B-4A3C-B53B-FB2FD6478AA5.200 (sessiondata = (null))
    2019/11/15 08:39:15.7496284 6408  15400 Agent           WU client calls back to download call {2E60CB24-57BD-4DB3-AF77-CD28CC318736} with code Call progress and error 0
    2019/11/15 08:39:16.0678020 6408  15400 Agent           WU client calls back to download call {2E60CB24-57BD-4DB3-AF77-CD28CC318736} with code Call progress and error 0
    2019/11/15 08:39:16.1195015 15268 12728 ComApi          Download call complete (succeeded = 1, succeeded with errors = 0, failed = 0, cancelled = 0, unaccounted = 0)
    2019/11/15 08:39:16.1195056 15268 12728 ComApi          * END *   Download ClientId = UpdateOrchestrator
    2019/11/15 08:39:16.1195457 6408  15400 Agent           WU client calls back to download call {2E60CB24-57BD-4DB3-AF77-CD28CC318736} with code Call complete and error 0
    2019/11/15 08:39:16.1197287 15268 15608 ComApi          Download call complete (succeeded = 1, succeeded with errors = 0, failed = 0, cancelled = 0, unaccounted = 0)
    2019/11/15 08:39:16.1197472 15268 15608 ComApi          * END *   All federated downloads have completed. ClientId = UpdateOrchestrator (cV = F6NIVSV+fEmeFEti.1.1)
    2019/11/15 08:39:16.1637456 6408  416   DataStore       Failed to find update with  global id of 49DFA08A-C2C7-4890-A6A8-6B2687CA14C8.200 (sessiondata = (null))
    2019/11/15 08:39:16.1637590 6408  416   DataStore       Failed to find update with  global id of A9CE9DE9-2902-4066-B106-0A671C2D35D2.200 (sessiondata = (null))
    2019/11/15 08:39:16.1637689 6408  416   DataStore       Failed to find update with  global id of 0FBBA5BA-CA11-41D3-8ED9-4D73A9D530E1.200 (sessiondata = (null))
    2019/11/15 08:39:16.1637799 6408  416   DataStore       Failed to find update with  global id of 9358C1BF-A005-4A69-B8FE-F33D2EBDC6EA.200 (sessiondata = (null))
    2019/11/15 08:39:16.1638282 6408  416   DownloadManager Getting IsImmediateInstallPreferred, updateId = F4E56F69-3B8B-4CDA-8DEF-5849BCB4BA3A.200, which is the child of update 82F0E17A-5A2F-487B-863C-C1CA804DA875.200
    2019/11/15 08:39:16.1640469 15268 4908  ComApi          *FAILED* [80004002] ISusInternal:: IsImmediateInstallPreferred
    2019/11/15 08:39:16.2418969 6408  15780 Agent           Pre-install check complete
    2019/11/15 08:39:16.2420206 6408  15780 DataStore       Failed to find update with  global id of 92B143DA-C18C-4486-861F-4D4682697259.200 (sessiondata = (null))
    2019/11/15 08:39:16.2420406 6408  15780 DataStore       Failed to find update with  global id of B9CE9BE8-019A-4C0B-8DA8-41C79943620B.200 (sessiondata = (null))
    2019/11/15 08:39:16.2420565 6408  15780 DataStore       Failed to find update with  global id of EF7BCF21-6E94-413F-9E14-6C71D96424E9.200 (sessiondata = (null))
    2019/11/15 08:39:16.2420695 6408  15780 DataStore       Failed to find update with  global id of BAD93690-19D6-419C-9DB7-1870754613BA.200 (sessiondata = (null))
    2019/11/15 08:39:16.2420835 6408  15780 DataStore       Failed to find update with  global id of EE4BA2BC-6957-4CD6-8CD8-B829B7203CB8.200 (sessiondata = (null))
    2019/11/15 08:39:16.2420961 6408  15780 DataStore       Failed to find update with  global id of D787F335-2270-48C9-A2C3-379EF8CF0C05.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421104 6408  15780 DataStore       Failed to find update with  global id of 1CE79097-43BE-4DB3-ABDD-BBCDF913DCD8.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421218 6408  15780 DataStore       Failed to find update with  global id of A7B7DD97-C686-4451-8CBA-A9DF2B2AE3EE.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421351 6408  15780 DataStore       Failed to find update with  global id of 942EC591-D56D-4D28-8CA7-8B2B1DDB17DA.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421470 6408  15780 DataStore       Failed to find update with  global id of CDFBCEC7-55AD-4421-97AD-8A1B6914D9D9.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421624 6408  15780 DataStore       Failed to find update with  global id of 15E66CF7-9BCD-4C3E-BABF-E80DED0D9C17.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421746 6408  15780 DataStore       Failed to find update with  global id of A93657ED-9DCA-42F9-8F64-E73CB4EF0FF8.200 (sessiondata = (null))
    2019/11/15 08:39:16.2421872 6408  15780 DataStore       Failed to find update with  global id of 9EC2C16B-93CB-4372-AF2C-B7BF00C1849A.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422011 6408  15780 DataStore       Failed to find update with  global id of 041567A9-5D63-4BD6-8F31-D9EDF311456C.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422128 6408  15780 DataStore       Failed to find update with  global id of 14F1B1F4-C5EC-4A5D-9423-F2349FE70CE0.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422251 6408  15780 DataStore       Failed to find update with  global id of 7CA1E679-69E0-461F-93E1-E17D6D732EBF.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422386 6408  15780 DataStore       Failed to find update with  global id of 930744FD-A6E1-4897-A8E2-A594EB668C6D.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422504 6408  15780 DataStore       Failed to find update with  global id of C8AFEF2D-9C2E-4128-89A2-F5073A9726E0.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422621 6408  15780 DataStore       Failed to find update with  global id of 946B4FBF-D7A5-41D4-A40B-97A199F72320.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422755 6408  15780 DataStore       Failed to find update with  global id of D5D61ED4-CD2D-46AF-B4A2-B989F6E159BD.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422871 6408  15780 DataStore       Failed to find update with  global id of 4C136519-6F3B-4F72-A45B-104E56E40F3D.200 (sessiondata = (null))
    2019/11/15 08:39:16.2422996 6408  15780 DataStore       Failed to find update with  global id of F4668C0C-503D-4166-A073-6E32BCDA8F00.200 (sessiondata = (null))
    2019/11/15 08:39:16.2423130 6408  15780 DataStore       Failed to find update with  global id of 59C76FEF-EA32-4274-9D61-1AEAB6C7718A.200 (sessiondata = (null))
    2019/11/15 08:39:16.2423249 6408  15780 DataStore       Failed to find update with  global id of A4EE705A-2C4D-46CC-B1B4-63E1B1956FAB.200 (sessiondata = (null))
    2019/11/15 08:39:16.2423368 6408  15780 DataStore       Failed to find update with  global id of 0D7A3576-B6C1-4A45-B9D4-CB57D1F079C9.200 (sessiondata = (null))
    2019/11/15 08:39:16.2429783 6408  15780 DataStore       Failed to find update with  global id of 497D69EC-1359-494B-A86F-BDB1EC956171.200 (sessiondata = (null))
    2019/11/15 08:39:16.2430028 6408  15780 DataStore       Failed to find update with  global id of D53566BC-E39C-47F3-9C02-5B8A3E3805CB.200 (sessiondata = (null))
    2019/11/15 08:39:16.2430252 6408  15780 DataStore       Failed to find update with  global id of 413A164F-736E-4728-976B-C93600C580AF.200 (sessiondata = (null))
    2019/11/15 08:39:16.2430378 6408  15780 DataStore       Failed to find update with  global id of B5C6EFE4-96A0-47C3-AA45-3E27335F9911.200 (sessiondata = (null))
    2019/11/15 08:39:16.2430614 6408  15780 Agent           WU client starts install in local system context

    <This is the end of the log>

    Is this something I should chase, or is normal to see these?

    Thanks Yic for working with me on this!! I am really stuck on this.



    Portland Public Schools / Systems Administrator II


    • Edited by Adam Seitz Friday, November 15, 2019 4:58 PM
    Friday, November 15, 2019 4:52 PM
  • Hi Adam,
      

    Thank you for your continuous update.
    But I am sorry that I have no better way to share it with you now. If possible, consider removing the existing WSUS role and database on the downstream server and then re-adding the role. For reference, the process is as follows: "How to completely remove old wsus settings - trying for a clean install".
      

    Hope the above can help you.
       

    Regards,
    Yic


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

    Monday, November 18, 2019 7:09 AM
  • WAM Would probably fix this issue, however

    https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, November 18, 2019 3:14 PM
  • Hi Adam,
      

    Thank you for your continuous update.
    But I am sorry that I have no better way to share it with you now. If possible, consider removing the existing WSUS role and database on the downstream server and then re-adding the role. For reference, the process is as follows: "How to completely remove old wsus settings - trying for a clean install".
      

    Hope the above can help you.
       

    Regards,
    Yic


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

    Hello Yic,

    I think I am going to create a premiere case for this and see if they can assist. Thanks for your help,  really appreciate it.

    Thanks again!!


    Portland Public Schools / Systems Administrator II

    Monday, November 18, 2019 5:51 PM
  • WAM Would probably fix this issue, however

    https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Adam,

    If it domes to uninstalling I will use the guide, I am goign to open a premiere case and see if they have any other ideas first.

    Thanks again!


    Portland Public Schools / Systems Administrator II

    Monday, November 18, 2019 5:53 PM
  • Hi Adam,
       

    Thank you for your feedback, and unfortunately did not help you solve it.
    In order to facilitate future follow-up, the current summary of this thread is as follows:
       

    • Issue Symptom
      The upstream server was unable to get an update status report for the client that is pointing to the downstream server.
        
    • Possible Cause
      The downstream server did not properly obtain or process the client report.
         
    • Troubleshooting Steps so far
      1. The WSUS upstream server reports the configuration.
      2. Connection problems between upstream-downstream-clients have been excluded.
      3. The client system service is running normally.
      4. WSUS server cleanup.
         
    • Next Step
      The case is escalated.
        
    Regards,
    Yic

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

    Thursday, November 21, 2019 6:00 AM