NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 44

Media Manager status code 44
HOWTO104425 | 2014-11-20
How To | CMS-XML

Device management status code 44

Device management status code 44
HOWTO104671 | 2014-11-20
How To | CMS-XML

Device configuration status code 44

Device configuration status code 44
HOWTO104585 | 2014-11-20
How To | CMS-XML

NetBackup status code: 44

NetBackup status code : 44
HOWTO103974 | 2014-11-20
How To | CMS-XML

Vmware Backups Fail with Status 58 Or " connect failed STATUS (18) connect_failed " Or "status: FAILED, (44) connect_timeout; system: (10061) No connection could be made because the target machine actively refused it" Or "getsockopt so_error returned 10061 0x274d"

Vmware Backups Fail with Status 58 Or " connect failed STATUS (18) connect_failed " Or " status : FAILED, ( 44 ) connect_timeout; system: (10061) No connection could be made because the target machine actively refused it" Or "getsockopt so_error returned 10061 0x274d"
TECH192643 | 2014-01-08
Technical Solutions | CMS-XML

NetBackup status code 44: network write failed

NetBackup status code : 44 Explanation
TECH57900 | 2009-01-12
Technical Solutions | CMS-XML

The Enterprise Media Manager (EMM) Service fails to start after installation. "EMM interface initialization failed, status = 334"

The Enterprise Media Manager (EMM) Service fails to start after installation. "EMM interface initialization failed&# 44 ; status = 334"
TECH54023 | 2007-01-14
Technical Solutions | CMS-XML

NetBackup EXIT STATUS 10: allocation failed

12:31:45.020 PM: [3316.5148] 2 Packer::open(): DBG - | An Exception of type [InvalidStateException] has occured at: | Module: @(#) $Source: src/ncf/tfi/lib/Packer.cpp,v $ $Revision: 1.90. 44 .1 $ , Function: Packer::open(), Line: 333 | Encryption is not configured correctly and initialization failed.
TECH203268 | 2014-10-15
Technical Solutions | CMS-XML

THIRD PARTY: Multiple client backups exit with status 24 when the network is heavily loaded.

12: 44 :14.293 AM: [5420.6320] 32 TransporterRemote::write[2](): FTL - SocketWriteException: send() call failed, could not write data to the socket, possible broken connection.
TECH56950 | 2014-05-01
Technical Solutions | CMS-XML

Backup of "Shadow Copy Components" completes with Status Code 1 for a Windows Server 2008 R2 system. The bpbkar log show an error fs_skip_object returned for BEDS for object 'Shadow Copy Components'

12:55: 44 .959: [1536.5096] 2 ov_log::v_globallogex: INF - beds_base::v_openforread(): fs_skip_object returned for BEDS for object Shadow Copy Components:\System Service\Background Intelligent Transfer Service The event viewer on the client machine may contain the following event:
TECH144975 | 2014-02-18
Technical Solutions | CMS-XML

Snapshot errors encountered with ibm4000 arrays (NetBackup status code 156)

23: 44 :48.007 [655588] 2 onlfi_vfms_logf: INF - snapshot services: ibmdsfi:Wed Mar 12 2008 23: 44 :48.007721 Thread id - 1 FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive= angela_javelin_4 userLabel= angela_javelin_4_flcp_4 ;].23:44:48.012
HOWTO88357 | 2013-09-30
How To | CMS-XML

NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed".

12: 44 :38.619 [4804.5184] 2 logconnections: BPCD ACCEPT FROM 10.1.2.3.47204 TO 10.1.2.37.13724
TECH56079 | 2013-04-24
Technical Solutions | CMS-XML

Storage unit characteristics mismatched to request (status code 154)

11/21/2008 5:36: 44 PM - requesting resource stu_med 11/21/2008 5:36: 44 PM - requesting resource lin04- x86.nbu_client.MAXJOBS.hyper_win_5.acme.com 11/21/2008 5:36:44 PM - requesting resource lin04- x86.nbu_policy.MAXJOBS.mapped_vm
HOWTO70804 | 2012-02-08
How To | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

47 49 4f 50 01 00 00 01 00 00 02 04 00 00 00 00 GIOP............ 00 00 00 01 00 00 00 03 00 00 00 1b 49 44 4c 3a ............IDL: 56 65 72 69 74 61 73 2f 45 4d 4d 2f 53 65 72 76 Veritas/EMM/Serv
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

Info bpbkar32(pid=3124) done. status: 44: network write failed network write failed(44) | Symantec Connect

Info bpbkar32(pid=3124) done. status: 44: network write failed network write failed(44) network write failed( 44 ) Discussion Filed Under:
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?