Ali well are you trying to do a inventory with the if yes then the issue can be resolved in two ways 1) uncheck the EMPTY MEDIA ACCESS PORT. Option and run the inventory or 2) apply the 5.0 and 5.1 device_mappings.txt file from the following link once applied it will allow the inventory to carry on even in case an empty media access port is detected. If its something else please do try the below mentioned steps Document ID: 264891 E-Mail this document to a colleague GENERAL ERROR: Robotic control daemon will not start. ________________________________________ Details: Overview: Robotic control daemon will not start. Troubleshooting: Check the /usr/openv/volmgr/misc/ directory for any *lock* files. Log Files: N/A Resolution: The main reason the robotic control daemon will not start, is that the robot is unavailable.

Media Manager software is part of NetBackup which manages the. Cannot connect to robotic software daemon. A connection to a robotic software daemon. Driver Smart Office Keyboard Ez 7000 more.

Ensure that the robot is available and is configured with the correct device path. If the daemon will still not start, perform the following: 1. Shut down all the VERITAS NetBackup (tm) daemons: #/usr/openv/netbackup/bin/goodies/netbackup stop 2. Verify all NetBackup daemons are down by running the command: #/usr/openv/netbackup/bin/bpps -a Do not proceed until all NetBackup processes are down. (Remember to exit from the GUI interface.) 3. Cd to /usr/openv/volmgr/misc/ 4. Delete the lock files (*lock*) that exist in this directory 5.

Lectra System Modaris V6 Software Update. Restart the NetBackup daemons: #/usr/openv/netbackup/bin/goodies/netbackup start The robotic control daemon should now start. Ciao Ankur Kumar.