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"?
>
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Monday, March 26, 2012
MAPI error 273
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!
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!
MAPI error 273
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.examnotes.net ***
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.examnotes.net ***
>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!
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.examnotes.net ***
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.examnotes.net ***
>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!
MAPI error 273
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.developersdex.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.developersdex.com ***
>Don't just participate in USENET...get rewarded for it!
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.developersdex.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.developersdex.com ***
>Don't just participate in USENET...get rewarded for it!
Friday, March 9, 2012
Managing SQL Server Agent
Hi,
I would like to know what are the possibilities to mange the Sql server Agent in the Sql Server 2005 express edition whit the Sql server mangement studio express, because I can't see it .
thanks
I would like to know what are the possibilities to mange the Sql server Agent in the Sql Server 2005 express edition whit the Sql server mangement studio express, because I can't see it .
thanks
Hi,
you can′t manage it, because it isn′t there:
Look at: http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
Saturday, February 25, 2012
Managing backup files using SQL Agent
My client has about 3 servers with several databases on each. These databases
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locally
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.
I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locally
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.
I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
Managing backup files using SQL Agent
My client has about 3 servers with several databases on each. These database
s
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locall
y
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
s
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locall
y
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
Larry Menzin
American Techsystems Corp.I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
Managing backup files using SQL Agent
My client has about 3 servers with several databases on each. These databases
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locally
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
--
Larry Menzin
American Techsystems Corp.I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
are backed up to disk using maintenance plans. This client wants to copy SQL
backup files on the disks of these servers to an additional server with a
tape drive to do consolidated backup to tape.
Is the best way to copy backup files already on disk to a network share to
use a DOS copy command through SQL Agent?
If so, is it best to run SQL Agent using a domain account with substantial
rights to ensure that SQL agent has appropriate file permissions both locally
and on network paths? When SQL agent runs under the local system account,
file copy operations fail with "Access denied" messages.
Does anyone have suggestions on how to do this task?
--
Larry Menzin
American Techsystems Corp.I run my SQL Agent using a Domain User account that is local administrator
on the server.
In your case, just add a step to the jobs that the maintenance plans created
that calls XP_Cmdshell to do a DOS copy of the files after the backup is
complete.
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.|||Hi
Do it as a OperatingSystemCommand (cmdExec) in SQL Agent.
Something like:
xcopy *.bak \\servername\sharename\*.* /E /Y
SQL Server has to use a domain account to run under, otherwise it does not
have a way to authenticate itself with the other server.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:B52A63D9-A817-430C-9B0F-17139F121FBC@.microsoft.com...
> My client has about 3 servers with several databases on each. These
> databases
> are backed up to disk using maintenance plans. This client wants to copy
> SQL
> backup files on the disks of these servers to an additional server with a
> tape drive to do consolidated backup to tape.
> Is the best way to copy backup files already on disk to a network share to
> use a DOS copy command through SQL Agent?
> If so, is it best to run SQL Agent using a domain account with substantial
> rights to ensure that SQL agent has appropriate file permissions both
> locally
> and on network paths? When SQL agent runs under the local system account,
> file copy operations fail with "Access denied" messages.
> Does anyone have suggestions on how to do this task?
> --
> Larry Menzin
> American Techsystems Corp.
Subscribe to:
Posts (Atom)