Haven’t seen the specific error you mention from UiPath, but had a similar scenario where the login would get up to a certain point and greeted with an error
We can’t sign into your account, This problem can often be fixed by signing out of your account and then signing back in. If you don’t sign out now, any files you create or changes you make will be lost.
This was observed after configuring RDS and setting up for “High-Density Mode” on a particular host.
We didn’t get to a point of testing a run with a Robot before fixing the issue, so can’t confirm if it was the same underlining issue. Our resolution was similar of in that we had to remove the corrupt profile by removing the User data along with removing the profile from the
ProfileList in the Registry before the profile would be recreated upon the initial login.
Quick update… I am in the process of setting up some new infrastructure the biggest difference from the old setup is Orchestrator and Robots are moving from Windows Server 2016 to Windows Server 2019.
Robot Hosts are configured with RDS / High Density and I’ve published a very simple process to test with. The process simply detects the screen resolution and takes a full screen screenshot and saves it to disk. This process works fine on my local machine and in the old infrastructure robots.
Upon running in the new environment (default Robot Settings logging into Console)
I started seeing the following errors in Windows Logs
Job ScreenDetection-Test/7ca93f06-abe5-4b44-93c4-8e0b57a850f9 with status Processing changed to Error: Object reference not set to an instance of an object.
Windows Search Service has created default configuration for new user 'domain\user' .
Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on.
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.
I deleted the Profile Files and Registry Keys and was not seeing the same errors above but was still getting the
Object reference not set to an instance of an object
Adjusting the robot settings to Console:False and 1600 x 900 I am getting your original errors and removing the profile is not correcting it.
SetResolution: Error updating screen resolution: -1
SetResolution: Error updating screen resolution: -2
Last update… Both the errors
Object reference not set to an instance of an object. and
SetResolution: Error updating screen resolution: -1 was occurring due to the Project I was testing with being set as a Background process upon setting that to No/False it ran as expected.