Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


<tuffty/>
2013-04-26T15:29:18Z
Hi

I am using Visual Cron to run Macro Scheduler to do some automation on our ERP system... all runs fine for days then I get the following error...

Std Err: Desktop Unlock/Logon failed in task: <task name>, reason: Failed to connect to Credential Provider Exception in Task: Could not find the specified Connection for Foreground execution.

I am using an 'Execute' task to fire up Macro Scheduler and its relevant macro file...

I am using foreground execution (as its a macro so needs to interact with the desktop) and the credentials of the user should be fine as it does actually run having logged out of the machine (Windows Server 2008 R2 x64)

I have set this to execute on any desktop session (did set it to an explicit one but thought this was the cause of the issue)... there are 8 tasks all doing a simialr thing that run in the same job after each other... normally when it fails it will do so on the first task in the list then carry on fine for the rest... today it did this for the first two tasks then carried on..

Visual Cron server is running under a domain account and has local admin rights...

If it was failing every time it might be easier to diagnose but as it is I can't see a pattern here...

Any help would be appreciated :)

<tuffty/>
Sponsor
Forum information
Support
2013-04-27T19:50:31Z
Maybe you have to "narrow" settings on the Foreground Task. For example, you may have bound foreground execution to a specific session - try Any session setting.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
<tuffty/>
2013-04-29T06:54:48Z
Originally Posted by: Support 

Maybe you have to "narrow" settings on the Foreground Task. For example, you may have bound foreground execution to a specific session - try Any session setting.



Its already set to execute on any desktop session as I explained in my initial post... Like I said before it will run fine for a few days then randomly throw this error... not always on the same day and I have checked windows logs to see if anything else was running or there was anything recorded as an error and there is nothing

<tuffty/>
Support
2013-04-29T09:54:46Z
Turn on extended debugging while you do this. It will log more details about what went wrong.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
<tuffty/>
2013-04-29T09:59:13Z
Thanks, I'll keep an eye on that over the coming week

<tuffty/>
Scroll to Top