VERY new to VC, please be patient.

Recently we got a couple errors on one of our servers running VC v5.6.0. The "descriptive name" has been removed to protect the innocent. We have an ODBC connection setup for it that uses a domain username/password. We're not sure why its descriptive name showed up. The other is another error. Job failed both times.

First one happened on one day:


Error in task sql: ERROR [HY008][Microsoft] [ODBC SQL Server Driver][SQL Server]Login failed for user ‘descriptive name’.

Error [28000][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘descriptive name’.



Second one happened another day:

Error in task sql: ERROR [HY008][Microsoft] [ODBC SQL Server Driver] Operation canceled.

Maybe your SQL Job requires domain Credentials when logging in, not just in the connection string. Then you need to create and select a Credential.

---

Sorry forgot to mention that part, we do have it setup using domain credentials (system dsn).

It's also happened on another job.

I think I'm better understanding the problem, we have the domain user credentials we want to use for the job setup in it as well as the System DSN. We can test connection in both VC and the System DSN all day long, tests fine.

When this error happens, the error message is showing the display name of a different user. We don't know where/how the other user credentials are getting passed along.

How/why is this happening?

Did you try to create a Credential in VisualCron and select it in the Task? This way it will be passed along.

---

Yes.

Ok, to check if it is the right Credential, try this:

1. deselect the Credential and click OK
2. stop the VisualCron service
3. double click on VisualCronService.exe in the VisualCron folder
4. Connect and try to run the Task again

---

Sorry, once again did not understand what I was looking at. In the task itself, there is No Credential but the connection is using the ODBC System DSN we've setup.

It is already currently set not using Credential but is using the ODBC connection.

Followed instructions, task completed successfully.

Great, thanks for the update.

---

Sorry, meant the task you had given me was complete, not our scheduled task. I normally don't suck quite this much.

Have assigned Credentials to two problematic jobs, awaiting update from user to see if it helped/fixed it.

Ok, please keep us posted.

---