Troubleshooting guide

Chapter 4, Status Codes and Messages 179
Status Codes
◆ A job (started by either the NetBackup-Java authentication service or user service)
cannot be monitored by the NetBackup-Java service. This is probably due to a lack of
system resources (insufficient memory).
◆ The maximum number of non-transient activity monitor jobs (>100) have already
been started.
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: 510
Message: File already exists: file_name
Explanation: The NetBackup-Java user service has attempted to create a file that already
exists.
Recommended Action: Remove the file, which can be identified in the user service log
files. Refer to “Troubleshooting the Java Administration Interface” on page 72.
Status Code: 511
Message: NB-Java application server interface error: Java exception
Explanation: This is a generic error for all non-socket IO/connection-broken related errors
(status code 507) that could occur when processing the data from the NetBackup-Java
authentication or user services. The Java exception will provide some additional detail
about the error.
This error usually results from system or network problems.
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.