NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

in-depth Troubleshooting Guide for Exit Status Code 50

Check /etc/syslog.conf file for location of *.debug and *. error log file. If it is commented out (if there is a # in front of *.debug and *.error), then syslog is not recording errors at the OS level.
TECH43182 | 2013-10-17
Technical Solutions | CMS-XML

Fixing indexing jobs that fail with status code 50 (client process aborted) when NBAC is enabled

Indexing jobs may fail with status code 50 (client process aborted) if NetBackup Access Control (NBAC) is enabled. Follow this procedure to fix the error .
HOWTO85206 | 2013-09-27
How To | CMS-XML

BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported

write_backup: unable to read bpduplicate message, network read error (h_errno = 10054)
TECH56753 | 2010-09-07
Technical Solutions | CMS-XML

in-depth Troubleshooting Guide for Exit Status Code 50 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1

50
TECH42465 | 2006-01-01
Technical Solutions | CMS-XML

Device management status code 50

Device management status code 50
HOWTO104676 | 2014-11-20
How To | CMS-XML

Media Manager status code 50

An invalid request to change volume information was sent to vmd on the EMM server. Examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide
HOWTO104431 | 2014-11-20
How To | CMS-XML

NetBackup status code: 50

An administrator uses an os-provided command line (for example, the kill command) to kill an active process. The job status does not reflect the change until one hour later, when the status changes to DONE and this status code is generated.
HOWTO103980 | 2014-11-20
How To | CMS-XML

STATUS CODE: 50 - Unable to label the new media in NetBackup (tm) 7.x

STATUS CODE : 50 - Unable to label the new media in NetBackup (tm) 7.x
TECH196071 | 2014-06-20
Technical Solutions | CMS-XML

Backup jobs fail with status 50 and NBJM core dumps with stacks referencing various memory related routines.

Backup jobs fail with status 50 and NBJM core dumps with stacks referencing various memory related routines.
TECH191206 | 2014-01-20
Technical Solutions | CMS-XML

Activity monitor reports status "50" for Image Cleanup when bpjobd has not received an update for 60 minutes. Image Cleanup job continues to run.

NOTE: There are no errors in the bpdbm log
TECH197519 | 2013-11-22
Technical Solutions | CMS-XML

Import phase1 or phase2 fails with a status code 50 (client process aborted)

The Status Code 50 error is generated when the user who is logged in to the VERITAS NetBackup (tm) server and has initiated the import logs off the server prior to the import completing. NOTE: The import will complete. The Status Code 50 failure is only a file write failure to the import log.
TECH28499 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Large SAP backups exit with status 50

GENERAL ERROR : Large SAP backups exit with status 50
TECH84193 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup catalog backup fails with status code 50 (client process aborted).

NetBackup catalog backup fails with status code 50 (client process aborted).
TECH34682 | 2013-10-23
Technical Solutions | CMS-XML

BUG REPORT: NetBackup Storage Lifecycle Policy (SLP) duplications may fail with Status Code 50.

6/29/2009 7:39:14 PM - Error bptm(pid=7016) Could not open file Global\NetBackup Media Manager SHM Info Path client_1246244490_copy1_3 to get shared memory information, The system cannot find the file specified.
TECH72227 | 2013-10-24
Technical Solutions | CMS-XML

BUG REPORT: Exit status 50 during an RMAN backup of a large Oracle piece.

document periodically as any changes to the status of the defect will be reflected here. Please
TECH67120 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?