NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 139

Media Manager status code 139
HOWTO104504 | 2014-11-20
How To | CMS-XML

STATUS CODE: 139, 50, Hot catalog backups are failing trying to connect to a non-existent media server.

139
TECH45920 | 2009-01-07
Technical Solutions | CMS-XML

Backup to Windows master server fails with status code 12 when using long client or policy names

Total combined length of the client name and the backup policy name is limited to 139 characters on Windows master servers. If this limit is exceeded then backups may fail with error status code 12 or 11.
TECH214234 | 2014-11-06
Technical Solutions | CMS-XML

Multiple File Restore on OpenVMS completes with status 0 but only the first file is restored

Directory N12345:[USER] ABCDEF.IND;14 File ID: (65502, 139 ,0) Size: 88KB/88KB
TECH213427 | 2014-04-15
Technical Solutions | CMS-XML

NetBackup automatic remote master replication fails status 84 when target MSDP media server resolves the source MSDP media server hostname to incorrect ipv6/ipv4 address.

19:11:33.138 [30164] 16 rpl_copy_image_set: wait failed: error 2060014 19:11:33. 139 [30164] 16 rpl_copy_cancel: async cancel failed: error 2060001: 19:11:33.139 [30164] 16 rpl_copy_image_set: copy cancel failed: error 2060001
TECH209579 | 2014-02-18
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pciex1077,2432.1077.138 pciex1077,2432.1077. 139 pciex1077,2432.1077.13D
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

Restore data transfer hangs after the tar header is transferred and fails with status 13 and status 5.

[15383] 2 write_to_out: ignoring [32] for DB Restore 07:54:46.958 [15383] 2 terminate_restore: [15365] waited for full buffer 0 times, delayed 139 times 07:54:46.958 [15383] 2 terminate_restore: [15365] sent 1 directories/files to client myclient
TECH162318 | 2011-06-14
Technical Solutions | CMS-XML

GENERAL ERROR: Flashbackup jobs are taking excessive amount of time before writing data.

bpbkar: 10:26:37. 139 PM: [4596.5260] 2 tar_base::v_vtarmsgw: INF - FIML startup time = 0 Excluded List processing was occurring in this time frame
TECH62435 | 2008-01-15
Technical Solutions | CMS-XML

Catalog backup fails with status 13 | Symantec Connect

Catalog backup fails with status 13 00:49:41.130 [1206] <16> bpbrm readline: socket read failed: errno = 62 - Timer expired 00:49:41. 139 [1206] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: vn_request_service_socket: 6 0x00000006 00:49:41.139 [1206] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bpjobd
Connect Forums | HTML

Netbackup 7.1.0.4 - MSDP storaged CRITICAL ERROR | Symantec Connect

Data storage Raw Size Used Avail Use% 4.8T 4.6T 4.4T 139 .6G 97% Number of containers : 19739
Connect Forums | HTML

Please help ASAP --- Error 13 | Symantec Connect

Thursday 019:00:00 024:00:00 115:00:00 120:00:00 Friday 019:00:00 024:00:00 139 :00:00 144:00:00 Saturday 019:00:00 024:00:00 163:00:00 168:00:00
Connect Forums | HTML

Client backup failing with error 25 | Symantec Connect

10:19:21.634 [49200.48036] <2> vnet_registerpbxserver: ../../libvlibs/vnet_pbx.c.144: alt_addr: 10.215.237. 139
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:28:43. 139 [4665] <2> db_end: Need to collect reply 14:28:48.647 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:28:48.652 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:51:15. 139 [5136.4148] <2> io_open_disk: file hqrm86_1345160188_c1_f1 successfully opened
Connect Forums | HTML

Status Code Chart

138 139 140
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?