MAPI_E_NO_ACCESS

Using SQL Mail and have found that the hex number of translates to MAPI_E_NO
_ACCESS. What should I look at next? It is obvious that I have some access v
iolation/rights issue that is hindering me from sending the mail out thru ou
r newly installed Exchanger
Server 2003.Have you tried deleting the mail profile and then start from
scratch and recreate it?
-Sue
On Mon, 5 Apr 2004 10:31:13 -0700, "JayKusch"
<anonymous@.discussions.microsoft.com> wrote:

>Using SQL Mail and have found that the hex number of translates to MAPI_E_NO_ACCESS
. What should I look at next? It is obvious that I have some access violation/rights
issue that is hindering me from sending the mail out thru our newly installed Excha
nge
r Server 2003.

MAPI_E_LOGON_FAILED

SQL Mail is failing. SQL Agent Mail works, but SQL Mail
does not.
The online help says: "When you look up the hex value
0x80040111, you see that this corresponds to the MAPI
error message MAPI_E_LOGON_FAILED, which indicates that
SQL Mail failed to logon with the mail profile provided.
You can then take corrective action based on the error
message."
OK, so what's the "corrective action"?Check the following article for troubleshooting the
problems:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
INF: Common SQL Mail Problems
http://support.microsoft.com/?id=315886
-Sue
On Mon, 13 Oct 2003 08:53:56 -0700, "Dennis Taylor"
<dennistaylor@.freightliner.com> wrote:
>SQL Mail is failing. SQL Agent Mail works, but SQL Mail
>does not.
>The online help says: "When you look up the hex value
>0x80040111, you see that this corresponds to the MAPI
>error message MAPI_E_LOGON_FAILED, which indicates that
>SQL Mail failed to logon with the mail profile provided.
>You can then take corrective action based on the error
>message."
>OK, so what's the "corrective action"?
>