OS WIM file stuck at Install Retrying
We have a pair of WIM images 2.5 and 3.4 GB in size. The images are at the initial revision 1, and the only DP selected is on a DP that is part of the central primary site. The DP on the central primary site server is not selected to deploy. The DP is on a remote WAN connection with very good connectivity. Putting the WIM package on one of the child primaries with DP servers works just fine. Other packages sent to the DP also work correctly. The only error we get is the one in the satus manager, and a very uninformative "Error occurred" log message in the DISTMGR. The section from the log is below. The WIM files are copied to the SMSPKGC$\PackageID locations by SCCM without any problem, but show up as failed. We've deleted and readded the package, rebooted the site and DP servers. Anyone have any ideas? Cannot copy package NY0001B4 from \\sccmpkgsource\source\Capture\Windows 7\x86\Windows 7 SP1 x86 v03.wim to \\CRPPMSSCCMNYZ\SMSPKGC$\NY0001B4\, Win32 Error = 0 SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 6772 (0x1A74) Failed to copy package NY0001B4 from \\sccmpkgsource\source\Capture\Windows 7\x86\Windows 7 SP1 x86 v03.wim to MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\SMSPKGC$\NY0001B4\ SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 6772 (0x1A74) STATMSG: ID=2328 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CRPPMS2SCCMNY0 SITE=NY0 PID=3516 TID=6772 GMTDATE=Mon May 16 19:26:51.982 2011 ISTR0="NY0001B4" ISTR1="\\sccmpkgsource\source\Capture\Windows 7\x86\Windows 7 SP1 x86 v03.wim" ISTR2="MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\SMSPKGC$\NY0001B4\" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="NY0001B4" AID1=404 AVAL1="["Display=\\CRPPMSSCCMNYZ\"]MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\" SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 6772 (0x1A74) Error occurred. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 6772 (0x1A74) Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 6772 (0x1A74) Cannot copy package NY0001AE from \\sccmpkgsource\source\Capture\Windows 7\x64\Windows 7 SP1 x64 v03.wim to \\CRPPMSSCCMNYZ\SMSPKGC$\NY0001AE\, Win32 Error = 0 SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:51 PM 4428 (0x114C) Failed to copy package NY0001AE from \\sccmpkgsource\source\Capture\Windows 7\x64\Windows 7 SP1 x64 v03.wim to MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\SMSPKGC$\NY0001AE\ SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4428 (0x114C) STATMSG: ID=2328 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CRPPMS2SCCMNY0 SITE=NY0 PID=3516 TID=4428 GMTDATE=Mon May 16 19:26:52.011 2011 ISTR0="NY0001AE" ISTR1="\\sccmpkgsource\source\Capture\Windows 7\x64\Windows 7 SP1 x64 v03.wim" ISTR2="MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\SMSPKGC$\NY0001AE\" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="NY0001AE" AID1=404 AVAL1="["Display=\\CRPPMSSCCMNYZ\"]MSWNET:["SMS_SITE=NY0"]\\CRPPMSSCCMNYZ\" SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4428 (0x114C) Error occurred. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4428 (0x114C) Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4428 (0x114C) DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) DP thread with thread handle 6160 and thread ID 6772 ended. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) Updating package info for package NY0001B4 SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4468 (0x1174) DP thread with thread handle 7264 and thread ID 4428 ended. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4468 (0x1174) Only retrying local DP update for package NY0001B4, no need to replicate package definition to child sites or DP info to parent site. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) Updating package info for package NY0001AE SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 4468 (0x1174) StoredPkgVersion (0) of package NY0001B4. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) SourceVersion (1) of package NY0001B4. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CRPPMS2SCCMNY0 SITE=NY0 PID=3516 TID=6484 GMTDATE=Mon May 16 19:26:52.070 2011 ISTR0="Windows 7 SP1 x86 v03" ISTR1="NY0001B4" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="NY0001B4" SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) Failed to process package NY0001B4 after 2 retries, will retry 98 more times SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954) Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 5/16/2011 3:26:52 PM 6484 (0x1954)Bob
May 16th, 2011 3:53pm

A few other minor pieces of info: Binary Differential Replication is disabled. Central Primary Site Server is WS2003 R2, DP is WS2008R2. Bob
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2011 3:55pm

disable any antivirus on the dp to see if that's a cause, how much free space is on that server ? My step by step SCCM Guides I'm on Twitter > ncbrady
May 16th, 2011 4:15pm

The SMSPKG$ directory is excluded already from SCCM, and other packages (soft dist) work just fine. Free space on the server > 90 GB, so it's not running out of space. The Primary has 40 GB free.Bob
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2011 4:21pm

But just to make sure I'm having the AV guys make sure it's excluded.Bob
May 16th, 2011 4:24pm

Looks like it may be AV. They set the exclusion wrong, we are testing it now.Bob
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2011 5:12pm

Well, it's not AV, we turned it off and there isn't any change. Started digging through the event logs and ran accross the following event for WMI that happens very close to all the failure times. The description for Event ID 5605 from source Microsoft-Windows-WMI cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: root\MicrosoftIISv2 Did some looking and found this article, which seems related. I don't think running the script to lower the permissions as suggested is the solution. I also don't see what would have lowered the permissions levels. But this does make some sense since the file is copied, I'm wondering if the issue is with BITS. Not sure why that would be the case since other packages update just fine. I'll go dig through the IIS logs maybe I'll find something there. Event ID 5605 — WMI Client Connections Updated: December 6, 2007 Applies To: Windows Server 2008 A WMI client is any process that connects to the WMI service. Event Details Product: Windows Operating System ID: 5605 Source: Microsoft-Windows-WMI Version: 6.0 Symbolic Name: WBEM_MC_WBEM_REQUIRES_ENCRYPTION_DENIED Message: Access to the %1 namespace was denied because the namespace is marked with RequiresEncryption but the script or application attempted to connect to this namespace with an authentication level below Pkt_Privacy. Change the authentication level to Pkt_Privacy and run the script or application again. Bob
May 17th, 2011 8:53am

Looks like it may be a network problem. Arg, I hate troubleshooting those.Bob
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2011 9:08am

did you iis logs reveal anything My step by step SCCM Guides I'm on Twitter > ncbrady
May 17th, 2011 2:44pm

Did you check it before? Event ID 5605 — WMI Client Connections http://technet.microsoft.com/en-us/library/dd363657(WS.10).aspx Hope it helps.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 5:19am

Sorry for not responding, it was a network issue which we resolved. The NIC on the DP was failing intermittently. Bob
May 26th, 2011 8:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics