NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 2052

NetBackup status code : 2052
HOWTO91396 | 2013-10-02
How To | CMS-XML

NetBackup status code: 2052

NetBackup status code : 2052
HOWTO51704 | 2012-11-19
How To | CMS-XML

NetBackup status code: 2052

NetBackup status code : 2052
HOWTO35814 | 2010-10-29
How To | CMS-XML

GENERAL ERROR: The error "CreateDesktop failed, error 8" appears in the Veritas NetBackup (tm) bptm or bpsched log files

00:01:18.359 [2052.1656] 2 bpsched_main: CreateDesktop failed, error 8 00:02:49.515 [2836. 2052 ] 2 bpsched_main: CreateDesktop failed, error 8 Resolution
TECH18910 | 2013-10-23
Technical Solutions | CMS-XML

bpbrm start_bpcd_stat: bpcd on redwood exited with status 11: system call failed

2 vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3504: vnet_init_connect_rec failed: 6 0x00000006 2 nb_connect_to_vnetd_or_legacy: comm.c. 2052 : vnet_connect_to_vnetd_or_service failed: 6 2 bpcr_connect: nb_connect_to_vnetd_service(redwood) failed: 48
TECH71865 | 2009-01-02
Technical Solutions | CMS-XML

Why does the bplist command fail with status 25?

log from client host: 07:19:57.755 [23849] 2 nb_connect_to_vnetd_or_legacy: comm.c. 2052 : vnet_connect_to_vnetd_or_service failed: 6 07:19:57.755 [23849] 2 bprd_connect: Cannot connect to server buster automatically: 48
TECH56282 | 2007-01-22
Technical Solutions | CMS-XML

bpclntcmd returns error code 25 | Symantec Connect

10:15:29.572 [13648] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3520: vnet_async_connect failed: 18 0x00000012 10:15:29.572 [13648] <2> nb_connect_to_vnetd_or_legacy: comm.c. 2052 : vnet_connect_to_vnetd_or_service failed: 18 10:15:29.572 [13648] <2> bpcr_connect: nb_connect_to_vnetd_service(dmzvm1) failed: 25
Connect Forums | HTML

Status Code Chart

2051 2052 2053
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

an ACS Library Storage Module (LSM) is offline See NetBackup status code : 2052 an entry in the filelist expanded to too many characters
HOWTO90266 | 2013-10-02
How To | CMS-XML

System State backups of Windows 2008 clients are slow

5:54:06.875 PM: [5656. 2052 ] 2 tar_base::v_vtarmsgw: WRN - can t open file: System State:\System Files\System Files (WIN32 -536805667: Unknown error )
TECH167788 | 2013-08-08
Technical Solutions | CMS-XML

NetBackup messages

an ACS Library Storage Module (LSM) is offline See NetBackup status code : 2052 an entry in the filelist expanded to too many characters
HOWTO50775 | 2012-11-19
How To | CMS-XML

NetBackup messages

See NetBackup status code: 2026 See NetBackup status code : 2052 See NetBackup status code: 70
HOWTO34884 | 2010-10-29
How To | CMS-XML

Configuring disk pool for DataDomain storage server: The operation has exceeded the time out limit...

13:04:22.128 [29252] 4 nbu_server01: ddcl_vrapid_get_host_ip: host_name datadomainapp01m has host_ip 20.17.43.219 13:04:22.128 [29252] 4 nbu_server01: ddcl_vrapid_get_host_port: host_name datadomainapp01m for pgm = 100005 has port 2052 13:04:22.309 [29252] 4 nbu_server01: ddcl_vrapid_get_host_ip: host_name datadomainapp01m has host_ip 20.17.43.219
TECH204280 | 2013-03-25
Technical Solutions | CMS-XML

BUG REPORT: Oracle process crashes doing sbtinfo2 or sbtremove2 if client temporarily cannot connect to bprd on the master server.

10:48:35.870 [9651] 2 vnet_async_connect: vnet_vnetd.c.3746: ran out of time before connect: 305 0x00000131 10:48:35.870 [9651] 2 vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3515: vnet_async_connect failed: 18 0x00000012 10:48:35.870 [9651] 2 nb_connect_to_vnetd_or_legacy: comm.c. 2052 : vnet_connect_to_vnetd_or_service failed: 18
TECH72405 | 2012-01-31
Technical Solutions | CMS-XML

During a clustered master server on Veritas Cluster Server (VCS) upgrade from 5.X to 6.X involving multiple subnets, connection issues occur from nbpushdata to physical node's bpcd port.

(From nbpushdata log:) 19:04:27.260 [6390] 2 nb_connect_to_vnetd_or_legacy: comm.c. 2052 : vnet_connect_to_vnetd_or_service failed: 18 19:04:27.260 [6390] 2 bpcr_connect: nb_connect_to_vnetd_service(node2) failed: 25
TECH56486 | 2010-01-05
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?