I've setup SQL Mail and I'm trying to setup SQL Server Agent mail as
well, but this does not work.
Both MSSQLServer and SQLServerAgent services run under the standard
local Administrator account. A mailprofile and a postbox is created for
this account, client is Outlook 2000, mailserver is Exchange 5.5. The
mailaccount works fine, I can sent and receive mail.
When activating SQLMail, no problem. I can use xp_sendmail without a
problem.
However, when trying to activate SQL Server Agent mail, after choosing
the Exchange profile(the same 1 as for SQL Mail, there is only 1
profile) I receive a MAPI Logon failed:
Error 22022:SQL Server Agent error: MapiLogon Ex Failed due to MAPI
error 273: MAPI Logon failed.
I can understand what this means:the Administrator account is not
recognized as a legal login. Since both services run under this login,
and this poses noprob for SQL Mail, it makes no sence to me. Obviously I
am missing something, but I don't know what.
I have googled the internet and came up with guiet a view similar
questions. Read several Q&A's, among others also the ones from
Microsoft, but either the suggested causes were not, or the possible
reasons did not aply. I found 1 solution which I tried: enter the
profile(BTW, there is only 1 profile), accept it tho testing it
generates the failure and stop&restart the SQLServerAgent. It did not
work.
Now a new feature has arissen: the mailsession droplist, with which to
set the mailprofile is greyed out, and the TEST button as well! This
means I cannot change the SQLServerAgent Mail settings anymore! Probably
I can rectify this by changing the service under which the
SQLServerAgent runs, but still I wouild like to know what is causing
this behaviour, and how to solve it.
Currently I'm not using SQLServerAgentMail, I use SQL Mail, but this
problem is nagging me and it irritates me that I cannot find out what is
wrong.
Systeminfo: SQL2K, W2K, Exchange 5.5, all applicable servicepacks and
patches, Outlook 2000 v9.0.0.2711.
Any hints apreciated,
Hans Brouwer
Tnx,
Hans Brouwer
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
It's not clear how you have the service accounts set up. If
by "standard local Administrator account" you mean Local
System, then this would be the problem. If you are using
Exchange as your mail server, the service account needs to
be setup as a domain account.
-Sue
On Wed, 14 Apr 2004 03:40:34 -0700, hansje
<hansjes@.anonymous.com> wrote:
>I've setup SQL Mail and I'm trying to setup SQL Server Agent mail as
>well, but this does not work.
>Both MSSQLServer and SQLServerAgent services run under the standard
>local Administrator account. A mailprofile and a postbox is created for
>this account, client is Outlook 2000, mailserver is Exchange 5.5. The
>mailaccount works fine, I can sent and receive mail.
>When activating SQLMail, no problem. I can use xp_sendmail without a
>problem.
>However, when trying to activate SQL Server Agent mail, after choosing
>the Exchange profile(the same 1 as for SQL Mail, there is only 1
>profile) I receive a MAPI Logon failed:
>Error 22022:SQL Server Agent error: MapiLogon Ex Failed due to MAPI
>error 273: MAPI Logon failed.
>I can understand what this means:the Administrator account is not
>recognized as a legal login. Since both services run under this login,
>and this poses noprob for SQL Mail, it makes no sence to me. Obviously I
>am missing something, but I don't know what.
>I have googled the internet and came up with guiet a view similar
>questions. Read several Q&A's, among others also the ones from
>Microsoft, but either the suggested causes were not, or the possible
>reasons did not aply. I found 1 solution which I tried: enter the
>profile(BTW, there is only 1 profile), accept it tho testing it
>generates the failure and stop&restart the SQLServerAgent. It did not
>work.
>Now a new feature has arissen: the mailsession droplist, with which to
>set the mailprofile is greyed out, and the TEST button as well! This
>means I cannot change the SQLServerAgent Mail settings anymore! Probably
>I can rectify this by changing the service under which the
>SQLServerAgent runs, but still I wouild like to know what is causing
>this behaviour, and how to solve it.
>Currently I'm not using SQLServerAgentMail, I use SQL Mail, but this
>problem is nagging me and it irritates me that I cannot find out what is
>wrong.
>Systeminfo: SQL2K, W2K, Exchange 5.5, all applicable servicepacks and
>patches, Outlook 2000 v9.0.0.2711.
>Any hints apreciated,
>Hans Brouwer
>
>
>Tnx,
>Hans Brouwer
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
|||Hi Sue,
I use the Administrator account of the server, where SQL Server is
installed, not the local system account.
Tnx,
Hans Brouwer
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||If you are using the Administrator's account local to the
server then this isn't a domain account and won't work. You
need a domain account if you are using Exchange as the mail
server.
-Sue
On Thu, 15 Apr 2004 00:21:04 -0700, hansje
<hansjes@.anonymous.com> wrote:
>Hi Sue,
>I use the Administrator account of the server, where SQL Server is
>installed, not the local system account.
>Tnx,
>Hans Brouwer
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
|||Tnx for the info Sue; it does kleave me flabbergasted. The server in
question is a stand-alone server, not part of a domain, obviously part
of the companynetwork. Why does SQLMail not need to be part of a
domainaccount? MSSQLServer is also running under the local
Adminstratoraccount.
I can think of 1 reason, why the SQLServerAgent should run under a
domainaccount, and that is for running jobs executing distributed
queries on remote servers. However, jobs can run which do not execute
remote queries. I can't imagine wy the mailfunctionality IS dependant on
a domaionaccount..
I know, if these are the facts I'll have to live with it, but I would
like to know the reason for choosing such a configuration.
Tnx anyway,
Hans Brouwer
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You can find the requirement of a domain account for SQL
Mail when using an Exchange mail server in the following
Microsoft knowledge base article:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
If you'd rather just use smtp to run mail related tasks,
take a look at a free extended stored procedure which uses
just smtp for mail. You can find it at:
http://www.sqldev.net/xp/xpsmtp.htm
-Sue
On Tue, 20 Apr 2004 04:12:11 -0700, hansje
<hansjes@.anonymous.com> wrote:
>Tnx for the info Sue; it does kleave me flabbergasted. The server in
>question is a stand-alone server, not part of a domain, obviously part
>of the companynetwork. Why does SQLMail not need to be part of a
>domainaccount? MSSQLServer is also running under the local
>Adminstratoraccount.
>I can think of 1 reason, why the SQLServerAgent should run under a
>domainaccount, and that is for running jobs executing distributed
>queries on remote servers. However, jobs can run which do not execute
>remote queries. I can't imagine wy the mailfunctionality IS dependant on
>a domaionaccount..
>I know, if these are the facts I'll have to live with it, but I would
>like to know the reason for choosing such a configuration.
>Tnx anyway,
>Hans Brouwer
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
No comments:
Post a Comment