€‹We see the following error quite often, when trying to login in to our virtual machines using the BP Login Agent:
"ERROR: Internal : Could not execute code stage because exception thrown by code stage: Named pipe handle is invalid"
Inspecting the code of the Login Agent BO, it is clear that the problems is related to access the named pipe "BluePrismCredentialProviderPipe"
Can anyone explain why this happens? I suspect that it might have something to do with the persmission level of the system user running the Login Agent (it needs access to the named pipe). But I might be off track here.
We are calling the LogOn action in the Login Agent BO with the correct parameters. We know this, because it does log on to some machines almost without problems.
An important point is that our machines run on Microsoft VDI(as far as I know), which is not recommended, but it does work quite well, as long as we have a continous RDP connection, and our IT-department is less than flexible about the choice of VM technology. However, when this error occurs we have made sure that the machine is freshly rebooted, and that no RDP connection has been established at any time since boot.
Any input is much appreciated.
