Run-time error '-2147467259 (80004005)'

Question

Run-time error '-2147467259 (80004005)'

michael.tang

SSC Veteran

Points: 279
More actions
November 22, 2008 at 4:49 am

#196203

Hi,
We have accounting system, APS, which is sitted in SQL2005 stnd. Two week ago,
because of shortage of hardware resource, we migrated the whole database to new
server. there is no error in the first week after migration. But later, most
of client users have been getting the error message sereral times casually a
day. The error messages as below
Run-time error '-2147467259 (80004005)':
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(send()).NumADOErrors:2 err(10054) [Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send()). err(11) [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your network
documentation.
At first I thought maybe it was network issue. I changed switch, cable and network card for the server. But these did not fix this issue.
Is there someone here to help me to fix this issue?
Many thanks in advance for your help

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Todd Engen SSCrazy Eights Points: 9869 More actions · Answer 1

Changing the switch, cable and NIC all sounds like a good steps, could still be some type of network configuration issue. For example, duplex mismatch.

If you haven't tried it yet, use something like robocopy to time copying a large data file to a known good server and to the new server to see if the times are consistent. At least that way you completely rule out SQL as having anything to do with it.

michael.tang SSC Veteran Points: 279 More actions · Answer 2

Many thanks for your reply. I already download robocopy GUI application but don't know how to use it. I put one of server folder in the source path, which contains 10GB file, and local c drive as target path. When I click run, only take one second, and I could not find the log.

But anyway, I still think it is SQL server setting issue instead of network issue.

Todd Engen SSCrazy Eights Points: 9869 More actions · Answer 3

I'm not familar the GUI robocopy but here's a command line example for comparison.

[font="Courier New"]robocopy c:\sourcefolder \\server1\destinationshare file1.txt [/font]

A 10GB file in 1 second seems too fast, a least on Gigabit ethernet, about 2-5 minutes would be closer.

Are you seeing something in an event log or error log that makes you think it's SQL?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

A general network error means that the connection has been suddenly and forcefully closed, and not by the application. Basically, the app tries to communicate over a channel that no longer exists.

On SQL's side that can mean that the connection has been killed, either by an admin issuing a kill command, or by an error with a severity of 20 or higher. Both will appear in the SQL Server error log.

If it's a kill command, then speak to your admin and ask him to stop killing connections. If it's a sev 20 or higher error, then you have a very serious problem.

If neither appears in the SQL error logs, then it's something in the network between the client PC and the Server.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Johan Bijnens SSC Guru Points: 135265 More actions · Answer 5

just my 2ct to add to the previous replies....

- double check the nic cables to see if the connectores are fixed.

- check for hardware firmware know issues and upgrade if needed

- run netmon software to monitor your nic. just trying to rule out that way.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Jeff Moden SSC Guru Points: 1003873 More actions · Answer 6

Oh lordy... I can see it now... some DBA decided that (s)he was gonna cleanup "unused" SPIDs and wrote some proc to kill all SPID's that don't have "Runnable" as a status.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)