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