ネットワークのトラブルシューティング

Unattended ロボットがマッピングされたドライブを見つけられない

説明

Occassionally, robots cannot find a mapped network drive when running an unattended automation.

潜在的な問題

This can happen due to the non-interactive nature of the Windows logon session.

解決策

To prevent this, map the network drive in the headless mode. This can be done by remapping the drive for every job the robot starts. The remapping also applies when the machine is restarted.

In the unattended automation workflow, explicitly run the net use Z: \\unc\path command before accessing the shared drive.

アセンブリをネットワークまたは Azure ファイル共有から読み込めない

説明

Trying to run a package from a network path or an Azure File Share fails with the "System.Xaml.XamlObjectWriterException: Cannot create unknown type [....]" error.

The robot logs the following error message: "System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework."

潜在的な問題

The Robot machine might not trust the web address for the Azure File Share, where the package is located. Alternatively, the account the robot uses might lack permissions for that specific location.

解決策

Make sure that the account under which the robot runs has the necessary permissions. Then, add the Azure File Share web address as a trusted network on the robot machine.

RDP を介してロボットが応答しない

説明

The Robot machine becomes unresponsive and shows high CPU usage at some point after starting the automation. It occurs on Windows 10 v1903 machines.

潜在的な問題

This is a Microsoft known issue on Windows 10 v1903 which affects the runtime of the DWM.exe file, leading to high CPU usage upon completion of a Remote Desktop session.