NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 338

NetBackup status code : 338
HOWTO90747 | 2013-10-02
How To | CMS-XML

NetBackup status code: 338

NetBackup status code : 338
HOWTO51095 | 2012-11-19
How To | CMS-XML

NetBackup status code: 338

NetBackup status code : 338
HOWTO35206 | 2010-10-29
How To | CMS-XML

NetBackup backups are failing with Status 24 due to network issue in the environment

) | Expected bytes: 131072 | (../TransporterRemote.cpp: 338 )
TECH217961 | 2014-05-30
Technical Solutions | CMS-XML

Microsoft Exchange DAG backup failing with error code "socket write failed(24) "

An Exception of type [SocketWriteException] has occured at: Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.54.126.1 $ , Function: TransporterRemote::write[2](), Line: 338
TECH193354 | 2013-11-11
Technical Solutions | CMS-XML

GENERAL ERROR: Vault begins a session and either hangs early on in the process or seems to not start at all. Eventually, the job has to be canceled by operator, ending in a status 50 or 150.

18:15:16.315 [25315] 16 vltrun@VaultJobMonitor::_send_try_msg^4: Failed to send try_msg: vault_dplctn_batch_start 1281617116 1 1 2 18:15:21. 338 [25315] 16 vltrun@VltSession::lock_and_operate^4 op_step=duplicate_bymid FAILED 18:15:21.340 [25315] 16 vltrun@VltSession::lock_and_operate^4 FAILed nb_ec=308 nb_msg=no images duplicated
TECH128761 | 2012-01-19
Technical Solutions | CMS-XML

BUG REPORT: Oracle restore fails with status 25 when bpbrm receives a signal during bpcd disconnect processing.

13:21:52.943 [23317] 2 set_job_details: LOG 1265570512 16 bpbrm 23317 could not disconnect from bpcd on myclient 13:21:53. 338 [23317] 16 bpbrm send_info_via_progress_file: could not close client_cmd_sock, Bad file number (9) 13:21:53.892 [23317] 16 bpbrm listen_for_client: listen for client protocol error - couldn t write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/5071.0.1265570219
TECH125637 | 2011-10-03
Technical Solutions | CMS-XML

BUG REPORT: NetBackup LiveUpdate jobs to update an AIX or HPIA64 NetBackup Master or Media server will fail with either status 1 or a status 77 in the Activity Monitor.

Jul 12, 2006 8:43:11 PM Disk space check for udpate name failed. Requested free space was 338 .467 (in MB).
TECH64983 | 2011-08-10
Technical Solutions | CMS-XML

GENERAL ERROR: NetBackup Flashbackup backup fails with a status 156 on a Windows client.

log file showed the following error: 09:36:11.338 [22824.26732] 4 bpfis: INF - EXIT STATUS 156: snapshot error encountered 09:36:11. 338 [22824.26732] 2 onlfi_vfms_logf: snapshot services: improper disposition parameter.
TECH55376 | 2009-01-16
Technical Solutions | CMS-XML

NBu 7.1.0.2 - Backup job hangs at "Begin Writing". No error! | Symantec Connect

NBu 7.1.0.2 - Backup job hangs at "Begin Writing". No error! 13:04:05.498 [2108.2376] <2> dsmlibp_register_factories: .\dsmlib_common.cpp: 338 sev 4 Registerd DiskServiceMgr OBV factories with orb 00000000029b36b0
Connect Forums | HTML

Getting Error Failed to initialize EMM connection. Please help... | Symantec Connect

Getting Error Failed to initialize EMM connection. Please help... 22:41:40. 338 [6428.2396] <16> nbemmcmd: Run time failure: Failed to initialize EMM connection. Verify that network access to the EMM server is available and that the services nbemm and pbx_exchange are running on the EMM server.
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:26:21.054 [4665] <2> db_end: Need to collect reply 14:26:26. 338 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:26:26.340 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:05:22.235 [5512.3504] <2> dsmlibp_register_factories: .\dsmlib_common.cpp: 338 sev 4 Registerd DiskServiceMgr OBV factories with orb 024c6f90
Connect Forums | HTML

Status Code Chart

337 338 339
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE: 41 and 150 - SAP backups with device type of "util_file_online" fail with Status Code 41 and 150. Client logs show Status Code 40.

The SAP client bpbkar log shows: 05:21:27. 338 [1364026] 4 bpbkar Exit: INF - EXIT STATUS 40: network connection broken Resolution:
TECH44488 | 2013-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?