Hi, I have created a SSIS package. The connection used in the SSIS is SQL
Authenticated. This runs perfectly when executed even after it is deployed.
However, I face problems when I want to execute this package as a job. The
error I get is - "Login failed for user - <user name>".

While creating a step as part of the job, if i select the "Package Soruce"
as "SSIS Package Soruce", then the SQL Authentication option is disabled. I
am forced to use Windows Authentication.

However, I have noticed that if I use Windows Authentication through out,
i.e. when i create the connection within SSIS Package, while deploying the
SSIS package and while creating the step in the Job, all goes fine.
Unfortunately, this is not what i want. All the connections should be SQL
Authenticated as against Windows Authentication.

Please help! Thanks!
Manjunath Basrur

Manjunath,

Try running the package with CmdExec with dtexec. Search Books on Line
for "dtexec" to get the full description of all options. For example,
there are options to use SQL Authentication and set the username and
password to run the package.

Bill E.
Hollywood, FL

Thanks Bill! Appreciate it. However, I do not have a problem running the
package by itself with SQL Authentication. I get the problem the moment I put
the package as part of a job. If I have used Windows Authentocation in the
connection manager for the data flow tasks within the SSIS package, and then
put this in a job, all goes well. Hope i have explained my problem clearly.
Please do let me know if there is anything else I need to do which I am
overlooking. I will look for more material as suggested by you. In the
meantime, if you get anything, please let me know. Thanks once again.

Manjunath Basrur

"billmiami2 (AT) netscape (DOT) net" wrote: