If these are failing when run manually, then you need to
take a look at the connections in the SQL Server connection
property. If you specified to connect to the SQL Server
connection using sa, you need to change the password here.
If they work manually but are now failing as scheduled jobs,
when you schedule a DTS package using the Schedule Package
functionality of DTS and you have registered SQL Server in
Enterprise Manager using sa then sa and the password are
used in the encrypted command line generated for the dtsrun
command of the job. The same thing if using the dtsrunui
utility to generate an encrypted command for dtsrun and you
specify sa when using this tool. In this case, you need to
change the dtsrun commands for the jobs.
-Sue
On Fri, 14 Nov 2003 08:31:05 -0800, Lara31
<anonymous (AT) discussions (DOT) microsoft.com> wrote:
Quote:
i recently assigned a password to the sa account and noticed that all my dts packages stopped working . why is that and how do i fix the problem. i reset the sa login to null and the packages ran . HELP |