Mike m. 2012-03-18 09:42:38
We just upgraded a bunch of PC’s from Win98 to WinXP.
We have a custom PowerBuilder front end to SQL 2000
database. Ever since the upgrade, the clients are now
getting SQL errors 10005, and 10025’s. None of the folks
still running on Win98 are getting these errors, and the
network (100 mb / switched) is clean.
I’ve exhausted my TechNet searches and was hoping someone
out here might have a clue.
Erland sommars 2012-03-18 09:42:41
Mike M. (firstname.lastname@example.org) writes:
To pick a nit, you are likely getting message from DB-Library, not from
SQL Server itself. I suppose these are the message you are getting.
10005 = “DBPROCESS is dead or not enabled.”
10025 = “Write to SQL Server failed”.
Since this is happening on such a wide scale, I would suspect some sort
of network configuration problem.
I would check:
o The SQL Server Error Log. There could be stack dumps.
o The Windows event log, both on the client machines and on the
Which communication protocol are you using? TCP/IP or named pipes?
Erland Sommarskog, SQL Server MVP, email@example.com
Books Online for SQL Server SP3 at
Mike m. 2012-03-18 09:42:43
This is a 9 month old network installation with about 80
users. Sniffers report no unusual traffic. All in all,
a very “clean” and lightly used network — which is why
I’m baffled by the errors.
There are no stack dumps on the SQL server (according to
the main SQL Admin).
I’m checking the library, but I’m 99% certain (alright,
maybe only 75%!!) we’re using TCP/IP, not named pipes.
Library, not from
suspect some sort
and on the