NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

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

54
TECH38514 | 2013-10-24
Technical Solutions | CMS-XML

in-depth Troubleshooting Guide for Exit Status Code 54 in Veritas NetBackup (tm) Server / NetBackup Enterprise Server 6.0

54
TECH43129 | 2008-01-03
Technical Solutions | CMS-XML

STATUS CODE 54: Some third-party software packages can link into the TCP/IP stack in Windows and cause a loss of connection between the Veritas NetBackup (tm) server and the bpcd process on the client.

Timed out connecting to client ( 54 ) status 25: cannot connect on socket
TECH88628 | 2014-05-19
Technical Solutions | CMS-XML

"robot number and robot type mismatch (54)" Error when doing Robot Inventory

robot number and robot type mismatch ( 54 )
TECH184699 | 2014-01-08
Technical Solutions | CMS-XML

STATUS CODE: 54, Client backups fail with a status 54 if the bp.conf file is empty or is missing a SERVER entry

STATUS CODE : 54 , Client backups fail with a status 54 if the bp.conf file is empty or is missing a SERVER entry
TECH38741 | 2013-10-23
Technical Solutions | CMS-XML

After installing Microsoft Windows XP Service Pack 2, client backups fail with "Status Code: 54 timed out connecting to client." The server could not complete the connection to the client. The accept winsock call timed out after 60 seconds.

Timed out connecting to client( 54 )
TECH32785 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 54, 24, 134, and 6 are all received while performing a backup. The final exit status is 6 indicates the backup has failed.

2. The bulk of status code 54 errors seen during the SQL backups are characterized by the presence of server status 24 and server status 134 messages written to the clients progress log. This appears to be a bpsched
TECH37196 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Restore of SQL database to an alternate location fails with a Status Code 25 or a Status Code 54.

GENERAL ERROR : Restore of SQL database to an alternate location fails with a Status Code 25 or a Status Code 54 .
TECH38716 | 2013-10-23
Technical Solutions | CMS-XML

Media Manager status code 54

Media Manager status code 54
HOWTO90932 | 2013-10-02
How To | CMS-XML

NetBackup status code: 54

NetBackup status code : 54
HOWTO90483 | 2013-10-02
How To | CMS-XML

Media Manager status code 54

Media Manager status code 54
HOWTO51281 | 2012-11-19
How To | CMS-XML

NetBackup status code: 54

NetBackup status code : 54
HOWTO50831 | 2012-11-19
How To | CMS-XML

WIN 2003 R2 Server failing backup with status 24/54/58

WIN 2003 R2 Server failing backup with status 24/ 54 /58
TECH169380 | 2011-09-12
Technical Solutions | CMS-XML

Status 25 or status 54 when not using vnetd for connect-back and a third-party service is allowed to listen on the same port

Status 25 or status 54 when not using vnetd for connect-back and a third-party service is allowed to listen on the same port
TECH154279 | 2011-06-14
Technical Solutions | CMS-XML

MPX DB extension backups fail intermittently with status 54.

MPX DB extension backups fail intermittently with status 54 .
TECH138071 | 2011-02-22
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?