SQL Restore problems

On restoring from tape the following error is given


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

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

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.
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.

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.

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):

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
P.S. I noted two other DBLIB process dead fixes in the detail of that serveice pack as well.
british041297Author Commented:
Thanks .. we actually found that Service Pack 2 or greater solved the problem.

Thanks for your prompt and helpful response

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.