This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 358863 (SHILOH_BUGS)
If you have two instances of Microsoft SQL Server 2000 on the same computer, and SQL Mail is configured with separate mail profiles on each instance, when you try to use the xp_sendmail extended stored procedure from one of the instances of SQL Server, you may receive the following error message:
"xp_sendmail: failed with mail error 0x80040111".
This error code means "MAPI_E_LOGON_FAILED."
However, the other instance of SQL Server can still run the xp_sendmail extended stored procedure successfully.
When two instances of SQL Server are running under two different accounts, and each account uses a different mail profile, xp_sendmail can be executed only in the instance in which the xp_startmail extended stored procedure was run first. Running xp_startmail in the other instance causes the error MAPI_E_LOGON_FAILED (0x80040111) to occur.
This is a limitation of the MAPI subsystem that is used by SQL Mail.
To work around this behavior, use the same service startup account and mail profile for both instances of SQL Server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Other circumstances, such as an improper configuration of SQL Mail, might also cause a MAPI logon failure. This article only applies to the scenario described in the "Symptoms" section of this article.
If you use an Internet Mail Server instead of a Microsoft Exchange server, you might experience conflicts with the Personal Store file (.pst).For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
313969 PRB: The Error "Cannot Open .pst File" Occurs When You Use a POP3 Server Profile with SQL Mail