Hello together,

I already postet a simmilar question. So sorry for the duplication. I found an interesting article which is listing the needed logs for SCCM 2012 R2. The last time I was told to search for logs that I xould not found which were responding to SCCM 2007.

So here's the Link http://www.acupofit.com/2013/08/sccm-logs-to-check-when-troubleshooting.html

So I checked all listed LOGs and I found the following which I thought is interesting.

WSYNCMGR.LOG:

Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 134.170.53.29:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS	SMS_WSUS_SYNC_MANAGER	4/10/2015 8:01:59 AM	5628 (0x15FC)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SITESERVER.services.internal SITE=000 PID=3692 TID=5628 GMTDATE=Fr Apr 10 06:01:59.099 2015 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 134.170.53.29:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4/10/2015 8:01:59 AM	5628 (0x15FC)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	4/10/2015 8:01:59 AM	5628 (0x15FC)
Setting sync alert to active state on site 000	SMS_WSUS_SYNC_MANAGER	4/10/2015 8:01:59 AM	5628 (0x15FC)
Sync time: 0d00h00m38s	SMS_WSUS_SYNC_MANAGER	4/10/2015 8:01:59 AM	5628 (0x15FC)
Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Starting Sync	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Performing sync on retry schedule	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Read SUPs from SCF for NE-SCCM-02.services.internal	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Found active SUP NE-SCCM-02.services.internal from SCF File.	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SITESERVER.services.internal SITE=000 PID=3692 TID=5628 GMTDATE=Fr Apr 10 07:01:59.854 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:01:59 AM	5628 (0x15FC)
Synchronizing WSUS server NE-SCCM-02.services.internal	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:00 AM	5628 (0x15FC)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SITESERVER.services.internal SITE=000 PID=3692 TID=5628 GMTDATE=Fr Apr 10 07:02:00.870 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:00 AM	5628 (0x15FC)
Synchronizing WSUS server ne-sccm-02.services.internal ...	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:00 AM	11276 (0x2C0C)
sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:00 AM	11276 (0x2C0C)
Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 134.170.58.121:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:39 AM	5628 (0x15FC)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SITESERVER.services.internal SITE=000 PID=3692 TID=5628 GMTDATE=Fr Apr 10 07:02:39.889 2015 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 134.170.58.121:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:39 AM	5628 (0x15FC)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	4/10/2015 9:02:39 AM	5628 (0x15FC)

RULEENGINE.LOG

Failed to download the update from internet. Error = 16389	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)
Failed to download ContentID 16936340 for UpdateID 16953422. Error code = 16389	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)

Failed to download any update	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)
Failed to download update contents.	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)
No new update was added to the package. Package "00000116" would not be updated.	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)
Failed to run the DownloadAction for the AutoDeployment.	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)
STATMSG: ID=8706 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_RULE_ENGINE" SYS=SITESERVER.services.internal SITE=000 PID=3692 TID=9660 GMTDATE=Do Apr 09 14:56:50.872 2015 ISTR0="SMS Rule Engine" ISTR1="Failed to download one or more content files" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_RULE_ENGINE	4/9/2015 4:56:50 PM	9660 (0x25BC)

CRuleHandler: Enforcing Actions for Rule 16777230 failed!	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
CRuleHandler: ResetRulesAndCleanUp()	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777222	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777223	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777224	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777225	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777226	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777227	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777228	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777229	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)
Updated Failure Information for Rule: 16777230	SMS_RULE_ENGINE	4/9/2015 4:57:03 PM	9660 (0x25BC)

Patchdownloader.log

