Video Screencast Help

error 150 but in logs error 24

Created: 30 May 2013 | 3 comments
jploui's picture

Hi All,

Im currently sitting in a difficult position with my backups.

I have backups failing with error 150, but in the logs it show error 24 and sometimes 14.

I disable on my master the firewals, the SEP, and the same on media server and client.

But the issue persists.

This is extract from clients bpbkar log that bugging me.

Anybody seen this?

3:13:58.258 PM: [7412.8136] <16> tar_tfi::processException:

An Exception of type [SocketWriteException] has occured at:

Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.54 $ , Function: TransporterRemote::write[2](), Line: 321

Module: @(#) $Source: src/ncf/tfi/lib/Packer.cpp,v $ $Revision: 1.90 $ , Function: Packer::getBuffer(), Line: 658

Module: tar_tfi::getBuffer, Function: D:\NB\NB_7.5\src\cl\clientpc\util\tar_tfi.cpp, Line: 311

Local Address: [::]:0

Remote Address: [::]:0

OS Error: 10053 (An established connection was aborted by the software in your host machine.

)

Expected bytes: 131072

3:13:58.258 PM: [7412.8136] <2> tar_base::V_vTarMsgW: FTL - socket write failed

Operating Systems:

Comments 3 CommentsJump to latest comment

Dyneshia's picture

1) What type of backup is this ?

2 ) does the error occur for only one client ?  If multiple clients, is it only when using a particular media server.

3) You must test the connectivity btwn the master - media - and client

4) Are you able to connect to the client through the host properties ?

Ankit Maheshwari's picture

Please share Activy monitor logs also..

Ankit Maheshwari

jploui's picture

problem resolved, issue was with nic settings, some changes in the enviroment changed and caused these timeouts.

change the duplex settings, the offload settings to disbaled etc.

Ill send more details when i get some free time.