NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 186

Media Manager status code 186
HOWTO91034 | 2013-10-02
How To | CMS-XML

NetBackup status code: 186

NetBackup status code : 186
HOWTO90603 | 2013-10-02
How To | CMS-XML

Media Manager status code 186

Media Manager status code 186
HOWTO51383 | 2012-11-19
How To | CMS-XML

NetBackup status code: 186

NetBackup status code : 186
HOWTO50951 | 2012-11-19
How To | CMS-XML

NetBackup status code: 186

NetBackup status code : 186
HOWTO35062 | 2010-10-29
How To | CMS-XML

Media Manager status code: 186

Media Manager status code : 186
HOWTO35493 | 2010-10-29
How To | CMS-XML

Restoring images at the subdirectory level fails. Restore fails with status 5; bpbrm 186 (tar received no data) and 92 (not in tar format); tar exit 6 "no data in archive"

Restoring images at the subdirectory level fails. Restore fails with status 5; bpbrm 186 (tar received no data) and 92 (not in tar format); tar exit 6 "no data in archive"
TECH33323 | 2005-01-28
Technical Solutions | CMS-XML

Backups of the same client using some media servers fail with status 21: socket open failed

14:22:34.783 [12439640] 2 ProcessRequests: vnetd.c.372: status: 11 0x0000000b 14:22:38.330 [12439640] 2 vnet_pop_byte: vnet.c. 186 : errno: 2 0x00000002 14:22:38.330 [12439640] 2 vnet_pop_byte: vnet.c.188: Function failed: 9 0x00000009
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

Backup and restore operation fail with status 25 when multi-homed Windows 2008 clients have stronghost enabled

13:22:51. 186 [8588.2032] 2 logconnections: BPCD ACCEPT FROM 192.168.1.2.592 TO 0.0.0.0 .13782
TECH63457 | 2013-04-16
Technical Solutions | CMS-XML

policy can't be modified with error 14 file write failed after creation or copy to new unless bppinfo

09:17:10.328 [5796.6116] 2 process_request: request complete: exit status 14 file write failed; query type: 198 09:18:01.109 [2272.5544] 2 vnet_cache_nbconf: ../../libvlibs/vnet_private.c. 186 : 0: caching vnet data: 0 0x00000000 5. it seems to be permission issue.
TECH199279 | 2013-02-06
Technical Solutions | CMS-XML

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

...snip... 08:44:53. 186 [15320] 16 bpbrm Exit: client restore EXIT STATUS 13: file read failed The vnetd debug log
TECH162318 | 2011-06-14
Technical Solutions | CMS-XML

restore failure: exit status 5

-- 9/26/2008 12:41:47. 186 v-117-250 [rescallback_i::requestFailed] resource request failed for allocation id=jobid=25264, EMM status=2005075
TECH63733 | 2010-01-24
Technical Solutions | CMS-XML

Oracle backup fails with status 25 when the connect back from the client is denied.

10/16/2009 1:38:27 PM - mounted; mount time: 00:00:31 10/16/2009 1:38:28 PM - positioning NT6984 to file 186 10/16/2009 1:38:57 PM - positioned NT6984; position time: 00:00:29
TECH76188 | 2009-01-29
Technical Solutions | CMS-XML

Dreaded Status 25 and 58 | Symantec Connect

Dreaded Status 25 and 58 <2> vnet_cached_gethostbyname: vnet_hosts.c.301: found host in cache: [client] <2> vnet_pop_byte: vnet.c. 186 : errno: 10054 0x00002746 <2> vnet_pop_byte: vnet.c.188: Function failed: 43 0x0000002b
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:21:21.091 [4665] <2> db_end: Need to collect reply 14:21:27. 186 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:21:27.187 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?