Connection Problem / Named Pipes ?
-
I've been happily and easily running a SQL2000 server for the past few years with no server problems ... until now.
All of the sudden, clients who connected with Named Pipes are getting connection errors and jobs that used to run flawlessly (backups of msdb, pubs and our data) are not running at all.
The only network change I've been able to discover is an upgrade in BackUp Exec which appears to have put MDAC 2.8 on the server. (We had trouble using it in the office and rolled all Win2000 pcs back to 2.6 awhile ago.)
The data backup that failed had this error message in Enterprise Manager:
Executed as user: MEDICINE\NETOFF. ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11) 10 percent backed up. [SQLSTATE 01000] (Error 3211). The step failed.
When I typed in the code of this job into query analyzer, the error message was slightly different:
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
The funny thing is that if I run the backup of the database in question from EM w/o a scheduled job, I am able to do it successfully.
I was able to determine that named pipes was still a viable option on the server a week ago.
Any suggestions?
-
Copule of questions.
Where are you backing the SQL Server to? Local drives? The LAN? The WAN?
Is BE backing up this server and other server(s) to a local tape unit?
What bandwidth is being consumed?
Are both BE and the maint plan firing at the same time?
Are both the maint plan and the push/pull subscriptions firing at the same time?
Are the subrcriber(s) current?
Is TCP port 445 expliclty enabled? http://support.microsoft.com/default.aspx?scid=kb;en-us;839269&Product=sql2k
Does BE use TCP port 445?
Can you rollback from MDAC 2.8? Compromise on MDAC 2.7?
And as a last resort can you fall back to TCP?
Just my $0.02
Hopefully this gives you something to look at.
----------------
Jim P.A little bit of this and a little byte of that can cause bloatware.
-
Thanks for the help.
Here are the answers I got to the questions:
Where are you backing the SQL Server to? Local drives? The LAN? The WAN?
- local drives
Is BE backing up this server and other server(s) to a local tape unit?
- SAN tape unit
What bandwidth is being consumed?
- non on main network - all on SAN backplane
Are both BE and the maint plan firing at the same time?
- no
Are both the maint plan and the push/pull subscriptions firing at the same time?
- no answer from my network folks
Are the subrcriber(s) current?
- no answer from my network folks
Is TCP port 445 expliclty enabled? http://support.microsoft.com/default.aspx?scid=kb;en-us;839269&Product=sql2k
- no answer from my network folks
Does BE use TCP port 445?
- no answer from my network folks
Can you rollback from MDAC 2.8? Compromise on MDAC 2.7?
- not likely as BackUp Exec 9.1 requires it
And as a last resort can you fall back to TCP?
-- TCP is enabled on the server already along with named pipes
Do you have any suggestions? These Named Pipes issues are sudden and nothing has changed my end yet all I can do is rely on the network folks to tell me what has changed on their end that is affecting my server.
Thanks again.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply