locked
SCCM: distribution point "Install Pending" for days RRS feed

  • Question

  • I am running SCCM 2007 SP1, 1 primary site and 3 Secondaries all acting as DPs, the problem I am having is with a single package update on a single DP.  The status remains Install Pending, I have removed the problem DP from the package's distribution points and waited a day for SCCM to clear itself.  I added the this DP back as a distribution point for this package and wind up exactly where I started.  I have waited days without seeing any change in status, yet all the other DPs update within minutes.  Other packages arrive and install just fine on this DP and this package installs just fine on the other 3 DPs.

    When reviewing the distmgr.log from the DP I find the following entry repeated over and over.

    Package xxxxxxxx requires a newer version (3) of source files and the new compressed files haven't arrived yet, current version is 2, skip C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\90LL7ZY6.PKG SMS_DISTRIBUTION_MANAGER 3/11/2009 2:30:00 AM 4064 (0x0FE0)

    There is free space on the volume, rights are all in place.  Are there any other logs that may help point out the problem?
    • Moved by Stan White [MSFT]Microsoft employee Thursday, March 12, 2009 9:20 PM Wrong category (Moved from Configuration Manager General to Configuration Manager Software Distribution)
    Tuesday, March 10, 2009 6:22 PM

Answers

All replies

  • The sender log might be useful as well.
    Kent Agerlund
    • Proposed as answer by Sid2985 Friday, July 4, 2014 12:08 PM
    Tuesday, March 10, 2009 7:04 PM
  • Something got messed up for that package. I would copy the missing .pck file(s) manually to the child site and use preloadpkgonsite.exe for that particular package.
    Tuesday, March 10, 2009 8:55 PM
  • Forgive me I'm still a rank novice in the ways of SCCM.  When I copy the .pck file from Primary to this site's \SMSPKG and run the following command line on the DP I get:

    PreloadPkgOnSite.exe XXXXXXXX
    ****** Preload Package On Site ******
    The compressed package path for package XXXXXXXX is already set in the database
    OR this is the site where the package was created.
     There is no need to use this tool for this package on this site.


    As for the sender log, here is my best guess at relevant lines:
    Created sending thread (Thread ID = AF0) SMS_LAN_SENDER 3/11/2009 9:18:16 AM 2984 (0x0BA8)
    Trying the No. 1 address (out of 1) SMS_LAN_SENDER 3/11/2009 9:18:16 AM 2800 (0x0AF0)
    No (more) send requests found to process. SMS_LAN_SENDER 3/11/2009 9:18:16 AM 2984 (0x0BA8)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 3/11/2009 9:18:16 AM 2984 (0x0BA8)
    FQDN for server DP00004 is DP00004.xx.xxx.com SMS_LAN_SENDER 3/11/2009 9:18:16 AM 2800 (0x0AF0)
    Passed the xmit file test, use the existing connection SMS_LAN_SENDER 3/11/2009 9:18:18 AM 2800 (0x0AF0)
    Package file = C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Poy SMS_LAN_SENDER 3/11/2009 9:18:18 AM 2800 (0x0AF0)
    Instruction file = C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Itv SMS_LAN_SENDER 3/11/2009 9:18:18 AM 2800 (0x0AF0)
    Checking for remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK SMS_LAN_SENDER 3/11/2009 9:18:18 AM 2800 (0x0AF0)
    Checking for remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.SNI SMS_LAN_SENDER 3/11/2009 9:18:18 AM 2800 (0x0AF0)
    Checking for remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Attempt to create/open the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Created/opened the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Attempt to create/open the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Created/opened the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Sending Started [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Poy] SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Attempt to write 1024 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK at position 0 SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Wrote 1024 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK at position 0 SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Attempt to write 221 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK at position 1024 SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Wrote 221 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.PCK at position 1024 SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Sending completed [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Poy] SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Attempt to create/open the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP SMS_LAN_SENDER 3/11/2009 9:18:19 AM 2800 (0x0AF0)
    Created/opened the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Attempt to create/open the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Created/opened the remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Sending Started [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Itv] SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Attempt to write 396 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP at position 0 SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Wrote 396 bytes to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP at position 0 SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Sending completed [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000F38.Itv] SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Renaming remote file \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP to \\DP00004.xx.xxx.com\SMS_SITE\20308SA1.SNI SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Rename completed [\\DP00004.xx.xxx.com\SMS_SITE\20308SA1.TMP] SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Sending completed successfully SMS_LAN_SENDER 3/11/2009 9:18:20 AM 2800 (0x0AF0)
    Wednesday, March 11, 2009 12:48 PM
  • Then you might want to have a look at: http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/312d86e3-e793-4147-97a7-7785295e4986/. But keep in mind that editing the database directly is not supported (unless PSS tells you to do so).
    Wednesday, March 11, 2009 2:17 PM
  • I was able to resolve the issue by deleting the package from the DP in the following directories:

    SMSPKG
    SMSPKGX$
    SMSPKGSIG
    SMSSIG$

    After doing that I ran Update all distribution points with a new package source version, and the package was successfully updated on ALL DPs.  Thanks for the tips I still have a lot to learn.
    Wednesday, March 11, 2009 3:41 PM
  • I was able to resolve the issue by deleting the package from the DP in the following directories:

    SMSPKG
    SMSPKGX$
    SMSPKGSIG
    SMSSIG$

    After doing that I ran Update all distribution points with a new package source version, and the package was successfully updated on ALL DPs.  Thanks for the tips I still have a lot to learn.

    This worked for me so I would not go chopping it out the database if you can help it

    Cheers

    Kev


    Kev :)
    Wednesday, November 30, 2011 3:24 PM
  • I'm having to stop/restart the sms_executive service for the packages to finish loading to SMSPKGD$.  The distmgr.log seems to get hung on:

    Could not register signatures for package S010003F, version 0 and TargetPath D:\SMSPKGD$\S010003F\. Will do full file deltas for updated files.

    Any workarounds or fixes?  I have about 100 DP secondary sites!!!

    Friday, December 2, 2011 7:06 PM
  • This helped resolve my DP problems as well.  Thanks
    Thursday, February 16, 2012 3:49 PM
  • I recently ran into a similar problem on a 2007 SCCM environment. There were several packages that were targeted for install on various DPs but would stay stuck in an install pending state. 

    I attempted to delete the DP and add it back. I also tried to refresh the distribution point. 

    In my case I had to delete an old package status from the SCCM database.

    This blog post details the fix: http://blog.tyang.org/2011/08/03/sccm-package-stuck-at-install-pending-state/

    I did not wait a couple of hours after removing the package and package status. I was able to immediately able to target and install to the DP.

    Saturday, October 25, 2014 11:35 AM
  • This worked For me too!! Thanks very much.
    Wednesday, November 12, 2014 4:09 AM