www.gsx.com | log in | register

Last update: . Author: Christian Stokes .

Exchange User Experience - Robot User Status - Could Not Load File or Assembly

Robot user experience tests can fail if there are missing prerequisites on the robot station performing the tests. When the failure details state it could not load a file or assembly, it is due to an incorrect version of PowerShell running on the robot station not meeting the necessary prerequisites.

Follow this article to resolve the file or assembly load issue by adding the missing prerequisite on the robot station.

GSX Gizmo Amsterdam+ | PowerShell

Symptoms

  • Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
  • Network Status is Down
  • Unable to resolve outlook.office365.com
  • Failed to connect to www.google.com on port 443

How to Solve the Issue

First, we will verify that the version of Windows PowerShell currently installed on the robot station needs to be updated. Next, we will upgrade PowerShell to at least version 4.0. Lastly, we will set the PowerShell execution policy to at least RemoteSigned.

Verifying the PowerShell version:

  1. On the robot station, click the Start menu and type PowerShell.
  2. Right-click PowerShell and select run as administrator.
  3. From PowerShell, run the following command and press enter:
    $PSVersionTable.PSVersion
  4. If the PowerShell version returns with less then 4.0, upgrade PowerShell.

Upgrading PowerShell:

  1. Download the Windows Management Framework 4.0 for your corresponding processor version below:
  2. Run the downloaded installer.

Reapplying the execution policy from PowerShell (x86):

  1. Click Start and type PowerShell.
  2. From the results list, right-click on Windows PowerShell (x86) and select run as administrator.
  3. From PowerShell (x86), type the following command and press enter:
    Set-ExecutionPolicy RemoteSigned
  4. Type y and press enter.
  5. Restart the robot station.

The Exchange user experience robot scans will now be successful.

 


Was this article helpful?

0 out of 0 found this helpful




Not finding what you are looking for?

Have more questions? Submit a request