NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 1557

NetBackup status code : 1557
HOWTO105094 | 2014-11-20
How To | 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

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

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

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
HOWTO103773 | 2014-11-20
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
HOWTO105746 | 2014-11-19
How To | CMS-XML

PBX port registration and usage

1557 : Was historically used by PBX to accept, from the local loopback interface only, connections from local processes on behalf of which it was listening. It is no longer used by NetBackup 7.0 and newer versions.
TECH73696 | 2014-10-15
Technical Solutions | CMS-XML

BUG REPORT: NetBackup master services terminate shortly after startup when having a lot of media servers in the environment

09/20/2011 11:51:06.449 [Debug] NB 51216 libraries 137 PID:18284710 TID:1 File ID:111 [No context] 4 [TAO] PBXIOP (18284710|1) pbxiop_acceptor::open_i cannot open acceptor in port range (1556, 1557 )- : Connection timed out
TECH174379 | 2012-04-04
Technical Solutions | CMS-XML

EMM will not stay running. Reporting "Exception caught attempting EMM orb startup = bad_param"

04/01/10 09:56:06.504 [Warning] Exchange cannot listen on legacy port 1557 for service registrations. Continuing, but this may impair cc-service functionality
TECH128321 | 2010-01-05
Technical Solutions | CMS-XML

nbemm fails to start due to "unable to open acceptor for <1556:EMM>: Invalid argument".

03/21/08 16:01:06.515 [Debug] NB 51216 137 PID:26163 TID:2597280 File ID:111 [No context] 4 [TAO] PBXIOP (26163|2597280) pbxiop_acceptor::open_i cannot open acceptor in port range (1556, 1557 )- : Bad file descriptor
TECH58807 | 2009-01-31
Technical Solutions | CMS-XML

PBX Port Question | Symantec Connect

PBX Port Question Was talking to a Symantec (Veritas) support guy the other day, and the topic of firewall ports came up. I mentioned that we're only allowing TCP 13724 (vnetd) and 1556 (pbx) through our firewalls, and he mentioned that I need TCP 1557 also. I've never heard of this one before; the only reference I can find mentions it as a "secondary" PBX port.
Connect Forums | HTML

Firewall ports needed for Netbackup MS <> Client | Symantec Connect

Firewall ports needed for Netbackup MS <> Client tcp 0 0 0.0.0.0:1556 0.0.0.0:* LISTEN 19148/pbx_exchange tcp 0 0 127.0.0.1: 1557 0.0.0.0:* LISTEN 19148/pbx_exchange tcp 0 0 127.0.0.1:60630 0.0.0.0:* LISTEN 19148/pbx_exchange
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?