15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Chapter 5, Media Manager Status Codes and Messages 363<br />

Status Codes<br />

Recommended Action: Examine the system log <strong>for</strong> a more detailed message on the error.<br />

Increase the level of verbosity by adding the VERBOSE option in the vm.conf file. Restart<br />

the device daemon ltid (UNIX) or <strong>NetBackup</strong> Device Manager service (<strong>Windows</strong>), then<br />

retry the operation and examine the system log file.<br />

Robot Error Status Code: 12<br />

Message: Usage error in creating child process<br />

Explanation: A robotic daemon/process could not create a child process due to an<br />

incompatibility between robotic software components.<br />

Recommended Action:<br />

1. Examine system logs <strong>for</strong> a more detailed message on the error.<br />

a. Increase the level of verbosity by adding the VERBOSE option in the vm.conf<br />

file. Restart the ltid device daemon (UNIX) or <strong>NetBackup</strong> Device Manager<br />

service.<br />

b. Retry the operation and examine the system log file.<br />

2. Verify that all Media Manager binaries are at a compatible version level.<br />

Robot Error Status Code: 14<br />

Message: You must be administrator to execute<br />

Explanation: A robotic process was started under a user account that was lacking<br />

Administrator privileges. This applies to <strong>Windows</strong> systems only.<br />

Recommended Action: Allow robotic daemons to be started automatically as needed by<br />

the <strong>NetBackup</strong> Device Manager service. Ensure that this service is being started from a<br />

user account with administrator privilege.<br />

Robot Error Status Code: 16<br />

Message: Devices located in multiple domains<br />

Explanation: A robotic daemon/process encountered an invalid device configuration, in<br />

which drives from different domains were configured to be controlled by a single logical<br />

robot.<br />

Recommended Action: Display the device configuration using tpconfig -d or a device<br />

configuration interface to see the robotic and drive in<strong>for</strong>mation that is already configured.<br />

Ensure that the drive addresses do not span physical domains. Drives can only be<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!