Troubleshooting guide

Chapter 3, Using the Logs and Reports 73

Troubleshooting the Java Administration Interface

The following are the four kinds of error messages seen in the NetBackup Java

Administration interface.

◆ NetBackup status codes and messages as documented in Chapter 4.

Operations performed in the Java Administration interface can result in errors

recognized in other parts of NetBackup. These errors usually appear exactly as

documented in Chapter 4.

Note The error message is not always accompanied by a status code. You can find the

status code by looking up the message in the alphabetical listing at the end of

Chapter 4. Then use the status code to find the full description of the message in the

first half of Chapter 4.

◆ NetBackup Java Administration interface: application server status codes and

messages as documented in Chapter 4.

These messages have status codes in the 500 range. Messages with status codes 500,

501, 502, 503 and 504 begin with "Unable to login, status:". Messages with status codes

511 and 512 may or may not begin with “Unable to login, status:".

The message is not always accompanied by a status code (see the above note).

◆ Java exceptions

These are generated by either the Java APIs or by NetBackup Administration APIs.

These messages begin with the name of the exception. For example:

java.lang.ClassCastException

vrts.nbu.NBUCommandExecutionException

Java exceptions usually appear in one of three places:

◆ In the status line (bottom) of the NB Administration window

◆ In the log file generated by the jnbSA or jbpSA commands

◆ When set up, in the output file of the Windows Display Console .bat file (see

“Enabling Detailed Activity Logging” below, for more detail)

◆ Operating system errors

Messages that do not match those documented in this manual are probably operating

system errors.