This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 4%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hi,
Under the Distribution Point Job queue Manger it show that 86 jobs are running for last 5 days.
I have checked Distmgr, PKGXfermgr log on primary server and SMSDPPRov log on DP but I dont see any issue. The DP which is showing 86 package running is Pull DP
Our Setup
CAS with 3 Primary Site With DP and Pull DP
My question is
Does it mean 86 Jobs are replicating to this server or is this server replicating 86 Job to other DP's
What logs i can check to see why it has 86 Job running for last 5 days.
Which server do I need check the logs from
Please advice
You can look at smsdbmon, smsdpusage on the dp. Is the content available on the source server? Is the data transfer always slow for the pull dp in question? Have you checked network for related issues? You can try switching to a different source server. Just be mindful of high network utilization.
I look at the same package which is showing as pending on Pull DP was successfully disputed to source DP.
Package on source DP was successfully disputed but on pull dp its showing as pending.
I'm not sure why its still in pending after 5 days
Source DP
Distribution Manager successfully distributed package "000001" to distribution point "["Display=\SOURCE-DP\"]MSWNET:["SMS_SITE=005"]\SOURCE-DP\".
Pull DP
Package Transfer Manager failed to update the package "000001", Version 1 on pull distribution point Pull-DP. This pull distribution point has no sources from which it can download content. We will try again later.
Possible cause: The content was not distributed to source distribution points.
Solution: Ensure that the content is distributed to at least one of the source distribution points.
Possible cause: The content was distributed to source distribution points, but the source distribution points have not finished downloading the content.
Solution: Check content status to see if this package is in-progress for the source distribution point.
Possible cause: The source distribution point list is empty.
Solution: Check the 'Pull Distribution Point' tab in distribution point properties in the admin console and ensure that the source distribution points are set correctly.
smsdbmon, smsdpusage log doenst show any information. the only thing i can see in smsdpusage package removed
Did you check status messages of the dp in question? What about pkgxfermgr?
I can't find any entry in pkgxfermgr log for same pull DP.
Try pre-staging content for 1 package and check if the status syncs with the primary or not. If it doesn't then the issue is with your pull dp configuration.
Hi, @lalajee
Thank you for posting in Microsoft Q&A forum.
If the query returns more than 50 jobs, it will not send any more jobs to the pull DP.
You may refer to this guidance for troubleshooting:
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-content-distribution#common-pull-dp-issues
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
May we know the current status of the problem?