ConnectionRead (WrapperRead())

When executing an sp from the Analyzer, I get the following:

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

I don't get this with other procedures, nor do the eventlog from w2k or errorlog from SQLServer indicate something is wrong. The procedure that I call, calls another procedure which gives this error. When I call that procedure directly, I do not get this (or any other) error.

Any idea?I think I've solved it by installing MDAC 2.8 and the patch that follows.|||Or so I thought...

It's a little bit different from the orignal though:

I have a tight loop in a procedure that works it way down a table, the loop is supposed to fill a temp-table with values. Eventually, based on that temp-table, the final table is filled.

I used to get the error when opening the cursor, that is: when I ran the procedure. Opening the cursor directly from the analyzer or running the select-itself: no error.

I've been fiddling about trying this and that, for some reason the error keeps popping-up. It has moved to someplace inside the loop, but I don't know what to look for next.

Any thoughts would be greatly appreciated.

Connection Problem with Remote Server

If I do this:
select * from tblAmcareDetail
I get my records back but as soon as try to specify column names I get:
Server: Msg 207, Level 16, State 3, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'apexorderid'.
I think it must be a connection problem because I don't have this problem on
local servers. The server is registered by it's ip address and I'm running
the query under the servers sa account.
Can anyone help?Doesn't sound like a connection problem.
Are you sure the table on the server.database you're connecting to has
this column?
Is the server/db/table you're connecting to perhaps setup with a
case-sensitive collation? If so, you'll need to query using the case of
column names as in the table definition.
Spike wrote:
> If I do this:
> select * from tblAmcareDetail
> I get my records back but as soon as try to specify column names I get:
> Server: Msg 207, Level 16, State 3, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
> 'apexorderid'.
> I think it must be a connection problem because I don't have this problem
on
> local servers. The server is registered by it's ip address and I'm runnin
g
> the query under the servers sa account.
> Can anyone help?
>

Connection problem with NT4

Ive installed SQL2000 in a NT4-SP6 server, but I cant connect from another machine.
I receive the following msg in Query analizer : "sql server does not exists or access denied"
Ive tried both authentications methods, created alias with IP and server name but nothing works.

If I use query analizer locally I can connect using the server name, but cant if use the ip.

Please, save me :)

thanks in advanceHi Felipe,

I faced a similiar problem when using a Business-Intelligence Client
to connect from a NT-Client to our cube located on a XP-PC with
MS SQL and MS OLAP.

I tried realy everthing:
At the end the following worked.

I added every user, who wants to connect locally(!) as an account.
I added a role to the MS OLAP cube and added the new user to this
role.

Hint:
These users must be domain-users
(and in our case local users too )

hth

Michael|||thanks for your time Michael, but I cant connect with "sa"

Connection problem

I have a multi-user web environment and amoccassionally receiving the following error msg with our SQL Server 2005 db:

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

I know there are numerous posts about this, but there doesn't seem to be a definitive "fix" for the issue after looking at the posts.

I am using the "WITH (NOLOCK)" option on some of the tables within my stored procedures. I need this option for certain tables I am accessing.

My ConnectionstringTimeout property is set for 45 seconds and my CommandTimeout property is set for 150 seconds.

Could a MS DBA please look into this issueASAP and get back with a definitive resolution?

btw, I am also using Connection Pooling with a min size of 2 and max size of 200.

Can someone please reply back who knows a definitive resolution to this problem?

|||

Hi wsyeager,

Well, seems thre is no ms dba answer your question here so i would try to deliver some effort. I searched through google and found this information. It makes sense to me

guess the problem is the connection pool. Recall that when you close
a connection from your .Net app, the connection to SQL Server is not
really closed. Instead ADO .Net lingers to it, for another 60 seconds,
and if the applicaiton opens a new connection during this time, it will
reuse the connection.

When you issue ALTER DATABASE WITH ROLLBACK IMMEDIATE, SQL Server will
terminate these connections. However, this is not something that ADO .Net
can detect. So it gives you a connection which it thinks is good, but
which isn't.

There are a couple of ways to approach this. One is to configure the
connection pool, so that all connections are dropped when you drop the
database. Another is to change the connection string, each time you
drop the database, as different connection strings gives different pools.

I would suggest that the best way, though, is simply to set up an exception
handler, so that you simply trap this error, and then try to reconnect.

See original artilce at:http://www.msdner.com/forum/thread476823.html

I sincerely hope it can help

|||

Bo, thanks a lot!

I simply look for that exception number (10054) in my middle tier object and retry the cmd again and it works fine now.