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.

Messages<br />

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

client did not start<br />

(<strong>NetBackup</strong> Status Code 49)<br />

client hostname could not be found<br />

(<strong>NetBackup</strong> Status Code 48)<br />

client is not validated to per<strong>for</strong>m the requested operation<br />

(<strong>NetBackup</strong> Status Code 135)<br />

client is not validated to use the server<br />

(<strong>NetBackup</strong> Status Code 131)<br />

client name mismatch<br />

(<strong>NetBackup</strong> Status Code 39)<br />

client process aborted<br />

(<strong>NetBackup</strong> Status Code 50)<br />

client timed out waiting <strong>for</strong> bpend_notify to complete<br />

(<strong>NetBackup</strong> Status Code 75)<br />

client timed out waiting <strong>for</strong> bpstart_notify to complete<br />

(<strong>NetBackup</strong> Status Code 74)<br />

client timed out waiting <strong>for</strong> the continue message from the media manager<br />

(<strong>NetBackup</strong> Status Code 65)<br />

client timed out waiting <strong>for</strong> the file list<br />

(<strong>NetBackup</strong> Status Code 68)<br />

client’s network is unreachable<br />

(<strong>NetBackup</strong> Status Code 56)<br />

178 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<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!