[DBNETLIB]ConnectionCheckForData (CheckforData())

Hi...

SQL SERVER 2000 SP3, WINDOWS 2K SERVER...

If i run this command on a remote server

select replicate(' ',190)

i have the following error

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.

Connection Broken

if i run select replicate(' ',60) on the same server it completes
succesfully...

any ideas?...

thanks...Sangines (javier.sangines@.gruposenda.com) writes:
> SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
> If i run this command on a remote server
> select replicate(' ',190)
> i have the following error
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> if i run select replicate(' ',60) on the same server it completes
> succesfully...

Interesting...

Often such events are accompnied by messages in the SQL Server errorlog
with a stack dump, indicating that there was an execution error in
SQL Server. However, given the statement you submit this sounds
unlikely. I assume that you run it from Query Analyzer?

So in this case, I would say that it smells a network problem of
some sort. Do you still get the message if you run the query locally
on the SQL Server machine? Do you get the message if you talk to
other SQL Servers?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||> Interesting...
> Often such events are accompnied by messages in the SQL Server errorlog
> with a stack dump, indicating that there was an execution error in
> SQL Server. However, given the statement you submit this sounds
> unlikely. I assume that you run it from Query Analyzer?
> So in this case, I would say that it smells a network problem of
> some sort. Do you still get the message if you run the query locally
> on the SQL Server machine? Do you get the message if you talk to
> other SQL Servers?

Thanks for quick response Erland...

Yes...it was a network problem, caused by misconfiguration in network device...

problem solved...

thanks again...