General Network Error

Question

General Network Error

Andrzej Biedrawa

SSC Journeyman

Points: 86
More actions
August 2, 2004 at 10:25 am

#112105

We are using MSDE 2000A over NamedPipes. On of actions in our setup is restoring of the clean database.
However on Windows XP restore often fails - DB is in "a middle of retore state", EM shows that it is Loading/Suspected.
Restore logs shows as follow:
Processed 752 pages for database 'DB', file 'DATA' on file 1.
Processed 8 pages for database 'DB', file 'TMP' on file 1.
[Named Pipes]ConnectionRead (WrapperRead()).
[Named Pipes]General network error. Check your network documentation.
Processed 1 pages for database 'DB', file 'LOG' on file 1
We cannot Login into this databse. Anyone has ever encounter same issue ? Maybe someone knows the solution?
brgds
Andrzej

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 1

have you tried using TCP/IP instead? - also make sure you connect by IP address and not by Server name, that way you avoid IP resolution issues.

MVDBA

Andrzej Biedrawa SSC Journeyman Points: 86 More actions · Answer 2

The problem is that this setup should work on Win98 and above. We had decided to use NamedPipes due to several reasons:

- it is deafult installed

- setup should work on Win98 which can be installed without TCPIP

- I heard that using TCPIP requires Printers/Folders sharing enabled on Win98.

- MS says that named pipes are more eficient than TCPIP

Today I had switched setup to use TCPIP on NT family. Because we are at the End Game stage i had a week to check if bugs number will decrease. But in fact this is only temporary workaround for me and problem is still present.

brgds,

Andrzej

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 3

on a fast network TCP/IP and named pipes are comparable, but over a slower network or WAN then Pipes are much slower as the are more interactive than TCP/IP

TCP/IP doesn't require printer sharing - although named pipes uses port 445 which is the same as the file and print sharing port (named pipes is an old protocol based around file and print sharing)

MVDBA

Andrzej Biedrawa SSC Journeyman Points: 86 More actions · Answer 4

Thanks for information and making some things clear. Lets say that we will leave our solution on TCPIP. What additional traps or issues can we find? For know we are seeing only the risk that there could be another SQL/MSDE instance installed so port 1433 can not be free, or the port can be used by any other application. Any other things we should be aware of?

Thanks once again,

Andrzej

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 5

you can configure the port settings for MSDE/SQL by using the server network utility - that way you can choose the TCP/IP port to listen on.

the only things i can think of to tell you are that if you are planing to use windows XP and install service pack 2 on any machines, then you need to make sure that you open up those ports on the client as they are Closed by default.

MVDBA

Andrzej Biedrawa SSC Journeyman Points: 86 More actions · Answer 6

I know that I should specify the port both in Client and Server Network utility. But the problem is that this value can be:

- fixed (hardcoded) in setup which can lead to a problem when a port is used

OR

- dynamically determination of free port on server and than configuring on all clients same port - which can be too complicated (must have a tool for detection of free port, must automatically redistribute information about the used port to clients)

Brgds,

Andrzej