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


Jeff Hilb
2016-03-22T17:15:25Z
We are running VC8 in trial mode (in preparation for migration of VC6 to VC8).
Set proper security policy on server. Server has been rebooted.
Still receiving error "PerformDesktopUnlock->Desktop Unlock/Logon failed in task: Execute, reason: Failed to connect to Credential Provider. Pipe result: 0
Exception in Task: Could not find the specified Connection for Foreground execution." when task runs.
Task is set up for Foreground execution on a specified desktop session, with use any session option on.
Same task setup as the machine running VC6.
Sponsor
Forum information
Support
2016-03-22T17:31:45Z
I assume this is a new machine?

Please attach server_startup.txt

Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-03-22T17:40:36Z
Correct, new machine. Win Server 2012 R2.
Checked that UAC was turned off, rebooted.
Attached. I am getting two server_startups. One in Program Files and the other in Program Files (x86).
Jeff Hilb
2016-03-22T17:52:53Z
😛 32423(2016-02-22 11:00:48) - protocol: 7.6.5
Support
2016-03-23T13:28:59Z
Jeff Hilb
2016-03-24T23:09:52Z
Still unable to connect to credential provider after applying 8.0.5 beta
Support
2016-03-25T08:38:58Z
Seems like you got an older build. Please follow these steps:

1. re-download
2. re-install
3. reboot computer
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-03-28T18:27:35Z
Still not working. 8.0.5 right? That is what the log says.
Do I need to FULLY uninstall the first install then re-install the beta 8.0.5 ?
Support
2016-03-28T19:25:01Z
Uninstall should not be needed. This is done everytime you install new version. Reboot is most important. Please send server_startup.txt along with log_serverDATE.txt. Send us the Job name as well so we can see it in action. Make sure you have Extended debug checked in Server settings before Task is scheduled.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-03-28T19:55:57Z
I did a full uninstall/reinstall but getting same results.

It's only the tasks set to run in the foreground that are the issue.

Will post logs asap
Jeff Hilb
2016-03-28T20:29:52Z
If running task in foreground and session is not locked, might that be the issue? I am thinking the setup is not correct although it's an exact port from V6 and I see busy errors in the serverstartup.
Support
2016-03-28T21:27:56Z
Originally Posted by: Jeff Hilb 

If running task in foreground and session is not locked, might that be the issue? I am thinking the setup is not correct although it's an exact port from V6 and I see busy errors in the serverstartup.

  server_startup_03282016.txt (3kb) downloaded 57 time(s).  log_server20160328.txt (104kb) downloaded 56 time(s).



I am not sure. The logs that you sent does not seem complete. Have you really checked "Extended debugging" before running? I am looking for the files:

server_startup.txt
log_serverDATE.txt

Both these should be in x86 folder - other folder not interesting.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-03-28T21:45:29Z
server_startup_03282016.txt is server_startup.txt

logserver20160328.txt is the logserverDATE.txt file

yes, extended debugging is on

should be the files you are looking for.

server still seems to be getting pipe busy error...

3/28/2016 1:48:53 PM Debug Output folder: C:\ProgramData\VisualCron\output
3/28/2016 1:48:53 PM Debug Startup function called
3/28/2016 1:48:53 PM Info Credential provider->OS version: WindowsServer2012Standard (x64)
3/28/2016 1:48:53 PM Info Credential provider->Prepare interaction
3/28/2016 1:48:53 PM Info Credential provider->Is Vista or higher: True
3/28/2016 1:48:53 PM Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx64.dll)
3/28/2016 1:48:53 PM Debug Credential provider->Credential provider registry test ok.
3/28/2016 1:48:53 PM Debug Credential provider->Credential provider connection test failed: Pipe busy (2)
3/28/2016 1:48:53 PM Debug Credential provider->Local Security Policy->Local Policies->Security options->Interactive logon: Do not require CTRL+ALT+DEL enabled - optimized for Credential provider support
3/28/2016 1:48:53 PM Info UAC enabled: False
3/28/2016 1:48:53 PM
Support
2016-03-28T22:00:11Z
Originally Posted by: Jeff Hilb 

server_startup_03282016.txt is server_startup.txt

logserver20160328.txt is the logserverDATE.txt file

yes, extended debugging is on

should be the files you are looking for.

server still seems to be getting pipe busy error...

3/28/2016 1:48:53 PM Debug Output folder: C:\ProgramData\VisualCron\output
3/28/2016 1:48:53 PM Debug Startup function called
3/28/2016 1:48:53 PM Info Credential provider->OS version: WindowsServer2012Standard (x64)
3/28/2016 1:48:53 PM Info Credential provider->Prepare interaction
3/28/2016 1:48:53 PM Info Credential provider->Is Vista or higher: True
3/28/2016 1:48:53 PM Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx64.dll)
3/28/2016 1:48:53 PM Debug Credential provider->Credential provider registry test ok.
3/28/2016 1:48:53 PM Debug Credential provider->Credential provider connection test failed: Pipe busy (2)
3/28/2016 1:48:53 PM Debug Credential provider->Local Security Policy->Local Policies->Security options->Interactive logon: Do not require CTRL+ALT+DEL enabled - optimized for Credential provider support
3/28/2016 1:48:53 PM Info UAC enabled: False
3/28/2016 1:48:53 PM



Is reboot taking less than 50 seconds?

Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-03-29T20:46:09Z
Jeff Hilb
2016-03-29T20:53:38Z
Tried starting the VC service delayed.

3/29/2016 3:50:13 PM Debug Startup function called
3/29/2016 3:50:13 PM Info Credential provider->OS version: WindowsServer2012Standard (x64)
3/29/2016 3:50:13 PM Info Credential provider->Prepare interaction
3/29/2016 3:50:13 PM Info Credential provider->Is Vista or higher: True
3/29/2016 3:50:13 PM Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx64.dll)
3/29/2016 3:50:13 PM Debug Credential provider->Credential provider registry test ok.
3/29/2016 3:50:13 PM Debug Credential provider->Credential provider connection test failed: Pipe busy (2)

Jeff Hilb
Support
2016-03-31T22:13:31Z
Thanks for the information. We are still doing some more tests and hope to add more debugging soon.

Meanwhile, could you explain your need for Foreground execution - maybe we can work around it?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2016-04-01T07:24:03Z
Please test this latest and reboot:

http://www.visualcron.co....aspx?g=posts&t=6564 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-04-01T14:47:00Z
Foreground execution was a carry over from our VC6 jobs where we needed to see some jobs running for testing purposes.
It does appear when we set to background they work, except they are all (200+) set to foreground currently.
Will try new version posted.
Jeff Hilb
2016-04-01T15:29:29Z
That post points to 8.0.5 which has already been tried (see above).

Support
2016-04-01T15:50:34Z
Originally Posted by: Jeff Hilb 

That post points to 8.0.5 which has already been tried (see above).



We do daily builds almost with changes, especially to this behaviour. Please download and re-install.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Jeff Hilb
2016-04-01T17:48:53Z
Jeff Hilb
2016-04-01T18:13:18Z
The good news is that I am not getting the pipe busy in the server startup log any longer.
Bad news is the job is still failing to connect to the credential provider.



bbusse
2016-04-01T18:57:59Z
Can you confirm the VisualCron Service (Services MMC) is set to 'Allow Service to interact with desktop' if 'Local System Account' is selected (Log On tab).

I feel like I remember seeing something like this previously when the default install changed that option when upgraded and then was subsequently changed back in future releases. We always use a service account instead of Local System Account so i don't recall what the default is on a fresh 8.0.4/5 install and don't have another system to try that on at the moment.

Brian
Scroll to Top