Jump to content


haribo48

Install Pending on Package Distribution to DP's

Recommended Posts

Hi There,

 

Our primary site server is constantly sitting on 'install pending' when trying to update distribution points with new package versions. This has been left full days with no effect.

 

The distmgr.log file seems to indicate it has picked up the command to update to a new version number of a package but then sits with the messages below

 

Used 3 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:27 PM 17216 (0x4340)
No more available threads left to process any more packages. SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:27 PM 17216 (0x4340)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:27 PM 17216 (0x4340)
Used 3 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:32 PM 17216 (0x4340)
No more available threads left to process any more packages. SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:32 PM 17216 (0x4340)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/22/2013 1:51:32 PM 17216 (0x4340)
The only option i have seen that actually works and kick starts the update of DP's is to kill the SMS_Executive process and re-start the SMS_Executive service.
We have had issues with the primary site server of this nature before for 1-2 days during busy roll outs but these issues have been ongoing for 2+-weeks and the system performance is being impacted. I am needing to restart the service nearly every time a package is updated.
Any advice would be welcome
Many Thanks

Share this post


Link to post
Share on other sites


Does it create the folders and the bits tmp files in there or does nothing appear?

 

check the distmgr and despool log.

 

If it's doing something like partially copying the files and appears to be stuck in the process, I've also restarted BITS on the DP on occassions. I try not to restart services on the site server if not all DPs are having issues.

Share this post


Link to post
Share on other sites

Hello Harvey,

 

Many thanks for the reply,

 

For new packages it varies sometimes it creates the package folder with no content, other times it creates nothing but shows the status as install pending.

 

For existing packages the folder is on the DP but doesn't get updated, even if the package is left over a weekend it does not update only until I manually kill the SMSExec process and start the SMS_Executive service does the update begin on the DP's completes within a few minutes depending on package size but the status stays as 'Installed' with the old package version.

 

I've checked the despool.log file and is full of "Waiting for ready instruction file.... SMS_DESPOOLER 10/24/2013 6:26:43 AM 3040 (0x0BE0)"

 

There are a few lines of the following as well:
SMS_EXECUTIVE started SMS_DESPOOLER as thread ID 10412 (0x28AC). SMS_DESPOOLER 10/24/2013 7:02:35 AM 8908 (0x22CC)
Despooler is starting... SMS_DESPOOLER 10/24/2013 7:02:35 AM 10412 (0x28AC)
CPublicKeyLookup::Initialize("e:\Microsoft Configuration Manager\inboxes\hman.box\pubkey") SMS_DESPOOLER 10/24/2013 7:02:35 AM 10412 (0x28AC)
CPublicKeyLookup::Initialize() Initializing the Public Key Store Path to e:\Microsoft Configuration Manager\inboxes\hman.box\pubkey SMS_DESPOOLER 10412 (0x28AC)

The distmgr log file looks like it begins to process the pacakge but uses all processing threads

 

Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 29412 (0x72E4)
Starting package processing thread,thread ID = 1140 SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 29412 (0x72E4)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 29412 (0x72E4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PSS1 SITE=TST PID=19908 TID=4416 GMTDATE=Thu Oct 24 07:18:42.703 2013 ISTR0="TestPackages1" ISTR1="TST004B1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="TST004B1" SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
No action specified for the package TST004B1. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
No action specified for the package on server ["Display=\\PSS-DP07\"]MSWNET:["SMS_SITE=TST"]\\PSS-DP07\. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
No action specified for the package on server ["Display=\\PSS-DP05\"]MSWNET:["SMS_SITE=TST"]\\PSS-DP05\. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
No action specified for the package on server ["Display=\\PSS-DP03\"]MSWNET:["SMS_SITE=TST"]\\PSS-DP03\. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
No action specified for the package on server ["Display=\\PSS1\"]MSWNET:["SMS_SITE=TST"]\\PSS1\. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Updating package info for package TST004B1 SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Created policy provider trigger for ID TST004B1 SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Package TST004B1 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
A program for package TST004B1 has changed, therefore it needs to be replicated to all child sites. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Package TST004B1 is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
StoredPkgVersion (0) of package TST004B1. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
SourceVersion (4) of package TST004B1. SourceVersion in database is 4. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PSS1 SITE=TST PID=19908 TID=4416 GMTDATE=Thu Oct 24 07:18:42.953 2013 ISTR0="TestPackages1" ISTR1="TST004B1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="TST004B1" SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:42 AM 4416 (0x1140)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:47 AM 29412 (0x72E4)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:47 AM 29412 (0x72E4)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:52 AM 29412 (0x72E4)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:18:52 AM 29412 (0x72E4)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:02 AM 29412 (0x72E4)
Starting package processing thread,thread ID = 202C SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:02 AM 29412 (0x72E4)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:02 AM 29412 (0x72E4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PSS1 SITE=TST PID=19908 TID=8236 GMTDATE=Thu Oct 24 07:22:02.830 2013 ISTR0="TestPackages1" ISTR1="TST004B1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="TST004B1" SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:02 AM 8236 (0x202C)
Start updating the package TST004B1... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:02 AM 8236 (0x202C)
CreatePackageSignature() called for Package TST004B1 with version 5 with source as \\SAN001\ICT_Service\Software\TestPackage1\v4.81\SCCM Source Files. KeepUnpackedSignature = 1 SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:07 AM 8236 (0x202C)
Used 2 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:07 AM 29412 (0x72E4)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 10/24/2013 8:22:07 AM 29412 (0x72E4)

 

It's almost like there is a backlog of packages that the system is getting stuck on, each time it retries to process it gets stuck and is released when i kill the SMS_Executive process and start the SMS_Executive service.

 

The issue affects all DP's we have 5 in total.

 

I've checked one of the DP's and Bits is currently running with the status below:

 

SERVICE_NAME: bits
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

 

 

I also noticed on the same DP that we've had a lot of WDS errors event ID 4101 (92 in the last 24hrs) not sure if this is related.

The Following Client failed TFTP Download:
IP:xx.xx.xx.xx
Filename: \smsboot\x64\wdsnbp.com
ErrorCode: 1460

 

 

Hope i've not done information overload!

 

Any advice or help would be welcome

 

Many thanks

 

 

Share this post


Link to post
Share on other sites

Hello All

 

Still having a problem with this.

 

I've been looking at similar posts and some advise to check folders under the inboxes - particularly the pkginfo.box and distmgr.box folders which has loads of files and folders in there, many of which are over 6months old, could this be an issue with orphaned packages though no SCCM log i've seem specifically mentioned a problem related to orphaned files or packages.

 

G:\Microsoft Configuration Manager\inboxes\pkginfo.box - 2091 files and folders

G:\Microsoft Configuration Manager\inboxes\distmgr.box - 175 files

 

Could this be creating a backlog of packages for processing which would cause the problems.

 

I've looked at despool.log file which seems to be filled with 'waiting for ready instruction file'

 

Any advice would be welcome.

 

Thank you in advance

Share this post


Link to post
Share on other sites

Hi

 

Still having issues with this any advice would be really welcome having to kill the SMS_Exec process and restart the service every time a package is updated to a new version on DP's

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...