NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
successful creation of and connection to the NetBackup-Java user service, all other child
processes are created by the NetBackup-Java user service on behalf of requests made by
the NetBackup-Java interface.
Note The cause of status code 509 can be found in the appropriate log file, either for
bpjava-msvc or bpjava-usvc. The cause can be categorized as one of the
following:
◆ A job (started by either the NetBackup-Java authentication service or user service) no
longer exists, and did not report its result status.
◆ 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 debug logging as explained under
“Enabling Detailed Debug Logging” in Chapter 3.
3. Restart the NetBackup-Java interface and examine the logs.
Note The error is probably the result of a system resource issue. When detailed debug
logging has been enabled, the details may be retrieved from the bpjava-msvc or
bpjava-usvc log files.
NetBackup 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 Administration Console” on page 51.
NetBackup Status Code: 511
Message: NB-Java application server interface error: Java exception
170 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows