Found send request.  ID: 1_V94M00, Dest Site: ASQ
There is no longer an address to destination site ASQ
Abandoning send request because address is not available.
Reset the send request to a pending state.

Contributed By: Cliff Hobbs [MVP SMS]
You're seeing this error because SMS is trying to contact the other Site (Site Code "ASQ" in the above example), 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.

In this specific example the error was 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.

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 to a Site that has been deleted from the hierarchy:

1. Make a note of the file SMS is trying to send ("1_V94M00" in this example).
    
2. 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
    
3. Load SMS Service Manager (navigate to "Systems Management Server | Site database (<site_code> - <site_description>) | Tools" then right-click "SMS Service Manager" select "All Tasks | Start SMS Service Manager")..

Although you could in theory stop the SMS Executive service to stop the SMS_LAN_SENDER thread, doing so would stop ALL of the threads that make up the SMS Executive and in effect bring your Site to a standstill. It is far better to use SMS Service Manager to just stop one of more threads of SMS Executive rather than all of them (unless you really to need to stop SMS on your Site). The other danger with trying to stop the SMS Executive on a busy Site is that sometimes Service Manager times out leaving the service in a "Stopping" state, the only way to resolve this is to reboot the server which may not always be possible/ desirable.

4. Within SMS Service Manager expand the SMS Site.
    
5. Expand "Components".
    
6. Expand the relevant Sender ("SMS_LAN_SENDER" if you're using the Standard Sender which was the case in this example), then click on the Site Server.
    
7. Select "SMS_LAN_SENDER" in the right-hand window/ details pane.
    
8. Click the yellow exclamation mark (!) on the toolbar to query the current state of the service.
    
9. The "Status" column should show as "Running".
    
10. Next click on the Stop button (the red square), on the toolbar.
     
11. Then click the yellow exclamation mark (!) on the toolbar to query the current state of the service.
     
12. Periodically click on the yellow exclamation mark (!) on the toolbar until the "Status" changes from "Running" to "Stopped".
     
13. Navigate to the "<drive>:\SMS\inboxes\schedule.box\outboxes\LAN" (assuming this file is being sent using the LAN Sender).
     
14. Delete the offending Send Request File (.SRQ), file noted in Step 1.
     
15. Go back to SMS Service Manager.
     
16. Click on the "SMS_LAN_SENDER".
     
17. Click the green Play button (green arrow pointing to the right), to start the "SMS_LAN_SENDER" thread.
     
18. Click the yellow exclamation mark (!) on the toolbar to query the current state of the service.
     
19. Periodically click on the yellow exclamation mark (!) on the toolbar until the "Status" changes from "Stopped" to "Running".
     
20. 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.

DON'T be tempted to delete all of the SRQ files in the Sender's outbox as these maybe perfectly good send requests destined to other Sites.  Also don't go deleting any of the other files in this directory otherwise you'll break your Site - if in doubt leave well alone..!!