Surface Automation failing on remote machine

[SamThornton]

Hi everyone, Within my process there is an object that uses surface automation to read a list of text. Within the dev environment it works absolutely fine at both process and control room speed. In the prod environment, it performs fine from a process and control room level if I am logged in to the machine locally. The issue I face is when I run the process from control room on a remote virtual machine (the same prod environment I ran in locally from), it cannot read the text (returns blanks or commas). I have attempted the following without success: €¢ Checked screen brightness and power saving options on the virtual machine €¢ Logged into the virtual machine and run locally at control room (works fine) €¢ Set move and resize logic to ensure the application is on the screen €¢ Double and triple checked data items to ensure font is installed and colour is correct. Can you please recommend any other fixes or courses of action to at least find out what the problem is? As at this point I have no idea why it is even failing, let alone how to fix it.

[JuhoLindblad]

Hi Sam, Are the Windows font smoothing disabled from both production and dev Runtime Resources? How do you perform the login for the VM when you are running the process over debugger? If you are using RDP connection, you are passing settings from your own local device such as the screen resolution and the font smoothing when creating the session. This might be the reason why the surface automation is working normally with RDP connection. When scheduled with Login Agent, the VM is using it's own settings which may differ from your dev environment. I would validate the production VM settings over VNC, Bomgar or other tool which you can use for monitoring the local VM session. Hope this helps, Juho