Hi,

I'm evaluating VisualCron for use on some servers at work, and I'm getting the "Failed to connect to Credential Provider" error when scheduling a job that needs to run in user space. I have enabled the "Do Not Require Ctrl+Alt+Delete" setting, as per http://www.visualcron.co...ml?interactive_logon.htm , but no love.

Here are the specifics:
Task Output:
Desktop Unlock/Logon failed in task: Execute, reason: Failed to connect to Credential Provider

Task runs fine during test (simple open of a database).

Execution Context:
Local VisualCron Server
Foreground Session
Execute on any desktop session
Logon/Unlock using Credential - My credentials set up (Local Login, Use User Profile)
After Execution: Do Nothing

Thanks,
Des

Have you rebooted the server since the VisualCron installation?

---

By the way, is it not enough to run the Executable with a Credential (Local logon + Load profile)?

---

Hi,

Of course I didn't try restarting the server, since it was the most obvious thing to do. :)

And it did fix the problem! Thank you!

I'm not sure what you mean by your second comment though.

Thanks,
Des

Great that it was resolved. I was just wondering about the need for running it in the foreground instead of just using the Execute Task with Credential instead?

---

Well, I sometimes like to have visual confirmation that something has run overnight when I get in in the morning, especially when there's insufficient logging. In this case, the test automates a process in an Access database which is set up to allow the user to prevent execution in the first 60 seconds. I think the point of having it in the foreground is primarily to make it easy to test that the parameters are correct, so we can see it run when we press the test button.

Oh, there's one other - if something fails, like a database login, and the process stops, waiting for credentials, it's nice to have the windows visible so that we can see what's going on and maybe even correct it so the job can complete. For overnight batches, I actually prefer to have these things run in the foreground just for that reason.

Ok, thanks for the explanation. We generally do not recommend foreground execution as you add more "layers" which could end up in more "error prone" Tasks.

---