June 3, 2004 at 11:02 pm
I amended a stored proc via QA and ran it (ALTER PROCEDURE) - no problem. The mod was minor – to an existing tried-and-tested procedure.
Then tried running it in QA (right-click/open) and got the following message:
(86 row(s) affected)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
My next idea was to revert the stored proc to its orig. state and run it again. But I still get the same message (with some variation in #row(s) affected).
Does anyone know what this message means and how to fix it?
Thanks.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
June 4, 2004 at 12:29 am
I need some more info about your setup
What version and SP of SQL Server and what platform?
Andy.
June 4, 2004 at 1:13 am
Windows 2000. SQL Server 2000 SP3.
Cheers
Phil
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
June 4, 2004 at 1:24 am
I have had this problem before and this is how I solved it I hope this will give you a little bit of help.
I had MDAC ver 2.8 and was using Named Pipes.
I changed to TCP/IP and it resolved the bug. (I think its a MDAC "thing")
Andy.
June 4, 2004 at 1:46 am
Excuse my lack of knowledge, but how do you control the method by which QA connects to a particular SQL Server instance?
Cheers.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
June 4, 2004 at 1:59 am
On the Start menu, point to Programs/Microsoft SQL Server , and then click Client Network Utility.
In the general TAB you will find Enabled and Disabled options. If Named Pipes is enabled and TCP/IP is Disabled my bugfix would be to enable TCP/IP and disable Named pipes.
Before you start changing options it would be a good idea to take note of all of the current settings so that you can roll back to the original settings if need be. To be honest I do not know why this worked for me so good luck.....
Andy.
June 4, 2004 at 5:43 am
I would start with what Andy mentioned too. The reason for TCP/IP running better vs. Named Pipes depends on your network set-up. IF you are in a LAN then TCP/IP IF WAN (DS3 connecting buildings, etc...) then Named-Pipes works better. This is due to the way they pass data back and forth and manage acknowledgements.
Another thing you may want to check is to make sure that no one else is having network problems. It could be a general network slowdown as well.
Good Luck,
Good Hunting!
AJ Ahrens
webmaster@kritter.net
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply