SCCM 2012 SP1 CU3 - I had a different issue, but similar because of the stuck "pending" packages. We had 10 Secondary Sites, but they were very unreliable compared to a regular DP, so I un-installed them and rebuilt them as regular DPs, they were taking too much of my time to nurse them along. Before I got rid of them, I opened a case with Microsoft because all 10 Secondary Sites had packages "pending" (this happened several times), below is some information from the ticket they may help, the UID snippet is from the link.
ISSUE: Multiple packages fail to distribute to secondary sites CAUSE: '.REQ' & '.JOB' files were missing from Schedule.box\UID on primary because of which it was not able to create scheduled jobs for sender RESOLUTION: We created the files in UID folder and redistributed the package, once the backlog was clear the package was successfully sent to the DP's. UID Before leaving the schedule.box folder we should stop a the UID folder. <http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Blogs-Components- WeblogFiles/00-00-00-59-74-metablogapi/1145.image_5F00_53.png> Description: Description: image In this folder we have two files - a .REQ and a .JOB. These are files used to track the progress of various items as they are sent through the scheduler. These files are critical to the operation of scheduler and should never be deleted. If they are you can recreate them as blank text files. If you have one file but not the other just take the filename of the one you have, increment it by a hundred or so and create the missing file with that new filename. If neither file are present you can recreate both - use a filename for both that would likely be above the value you might expect there. I like to use a filename of 00100000 since it would take a really long time for a site to send that many jobs so the filename is likely safe and leaves plenty of room to grow. http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-si te-communication-in-sms-sccm.aspx From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Gonzalez Sent: Monday, February 02, 2015 12:37 PM To: '[email protected]' Subject: [mssms] schedule.log destsite I've been doing some powershell to determine as to why some jobs are not processing on my secondary. Well, I noticed something very strange when I ran my script to the schedulequeue and found I have 4 jobs with no pkgid and they are going to two old sites, that we decomm'd quite some time ago. As to why these 4 jobs are residing has me perplexed. So I ran the bitsadmin module and didn't see jobs, and executed the DP monitor and do not see them but I see the send request, jobid and destsite and the state for all 4 is pending. Not sure where these reside at in the inboxes and I've been searching and running out of Booleans on bing and google. I verified on the DB site and queried in sysreslist, sitecontrol, sitecontrolnotification, etc, and all I have is my 1 primary and 1 secondary. Even did preinst /delsite on those two old site codes (NOTHING) Has anyone come across this before and if so, how do you remove those stale jobids? Description: Description: new title
