We are in the process of upgrading from V5.5 to V6.2.2 and was testing a Job with a execute task.
Looks like the "run as credentials" options is not working as expected in V6.2.2.

My execute task runs an exe, which calls a DB with integratedsecurity. But when this tries to execute, it runs it as User: NT AUTHORITY\SYSTEM
And errors :
Error: Cannot open database "<DBNAME>" requested by the login. The login failed.
Login failed for user '<domainname>\<Machinename>$'.

I am trying to execute this using a local profile\user credential.
Mak

Try checking "Local login" and "Load user profile" in the Credential.

---

Sorry I should have mentioned that before. I have done that but its same issue.
Let me explain what I have tried so far.
My task tries to call an exe under ProgramFiles, which in turn calls DB.
When i try to run it as "Execute" task to run under certain credetials it fails with the error I have intially mentioned.
So tried creating a vbs script to call the exe, and if I run it as "Execute" task it fails with same error, but if I run it as "Execute script" task , it uses the right credentials.
This sort of gets me thinking that the "Execute" task isnt applying the credetials correctly and this might be a bug.

It might be some configuration error. I can confirm that the Execute Task and Credentials work - it is the most widely used Task. What you can check in the Task manager - which user a process is running as.

Basically we use almost the same approach. Only thing that is important that you have:

1. selected a Credential
2. that you are running with a user with Local login and Load profile

You can also test that the actual Credential works in the Credential window.

---