Install Pending on Branch DP

i have a boot image that refuses to install on a branch DP. I've been fighting this for a week and have gotten no where. The boot image had previously installed fine on this branch DP but is now stuck at "Install Pending".  The Branch DP is functioning as I am able to distribute other packages to it. And the package appears to be find as it installs on other DP's without issue. I've tried removing the package from the DP and re adding it. I've also tried manually deleting the package from the DP and re adding it but all that i get is "install pending" for days. Here is a snippet from the distmgr.log when i try to install the package on the branch DP.
 
5/28/2012 11:21:11 PM    Starting package processing thread,thread ID = 944
5/28/2012 11:21:11 PM    Sleep 3600 seconds...
5/28/2012 11:21:11 PM    STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SRV-SCCM SITE=SC0 PID=5692 TID=2372 GMTDATE=Tue May 29 04:21:11.994 2012 ISTR0="Boot Image (x64)" ISTR1="SC000083" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SC000083"
5/28/2012 11:21:11 PM    No action specified for the package SC000083.
5/28/2012 11:21:12 PM    No action specified for the package on server ["Display=\\SRV-DCDH1\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=SC0"]\\SRV-DCDH1\SMSPXEIMAGES$\.
5/28/2012 11:21:12 PM    Start adding package to server ["Display=\\srv-dcdh1\"]MSWNET:["SMS_SITE=SC0"]\\srv-dcdh1\...
5/28/2012 11:21:12 PM    DPID 12 - NAL Path ["Display=\\srv-dcdh1\"]MSWNET:["SMS_SITE=SC0"]\\srv-dcdh1\ is a Branch DP
5/28/2012 11:21:12 PM    Processing for Branch DP
5/28/2012 11:21:12 PM    STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SRV-SCCM SITE=SC0 PID=5692 TID=2372 GMTDATE=Tue May 29 04:21:12.026 2012 ISTR0="Boot Image (x64)" ISTR1="["Display=\\srv-dcdh1\"]MSWNET:["SMS_SITE=SC0"]\\srv-dcdh1\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="SC000083" AID1=404 AVAL1="["Display=\\srv-dcdh1\"]MSWNET:["SMS_SITE=SC0"]\\srv-dcdh1\"
5/28/2012 11:21:12 PM    Successfully updated PeerDPPkgMap for DPID 12 and PkgID SC000083.
5/28/2012 11:21:12 PM    Successfully inserted MachineID for DPID 12 into PeerDPResMapChg_Notif table.
5/28/2012 11:21:12 PM    Created policy provider trigger for ID SC000083
5/28/2012 11:21:12 PM    No action specified for the package on server ["Display=\\SRV-SCCM\"]MSWNET:["SMS_SITE=SC0"]\\SRV-SCCM\.
5/28/2012 11:21:12 PM    No action specified for the package on server ["Display=\\SRV-SCCM\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=SC0"]\\SRV-SCCM\SMSPXEIMAGES$\.
5/28/2012 11:21:12 PM    Updating package info for package SC000083
5/28/2012 11:21:12 PM    Package SC000083 does not have a preferred sender.
5/28/2012 11:21:12 PM    The package and/or program properties for package SC000083 have not changed,  need to determine which site(s) need updated package info.
5/28/2012 11:21:12 PM    StoredPkgVersion (0) of package SC000083. StoredPkgVersion in database is 0.
5/28/2012 11:21:12 PM    SourceVersion (38) of package SC000083. SourceVersion in database is 38.
5/28/2012 11:21:12 PM    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SRV-SCCM SITE=SC0 PID=5692 TID=2372 GMTDATE=Tue May 29 04:21:12.073 2012 ISTR0="Boot Image (x64)" ISTR1="SC000083" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SC000083"
5/28/2012 11:21:12 PM    Exiting package processing thread.
5/28/2012 11:21:17 PM    Used 0 out of 3 allowed processing threads.
5/28/2012 11:21:17 PM    Sleep 3600 seconds...
5/28/2012 11:21:22 PM    Used 0 out of 3 allowed processing threads.
5/28/2012 11:21:22 PM    Sleep 3600 seconds...
 
Thanks in advance for any help,
Justin

What are BITS settings set under Computer Client Agent to?  If they are set to low nothing will happen. Trying unticking any throttling and watch the log so see if there is any change (I would do this outside of hours to reduce any possible impact on your users) 
 
The fix that we found for this issue was to ensure that the following was set for the CCM_Imcoming site on the the distribution point server/s and also the primary server.

• IIS manager
• Default site
• CCM_Incoming
• Double click on BITS
• Tick 'Allow Clients to upload files'

This changed our BDP sites from reporting Install pending though the package was being successfully installed to a status of installed.

Check datatransfer or contenettransfer logs on the BDP. IF BITS is failing or having an issue, the download shuold fall back to a regular UNC SMB path.

msmith515


What are BITS settings set under Computer Client Agent to?  If they are set to low nothing will happen. Trying unticking any throttling and watch the log so see if there is any change (I would do this outside of hours to reduce any possible impact on your users) 

The fix that we found for this issue was to ensure that the following was set for the CCM_Imcoming site on the the distribution point server/s and also the primary server.

• IIS manager
• Default site
• CCM_Incoming
• Double click on BITS
• Tick 'Allow Clients to upload files'

This changed our BDP sites from reporting Install pending though the package was being successfully installed to a status of installed.

 
BITS settings on the Computer Client Agent  set to "Apply to BDP only" and the transfer rate for both inside and outside of the throttling windows are set to 9999kbps. so this appears to be fine. The IIS settings also appear to correct.

CAP


Check datatransfer or contenettransfer logs on the BDP. IF BITS is failing or having an issue, the download shuold fall back to a regular UNC SMB path.

 
I dont see anything in the DataTransfer log regarding the package in question. In the ContentTransfer log I see this a few times:
 
5/29/2012 4:46:12 AM    Starting CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39}.
5/29/2012 4:46:12 AM    Created CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} for user S-1-5-18
5/29/2012 4:46:12 AM    Created and Sent Location Request '{7342B3AF-3AF9-4134-B00F-F9B06E346451}' for package SC000083
5/29/2012 4:46:12 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
5/29/2012 4:46:12 AM    Queued location request '{7342B3AF-3AF9-4134-B00F-F9B06E346451}' for CTM job '{D0267A9B-4B2D-4A07-8971-5B1726745B39}'.
5/29/2012 4:46:13 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 5:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 6:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 7:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 8:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 9:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 10:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 11:38:56 AM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 12:38:56 PM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended
5/29/2012 1:38:56 PM    CTM job {D0267A9B-4B2D-4A07-8971-5B1726745B39} suspended

you may need to get the BITSAdmin Tool to cancel the BITS jobs on that BDP. Upon doing that it shuold resync and create a new CTM job to download agian.

CAP


you may need to get the BITSAdmin Tool to cancel the BITS jobs on that BDP. Upon doing that it shuold resync and create a new CTM job to download agian.

 
The BITSAdmin tool wont run on the BDP as BITS is not installed on it. When I run the tool on the Primary site server/DP it tells me "Listed 0 Jobs"

Go to the branch DP in question and run Bitsadmin /list /allusers /verbose >>bitsout.txt and then look in that file to see if there is a bits job hung from the branch DP.  If there is you will want to post the errors that you get from the bits job.  If not check the actual peerdp log file on the branch DP to see that is showing that it is ready to receive the package

mhullnc


Go to the branch DP in question and run Bitsadmin /list /allusers /verbose >>bitsout.txt and then look in that file to see if there is a bits job hung from the branch DP.  If there is you will want to post the errors that you get from the bits job.  If not check the actual peerdp log file on the branch DP to see that is showing that it is ready to receive the package

 
Here the the output I get when running the BitsAdmin Tool on the BDP
 

BITSADMIN version 3.0 [ 7.5.7601 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

Unable to enum jobs - 0x80070005
Access is denied.

You may want to run that at the system level.  You should have bits installed on a branch DP as that is what it uses to transfer data from the standard DP in the site over IIS.  To make sure that you have access, download psexec.exe , you can find it as part of the pstools from sysinternals (now Microsoft).  Then run a DOS prompt as administrator, you are still not at the system level, so run
psexec.exe -i -s
now another command prompt with show that is at the system level where you can run bitsadmin /list /allusers
 
You also need to make sure you are an administrator on the branch DP server
 
Post what you get from bits at that point. 
 
I also posted a guide to troubleshooting branch DP's on this forum, that has more details.
 
Thanks