NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 1557

NetBackup status code : 1557
HOWTO91612 | 2013-10-02
How To | CMS-XML

NetBackup status code: 1557

NetBackup status code : 1557
HOWTO72937 | 2012-11-19
How To | CMS-XML

GENERAL ERROR: An incorrect or incomplete installation of Private Branch Exchange (PBX) may cause CORBA issues and status code 811 failures on a media server upgraded from NetBackup 5.x to NetBackup 6.x.

Ensure the PBX process is running on the media server, and that it can listen on the defined PBX ports (1556/ 1557 ). The problem may not be related to the installation of PBX (ICS), but a problem with PBX being started or listening correctly.
TECH59148 | 2010-01-21
Technical Solutions | CMS-XML

NDMP directory specific restore fails with status 5 and "no files matched in the given date range"

#1 0xc000000011a879a0:0 in nbe_catimage::getNextNode () at nbe_cat_image.cpp: 1557 #2 0xc000000011afc9b0:0 in nbe_catfile_bin::getNextNode ()
TECH63017 | 2009-01-03
Technical Solutions | CMS-XML

BUG REPORT: Intermittent 83 errors using NetBackup Key Management Service (KMS)

22:37:56.313 [29676] 2 TAO: PBXIOP (29676|1) pbxiop_acceptor::open_i() trying to listen on port 1556 22:37:56.377 [29676] 2 TAO: PBXIOP (29676|1) pbxiop_acceptor::open_i cannot open acceptor in port range (1556, 1557 )- : No such file or directory 22:37:56.379 [29676] 2 TAO: TAO (29676|1) unable to open acceptor for 1556:nb_29676_2000699252 : Invalid argument
TECH73324 | 2009-01-10
Technical Solutions | CMS-XML

GENERAL ERROR: While upgrading from NetBackup 5.x to NetBackup 6.0, the installation fails with the error message, "Error 1920.Service VERITAS Private Branch Exchange"

- Review the output of the netstat command and see if ports 1556 or 1557 are in use. Log Files
TECH50230 | 2008-01-10
Technical Solutions | CMS-XML

Netbackup 6.5 - Solaris 10 status"6" | Symantec Connect

11:39:31.194 [7015] <2> vnet_read_service_file: vnet_text.c.477: Function failed: 19 0x00000013 11:39:31.194 [7015] <2> process_service_socket_plus: vnetd.c. 1557 : vnet_read_service_file failed: 19 0x00000013 Marianne Trusted Advisor
Connect Forums | HTML

Status Code Chart

1556 1557 1558
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE: 77 - When installing a NetBackup maintenance pack, the following error occurs: "EMM interface initialization failed, status = 77"

11/28/06 09:49:57.815 [TAO] PBXIOP (11433|1) pbxiop_acceptor::open_i cannot open acceptor in port range (1556, 1557 )- : Connection refused
TECH49764 | 2008-01-30
Technical Solutions | CMS-XML

Storage lifecycle policy Validation Report tab

See NetBackup status code: 1556 See NetBackup status code : 1557 See NetBackup status code: 1558
HOWTO86952 | 2013-10-04
How To | CMS-XML

NetBackup messages

must specify mirror retention when target storage unit is mirror capable See NetBackup status code : 1557 NB database backup failed, a path was not found or is inaccessible
HOWTO90266 | 2013-10-02
How To | CMS-XML

NetBackup messages

must specify mirror retention when target storage unit is mirror capable See NetBackup status code : 1557 NB database backup failed, a path was not found or is inaccessible
HOWTO50775 | 2012-11-19
How To | CMS-XML

Registered ports and dynamically-allocated ports on UNIX/Linux

Note : NetBackup recommends that the port numbers that are associated with PBX (1556 and 1557 ) not be changed. dynamically-allocated ports
HOWTO66752 | 2013-10-15
How To | CMS-XML

Registered ports and dynamically-allocated ports

Note: Symantec recommends that the port numbers that are associated with PBX (1556 and 1557 ) not be changed. dynamically-allocated ports
HOWTO86369 | 2013-09-29
How To | CMS-XML

Registered ports and dynamically-allocated ports on Windows

Note : NetBackup recommends that the port numbers that are associated with PBX (1556 and 1557 ) not be changed. dynamically-allocated ports
HOWTO67897 | 2013-07-01
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?