Troubleshooting guide

Status Codes
180 NetBackup Troubleshooting Guide - UNIX
3. Restart the NetBackup-Java interface and examine the logs.
Note The error is probably the result of a system resource issue. When detailed activity
logging has been enabled, the details may be retrieved from the bpjava-msvc or
bpjava-usvc log files.
Status Code: 512
Message: Internal error - a bad status packet was returned by NB-Java application server
that did not contain an exit status code.
Explanation: The NetBackup-Java authentication or user service returned a data packet
indicating an error, but no status code or error message was contained within it.
Recommended Action:
1. If the problem persists, restart the NetBackup-Java interface and try again.
2. If the problem still persists, enable detailed activity logging as explained under
“Enabling Detailed Activity Logging” on page 74.
3. Restart the NetBackup-Java interface and examine the logs.
Note The error is probably the result of a system resource issue. When detailed activity
logging has been enabled, the details may be retrieved from the bpjava-msvc or
bpjava-usvc log files.
Status Code: 513
Message: bpjava-msvc: the client is not compatible with this server version
(server_version).
Explanation: The NetBackup-Java application server (on the remote host you are logging
in to) is not the same version as the NetBackup-Java interface on your local host. The two
are therefore incompatible.
Recommended Action:
◆ Log in to a different NetBackup remote host.
◆ Upgrade the NetBackup software on either the machine specified in the login dialog
or on the local host where you started the NetBackup Java interface.