Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-05-23 : 08:59:54
|
| Bruce writes "When our SQL Server 7 loses network connectivity with the email server that SQL server Agent uses for sending alerts (eg the Exchange server gets a reboot) the emailing of alerts fails (local windows messaging locks up - stopping and restarting the mapi32 service sometimes fixes the problem) until the server is rebooted.Is there an easy alternative way to send alerts (including the information about the alert) without having to use the standard method of using SQLmail or SQLAgentMail?Can SQLAgentMail be configured to call a command line emailer tool and pass it all the details of the alert as a parameter?Microsoft have a known issue with SQL needing 100% connectivity to the mail server.We don't want to have to bring down the servers everytime this happens." |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-05-23 : 11:15:45
|
| If you catch it early enough, you should only have to stop and restart the SQL Mail service. However, this often hangs, and results in one having to stop and restart the SQL Agent. Again, SQL Mail can cause problems with SQL Agent, which may require restarting SQL Server...and may eventually lead to the reboot you are doing now.I've started sending errors and reports to a specific table, and using CDONTs calls to mail the reports out. If Exchange is unavailable, I can resend the reports. Also, the process doesn't care whether Exchange is up - kind of a 'send and forget' so it doesn't lock up processes on the SQL Server. I've had good luck just writing errors to the event log, and having my CDONTs email solution tell me when I need to check it. I have to add the 'report' code to each SP or Scheduled Job I want included.But this is hardly the 'easy' remedy you are looking for. |
 |
|
|
|
|
|