Examine the command output (if available) and the daemon and reqlib debug logs for a more detailed message on the error.

See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference Guide.

Identify the targeted robotic process: look at the robot type and at the robot host on the robotic request or the robot host field of the volume being operated on. Verify that the robotic process to use for robotic control is available and that it handles requests.

See "Media and device management components" in the NetBackup Logging Reference Guide.

Identify the robot control host by checking the device configuration. Only one configured robot control host should exist for each TL8, TLD, and TLH robot. All volumes in the volume configuration should have a robot host that matches the configured robot control host.

Check the system log on the robot control host to see if the robotic process handles requests when communications with it are attempted.

See "Resolving network communication problems with UNIX clients" in the NetBackup Troubleshooting Guide.

See "Resolving network communication problems with PC clients" in the NetBackup Troubleshooting Guide.