Post reply

SQL Mail problem - profiles configured correctly

  • October 20, 2003 at 9:17 am

    #65428

    I am having a problem with SQL Mail. Here's a little background. SQL Server is set to run under one domain user account (with an email box on Exchange server) and the SQL Server Agent is set to run under a different domain account (with it's own, seperate mailbox). This server was working fine up until a few days ago, and there haven't been any changes to anything that I am aware of.

    SQL Server Agent sends mail fine (automated messages, testing operators, etc.). I can also log into the server as the SQL Server service account, open Outlook 2000, and send and receive email just fine. I can also test the profile on the SQL Server propertied dialog fine as well.

    Outlook is defined as the email program under internet options, and there is nothing else I can think of to check. Every time I try to send an email through xp_sendmail, I get a MAPI login error (xp_startmail: failed with mail error 0x80040111).

    If anyone has any ideas, please let me know! THis is driving me crazy. I've never had this much trouble fixing a SQL Mail problem.

  • October 20, 2003 at 9:24 am

    #478808

    http://support.microsoft.com/default.aspx?scid=kb;en-us;327552&Product=sql

    Which service pack and hotfixes do you run?

  • October 20, 2003 at 9:28 am

    #478809

    The server is on SP2 (ver 8.00.524) - It's a little behind due to an application requirement.

  • October 20, 2003 at 9:33 am

    #478811

    Sorry, that version should have been 8.00.534.

  • October 20, 2003 at 11:49 pm

    #478892

    See Microsoft KB Article 320407 as there are issues with SQLmap70.dll ( can stop XP_sendmail working ) version 8.00.603 is better.

    Update to Service pack 3a for SQL2000 after testing . Immediate short term fix is to reboot server (worked on my Production Server)

  • October 21, 2003 at 7:14 am

    #478942

    Having similar error messages trying to get SQL Mail working... here's the thread:

    http://qa.sqlservercentral.com/forum/topic.asp?TOPIC_ID=17320&FORUM_ID=5&CAT_ID=1&Topic_Title=xp%5Fsendmail+with+%40query+parameter&Forum_Title=Administration>

    Good luck!

  • October 21, 2003 at 7:54 am

    #478946

    michaelr777 made very good point.

    I replaced SQLmap70.dll (File Version 2000.80.834.0) from another server (File Version 2000.80.760.0) in test server and it starts to work.

  • October 21, 2003 at 8:37 am

    #478959

    quote:

    michaelr777 made very good point.

    I replaced SQLmap70.dll (File Version 2000.80.834.0) from another server (File Version 2000.80.760.0) in test server and it starts to work.

    I think I read that KB article about fifty times already... It's confusing because it says the resolution is to install SP 3, which we have already done (SP 3a)... Anyway, I cannot find a DLL with that version on ANY of my servers (that damn DBA actually kept the servers in sync!). Where can I find a copy of the sql7map.dll to which you refer?

    --

    Thanks,

    Jay Pipes

  • October 21, 2003 at 9:18 am

    #478964

    Both MS03-031 security fix and KB 826161 will give you version 2000.80.811. If you need version 2000.80.778, you need call Microsoft to ask hotfix "http://support.microsoft.com/default.aspx?scid=kb;en-us;812915&Product=sql" that includes version 2000.80.778. Version 2000.80.760 is included in service pack 3a.

  • October 23, 2003 at 7:00 am

    #479277

    quote:

    Both MS03-031 security fix and KB 826161 will give you version 2000.80.811. If you need version 2000.80.778, you need call Microsoft to ask hotfix "http://support.microsoft.com/default.aspx?scid=kb;en-us;812915&Product=sql" that includes version 2000.80.778. Version 2000.80.760 is included in service pack 3a.

    Thanks, Allen. Much appreciated!

  • October 23, 2003 at 2:31 pm

    #479372

    I just resolved the problem, along with Microsoft PSS. They had me use a different mail profile for the SQL Server and the SQL Server Agent. The profiles pointed to the same mail account, though. After a stop and restart of SQL Server, it started working again.

    I haven't seen this suggestion on any of the troubleshooting KB articles, or anywhere else, for that matter.

    Thanks for all of the suggestions. Chris

Viewing 11 posts - 1 through 10 (of 10 total)

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