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


persi
  •  persi
  • Paid support Topic Starter
2016-03-10T16:47:08Z
Hi Everbody,

i would like to execute some jobs in the foreground.
This output appears after the execution:
PerformDesktopUnlock->Desktop Unlock/Logon failed in task: Ausführen, reason: Failed to connect to Credential Provider. Pipe result: 0

I erased the certifcates, but in two log-files the error "pipe busy" occurs:

Server_startup.txt
log_serverxxxxx.txt
  server_startup.txt (16kb) downloaded 44 time(s).  log_server20160310.txt (760kb) downloaded 44 time(s).




Thanks for your help...
Regards
Frank
Sponsor
Forum information
Support
2016-03-11T07:14:08Z
Have you rebooted the server since you made the changes?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
persi
  •  persi
  • Paid support Topic Starter
2016-03-11T08:24:12Z
Hi Henrik,

thank you for your fast answer.

I reboot the Server several time.

Support
2016-03-11T14:27:45Z
Please open the Server settings in VisualCron Client and verify that UAC is turned off there.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
persi
  •  persi
  • Paid support Topic Starter
2016-03-11T15:05:03Z
11.03.2016 15:54:32 Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx86.dll)
11.03.2016 15:54:32 Debug Credential provider->Credential provider registry test ok.
11.03.2016 15:54:32 Debug Credential provider->Credential provider connection test failed: Pipe busy (2)
11.03.2016 15:54:32 Debug Credential provider->Local Security Policy->Local Policies->Security options->Interactive logon: Do not require CTRL+ALT+DEL enabled - optimized for Credential provider support
11.03.2016 15:54:32 Info UAC enabled: False

The uac is disabled, the local policy is modified.
Support
2016-03-11T22:52:19Z
Originally Posted by: persi 

11.03.2016 15:54:32 Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx86.dll)
11.03.2016 15:54:32 Debug Credential provider->Credential provider registry test ok.
11.03.2016 15:54:32 Debug Credential provider->Credential provider connection test failed: Pipe busy (2)
11.03.2016 15:54:32 Debug Credential provider->Local Security Policy->Local Policies->Security options->Interactive logon: Do not require CTRL+ALT+DEL enabled - optimized for Credential provider support
11.03.2016 15:54:32 Info UAC enabled: False

The uac is disabled, the local policy is modified.



Is your system really 32 bit?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
persi
  •  persi
  • Paid support Topic Starter
2016-03-14T08:14:43Z
No it is 64 bit 2008 R2 SP1.
It is possible to change the dll-reference?
Support
2016-03-14T10:11:04Z
Originally Posted by: persi 

No it is 64 bit 2008 R2 SP1.
It is possible to change the dll-reference?



You could delete the file, copy the x64 file and rename it to that file name and reboot.

But I have no idea how this happened - VisualCron is determining the file to install based on the architecture of the server.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
persi
  •  persi
  • Paid support Topic Starter
2016-03-14T11:06:45Z
The file server_startup.txt looks good (no "pipe busy"):
14.03.2016 11:32:13 Info Credential provider->Credential provider was already installed (C:\Program Files (x86)\VisualCron\InteractiveLogonCPx86.dll)
14.03.2016 11:32:13 Debug Credential provider->Credential provider registry test ok.
14.03.2016 11:32:13 Debug Credential provider->Credential provider connection test ok.
14.03.2016 11:32:13 Debug Credential provider->Local Security Policy->Local Policies->Security options->Interactive logon: Do not require CTRL+ALT+DEL enabled - optimized for Credential provider support
14.03.2016 11:32:13 Info UAC enabled: False

But runnung the job by right mouse-click and Job start with options the result is:
PerformDesktopUnlock->Desktop Unlock/Logon failed in task: Ausführen, reason: Failed to connect to Credential Provider. Pipe result: 0

Attached the Foreground execution settings:

visualcron foreground execution.jpg
persi
  •  persi
  • Paid support Topic Starter
2016-03-14T12:50:39Z
Hi Henrik,

i read the log_Server-Log file and thinking about the user, who is active in session.

14.03.2016 13:40:01 Debug Interactive logon: Session id: 0, username: , state: WTSDisconnected
14.03.2016 13:40:01 Debug Interactive logon: Session id: 1, username: automat, state: WTSActive
14.03.2016 13:40:01 Debug Interactive logon: Session id: 3, username: , state: WTSConnected
14.03.2016 13:40:01 Debug Interactive logon: Session id: 65536, username: , state: WTSListen
14.03.2016 13:40:01 Debug Interactive logon: Sessions dump ended.
14.03.2016 13:40:01 Debug Interactive logon: Active Console Session id = 3
14.03.2016 13:40:01 Debug Interactive logon: Active User Name =
14.03.2016 13:40:01 Debug Interactive logon: IsWorkstationLocked->Checking if workstation is locked
14.03.2016 13:40:01 Debug Interactive logon: EstablishConnection->Create file - retry: 0
14.03.2016 13:40:01 Debug Interactive logon: EstablishConnection->Invalid value (-1)
14.03.2016 13:40:01 Debug Interactive logon: EstablishConnection->Pipe busy - waiting for 10 seconds
14.03.2016 13:40:01 Debug Interactive logon: EstablishConnection->Wait named pipe failed - try EstablishConnection again
14.03.2016 13:40:03 Debug Interactive logon: EstablishConnection->Create file - retry: 1
14.03.2016 13:40:03 Debug Interactive logon: EstablishConnection->Invalid value (-1)
14.03.2016 13:40:03 Debug Interactive logon: EstablishConnection->Pipe busy - waiting for 10 seconds
14.03.2016 13:40:03 Debug Interactive logon: EstablishConnection->Wait named pipe failed - try EstablishConnection again

I logon via RDP with the local user "automat" and the job also use this user, can this be the reason for the "busy"-error?

thanks
Support
2016-03-14T15:40:14Z
Did you delete,copy rename and reboot as I described?

The reason while you get Pipe error is cannot communicate with the dll. Most probably because the wrong dll is set now. You need to perform the steps.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
persi
  •  persi
  • Paid support Topic Starter
2016-03-14T15:49:56Z
Yes, i did these steps.
Now the files look like this: dlls.jpg

As you can see the filesize of both x86 and x64 file are the same, because both are the x64 file.
Support
2016-03-23T13:29:33Z
Scroll to Top