error 10005 dbprocess is dead or not enabled

MsSQL Server 2000
PowerBuilder 8 Application
20 client on LAN ethernet
2 client on 64 K router-to-router LAN

on 2 remote client I have this error.

There are two router Cisco whit idle-timeout on 1800 sec, but evry 1/2
minutes on the 2 remote clients there are the error: 10005 dbprocess
is dead or not enabled.

this is a new problem after migration from SQL Server 6.5-PB7 to Sql
server 2000-PB8.

Thanks
Maxmdalica (mdalica@.libero.it) writes:
> MsSQL Server 2000
> PowerBuilder 8 Application
> 20 client on LAN ethernet
> 2 client on 64 K router-to-router LAN
> on 2 remote client I have this error.
> There are two router Cisco whit idle-timeout on 1800 sec, but evry 1/2
> minutes on the 2 remote clients there are the error: 10005 dbprocess
> is dead or not enabled.
> this is a new problem after migration from SQL Server 6.5-PB7 to Sql
> server 2000-PB8.

Very difficult to diagnose remotely. It's even very difficult to
diagnose locally.

The message itself, is fairly generic. It could be due to a crash on
the SQL Server side, so check the SQL Server errorlog for stack dumps
or other messages. But since you get it so frequently, I would guess
this is a network problem of some sort.

I'm by no means a network knowledgable person, so I can only give
general tips: check the Windows event log, both on client and server.
Trying using different communications protocols. (You can change this
in the Client Network Utility and the Server Network Utility.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message news:<Xns93F453D7825DYazorman@.127.0.0.1>...
> mdalica (mdalica@.libero.it) writes:
> > MsSQL Server 2000
> > PowerBuilder 8 Application
> > 20 client on LAN ethernet
> > 2 client on 64 K router-to-router LAN
> > on 2 remote client I have this error.
> > There are two router Cisco whit idle-timeout on 1800 sec, but evry 1/2
> > minutes on the 2 remote clients there are the error: 10005 dbprocess
> > is dead or not enabled.
> > this is a new problem after migration from SQL Server 6.5-PB7 to Sql
> > server 2000-PB8.
> Very difficult to diagnose remotely. It's even very difficult to
> diagnose locally.
> The message itself, is fairly generic. It could be due to a crash on
> the SQL Server side, so check the SQL Server errorlog for stack dumps
> or other messages. But since you get it so frequently, I would guess
> this is a network problem of some sort.
> I'm by no means a network knowledgable person, so I can only give
> general tips: check the Windows event log, both on client and server.
> Trying using different communications protocols. (You can change this
> in the Client Network Utility and the Server Network Utility.)

There are not error on server and client logs, the server run
correctly, the local clients run correctly. I think that the problems
is instable connection, bat I don't know a possible solution.