We recently changed the sa password on our SQL Server
2000. After we did that, our DTS Package stopped running
successfully. The package generates an error "18456-
Login Failed for "sa". The owner of the job is sa. We
checked that sa is still setup as a system
administrator. We also verifyied the SQL Server Agent
had the correct sa password. We're tried everything. We
also tried assigning a different owner and it still
complains about sa.

Any help on this would be greatly appreciated.

Rebecca

Have you done a complete DTS walkthrough? Check the login/pw's for all bulk
insert and connection tasks. Somewhere in your package the old login is
still being referenced.

"Rebecca" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Yes, we checked that. The strange thing is we can
execute the package successfully but we just can't run it
as a job.

In article <2d73e01c469ce$6363c980$a301280a (AT) phx (DOT) gbl>, Rebecca wrote:
There are two possible areas of problems

1. In the DTS packages themselves you specify sa as the account to use
to logon to servers which you have recently changed the password.

2. This is my best bet. Your SQL Server Agent job that fires the
package looks like this

DTSRun
/~Z0xBBA31C49DCFAC9543989D6EF45E60D7FA2BAF5465E090B 679CE824E75B2AF75B22
.........................


This contains the login information you need to connect to the sql
server to get at your package. Unfortunately you probably specified sa
as the logon info and the is now out of date.

You can generate a new string using

Start | Run | DTSRUNUI





Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs

Thanks Allan! That did it! Thanks so much for your help!
We had re-created the job but were copying over the same
DTSRun command.

Thanks again!