We are trying to change the credentials for running a task to a new user. For some reason, the task seems to pick up the old credentials instaed of the new one. We are running a few other tasks with the old credentials and hence we cannot remove that from the VC server.

We tried restarting the VC services also, to no avail.

Please advise

That sounds really strange. How do you *know* that it is using the wrong Credentials? And if you are sure you are using the right, are you able to create a new Job and Task and succeed?

---

It is actually a SQL server job on a different database server. When we connect thru SQL Server management studio to check the job logs, it says that the job used the particular credentials instaed of the new one.

The Credential is used to be able to use "Integrated security". Does your Job run successfully? I mean, is the problem that your Job does not run properly or that you see the wrong name in the log file of the SQL server? And what happens if you specify no Credential at all?

---

We tried deleting and recreating the job. Still the SQL job is being invoked by the domain user account instead of the service account. I am not sure why Visual Cron uses the user account instead of the service account. Please advise.

Yes, the job runs successfully. Since it is in production, I have limted permissions to test any time.

If it is being invoked by the domain user it is because you use the Credential. Unselect the Credential and it will execute from service SYSTEM account.

---