Things I've seen this before with

1.  NT pre service pack 5

2.  Bad NIC

3.  Duplexing on the switch differs from that of card (NEVER use
auto-detect)

4. High CPU Utilization on either the media server or the client.

Bob

-----Original Message-----
From: O'Shea, Don [mailto:Don.OShea AT emergis DOT com]
Sent: Monday, June 26, 2000 12:33 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Socket Operation Failed


I am encountering a problem where 1 server out of the 20 or so that are
backed up fails. A check of problem log shows the following error messages:

>From Client servername: FTL TAR FILE WRITE ERROR(10054)

Socket Operation Failed 10004[at ../child.c.819]

Unable to perform read from client socket, connection may have been broken.

backup of client servername exited with status 14(File write failed)

schedular exiting - file write failed.

Everything looks fine with the network. This is a primary database server so
if there was a network problem the whole application would stop running and
that is not happening. If anybody has seen this before and knows what is
causing it, I would appreciate any information you could provide.

Don O'Shea
Sr. Operations Analyst
BCE Emergis
Financial Services Division
Phone: (905) 707-4000 Ext. 3765
Fax: (905) 707-4329
mailto:don.oshea AT emergis DOT com

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu