Post reply

SQL Mail Error

  • April 21, 2006 at 6:05 am

    #113952

    I'm getting this error:

    xp_sendmail: failed with mail error 0x80040119

    When trying to run this T-SQL

    xp_sendmail

    @recipients='xxx@xxx.com',

    @subject='Here are your query results',

    @query='SELECT count (*) FROM database.dbo.table'

    From the Master database in SQL Query Analyzer.

    email address and database info is changed to protect the innocent

    I'm simply trying to get a count of records from a table emailed to me every day.

    I've seen the MS site info on this error message but Outlook is running fine on the box and is sending out other reports run from DTS packages. Any suggestions?

    Thanks

  • April 21, 2006 at 6:50 am

    #633485

    Pls check the SQL Mail..Test....under Support services ..Enterprise Manager.

  • April 21, 2006 at 8:03 am

    #633509

    Tested, got msg saying Succesfully Started and Stopped MAPI blah blah. Reran TSQL, same error msg. ;-(

  • April 21, 2006 at 6:44 pm

    #633632

    Perfect !!!...in that case the fault is ur SQL Server couldnt connect to ur Microsoft Exchange server...its the matter of some rule settings with your networks...You ll have to confirm things with your Network Administrator.

    Hope that helps !!!

  • April 21, 2006 at 7:24 pm

    #633634

    hey Also...Ask your network admin watz the email id that SQL Server uses....try sending an email to that id...

    find is that reaching SQL inbox using xp_readmail.

  • May 1, 2006 at 2:08 pm

    #635211

    Hi,

     

    Have you got it resolved? I got the same error message.

     

    Thank you very much,

     

    Liping

  • May 1, 2006 at 2:34 pm

    #635221

    Not yet, I found this link, but haven't had the time to try to fix this, if it help you will you post here and let me know?

    http://support.microsoft.com/?kbid=814441

  • May 16, 2006 at 6:09 pm

    #638324

     issue was resolved by restarting the sql server service

  • July 6, 2006 at 4:02 pm

    #647854

    Just worked through the same condition on our SQL Server 2005 system. Restarting the service wasn't an option in our case. We got the error after reconfiguring the Outlook profile to use a new Exchange server.

    It turns out that sqlservr.exe was hanging on to an *.oab file in the old and possibly corrupt Outlook profile. We found this out using ProcessExplorerNt.

    Ran xp_stopmail, deleted and recreated the Outlook profile, ran xp_startmail. And xp_sendmail started working again.

    Hopefully, this will save someone else a headache.

    --Tom

    Kindest Regards,

    Thomas Brittain
    kerpau.net

  • July 6, 2006 at 4:07 pm

    #647858

    Thanks Tom, we're still struggling with this and will give this a try.

    Ron

  • July 21, 2006 at 11:00 am

    #650805

    Thanks Tom,

    Had the same problem, did exactly what you suggested and everything is back in working order.

    Many thanks for saving me a weekend of grief, now I have one that I can relax and enjoy.

    Darren

     

  • March 21, 2007 at 1:08 am

    #696093

    Ditto, worked like a dream.

  • March 26, 2008 at 1:19 pm

    #794309

    Huh. I have three servers that email me their DBCC summaries. I'm out of the office for a week and a half and all three stop. Of course everyone denies any changes to Exchange or passwords or anything. I do an xp_stopmail and xp_startmail and one server starts working. I do it on another, and nada. Do it on the third, nada. Go back to the second, that server stops the SQL Server service every night to FTP everything to a DR server. Eventually it starts working again. Go back to the third server, xp_stop/start again, nada. Tell the application admin on that box that I need to bounce SQL yesterday evening but I end up off-site at close of business and can't bounce it. Get back in the office this morning and it has emailed me its DBCC summary, along with the second server sending me its summary.

    So what's the xp_ for exorcising SQL Server?

    I looked at the corrupt OAB angle but couldn't clear it, and since one of the affected servers is our ERP system, I can't work on it as easily as the others. But at least everything is working now.

    *sigh* *pounds head into desk*

    -----
    [font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]

  • February 21, 2011 at 5:53 am

    #1289385

    Thomas Brittain (7/6/2006)

    Just worked through the same condition on our SQL Server 2005 system. Restarting the service wasn't an option in our case. We got the error after reconfiguring the Outlook profile to use a new Exchange server.

    It turns out that sqlservr.exe was hanging on to an *.oab file in the old and possibly corrupt Outlook profile. We found this out using ProcessExplorerNt.

    Ran xp_stopmail, deleted and recreated the Outlook profile, ran xp_startmail. And xp_sendmail started working again.

    Hopefully, this will save someone else a headache.

    --Tom

    Thank you Tom, this worked for me in my SQL Server 2000, thank you soooo very much

  • March 30, 2011 at 7:07 am

    #1305415

    Bouncing the email session seemed to do the trick for us. We are running SQL 2000 and a job tries to send a status following a step via email.

    We inserted the following as a new first step to the job:

    xp_stopmail

    xp_startmail

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply