February 24, 2003 at 10:22 am
We're having problems with SQL Mail on two servers.
Attempts to run xp_sendmail in a scheduled job fail with this message:
xp_sendmail: failed with mail error 0x80040115 [SQLSTATE 42000] (Error 18025). The step failed.
Both servers are SQL 2000, one has SP2 + latest security patch, the other has SP3. One other bizarre thing is that the jobs alternate between working and failing. We've tried stopping and starting SQL Agent, and rebooting the servers, but nothing seems to work. We have lots of other SQL 2000 servers with SP2 that do not have this problem. I have not been able to find anything in the online help that addresses this specific error. Thanks for any
suggestions.
February 27, 2003 at 8:00 am
This was removed by the editor as SPAM
February 27, 2003 at 4:06 pm
Is the following article applicable?
http://support.microsoft.com/default.aspx?scid=kb;en-us;274330
Thanks
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
February 28, 2003 at 2:46 pm
Thank you very much for taking the time to research this. Unfortunately, the mantra of "just install the latest service pack" doesn't cover this problem. We're seeing this on servers with SP2 and SP3, and have about 20 other SQL 2000 SP2 servers with no problem. As near as we can tell, it's network issue of some kind. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;238119 The hex code 0x80040115 indicates a MAPI extended function encountered a network problem. I'm working with our Microsoft technical account mgr now on this for more troubleshooting. Thanks again for your interest and response.
quote:
Is the following article applicable?http://support.microsoft.com/default.aspx?scid=kb;en-us;274330
Thanks
Phill Carter
--------------------
Colt 45 - the original point and click interface
March 24, 2003 at 8:44 am
We have the same problem in 2 variations: one job behaves exactly how you described but another actually sends an email and then completes with a failure message. The majority of our servers are SQL 2000 with SP2 and latest security patches. From what we observed it happens the first time after exchange server reboot. That's why you see this problem on and off.
We had a similar issue with SQL email notification: once in a while jobs finished with a message "NOTE: failed to notify <xxx>...". As I said before it happened only first time after exchange server reboot. What we ended up with was setting a dummy job on each SQL server that does not do anything but sends email notification right after scheduled exchange reboot and before any "significant" jobs run. So far (a couple of months) so good.
I will probably build a similar job with xp_sendmail to see if it helps. It's not an elegant solution and I would be interested in outcome of your contact with Microsoft technician.
Thank you
Marina
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply