When you schedule the package through the scheduling
functionality of DTS packages themselves in Enterprise
Manager, an encrypted dtsrun command line string is created
for the job step. This command will use the login you used
to register SQL Server in Enterprise Manager.
You can generate a new dtsrun command with using the
dtsrunui utility.From the advanced button on the dtsrunui
utility, there is an option to generate a command line.
Or you will need to manually create the dtsrun run command
line for the job. You can find the parameters needed for
dtsrun in books online.
If you use Windows Authentication for the dtsrun command,
you won't have to deal with changing the job when passwords
change.
-Sue
On Thu, 5 Oct 2006 12:19:01 -0700, Pedja
[quoted text, click to view] <Pedja@discussions.microsoft.com> wrote:
>Hi,
>We have sql server 2000 with sp3. I developed DTS package which contains one
>connection object. It is defined to use user account which appropriate
>permission in the database. However, when I saved and scheduled the package,
>this server was registered in my enterprise manager with 'sa' account. 'sa'
>account is not being used at all in the package itself.
>
>However here is the problem: each month we change 'sa' password according to
>some security standards. When we changed it last month, job started failing
>with "login failed" error message. I double checked, there is no 'sa' account
>defined in the package (there is only one connection, and it uses different
>account). So I had to register this server under my domain account, open the
>package again, and save it and schedule it again. After we changed 'sa'
>password at the beginning of October, IT FAILED AGAIN with the same error
>message!
>
>Obviously, account which is being used first time when creating DTS package,
>stays inside the package and it is not easy to change it.
>
>Does anybody have an idea how to fix this?
>Thanks
