On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.
There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.
|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
sql
Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Wednesday, March 21, 2012
Job Notification
On our SQL 2000 server there is no MAPI client or Outlook installed. The NET
SEND command has been disabled on the server/network. The xp_sendmail can n
ot be used due to SQL Mail not started due to no Outlook profile. I don't fi
nd that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writi
ng the Log to Application Event Log. Any feedback would be appreciated.There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdo
sysmail in the Master database but could find them. Could you please let me
know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me
know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thank
s...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmai
l in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks.
.Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
>
SEND command has been disabled on the server/network. The xp_sendmail can n
ot be used due to SQL Mail not started due to no Outlook profile. I don't fi
nd that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writi
ng the Log to Application Event Log. Any feedback would be appreciated.There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdo
sysmail in the Master database but could find them. Could you please let me
know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me
know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thank
s...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmai
l in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks.
.Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
>
Job Notification
On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification page allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.Check out SMTPMail on SQLDev.NET. You can either add that
as a job step on failure, or create a job that is called
when an alert executes. I believe there is an example of
the latter on that website.
FYI, SQL 2005 is going to support both MAPI-based and SMTP-
based email notification.
>--Original Message--
>On our SQL 2000 server there is no MAPI client or Outlook
installed. The NET SEND command has been disabled on the
server/network. The xp_sendmail can not be used due to SQL
Mail not started due to no Outlook profile. I don't find
that the Notification page allows to attach a command or
batch file to do this job. It is just writing the Log to
Application Event Log. Any feedback would be appreciated.
>.
>|||There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
> "Richard Ding" wrote:
> > There're about three ways to email a notification for a job:
> > 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> > 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> > 3. Install sp_send_cdosysmail and use this stored procedure to send out
> > email.
> >
> > I personally prefer sqlmail due to it's rich features. But be aware of its
> > total dependency on MS Exchange.
> >
> >
> > "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> > news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> > NET SEND command has been disabled on the server/network. The xp_sendmail
> > can not be used due to SQL Mail not started due to no Outlook profile. I
> > don't find that the Notification page allows to attach a command or batch
> > file to do this job. It is just writing the Log to Application Event Log.
> > Any feedback would be appreciated.
> >
> >
> >
as a job step on failure, or create a job that is called
when an alert executes. I believe there is an example of
the latter on that website.
FYI, SQL 2005 is going to support both MAPI-based and SMTP-
based email notification.
>--Original Message--
>On our SQL 2000 server there is no MAPI client or Outlook
installed. The NET SEND command has been disabled on the
server/network. The xp_sendmail can not be used due to SQL
Mail not started due to no Outlook profile. I don't find
that the Notification page allows to attach a command or
batch file to do this job. It is just writing the Log to
Application Event Log. Any feedback would be appreciated.
>.
>|||There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
> "Richard Ding" wrote:
> > There're about three ways to email a notification for a job:
> > 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> > 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> > 3. Install sp_send_cdosysmail and use this stored procedure to send out
> > email.
> >
> > I personally prefer sqlmail due to it's rich features. But be aware of its
> > total dependency on MS Exchange.
> >
> >
> > "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> > news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> > NET SEND command has been disabled on the server/network. The xp_sendmail
> > can not be used due to SQL Mail not started due to no Outlook profile. I
> > don't find that the Notification page allows to attach a command or batch
> > file to do this job. It is just writing the Log to Application Event Log.
> > Any feedback would be appreciated.
> >
> >
> >
Monday, March 12, 2012
Job fails when run as SQL Agent
Hi,
I have developed a package which selects records from SQL 2000 table from a server on network and writes it into an excel sheet.
The package runs fine from IDE. I am using "DoNotSaveSensitive" option. I have deployed this package on my local server which is SQL 2005 with SP2.
and scheduled through a job to run as SQLAgent. But I am getting the following error:
Message
Executed as user: STEL540\SYSTEM. ...on 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:22:20 p.m.
Error: 2007-08-20 15:22:22.00
Code: 0xC0202009
Source: LastMonthCallTagging Connection manager "HAMDB02-GenCallTagging"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "Communication link failure". An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.".
End Error Error: 2007-08-20 15:22:22.02 Code: 0xC020... The package execution fa... The step failed.
Can someone please guide on this error?
Thanks,
How are you connecting to HAMDB02-GenCallTagging? Windows or sql server authentication?
|||When you are running packages it is all about context, when you run it manually it runs in the context of your permissions, as a Job it runs in the context of SQL Server Agent. Try the links below for details the Agent and the owner of the package needs admin level permissions.
http://support.microsoft.com/kb/918760/
http://support.microsoft.com/kb/938086/en-US
Job fails when run as SQL Agent
Hi,
I have developed a package which selects records from SQL 2000 table from a server on network and writes it into an excel sheet.
The package runs fine from IDE. I am using "DoNotSaveSensitive" option. I have deployed this package on my local server which is SQL 2005 with SP2.
and scheduled through a job to run as SQLAgent. But I am getting the following error:
Message
Executed as user: STEL540\SYSTEM. ...on 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:22:20 p.m.
Error: 2007-08-20 15:22:22.00
Code: 0xC0202009
Source: LastMonthCallTagging Connection manager "HAMDB02-GenCallTagging"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "Communication link failure". An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80004005
Description: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.".
End Error Error: 2007-08-20 15:22:22.02 Code: 0xC020... The package execution fa... The step failed.
Can someone please guide on this error?
Thanks,
How are you connecting to HAMDB02-GenCallTagging? Windows or sql server authentication?
|||When you are running packages it is all about context, when you run it manually it runs in the context of your permissions, as a Job it runs in the context of SQL Server Agent. Try the links below for details the Agent and the owner of the package needs admin level permissions.
http://support.microsoft.com/kb/918760/
http://support.microsoft.com/kb/938086/en-US
Friday, March 9, 2012
job failed to start - access denied
Hi,
the SQL Server Agent job that runs a backup to a network
drive wont start.The syntax is as follows :
BACKUP DATABASE Mydb
TO
DISK='\\ServerName\BACKUP\MyDB.BAK'
WITH INIT
In the error log and in the event viewer I can see the
following error message :operating system error 5 ( access
is denied). I can not figure it out why I can not run this
job since the SQL Server Agent startup account use the
domain user account that has sufficient permissions across
the domain and the job itself is owned by the same account.
Is there something else that I should pay attention to ?
Any view is apreciatedThe backup command runs under the security context of the SQL Server service
account. Ensure that account has the needed permissions.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mirko" <anonymous@.discussions.microsoft.com> wrote in message
news:023c01c3b978$a2a45a80$a001280a@.phx.gbl...
> Hi,
> the SQL Server Agent job that runs a backup to a network
> drive wont start.The syntax is as follows :
> BACKUP DATABASE Mydb
> TO
> DISK='\\ServerName\BACKUP\MyDB.BAK'
> WITH INIT
> In the error log and in the event viewer I can see the
> following error message :operating system error 5 ( access
> is denied). I can not figure it out why I can not run this
> job since the SQL Server Agent startup account use the
> domain user account that has sufficient permissions across
> the domain and the job itself is owned by the same account.
> Is there something else that I should pay attention to ?
> Any view is apreciated
>
the SQL Server Agent job that runs a backup to a network
drive wont start.The syntax is as follows :
BACKUP DATABASE Mydb
TO
DISK='\\ServerName\BACKUP\MyDB.BAK'
WITH INIT
In the error log and in the event viewer I can see the
following error message :operating system error 5 ( access
is denied). I can not figure it out why I can not run this
job since the SQL Server Agent startup account use the
domain user account that has sufficient permissions across
the domain and the job itself is owned by the same account.
Is there something else that I should pay attention to ?
Any view is apreciatedThe backup command runs under the security context of the SQL Server service
account. Ensure that account has the needed permissions.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mirko" <anonymous@.discussions.microsoft.com> wrote in message
news:023c01c3b978$a2a45a80$a001280a@.phx.gbl...
> Hi,
> the SQL Server Agent job that runs a backup to a network
> drive wont start.The syntax is as follows :
> BACKUP DATABASE Mydb
> TO
> DISK='\\ServerName\BACKUP\MyDB.BAK'
> WITH INIT
> In the error log and in the event viewer I can see the
> following error message :operating system error 5 ( access
> is denied). I can not figure it out why I can not run this
> job since the SQL Server Agent startup account use the
> domain user account that has sufficient permissions across
> the domain and the job itself is owned by the same account.
> Is there something else that I should pay attention to ?
> Any view is apreciated
>
Friday, February 24, 2012
JDBC SP3 and SSL
Hello all,
If I enable SSL on my SQL Server (using the Force Protocol Encryption in
Server Network Utility) and then use JDBC SP3 to connect (and Java 5 Update
2), will the connection succeed? If the current version of Microsoft's JDBC
Driver for SQL Server won't make a SSL connection, are there plans on a
future version having this capability?
The reason I ask is because we have one application that uses JDBC to
connect to SQL Server and it has to use Microsoft's JDBC Driver in order to
work, so using a Type 3 JDBC driver isn't an option for us.
Thanks,
Jason
Why does your application have to use the MS driver? There are a lot of
commercial type 4 drivers out there and a pretty good open source one,
too. All of these support SSL.
Alin,
The jTDS Project.
|||Alin,
The application I'm referring to is a purchased application, and I believe
it is coded to use the Microsoft JDBC driver. At least that is what the
installation instructions lead me to believe.
Thanks,
Jason
"Alin Sinpalean" wrote:
> Why does your application have to use the MS driver? There are a lot of
> commercial type 4 drivers out there and a pretty good open source one,
> too. All of these support SSL.
> Alin,
> The jTDS Project.
>
|||Jason Delaune wrote:
> Alin,
> The application I'm referring to is a purchased application, and I
believe
> it is coded to use the Microsoft JDBC driver. At least that is what
the
> installation instructions lead me to believe.
Usually applications are coded to use the JDBC specification. Relying
on non-standard features of particular implementations is not a good
idea. If that's the case then you're out of luck.
You could still try another driver, though. In 90% of the cases it
works.
Alin.
|||Alin,
Which driver(s) would you recommend that supports connections to SQL Server
using SSL?
Thanks,
Jason
"Alin Sinpalean" wrote:
> Jason Delaune wrote:
> believe
> the
> Usually applications are coded to use the JDBC specification. Relying
> on non-standard features of particular implementations is not a good
> idea. If that's the case then you're out of luck.
> You could still try another driver, though. In 90% of the cases it
> works.
> Alin.
>
|||I would of course recommend the open source jTDS JDBC driver (which I'm
a developer of); you can get it from http://jtds.sourceforge.net
There are also quite a few commercial drivers out there if you don't
trust open source, but they do cost a lot and are not necessarily
better. Just do a Google search and they will turn up.
Alin,
The jTDS Project.
If I enable SSL on my SQL Server (using the Force Protocol Encryption in
Server Network Utility) and then use JDBC SP3 to connect (and Java 5 Update
2), will the connection succeed? If the current version of Microsoft's JDBC
Driver for SQL Server won't make a SSL connection, are there plans on a
future version having this capability?
The reason I ask is because we have one application that uses JDBC to
connect to SQL Server and it has to use Microsoft's JDBC Driver in order to
work, so using a Type 3 JDBC driver isn't an option for us.
Thanks,
Jason
Why does your application have to use the MS driver? There are a lot of
commercial type 4 drivers out there and a pretty good open source one,
too. All of these support SSL.
Alin,
The jTDS Project.
|||Alin,
The application I'm referring to is a purchased application, and I believe
it is coded to use the Microsoft JDBC driver. At least that is what the
installation instructions lead me to believe.
Thanks,
Jason
"Alin Sinpalean" wrote:
> Why does your application have to use the MS driver? There are a lot of
> commercial type 4 drivers out there and a pretty good open source one,
> too. All of these support SSL.
> Alin,
> The jTDS Project.
>
|||Jason Delaune wrote:
> Alin,
> The application I'm referring to is a purchased application, and I
believe
> it is coded to use the Microsoft JDBC driver. At least that is what
the
> installation instructions lead me to believe.
Usually applications are coded to use the JDBC specification. Relying
on non-standard features of particular implementations is not a good
idea. If that's the case then you're out of luck.
You could still try another driver, though. In 90% of the cases it
works.
Alin.
|||Alin,
Which driver(s) would you recommend that supports connections to SQL Server
using SSL?
Thanks,
Jason
"Alin Sinpalean" wrote:
> Jason Delaune wrote:
> believe
> the
> Usually applications are coded to use the JDBC specification. Relying
> on non-standard features of particular implementations is not a good
> idea. If that's the case then you're out of luck.
> You could still try another driver, though. In 90% of the cases it
> works.
> Alin.
>
|||I would of course recommend the open source jTDS JDBC driver (which I'm
a developer of); you can get it from http://jtds.sourceforge.net
There are also quite a few commercial drivers out there if you don't
trust open source, but they do cost a lot and are not necessarily
better. Just do a Google search and they will turn up.
Alin,
The jTDS Project.
Subscribe to:
Posts (Atom)