Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM 2303 WSUS SYNCHRONISATION FAILED CODE 0X800C0008

PASCAL JOURDAN

Well-Known Member
Messages
120
Solutions
3
Reaction score
2
Points
18
Hi ,
Hello I have a recent problem of WSUS in connection with SCCM or synchronization is failed. Can you give me a line of research.
-----------------------------------------------------------
Process O365 update manifest with no proxy. $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:26:45.717-240><thread=7720 (0x1E28)>
Failed to download file- "http://officecdn.microsoft.com/pr/6...6a4f5be/office/data/16.0.16501.20180/s640.cab" from internet. Using proxyserver - 0. Error = 403 $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.619-240><thread=7720 (0x1E28)>
Failed to download or process the O365 file manifest. Caught exception: System.IO.FileNotFoundException: Failed to download file manifest for O365 from http://officecdn.microsoft.com/pr/6...6a4f5be/office/data/16.0.16501.20180/s640.cab, with error 403~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.DownloadAndExtractCabFile(String cabFileUrl, String fileNameInCab) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.627-240><thread=7720 (0x1E28)>
GetOfficeFileHash_O365Service() failed to get file hash for O365 file. Caught exception: System.IO.FileNotFoundException: Failed to download file manifest for O365 from http://officecdn.microsoft.com/pr/6...6a4f5be/office/data/16.0.16501.20180/s640.cab, with error 403~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.DownloadAndExtractCabFile(String cabFileUrl, String fileNameInCab)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.GetOfficeFileHash_O365Service(O365FileList o365FileList, String fileContainingHash, String updateId) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.641-240><thread=7720 (0x1E28)>
ProcessOfficeFile() failed to get file properties from file manifest. Caught exception: System.IO.FileNotFoundException: Failed to download file manifest for O365 from http://officecdn.microsoft.com/pr/6...6a4f5be/office/data/16.0.16501.20180/s640.cab, with error 403~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.DownloadAndExtractCabFile(String cabFileUrl, String fileNameInCab)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.GetOfficeFileHash_O365Service(O365FileList o365FileList, String fileContainingHash, String updateId)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.ProcessOfficeFile_O365Service(O365FileList o365FileList, Int32 iFile, XmlWriter xml, String updateId) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.648-240><thread=7720 (0x1E28)>
ProcessFileManifest() failed to process O365 file manifest. Caught exception: System.IO.FileNotFoundException: Failed to download file manifest for O365 from http://officecdn.microsoft.com/pr/6...6a4f5be/office/data/16.0.16501.20180/s640.cab, with error 403~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.DownloadAndExtractCabFile(String cabFileUrl, String fileNameInCab)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.GetOfficeFileHash_O365Service(O365FileList o365FileList, String fileContainingHash, String updateId)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.ProcessOfficeFile_O365Service(O365FileList o365FileList, Int32 iFile, XmlWriter xml, String updateId)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.ProcessFileManifest_O365Service(String sO365ServiceUrl, XmlWriter xml, String updateId) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.659-240><thread=7720 (0x1E28)>
Failed to synchronize O365 update 77b6e380-a318-42b0-b225-f1d07b03d84b - Microsoft 365 Apps Update - Current Channel (Preview) Quality Update for x64 based Edition Version 2305 (Build 16501.20180) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.667-240><thread=7720 (0x1E28)>
STATMSG: ID=6709 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=LEASVRMGMT10.LEALGROUP.LOCAL SITE=LEA PID=4128 TID=7720 GMTDATE=Tue May 30 09:27:07.673 2023 ISTR0="Microsoft 365 Apps Update - Current Channel (Preview) Quality Update for x64 based Edition Version 2305 (Build 16501.20180)" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.673-240><thread=7720 (0x1E28)>
sync: SMS synchronizing updates, processed 4287 out of 4287 items (100%) $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.685-240><thread=7720 (0x1E28)>

