Solved

SQL Restore problems

Posted on 1997-09-29
3
294 Views
Last Modified: 2008-03-17
On restoring from tape the following error is given

ERROR 10005:[DB_LIBRARY] DB PROCESS IS DEAD OR NOT ENABLED

in short .. HELP! .. this is fairly urgent so a quick response would be appreciated :)

thanks
0
Comment
Question by:british041297
  • 2
3 Comments
 
LVL 9

Accepted Solution

by:
cymbolic earned 400 total points
ID: 1088967
Perhaps the following relate sto your problem.  I noted that it is fixed by the latest service pack update.

Microsoft Knowledge Base

FIX: Win16 DBLIB Does Not Restrict Packet Size to 512 for SPX

Last reviewed: April 8, 1997
Article ID: Q152130 The information in this article applies to:

•Microsoft SQL Server, version 6.5

SYMPTOMS
A DB-Library application for Windows may return the following error when executing a query that returns a large number of rows under IPX/SPX:
   Possible Network Error; Read From SQL Server Failed.
   This command did not return data, and it did not return any rows
   DB-Library Process Dead - Connection Broken

When this occurs, the connection will be lost, and closing the application may cause Windows to stop responding.
CAUSE
The Win16 DB-Library DLL (W3dblib.dll or Msdblib3.dll) does not correctly detect the IPX/SPX Net-Library for Windows. As a result, it does not automatically restrict the TDS packet size to 512 bytes. This causes DB- Library to use the default "Network Packet Size" setting on the server side, which is 4096 bytes by default. Due to the architecture limit in DBMSSPX3.DLL, a larger TDS buffer size is not supported. Attempting to use a larger TDS packet size can cause unexpected errors or make the system otherwise unstable.

WORKAROUND
You can work around this problem either by forcing the packet size to 512 through the DBSETLPACKET() DBLIB function or by reducing the default "Network Packet Size" on the server side to 512 bytes.

STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the latest U.S. Service Pack for SQL Server version 6.5. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
0
 
LVL 9

Expert Comment

by:cymbolic
ID: 1088968
P.S. I noted two other DBLIB process dead fixes in the detail of that serveice pack as well.
0
 
LVL 1

Author Comment

by:british041297
ID: 1088969
Thanks .. we actually found that Service Pack 2 or greater solved the problem.

Thanks for your prompt and helpful response

BRiTiSH
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now