Backlog for obsolete job schedule\outbox\LAN

I have written this post on behalf of my one best friend Christian, Who suggest me to do some work with obsolete jobs  in SCCM inboxes whenever a site is removed and preinst /deljob is not helping to stop ongoing jobs.

        How to Identify obsolete jobs

You're Seeing this error because SMS is trying to contact to site S3F and is unable To. There are several possible reasons for this, the most likely being that the Target site is offline or unreachable for some reason. Your first course of Action should be to check that the target Site is up and running and Functioning correctly, including network connectivity. But in most cases, the The error is being generated in the log because although the Site had been removed From the SMS hierarchy, there were still outstanding jobs in SMS waiting to be Sent to the target Site.

      Workaround to solve this issue

     Note:

It's A good idea once you've removed a Site from your SMS hierarchy and given plenty Of time for the dust to settle to run the "preinst" command to delete Any outstanding jobs targeted to the deleted Site first, as well as running it Again to check that the actual Site Code has been deleted from the SMS Hierarchy and if it hasn't to do so.

         So if You have pending jobs in SMS trying to be sent in a Site that has been deleted From the hierarchy,            perform the following steps to remove these jobs: 

         a)  Make a note of the file SMS is trying to send ("23GLFPSG" in this example).

b) Load SQL Query Analyzer and run the following Command to check that SMS does not think this is still a valid Site and is Simply unable to communicate with it, for example if the server is offline: 

SELECT * FROM Sites 

         c) Load ConfigMgr Service Manager in SCCM

          

         

        d) Stop the SMS_LAN_SENDER

        

  e) Navigate to the <\\SITESERVER>\d$\Program Files\Microsoft Configuration     Manager\inboxes\schedule.box\outboxes\LAN”

         f) Delete the offending Send Request Files (. SRQ), File noted in Step a.

  

        g) Go back to ConfigMgr Service Manager and Start SMS_LAN_SENDER Service.

        h) Check the Sender.log to ensure there aren't Any more similar errors. If there are then you'll need to repeat the process Again.