Just an update… our issue was related to how we were logging out of bot machines.
For reference, we have “Login To Console” set to “No” and our bot resolution set to 1920x1080 with a depth of 32 through orchestrator.
The problem was that developers and support staff were only disconnecting from the RDP sessions and not signing out of the machines. (We have specific bot user accounts that the team can access to monitor the bots if necessary). Since that bot account was being left signed in, the RDP session set the screen resolution and when orchestrator went to sign in, it was unable to apply the appropriate screen resolution. While I’m not 100% sure of why this was our issue, ever since we have started signing out instead of disconnecting from the bot machines, the exception related to Win32 has not occurred.
Hope some of this information helps!
Hope some of these details help so
ashokkarale
MD_Farhan1
Ajay_Mishra
postwick
Dheerendra_vishwakarma
Anil_G
chandreshsinh.jadeja
Gautham_Pattabiraman
vrdabberu
aravindbalineni123