The robotic library device cannot be opened due to one of the following reasons:

• The robot device, path, or library name in the device configuration may not be valid.

• The configured robotic device may not exist.

• The robotic device may be incorrect, such as a UNIX and Linux device file that does not have a character special file format.

• The robotic daemon/process lock file cannot be opened or a lock obtained.

• The open operation on the device or through the API interface (such as NDMP) failed.

• Stop any robot test utilities that may be running, since they have the lock on the robotic device when they are active.

• Check the configuration of the robot against the recommended configuration as indicated in the robot configuration documentation.

• Check the health of the robotic device by using a robot test utility, then close the test utility when finished.

• Check for the existence and permissions of the lock file itself and the lock file directory, which is /usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) or install_path\Volmgr\misc\vmd.lock (Windows). Create the directory/folder and adjust the permissions as needed so that the robotic daemon/process can use the lock file. Stop and restart ltid (the device daemon on UNIX and Linux or the NetBackup Device Manager service on Windows).