DBPROCESS is dead or not enabled

We started getting this error a couple of weeks ago:
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
JimSQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
>
>|||Hi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim