tcp/ip and named pipes problems

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Development (2000)

tcp/ip and named pipes problems

Author

Topic

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-03-15 : 06:24:29

I've got a weird problem with one of my sql servers.
Microsoft SQL Server 2000 - 8.00.2039
Windows 2003 SP1

i've got named pipes and tcp/ip enabled.

but today i've been getting
tds buffer length too large
errors

and the queries takes a loooong time
if i disable the TCP/IP and use only named pipes
the queries take a normal time to execute.
i'm a bit stumped...

any thoughts?

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2007-03-15 : 06:26:15

Local installation?
Via router to remote machine?

Peter Larsson
Helsingborg, Sweden

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-03-15 : 06:32:56

it's a server in our LAN.
It's kind of weird...
we get different running times from different computers in the network.
and our network seems ok...

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2007-03-15 : 06:35:32

Seems the packets are getting screwed by some router or switch.

Peter Larsson
Helsingborg, Sweden

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-03-15 : 06:37:51

hmm... i'll check...

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2007-03-15 : 06:39:15

Do you have the same issue when having local access to the sql server?
Can you rdp the server and run ssms locally? Or can you get physical local access? Still same issues?

Peter Larsson
Helsingborg, Sweden

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-03-15 : 06:45:03

i can connect to the server and the same query runs great on the server.
as far as i can see the server processing itself isn't the problem.
it's the transport mechanism to the client.

I've read about some network buffers on the server when sending data to the client
that can get clogged up but i have no idea about that.

i'm not much of a network guy

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-03-15 : 08:22:49

router and switch both seem ok.
this is weirding me out...

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

TRACEYSQL
Aged Yak Warrior

594 Posts

Posted - 2007-04-01 : 09:06:20

the tds buffer length too large how did you determine this.
Is this from the ODBC to the SQL.

Im having similar problems....where all of a sudden 10 -15 get disconnected, network errors when using an erp system application..some users are good some are not.

How do i determine whats in the pipe...tcp/ip
If i run from citrix to odbc to sql at what stage does SQL say hey i have enough is it in the TCP/IP ?

Thanks

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-04-01 : 09:32:42

well in the end we traced the problem to the network card on the sql server.
it was put into full duplex mode.

we put in in auto mode and it all worked great.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

TRACEYSQL
Aged Yak Warrior

594 Posts

Posted - 2007-04-01 : 09:39:52

Where did these errors tds get reported?

well in the end we traced the problem to the network card on the sql server.
it was put into full duplex mode.

Did sql just stop or just slow? Any suggestions would be appreciated perhaps i have same thing to.

But i think ours was one of our citrix servers we use citrix to odbc to sql and when i did trace on odbc it would not save file after reboot it was fine.

Do you know when ODBC talks to SQL through TCP IP does the TCP/IP commands wait until SQL can accept them...and how many this is?

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-04-01 : 10:13:44

These errors got reported in the SSMS.
So on the client.

Well it depends on what you have enabled in your allowed protocols in the sql server.
TCP/IP is the default one.

ODBC, OLEDb and ADO.Net are all client connectivity providers and you have to look at the client to see which one is bring used.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

TRACEYSQL
Aged Yak Warrior

594 Posts

Posted - 2007-04-01 : 17:53:51

We use TCP/IP i don't see any errors coming in on SQL at all.
Do i have to enable certain messages for get this being reported.

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-04-02 : 03:40:05

not that i know of.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources