Asked by:
W2016 WSUS Server no updates error 0x80244019
Question
-
Hi All,
I'm running W2016 standard running WSUS v10.0.14393.3085 with on proxy on a dell poweredge r510, which is on an enterprise domain (my managed WSUS GPOs for clients and server in my OU).
Within WSUS, all clients within the computer and server groups (two separate GPOs w/ intranet, statistics, and alternative address as http://myservername.server.enterprise.com:8530) have been reporting and getting updates for some time (Synched from Microsoft Update), EXCEPT for the W2016 WSUS server itself (reports and tries to download only). When approved updates are pushed to all clients from this WSUS server, this server as a client, always results a download error 0x80244019 for its scheduled updates.
I have tried the wupdate troubleshooter, stop services to delete the Software Distribution folder, run sfc and dism tools successfully, extending the IIS limits as often recommended, ran a script to update the synch point,.and other troubleshooting steps.
Generally, the wupdate logs on this W2016 WSUS server show "Failed to connect to the DO service", GetDOManager() failed, DO download failed with error 80246008[Extended: 80040154], falling back to BITS, DownloadManager Downloading from http://myservername.server.enterprise.com:8530/c/msdownload/update/software/secu/2019/09/windows10.0-kb4512574-x64-express_b177e2c2174b489ceff667d52df7f4c8ce03a9f3.cab to C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae\Windows10.0-KB4512574-x64-express.cab (full file). DownloadManager Error 0x80244019 occurred while downloading update; notifying dependent calls., DownloadManager The update's sandbox is in use.
In regard to the Wsus server as client logs, I don't understand the "Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found)". Also, what and from where is the Wsus server trying to download and install that is different from the others?
Thanks
Differences in Wsus, PC and Server WU logs are:
Wsus Server as client:
2019/09/12 10:56:26.6109407 1036 7912 Agent Initializing Windows Update Agent
2019/09/12 10:56:26.6110934 1036 7912 DownloadManager Download manager restoring 0 downloads
2019/09/12 10:56:26.6112237 1036 7912 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2019/09/12 10:56:26.6338555 1036 7656 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019/09/12 10:56:26.6338680 1036 7656 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019/09/12 10:56:26.6340696 1036 7656 Shared Power status changed
2019/09/12 10:56:26.6401693 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:26.6401712 1036 11224 DownloadManager Power state change detected. Source now: AC
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 11): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 12): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 13): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 14): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:48.6583863 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 11.
2019/09/12 10:56:48.6653620 1036 11224 DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = F4A4BC25-72E3-4138-91AA-0BBE8787A39F]
2019/09/12 10:56:48.6653695 1036 11224 DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2019/09/12 10:56:48.6653704 1036 11224 DownloadManager Updates to download = 1
2019/09/12 10:56:48.6653718 1036 11224 Agent Title = 2019-09 Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB4512574)
2019/09/12 10:56:48.6653779 1036 11224 Agent UpdateId = DF51B003-58D6-42D6-AD9E-D81ADAA1437E.200
2019/09/12 10:56:48.6653788 1036 11224 Agent Bundles 1 updates:
2019/09/12 10:56:48.6653844 1036 11224 Agent 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:48.6654551 1036 11224 DownloadManager No locked revisions found for update DF51B003-58D6-42D6-AD9E-D81ADAA1437E; locking the user-specified revision.
2019/09/12 10:56:48.6917724 1036 11224 DownloadManager No locked revisions found for update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1; locking the user-specified revision.
2019/09/12 10:56:48.7121951 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category PerUpdate.
2019/09/12 10:56:48.7121970 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Low.
2019/09/12 10:56:48.7121984 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Normal.
2019/09/12 10:56:48.7121988 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category High.
2019/09/12 10:56:48.7593079 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:48.9161840 1036 11224 DownloadManager Queueing update {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200 for download handler request generation.
2019/09/12 10:56:48.9250379 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 11): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 12): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 13): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:49.0097850 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:49.0097915 1036 11224 Agent Released network PDC reference for callId {F4A4BC25-72E3-4138-91AA-0BBE8787A39F}; ActivationID: 11
2019/09/12 10:56:49.0097989 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 16.
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 14): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:49.0169418 1036 10580 Agent WU client calls back to download call {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with code Call progress and error 0
2019/09/12 10:56:49.0225203 1036 11224 DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
2019/09/12 10:56:49.0225268 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:49.0225347 1036 11224 Agent Obtained a network PDC reference for callID {6B4A26A7-EC8A-4366-804A-5005A33AC493} with No-Progress-Timeout set to 4294967295; ActivationID: 17.
2019/09/12 10:56:49.0259758 1036 11224 DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = 6B4A26A7-EC8A-4366-804A-5005A33AC493]
2019/09/12 10:56:49.0259828 1036 11224 DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2019/09/12 10:56:49.0259842 1036 11224 DownloadManager Updates to download = 1
2019/09/12 10:56:49.0259851 1036 11224 Agent Title = 2019-09 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4516044)
2019/09/12 10:56:49.0259916 1036 11224 Agent UpdateId = 5BD21FF7-DD92-4CB4-A08A-E15994C99CAD.200
2019/09/12 10:56:49.0259921 1036 11224 Agent Bundles 1 updates:
2019/09/12 10:56:49.0259977 1036 11224 Agent B8FB5A48-445F-43FE-87E6-30AF9B0482D8.200
2019/09/12 10:56:49.0260582 1036 11224 DownloadManager No locked revisions found for update 5BD21FF7-DD92-4CB4-A08A-E15994C99CAD; locking the user-specified revision.
2019/09/12 10:56:49.0305503 1036 11104 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.0334440 1036 11224 DownloadManager No locked revisions found for update B8FB5A48-445F-43FE-87E6-30AF9B0482D8; locking the user-specified revision.
2019/09/12 10:56:49.0583900 1036 11104 DownloadManager Generating download request for update {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200
2019/09/12 10:56:49.0596416 1036 11104 DownloadManager Calling into handler 0x8 to generate download request for update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:49.0596840 1036 11104 Handler Generating request for CBS update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1 in sandbox C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae
2019/09/12 10:56:49.0714944 1036 11104 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.0715079 1036 11104 Handler Selected payload type is Express
2019/09/12 10:56:49.0715610 1036 11104 Handler Detected download state is dsStart
2019/09/12 10:56:49.0715805 1036 11104 Handler Adding Windows10.0-KB4512574-x64-express.cab (entire file) to request list.
2019/09/12 10:56:49.2843768 1036 11104 Handler Saved state: cCompleteIterations: 0, pt: Express, nNextRequestID: 1.
2019/09/12 10:56:49.2843838 1036 11104 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019/09/12 10:56:49.6963948 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.7157637 1036 11224 DownloadManager Failed to connect to the DO service; (hr = 80040154)
2019/09/12 10:56:49.7157651 1036 11224 DownloadManager GetDOManager() failed, hr=80246008, hrExtended=80040154
2019/09/12 10:56:49.7157670 1036 11224 DownloadManager Failed creating DO job with hr 80246008
2019/09/12 10:56:49.7236690 1036 11224 DownloadManager DO download failed with error 80246008[Extended: 80040154], falling back to BITS and retrying with new Download Job.
2019/09/12 10:56:49.7339323 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.0735368 1036 11224 DownloadManager BITS job initialized: JobId = {39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD}
2019/09/12 10:56:50.1283929 1036 11224 DownloadManager Downloading from http://myservername.server.enterprise.com:8530/c/msdownload/update/software/secu/2019/09/windows10.0-kb4512574-x64-express_b177e2c2174b489ceff667d52df7f4c8ce03a9f3.cab to C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae\Windows10.0-KB4512574-x64-express.cab (full file).
2019/09/12 10:56:50.1369493 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Express, nNextRequestID: 1.
2019/09/12 10:56:50.1501319 1036 11224 DownloadManager New download job {39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD} for UpdateId 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:50.1900991 1036 11224 DownloadManager Download job 39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD resumed.
2019/09/12 10:56:50.1979517 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.2421252 1036 11224 DownloadManager UpdateId = {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200, Job ID = 39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD, xszResponseHeaders = HTTP/1.1 404 Not Found Date: Thu, 12 Sep 2019 14:56:50 GMT Content-Length: 0 Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET .
2019/09/12 10:56:50.2528209 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:50.2528292 1036 11224 Agent Released network PDC reference for callId {F4A4BC25-72E3-4138-91AA-0BBE8787A39F}; ActivationID: 16
2019/09/12 10:56:50.2528418 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 18.
2019/09/12 10:56:50.2532267 1036 10580 Agent WU client calls back to download call {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with code Call progress and error 0
2019/09/12 10:56:50.2939647 1036 11224 DownloadManager Queueing update {B8FB5A48-445F-43FE-87E6-30AF9B0482D8}.200 for download handler request generation.
2019/09/12 10:56:50.8185462 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.9221381 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:50.9221451 1036 11224 Agent Released network PDC reference for callId {6B4A26A7-EC8A-4366-804A-5005A33AC493}; ActivationID: 17
2019/09/12 10:56:50.9221539 1036 11224 Agent Obtained a network PDC reference for callID {6B4A26A7-EC8A-4366-804A-5005A33AC493} with No-Progress-Timeout set to 4294967295; ActivationID: 19.
2019/09/12 10:56:50.9225836 1036 10580 Agent WU client calls back to download call {6B4A26A7-EC8A-4366-804A-5005A33AC493} with code Call progress and error 0
2019/09/12 10:56:50.9761559 1036 11224 DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
PC Clients:
019/09/13 09:38:12.5750696 4168 2724 Agent Initializing Windows Update Agent
2019/09/13 09:38:12.5753639 4168 2724 DownloadManager Retrieved 1 persisted download jobs
2019/09/13 09:38:12.5753666 4168 2724 DownloadManager Restoring download no. 0
2019/09/13 09:38:12.5754460 4168 2724 DownloadManager JobId = {0E018B54-02A6-496A-A6BA-12CEF4FF7DA5}, ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}
2019/09/13 09:38:12.5762955 4168 2724 DownloadManager UpdateId = B4584583-B243-4D7B-8BBA-BD07BF83BEA1.200
2019/09/13 09:38:12.5763717 4168 2724 Reporter OS Product Type = 0x00000079
2019/09/13 09:38:12.6064019 4168 2724 DownloadManager Restored download job.
2019/09/13 09:38:12.6073285 4168 2724 DownloadManager Job 0E018B54-02A6-496A-A6BA-12CEF4FF7DA5 is not expired (calculated)
2019/09/13 09:38:12.6077997 4168 2724 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2019/09/13 09:38:12.7647717 4168 5600 DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2019/09/13 09:38:12.7709409 4168 5600 DownloadManager PurgeExpiredUpdates::Found 463 non expired updates.
2019/09/13 09:38:13.6763133 4168 5600 DownloadManager PurgeExpiredUpdates::Found 8 expired updates.
2019/09/13 09:38:13.6771823 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\a4bd801f0e536884769eb693a915067d.
2019/09/13 09:38:13.6951493 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\48753d529f3eb2734adb21e35d7eb758.
2019/09/13 09:38:13.9987529 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\86b10c9d5dc07d0f644277e691551232.
2019/09/13 09:38:14.0156075 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\3b8eab9088db939137cfd5ed911a5049.
2019/09/13 09:38:14.0178087 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\e73235a3433b5263a73b3eff91dc918c.
2019/09/13 09:38:14.0343858 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\f10978b1cc63e70018ca89391b3068a0.
2019/09/13 09:38:14.0370973 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\70cf8f64a467b1a627b7aac3acf986d0.
2019/09/13 09:38:14.0396303 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\e3d5b790a8a94cf311f3b292f4992a89.
2019/09/13 09:39:47.3755734 4168 2724 Agent Adding timer:
2019/09/13 09:39:47.3758810 4168 2724 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:40:01.6109071 4168 5600 DownloadManager Received power state change notification: Old: <unknown>; New: AC.
2019/09/13 09:40:01.6110610 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category PerUpdate.
2019/09/13 09:40:01.6110663 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category Low.
2019/09/13 09:40:01.6110740 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category Normal.
2019/09/13 09:40:01.6111597 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category High.
2019/09/13 09:40:01.7019756 4168 5600 DownloadManager Power state changed from <unknown> to AC.
2019/09/13 09:48:12.3570675 4168 8736 Agent Earliest future timer found:
2019/09/13 09:48:12.3570887 4168 8736 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:48:13.3584408 4168 2724 Misc CSusClientGlobal::DoServicePreShutdown
2019/09/13 09:48:13.3585729 4168 2724 IdleTimer Idle timer disabled in preparation for service shutdown
2019/09/13 09:48:13.3585874 4168 2724 Misc WUTaskManager uninit
2019/09/13 09:48:13.3585914 4168 2724 Agent Earliest future timer found:
2019/09/13 09:48:13.3586109 4168 2724 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:48:13.3655323 4168 2724 Misc CreateSessionStateChangeTrigger, TYPE:2, Enable:No
2019/09/13 09:48:13.3655711 4168 2724 Misc CreateSessionStateChangeTrigger, TYPE:4, Enable:No
2019/09/13 09:48:13.5914282 4168 2724 Misc Agent uninit
2019/09/13 09:48:13.5971769 4168 2724 Misc Reporter uninit
2019/09/13 09:48:13.5974957 4168 2724 Misc network cost manager uninit
2019/09/13 09:48:13.5975248 4168 2724 Misc Eventer uninit
2019/09/13 09:48:14.5984565 4168 2724 Misc ServiceManager uninit
2019/09/13 09:48:14.5985664 4168 2724 Misc PersistentTimeoutScheduler uninit
2019/09/13 09:48:14.5985681 4168 2724 Misc datastore uninit
2019/09/13 09:48:14.6468813 4168 2724 Misc setting cache uninit
2019/09/13 09:48:14.6468843 4168 2724 Misc security checker uninit
2019/09/13 09:48:14.6468883 4168 2724 Misc Test Hook uninit
2019/09/13 09:48:14.6468890 4168 2724 Misc IdleTimer uninit
2019/09/13 09:48:14.6472488 4168 2724 Shared * END * Service exit Exit code = 0x240001
Other Server as Client:
2019-09-13 11:08:23:007 936 1348 AU #############
2019-09-13 11:08:23:007 936 1348 AU ## START ## AU: Search for updates
2019-09-13 11:08:23:007 936 1348 AU #########
2019-09-13 11:08:23:021 936 1348 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:08:23:021 936 1978 Agent *************
2019-09-13 11:08:23:021 936 1978 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2019-09-13 11:08:23:021 936 1978 Agent *********
2019-09-13 11:08:23:021 936 1978 Agent * Online = Yes; Ignore download priority = No
2019-09-13 11:08:23:021 936 1978 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2019-09-13 11:08:23:021 936 1978 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019-09-13 11:08:23:021 936 1978 Agent * Search Scope = {Machine}
2019-09-13 11:08:23:021 936 1978 Setup Checking for agent SelfUpdate
2019-09-13 11:08:23:053 936 1978 Setup Client version: Core: 7.6.7601.24436 Aux: 7.6.7601.24436
2019-09-13 11:08:23:099 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:233 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:237 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPC502.tmp with dwProvFlags 0x00000080:
2019-09-13 11:08:23:292 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:330 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:340 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:344 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:353 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:379 936 1978 Setup Determining whether a new setup handler needs to be downloaded
2019-09-13 11:08:23:380 936 1978 Setup SelfUpdate handler is not found. It will be downloaded
2019-09-13 11:08:23:380 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:419 936 1978 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:420 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:548 936 1978 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:549 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:723 936 1978 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:724 936 1978 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2019-09-13 11:08:24:440 936 1978 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2019-09-13 11:08:24:440 936 1978 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://myservername.server.enterprise.com:8530/ClientWebService/client.asmx
2019-09-13 11:08:24:461 936 1978 PT WARNING: Cached cookie has expired or new PID is available
2019-09-13 11:08:24:466 936 1978 PT Initializing simple targeting cookie, clientId = b3f1d818-dacc-4bd0-9230-5118f418f423, target group = Servers, DNS name = imm-srv-01.univ.pitt.edu
2019-09-13 11:08:24:466 936 1978 PT Server URL =http://myservername.server.enterprise.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2019-09-13 11:09:57:227 936 1978 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2019-09-13 11:09:57:227 936 1978 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://myservername.server.enterprise.com:8530/ClientWebService/client.asmx
2019-09-13 11:09:57:601 936 1978 Agent * Added update {BFAF434D-585E-4666-8ECC-9D4526D0B60E}.200 to search result
2019-09-13 11:09:57:601 936 1978 Agent * Added update {2641EC1C-3A24-4D10-8392-F99E50A0BDF7}.200 to search result
2019-09-13 11:09:57:601 936 1978 Agent * Found 2 updates and 82 categories in search; evaluated appl. rules of 1295 out of 2754 deployed entities
2019-09-13 11:09:57:632 936 1978 Agent *********
2019-09-13 11:09:57:632 936 1978 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2019-09-13 11:09:57:632 936 1978 Agent *************
2019-09-13 11:09:57:635 936 1f04 AU >>## RESUMED ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:09:57:635 936 1f04 AU # 2 updates detected
2019-09-13 11:09:57:635 936 1f04 AU #########
2019-09-13 11:09:57:636 936 1f04 AU ## END ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:09:57:636 936 1f04 AU #############
2019-09-13 11:09:57:636 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:09:57:636 936 1f04 AU Featured notifications is disabled.
2019-09-13 11:09:57:637 936 1f04 AU AU setting next detection timeout to 2019-09-14 11:10:32
2019-09-13 11:09:57:637 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:09:57:639 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {44DB017A-8D90-4799-9D9A-AE7F54FFF4FB} 2019-09-13 11:09:57:623-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 2 updates.
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {21786D9B-15D2-455F-A47E-F6D49BEC30BE} 2019-09-13 11:09:57:631-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2019-09-13 11:16:27:663 936 1978 Report Uploading 2 events using cached cookie, reporting URL = http://myservername.server.enterprise.com:8530/ReportingWebService/ReportingWebService.asmx
2019-09-13 11:16:27:674 936 1978 Report Reporter successfully uploaded 2 events.
Friday, September 13, 2019 4:14 PM
All replies
-
Hi, Use IP of WSUS servers instead of long name..
Follow up this for some missing troubleshoot steps,
https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0
Friday, September 13, 2019 4:52 PM -
Hi, Use IP of WSUS servers instead of long name..
Follow up this for some missing troubleshoot steps,
https://gallery.technet.microsoft.com/Troubleshooting-WSUS-d63da113?redir=0
That is a horrible way to go. Best practices are to use FQDN, not IP.
Anyways, verify the server's IPv6 is ENABLED. IPv6 is used to communicate with other services on itself (like WSUS).
Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for ITFriday, September 13, 2019 6:30 PM -
Hi ksdst1,
Notice that your WSUS server uses a proxy, and the WSUS server also reported some bugs about BITS. Please consider the method mentioned in this article to check the configuration of the network proxy: "Downloading updates 0%" Issue on Windows Server 2016 And Windows 10.
* Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
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.- Edited by Yic LvMicrosoft contingent staff Monday, September 16, 2019 3:24 AM Add notes.
Monday, September 16, 2019 2:47 AM -
Hi All,
tnx for the replies. I tried the IP instead of the FQDN just for the heck of it, followed the troubleshooting wsus .pdf sheet, and double checked that IPv6 is enabled. When I ran the WSUS client diag test, all passed but got msg "GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002 The system cannot find the file specified." I'm researching that now.
Yic, can you please tell me what you saw to make you think the server uses a proxy (wsus is not set to use a proxy). Also, what in the log for the wsus server did you see about BITS bugs? I'll look into the web link about that.
tnx..
Monday, September 16, 2019 3:29 PM -
To add a point, I notices that for my Server GPO, the "enable client-side targeting" option is enabled. This was also the case when we were using the old WSUS that I migrated from, to this newer W2016 server.
I've noticed in the W2016 (WSUS) client update log that, when AU agent starts "search for updates" online using SelfUpdate, and it goes through the "SelfUpdate check completed. SelfUpdate is NOT required" phase, then the "Synchronizing server updates" phonse, it assigns a particular SeriveID and Server Url (the http fqdn server url to the ClientWebService/client.asmx link, there is a WARNING that the cached cookie has expired. It initiallizes a simple targeting cookie with a clientID, target group = Servers (the name of the computer group w/in WSUS and referenced in client-side targeting) and the DNS name = my-oldwsus-servername.server.enterprise.com
It recognizes the correct Server URL =http://myservername.server.enterprise.com:8530/SimpleAuthWebService/SimpleAuth.asmx properly, adds two updates to search results, and finishes with:
2019-09-13 11:09:57:637 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:09:57:639 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {44DB017A-8D90-4799-9D9A-AE7F54FFF4FB} 2019-09-13 11:09:57:623-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 2 updates.
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {21786D9B-15D2-455F-A47E-F6D49BEC30BE} 2019-09-13 11:09:57:631-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2019-09-13 11:16:27:663 936 1978 Report Uploading 2 events using cached cookie, reporting URL = http://myservername.server.enterprise.com:8530/ReportingWebService/ReportingWebService.asmx
2019-09-13 11:16:27:674 936 1978 Report Reporter successfully uploaded 2 events.I am wondering where the old WSUS server name for the cookie is being pulled from and if this some how indicates an issue that the old WSUS is still being referenced some how and causing the problem.
Tnx..
Monday, September 16, 2019 6:23 PM -
Hi,
Consider executing the following command on the affected client with the elevated CMD:
netsh winhttp show proxy
Please check if the result of the run is the correct proxy server information.
If the result of the run is "Direct access (no proxy server)", consider adding proxy server information by running the following command:
netsh winhttp set proxy servername:8080
Regards,
Then check again if the update is available for download.
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, September 18, 2019 5: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, as always.
Regards,
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, September 25, 2019 7:57 AM -
Hey All,
Sorry for the delay, but I get caught up with other work related issues.
Yic. Is setting a proxy necessary now with W2016 WSUS?
I set it as instructed and again DownloadManager starts to try to download updates, fails to connect to DO Service, finds proxy my.server.com:8080 for BITS job, and hits a transient error "can't connect to server" (see excerpt from log below). Does this indicate something important?
Also, comparing the three logs in my first post, I don't understand why the Windows Update Agent of the W2016 WSUS as a client, has a different download process then the other client and client-server log examples. Can anyone explain what it is trying to do differently? Is it trying to download locally, because it is not set to store updates locally but instead supposed to "synchronize from Microsoft Update" which i though was their web resource.
Thanks
2019/09/24 11:50:37.9003474 1028 7696 DownloadManager Attempt no. 1 to resume the job
2019/09/24 12:33:39.8563434 1028 7460 DownloadManager Found proxy my.server.com.immun.pitt.edu:8080 for BITS job 6A5376C7-0F27-4769-A0AC-766278C58411. Bypass-list: NULL
2019/09/24 11:50:39.8270086 1028 2168 Misc Got WSUS Client/Server URL: http://my.server.com:8530/ClientWebService/client.asmx""
2019/09/24 11:50:39.8277170 1028 2168 ProtocolTalker OK to reuse existing configuration
2019/09/24 11:50:39.8277254 1028 2168 ProtocolTalker Existing cookie is valid, just use it
2019/09/24 11:50:39.8277277 1028 2168 ProtocolTalker PTInfo: Server requested registration
2019/09/24 11:50:39.8577663 1028 2168 Misc Got WSUS Reporting URL: http://my.server.com:8530/ReportingWebService/ReportingWebService.asmx""
2019/09/24 11:50:39.8584179 1028 2168 WebServices Auto proxy settings for this web service call.
2019/09/24 11:50:39.9741651 1028 7724 DownloadManager BITS job {33406CDD-EBA6-4A45-BAB6-F2A2AE820318} hit a transient error, updateId = {A54AC40F-4382-424E-9ACE-ED22207B0923}.200 <NULL>, error = 0x80072EFD
2019/09/24 12:33:40.7921936 1028 7368 DownloadManager BITS job {33406CDD-EBA6-4A45-BAB6-F2A2AE820318} hit a transient error, updateId = {A54AC40F-4382-424E-9ACE-ED22207B0923}.200 <NULL>, error = 0x80072EFDWednesday, September 25, 2019 7:22 PM -
Hi,
Is there any other firewall enabled on the server as WSUS?
Regards,
Make sure that the Microsoft Update related sites mentioned in this article are accessible.
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Thursday, September 26, 2019 6:02 AM -
So you just added a pretty important piece of information. WSUS currently is set to not store updates. I have seen this before!
Enable the WSUS server to store updates (for testing). Let the updates download. See if this changes it.
I've seen this before where a problem existed because the WSUS server did not have the updates locally. I can't remember the exact scenario, but the solution was to enable the downloads.
Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for ITThursday, September 26, 2019 2:51 PM -
Hey Yic,
The Window FW is inactivated through GP and I deactivated the Symantec Endpoint Protection for testing. Also, all machines are behind our Enterprise firewall but there is no limit to internet URL traffic and the other clients (workstations and servers) have to trouble downloading the updates from Microsoft Update.
Adam, I don't really want to download all updates locally to the Server for testing sake. Even if that works, I don't see how that would help when reverting back to using Microsoft Update, especially when all other machines are having no issues.
I was hoping someone could help explain the Download Management process listed in the WSUS log above, and what and where it is actually trying to download from. I don't understand the "Unknown( 10): GUID" download entries and the "DownloadManager No locked revisions found for update" entries. These don't exist in the client and other server logs.
Thanks
Friday, September 27, 2019 8:46 PM -
Hi All,
After the issues with my W2016 WSUS setup, I decided to uninstall WSUS role and the DB, (full uninstall), etc., then do a W2016 in place upgrade just to make sure the system was good. After, I decided to delete the IIS role as well. Then reinstalled\configured the WSUS role (installs IIS), and later updated .NET to v4.7. My two wsus client-side GPOs for the “servers” and “computers” groups I created, have once again been populated with the PCs, but alas still problems.
After a few days, about half the computers (a mix, W10, 8.1 and 7) have “not yet reported”. The other half have reported and are showing updates Installed as 99 to 100%, but half of those have “updates with error”. In the case of my own W10 PC as an e.g., the log shows:
5852 WebServices WS error: Server was unable to process request. ---> The type initializer for 'Microsoft.UpdateServices.Internal.Reporting.WebService' threw an exception. ---> A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) ---> No process is on the other end of the pipe
So, the PC and server are communicating, where the PC is stuck at downloading 0%. Interestingly, on the WSUS box, I see a sporadic event viewer error “The Reporting Web Service is not working”, so went through the WSUS W2016 box IIS settings and compared them to the MS Doc IIS MS write up’s settings list. The one different setting is for ReportingWebService “AppIsolated : (INTEGER) 0”, so 0 instead of 2. The MS Doc does not explain what to do if these settings don’t match.
I have not been able to find info that focuses on mainly “The Reporting Web Service is not working” problem. Usually folks have all the web services not working.
Another e.g. is that I logged into a “not yet reported W8.1 PC and ran windows update. It checked with the server, sound new updates and I installed them. However, even now it still shows as “not yet reported”.
Help with “the reporting web service is not working” issue and any other helpful hints are appreciated.
Tnx..
Monday, October 21, 2019 8:24 PM