Update 5281dbfc-2b22-4d52-a350-8a67f7f80198 not synced due to content download issue $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.931-240><thread=7720 (0x1E28)>
Update 5866f50d-0ca5-4e86-b242-4f2a59a0ba76 not synced due to content download issue $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:07.937-240><thread=7720 (0x1E28)>
--------------------------------------------------------------------------------
WSYNCMRGR.LOG
Sync failed: Some Office updates not synced due to content download issue. Reason: The download of the specified resource has failed.. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:08.895-240><thread=13400 (0x3458)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=LEASVRMGMT10.LEALGROUP.LOCAL SITE=LEA PID=4128 TID=13400 GMTDATE=Tue May 30 09:27:08.901 2023 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Some Office updates not synced due to content download issue" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X800c0008 $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:08.901-240><thread=13400 (0x3458)>
Sync failed because top site Office content processing failure. Sync will *not* retry further. $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:08.948-240><thread=13400 (0x3458)>
Setting sync alert to active state on site LEA $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:08.955-240><thread=13400 (0x3458)>
Sync time: 0d00h17m40s $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:09.038-240><thread=13400 (0x3458)>
Skipping Delete Expired Update relations since this is not a scheduled sync. $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:09.048-240><thread=13400 (0x3458)>
Inbox source is local on LEASVRMGMT10.LEALGROUP.LOCAL $$<SMS_WSUS_SYNC_MANAGER><05-30-2023 13:27:09.126-240><thread=13400 (0x3458)>
------------------------------------------------------------------------------WSUSCTRL LOG
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 12:45:40.397-240><thread=13384 (0x3448)>
Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 12:45:40.422-240><thread=13384 (0x3448)>
There are no unhealthy WSUS Server components on WSUS Server LEASVRMGMT10.LEALGROUP.LOCAL~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 12:45:40.456-240><thread=13384 (0x3448)>
Successfully checked database connection on WSUS server LEASVRMGMT10.LEALGROUP.LOCAL~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 12:45:40.506-240><thread=13384 (0x3448)>
~Waiting for changes for 57 minutes $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 12:45:40.521-240><thread=13384 (0x3448)>
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.507-240><thread=13384 (0x3448)>
Checking for supported version of WSUS (min WSUS 4.0)~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.516-240><thread=13384 (0x3448)>
Checking runtime v4.0.30319...~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.526-240><thread=13384 (0x3448)>
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.17763.1~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.543-240><thread=13384 (0x3448)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.17763.2931~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.559-240><thread=13384 (0x3448)>
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.568-240><thread=13384 (0x3448)>
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.578-240><thread=13384 (0x3448)>
Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.604-240><thread=13384 (0x3448)>
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.679-240><thread=13384 (0x3448)>
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.687-240><thread=13384 (0x3448)>
Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.711-240><thread=13384 (0x3448)>
There are no unhealthy WSUS Server components on WSUS Server LEASVRMGMT10.LEALGROUP.LOCAL~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.735-240><thread=13384 (0x3448)>
Successfully checked database connection on WSUS server LEASVRMGMT10.LEALGROUP.LOCAL~ $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.782-240><thread=13384 (0x3448)>
~Waiting for changes for 57 minutes $$<SMS_WSUS_CONTROL_MANAGER><05-30-2023 13:42:40.791-240><thread=13384 (0x3448)>
 
Last edited:
Solution
Hi GARTH ,

thank you for your support, I finally opted for the reinstallation of the Wsus server which allowed me to leave on a clean base and less heavy also in storage sizes.

Step 1
Uninstall the SUP role and wait for some time . Any SUP object like updates lists, templates SUPSetup.log file in the logs directory will show you the status of the uninstall action.

Step 2
Uninstall WSUS from Add/Remove programs.

Step 3
Restart the server.

Step 4
Install WSUS and add SUP site server role on SCCM server.

Again check the SUPSetup.log for results.

This completes the procedure.

tks for your help

Regards
Hi GARTH ,

thank you for your support, I finally opted for the reinstallation of the Wsus server which allowed me to leave on a clean base and less heavy also in storage sizes.

Step 1
Uninstall the SUP role and wait for some time . Any SUP object like updates lists, templates SUPSetup.log file in the logs directory will show you the status of the uninstall action.

Step 2
Uninstall WSUS from Add/Remove programs.

Step 3
Restart the server.

Step 4
Install WSUS and add SUP site server role on SCCM server.

Again check the SUPSetup.log for results.

This completes the procedure.

tks for your help

Regards
 
Solution
Back
Top