well, I would either move all the files to different folder and drop few files back to process OR stop the sms exectuive service,component manager,remove the backlogs and then start the service as what i can see possible solution.
------------------------------------ Eswar Koneti Configmgr Consultant www.eskonr.com-----------------------------------Date: Wed, 19 Mar 2014 08:34:36 -0400 Subject: Re: [mssms] Tips to deal with a backlog in Schedule.box on a 2007 infrastructure From: [email protected] To: [email protected] Thanks for the reply Eswar, I've found your blog to be so helpful over the years :) In my case, I've cleaned up all of the jobs in sender, the backlog is actually in schedule.box. On Wed, Mar 19, 2014 at 4:59 AM, Eswar Koneti <[email protected]> wrote: I don't see a way to speed up rather waiting for the site server to finish the jobs.backlogs could have caused if the respective component manager was stopped or not responding to process the jobs. If you really want to clear all the jobs (if you feel theu don't require to process now), then i wold stop the sender component, delete the jobs(not recommended ;) ) , more http://eskonr.com/2013/01/sccm-configmgr-find-packageid-from-sender-log-and-stop-the-process-which-is-being-sent-to-child-sites/. Regards, Eswar Koneti www.eskonr.com --- Original Message --- From: "Stephen Owen" <[email protected]> Sent: March 19, 2014 8:03 AM To: [email protected] Subject: [mssms] Tips to deal with a backlog in Schedule.box on a 2007 infrastructure Hi guys, We're having trouble this week getting a primary site to notice changes to a package, and I realized there are nearly 2,000 .JOB files in the schedule.box folder on this site. Looking through the messages, I don't see any dead-giveaways as to what has caused this backlog either. I've tried pausing then stopping Offer Manager, Hierarchy Manager, and Distribution Manager, after reading Eswar's blog http://eskonr.com/tag/site-control-manager/ and noting which components create jobs to report their status up the chain. I then read this blog http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-site-communication-in-sms-sccm.aspx and decided to stop ReplMgr as well, to try to keep the backlog from getting worse. Looking at the schedule.box folder and the schedule and sender logs, it looks like the scheduler is ever so slowly crunching through these files. I need them cleared STAT for a Nomad implementation, however. Anyone have any tips as to ways I can speed up this process? I found a ton of outdated jobs in sender refering to sites that no longer exist, so I cleaned those up using preinst and then removed the files for them. Thanks,