Failed to move C:\Windows\TEMP\CAB7665.tmp to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1\windows8.1-kb3000850-x64.cab, error 32	Software Updates Patch Downloader	4/9/2015 4:53:13 PM	11328 (0x2C40)
Will retry in 5000ms	Software Updates Patch Downloader	4/9/2015 4:53:13 PM	11328 (0x2C40)
Successfully moved C:\Windows\TEMP\CAB7665.tmp to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1\windows8.1-kb3000850-x64.cab	Software Updates Patch Downloader	4/9/2015 4:55:05 PM	11328 (0x2C40)
Renaming \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050	Software Updates Patch Downloader	4/9/2015 4:55:05 PM	9660 (0x25BC)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 64	Software Updates Patch Downloader	4/9/2015 4:56:20 PM	9660 (0x25BC)
Will retry in 10000ms	Software Updates Patch Downloader	4/9/2015 4:56:20 PM	9660 (0x25BC)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5	Software Updates Patch Downloader	4/9/2015 4:56:30 PM	9660 (0x25BC)
Will retry in 10000ms	Software Updates Patch Downloader	4/9/2015 4:56:30 PM	9660 (0x25BC)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5	Software Updates Patch Downloader	4/9/2015 4:56:40 PM	9660 (0x25BC)
Will retry in 10000ms	Software Updates Patch Downloader	4/9/2015 4:56:40 PM	9660 (0x25BC)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5	Software Updates Patch Downloader	4/9/2015 4:56:50 PM	9660 (0x25BC)
MoveFile() failed to rename \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050 with GetLastError() = 5	Software Updates Patch Downloader	4/9/2015 4:56:50 PM	9660 (0x25BC)
ERROR: DownloadContentFiles() failed with hr=0x80004005	Software Updates Patch Downloader	4/9/2015 4:56:50 PM	9660 (0x25BC)

As I still could not found any solutions I am asking the community again.

next thing i am facing here is

all Patches with 8.1 in name can not be renamed from XYZ.1 to XYZ

A repetative Issue

If I try to download the Patch manualy I get:

  Error: Failed to download content id 16930935. Error: There was an error downloading the software update. (16389)
Package:
  Success: The software updates were placed in the existing package:
    Patches
Software updates that will be downloaded from the internet
  Error: Windows Server 2012 R2 Update (KB2919355)
Errors
    Failed to download content id 16930935. Error: There was an error downloading the software update. (16389)

from the WSYNCMGR.LOG that the "failing patches" are on "Synchronizing Update". All others are Skipped or downloaded. Should I maybe delete the files from TEMP?

Synchronizing update cfc1739b-1fb2-4ee7-802b-b87c08428235 - Security Update for Windows Server 2003 (KB3050995)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:42 AM	4696 (0x1258)
Synchronizing update 086110f9-6500-4ada-902d-7861cd2cd90b - Update for Windows Server 2012 R2 (KB3000850)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:46 AM	4696 (0x1258)
Synchronizing update 20e9f58b-64d4-49cc-86d8-b75562b893d0 - Update for Windows 8.1 (KB3000850)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:49 AM	4696 (0x1258)
Synchronizing update bdf42393-64c7-4d66-9e53-c58020f8f797 - Update for Windows 8.1 for x64-based Systems (KB3000850)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:51 AM	4696 (0x1258)
Synchronizing update c675e91f-d28e-45a9-b4a3-8ba53c603631 - Update for Windows 8.1 (KB3042085)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:53 AM	4696 (0x1258)
Synchronizing update d037967e-0fef-493c-bd34-9d99eb63756c - Update for Windows 8.1 for x64-based Systems (KB3042085)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:54 AM	4696 (0x1258)
Synchronizing update 5414fab1-738f-47aa-9198-c7b902206a48 - Update for Windows Server 2012 R2 (KB3042085)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:55 AM	4696 (0x1258)
Synchronizing update 26e2a7ee-34d5-4161-ab79-56625337046f - Windows 8.1 Update for x64-based Systems (KB2919355)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:11:56 AM	4696 (0x1258)
Synchronizing update 8452bac0-bf53-4fbd-915d-499de08c338b - Windows Server 2012 R2 Update (KB2919355)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:12:01 AM	4696 (0x1258)
Synchronizing update 4ca4dbaa-fae4-4a7c-9760-8e202d10128f - Windows 8.1 Update (KB2919355)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:12:05 AM	4696 (0x1258)
sync: SMS synchronizing updates, processed 14844 out of 14844 items (100%)	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:12:09 AM	4696 (0x1258)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:12:09 AM	4696 (0x1258)
Removed 2 unreferenced updates	SMS_WSUS_SYNC_MANAGER	4/10/2015 11:12:10 AM	4696 (0x1258)

After excluding both patches I get no more Errors. Which is not an option.

Hi,

Please use Network Monitioring tool to do a trace when you download the updates manually. Then analyze it to see if there is anything interfering the download.

Best Regards,

Joyce