Failed to schedule DTS in SQL 2005

Hello,

I am trying to to schedule DTS Package but this message appear .

Message
The job failed. The Job was invoked by User sa. The last step to run was step 1 (1). and this

Message
Executed as user: Computer name\SYSTEM. The package execution failed. The step failed

so how I can schedule DTS Package in sql 2005 .

Do you have logging enabled for this package? if enabled check the log file it should have more detailed information on the error.

The error you have posted is a very generic error from the job agent, and it does not give any information.

Thanks

|||

Sounds like you might have some issues with the account settings. See the following thread for tips on setting up proxies / credentials / jobs etc.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1

|||

Thanks, all

But still the same problem even I did all thing to solve but still can't schedule DTS, but when I see th proparites of the

SQL Server Agent-->Connection and found the sql server connection grayed out and can't select or change it . so may be this is the problem but how to run the agent under sa account .

|||

Assuming you are talking about the connection infromation on the left hand side of the job properties screen, that connection information is how you are currently connected to the sql server. You would need to look at the steps tab and click edit on the step associated with the package you are trying to run. At the top of this screen there will be a place for the step name (i.e. run package x), the type (sql server integration services package) and the run as. You would select the correct proxy name from the run as drop down that ties to your sa account...

|||

Thanks very much for you reply but I still can't schedule the DTS even though when I execute the dts it's work fine and I did all thing what said here http://www.codeproject.com/useritems/Schedule__Run__SSIS__DTS.asp

|||

I am trying to schedule working DTS in sql server 2005 sp 2 . but I it failed and got this message . I searched at Internet and found this

http://support.microsoft.com/kb/904796

but I can’t understand how to solve it, any one can help please .

Message

Executed as user: ComputrName\Administrator. ...00.3042.00 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.Started:10:16:11 ?Error: 2007-08-17 22:16:12.95Code: 0x00000000Source: Copy Data from ROOM toDBNamedboER_ROOMTaskDescription: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.at DTS.PackageClass.Execute()at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()End ErrorError: 2007-08-17 22:16:14.75Code: 0x00000000Description: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.at DTS.PackageClass.Execute()at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()End ErrorError: 2007-08-17 22:16:15.14Code: 0x00000000The package execution fa...The step failed.

|||

how to Reinstall the SQL Server 2000 tools? where to find it .

Still no solution can solve this issue .

sql

Failed to notify 'DBA' via email

We have some SQL jobs those run on a schedule basis. These jobs are setup to
notify us via email in case of job fails. However, Some time we get this
error "Failed to notify 'DBA' via email." Initially I thought it may be b/c
of mail server was not available but our exchnage server admin has looked at
exchange logs and not found any thing at that time. I also looked at the SQL
server logs and did not find any issues. My question is: is there any thing
can go wrong in the SQL server that can cause this probelm?
Help is appreciated.
Thanks,
MohMoh,
FWIW - SQL Server MAPI will only wait a certain amount of time to deliver a
message. If it cannot get out, then the mail will 'fail' even though
Exchange is up and running and healthy. It might be Exchange, networking,
domain issues, etc. that cause the problem.
If you Google on "sql mail Failed to notify" you will see a few comments on
this, without any real help that I could find.
(Unless xp_smtp_sendmail would work for you.)
RLF
"Moh Abb" <mabbas@.aligntech.com> wrote in message
news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> We have some SQL jobs those run on a schedule basis. These jobs are setup
to
> notify us via email in case of job fails. However, Some time we get this
> error "Failed to notify 'DBA' via email." Initially I thought it may be
b/c
> of mail server was not available but our exchnage server admin has looked
at
> exchange logs and not found any thing at that time. I also looked at the
SQL
> server logs and did not find any issues. My question is: is there any
thing
> can go wrong in the SQL server that can cause this probelm?
> Help is appreciated.
> Thanks,
> Moh
>|||"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:ePA64pj3EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Moh,
> FWIW - SQL Server MAPI will only wait a certain amount of time to deliver
a
> message. If it cannot get out, then the mail will 'fail' even though
> Exchange is up and running and healthy. It might be Exchange, networking,
> domain issues, etc. that cause the problem.
> If you Google on "sql mail Failed to notify" you will see a few comments
on
> this, without any real help that I could find.
Generally I find if you don't absolutely need to use Exchange, setup a local
SMTP server right on teh SQL box and send email through that directly.
Eliminates timeouts, etc.
> (Unless xp_smtp_sendmail would work for you.)
> RLF
> "Moh Abb" <mabbas@.aligntech.com> wrote in message
> news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> > We have some SQL jobs those run on a schedule basis. These jobs are
setup
> to
> > notify us via email in case of job fails. However, Some time we get this
> > error "Failed to notify 'DBA' via email." Initially I thought it may be
> b/c
> > of mail server was not available but our exchnage server admin has
looked
> at
> > exchange logs and not found any thing at that time. I also looked at the
> SQL
> > server logs and did not find any issues. My question is: is there any
> thing
> > can go wrong in the SQL server that can cause this probelm?
> >
> > Help is appreciated.
> >
> > Thanks,
> > Moh
> >
> >
>
>