May 25, 2011 at 9:45 pm
Hi all,
I've configured and am using database mail to send out regular SQL Server status reports (very 5 minutes). Most of the time this works without an issue, but every now and then I get this error:
The mail could not be sent to the recipients because of the mail server failure.
(Sending Mail using Account 2 (2011-05-24T19:26:44). Exception Message: Could not connect to mail
server. (A connection attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because connected host has failed to
respond x.x.x.x:25). (Note the IP is actually correct.)
After this the SQL Server becomes unresponsive, the SQL Agent stops running the alert job as seen by the job history, and we have to restart the server.
I'm running SQL 2008 SP2 on Window 2008 R2 on a VM.
Has anyone come across this before? Any ideas why SQL could become unresponsive?
I'm mnot getting any joy after hunting through all logs. There are no SQL Dumps and no errors that come to light besides the one above.
I'd appreciate some help.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
May 26, 2011 at 1:32 am
There might be two issues
One) With the mail server, may be too many mails hits the mail server, you can check with the IT team.
Two) Why SQL Server become unresponsive need investigation. After how many mails this happens ? There might be too many mail queue or any kind og locking in MSDB ( Service broker). Chcek SP_who2 for any blocking in MSDB if yes kill it or check if any one is dissabling the service broker in MSDB. SP_who2 will give you more info.
Next time please chk and post the result.
"More Green More Oxygen !! Plant a tree today"
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply