Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, March 2, 2017 2:31 PM
Hi All,
I want to distribute 10 packages to DP but when i assigned packages from primary to DP it will get stuck in content updating.
Distmgr.log shows as given below for all packages:
Adding package 'Z000109E' to package processing queue.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
7268 (0x1C64)
Currently using 0 out of 50 allowed package processing threads.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
7268 (0x1C64)
Started package processing thread for package 'Z000109E', thread ID = 0x8970 (35184)
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
7268 (0x1C64)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER
3/2/2017 12:29:22 PM 7268 (0x1C64)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=A00SVCMEU0P01.ZA.IF.ATCSG.NET SITE=EU0 PID=5260 TID=35184 GMTDATE=Thu Mar 02 11:29:22.935 2017 ISTR0="Office2016MUI" ISTR1="Z000109E" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="Z000109E"
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
35184 (0x8970)
Processing package Z000109E (SourceVersion:1;StoredVersion:1)
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
35184 (0x8970)
No action specified for the package Z000109E, however there may be package server changes for this package.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:22 PM
35184 (0x8970)
The contents for the updated package Z000109E hasn't arrived from site 000 yet, will retry later.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:23 PM
35184 (0x8970)
STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=A00SVCMEU0P01.ZA.IF.ATCSG.NET SITE=EU0 PID=5260 TID=35184 GMTDATE=Thu Mar 02 11:29:23.014 2017 ISTR0="Z000109E" ISTR1="000" ISTR2="EU0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="Z000109E"
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:23 PM
35184 (0x8970)
Created policy provider trigger for ID Z000109E SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
Package Z000109E does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=Z000109E, Version=1, Status=2301
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
StoredPkgVersion (1) of package Z000109E. StoredPkgVersion in database is 1.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
SourceVersion (1) of package Z000109E. SourceVersion in database is 1.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=A00SVCMEU0P01.ZA.IF.ATCSG.NET SITE=EU0 PID=5260 TID=35184 GMTDATE=Thu Mar 02 11:29:27.287 2017 ISTR0="Office2016MUI" ISTR1="Z000109E" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="Z000109E"
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
Exiting package processing thread for package Z000109E.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
35184 (0x8970)
Currently using 0 out of 50 allowed package processing threads.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
7268 (0x1C64)
Exiting package processing thread for package Z0001094.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:37:29 PM
38192 (0x9530)
it is giving same status for all 10 package.
any suggestion would be helpful
All replies (17)
Thursday, March 2, 2017 2:35 PM | 1 vote
Currently using 0 out of 50 allowed package processing threads.
SMS_DISTRIBUTION_MANAGER 3/2/2017 12:29:27 PM
Distmgr is doing nothing. You can also use DP Job Monitor from the ConfigMgr toolkit to get additional details, but I doubt that something's moving. What does the monitoring node tell?
Torsten Meringer | http://www.mssccmfaq.de
Thursday, March 2, 2017 2:40 PM
Where is this distmgr.log from? Is it a primary site in a hierarchy with a CAS or is it a secondary site?
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, March 2, 2017 2:56 PM
Hello Torsten,
I have tried with DP Job monitor also it shows 0 running jobs.
Monitoring node also gives same status as waiting for content.
Thursday, March 2, 2017 2:57 PM
distmgr.log is from primary site
Thursday, March 2, 2017 2:58 PM
is there any other way to check package processing in SCCM 2012 CMCB except distmgr.log and PkgXfermgr.log?
Thursday, March 2, 2017 3:05 PM
So site 000 is a CAS?
Jason | http://blog.configmgrftw.com | @jasonsandys
Friday, March 3, 2017 6:57 AM
Hello Jason
yes site 000 is CAS but i have assigned package from its primary and package which i assigned is already distributed on primary to which DP belongs to.
Friday, March 3, 2017 8:09 AM
Could you check the following?:
Go to Administration > Distribution points. Go to the properties for one of the DP's that is waiting.
Is there a checkmark before "Enable this distribution point for prestaged content" ?
If so, then remove it.
Friday, March 3, 2017 8:19 AM
There is no checkmark for "Enable this distribution point for prestaged content"
Friday, March 3, 2017 9:46 AM
Allright.
So is it just updating an existing package or only updating?
You can try to delete the package from a specific DP. Through administration > Distribution Points, go to properties from a specific DP. Then in the Content tab, search for a package e.q. Z000109E.
Then remove it. You can also check if there are already some files for this package on the DP. If they are not deleted automatically when removing it from the server (through the console) then delete them manually.
Go to your application and "distribute content". You can now select the specific DP again.
When doing this, be sure to open Distmgr.log, Pkgxfer.log and smsdbmon.log (with CMtrace) and just wait.
Just another question. Are these new (clean) dp's? Are other pacakges/applications already distribute to these dp's?
Another thing you can check is the number of Maximum threads per package in Software distribution conponent properties under Sites>Sitename>Configure site components > Software Distribution.
Here you can change the maximum threads. You have to be patient for it to become active.
Friday, March 3, 2017 10:40 AM
I have deleted all package file from DP and unassign package from DP.
Assigned package again but no progress.
This is new DP in our infra and maximum threads are 50.
actually 450 packages are supposed to be distributed on DP out of which 300 are distributed.
but after that it is not processing single package from last two weeks situation is same.
There is no network issue because package targeted in slots.
Friday, March 3, 2017 1:17 PM
Hmmm...
I think you've checked this, but is your primary site server in the local administrators group on the DP? I think it is because otherwise those 300 wouldn't have been distributed. But still, maybe something has changed on the DP.
Disk space is not an issue?
Have you already checked pkgxfer.log? Do you see lines which refer to the specific packages?
Are those packages succesfully distributed to other DP's? Could it be something you typed in the content path? Did you use the FQDN?
What happens after a content validation?
Sorry for a lot questions, but I know from my own experience that when you're stuck on such issue, you sometimes don't see everything clear anymore. Sometimes it's just a small thing which can hold you up for days.
Friday, March 3, 2017 1:30 PM
Yes i have checked pkgxfermgr.log it is showing waiting for instruction.
yes that packages are successfully distributed to other DP.
Package is already created on console and distributed on other DP, I have just added DP in available package.
Friday, March 3, 2017 1:31 PM
what this line in log exactly mean
No action specified for the package Z00007F2, however there may be package server changes for this package.
Friday, March 3, 2017 8:05 PM
> "already distributed on primary "
That's not possible, there's no such thing as distributing to a primary site. The log file is clear, the primary site does not have the content. You need to check sender.log on the CAS as well as distmgr.log on the CAS.
Jason | http://blog.configmgrftw.com | @jasonsandys
Monday, March 6, 2017 8:43 AM
Yes you are right.
Distribution on Primary is happened long back thats is reason it is not showing in log.
Tuesday, March 7, 2017 8:52 AM
We're now 5 days further. Did a validation on the DP's taken place?
Maybe this blog article is worth reading for you:
https://blogs.technet.microsoft.com/sudheesn/2013/12/15/content-distribution-to-distribution-points-part-ii/