The problem is that the connections in my package are defined using Windows Integrated security. When the package tries to connect, I get a login error with the user identified as "NT Authority/Anonymous Logon".

I has assumed that the domain account that I am using to run Control-M would be passed to the package but this does not seem to be the case.

Using SQL Server authentication on my package connections does work, but I prefer to use Integrated security.

Use the "log as user" and in the job definition indicate a user that can connect to the target machine and still connect to the DB.
In the Ms sql server i have tried to use windows authentication but dont work. But in my case the DB was on a remote host, not on the machine were i have the agent installed.

To see the configuration for the "logon as user" settings see page 27-28 on the agent administration guide, and in windows remember to add "run batch jobs" to the user policy.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum