Showing posts with label analyzer. Show all posts
Showing posts with label analyzer. Show all posts

Sunday, March 25, 2012

Connecto to remote SQL Server

Hi, community

I want to connect a program (like query analyzer) in home, to the sql server in office via internet, but i can't log in to the remote server. Someone know how to establish the connection?

Thanks to all of you!!!You will need to get permission from you network group to VPN into the network.|||thank you, but can you be a little more detailed?|||You need to talk to your network group and have them give you VPN access and tell you how to use it.|||I've tryed lot of things but cant connect!!!!, i try to establish a VPN in win 2k3 server as Server and winXP Prof as client, but it is impossible to get connected!!!

I finally get the VPN connection, i've missing directives, but now i cant connect to SQL Server!

Monday, March 19, 2012

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.

ConnectionRead (InvalidParam()) error

I get the following error sometimes when I execute a store procedure from SQ
L
Query Analyzer. After a few more attempts, the query succeeds... How can I
troubleshoot this network error...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (Inv
alidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection BrokeFirst thing to check, just like the message stated, "General network error.
Check your network documentation." The fact that it sometimes works and
sometimes not points to an unstable network.
hth
Quentin
"Shaila" <Shailaja @.discussions.microsoft.com> wrote in message
news:03329249-66CC-4806-91A9-D5434C3130D9@.microsoft.com...
>I get the following error sometimes when I execute a store procedure from
>SQL
> Query Analyzer. After a few more attempts, the query succeeds... How can I
> troubleshoot this network error...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

ConnectionRead (InvalidParam()) error

Somtimes I get the following error in SQL query Analyzer when executing a
store procedure. After a few attempts the query succeeds but how can i
resolve this issue...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (Inv
alidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection BrokeHi,
This is due to the network that you are having. Due to network congestion u
might be facing this problem. Try to enhance the network and try again
"Shaila" wrote:

> Somtimes I get the following error in SQL query Analyzer when executing a
> store procedure. After a few attempts the query succeeds but how can i
> resolve this issue...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (I
nvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

ConnectionRead (InvalidParam()) error

Somtimes I get the following error in SQL query Analyzer when executing a
store procedure. After a few attempts the query succeeds but how can i
resolve this issue...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection BrokeHi,
This is due to the network that you are having. Due to network congestion u
might be facing this problem. Try to enhance the network and try again
"Shaila" wrote:
> Somtimes I get the following error in SQL query Analyzer when executing a
> store procedure. After a few attempts the query succeeds but how can i
> resolve this issue...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

ConnectionRead (InvalidParam()) error

I get the following error sometimes when I execute a store procedure from SQL
Query Analyzer. After a few more attempts, the query succeeds... How can I
troubleshoot this network error...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection BrokeFirst thing to check, just like the message stated, "General network error.
Check your network documentation." The fact that it sometimes works and
sometimes not points to an unstable network.
hth
Quentin
"Shaila" <Shailaja @.discussions.microsoft.com> wrote in message
news:03329249-66CC-4806-91A9-D5434C3130D9@.microsoft.com...
>I get the following error sometimes when I execute a store procedure from
>SQL
> Query Analyzer. After a few more attempts, the query succeeds... How can I
> troubleshoot this network error...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

ConnectionRead (InvalidParam()) error

I get the following error sometimes when I execute a store procedure from SQL
Query Analyzer. After a few more attempts, the query succeeds... How can I
troubleshoot this network error...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broke
First thing to check, just like the message stated, "General network error.
Check your network documentation." The fact that it sometimes works and
sometimes not points to an unstable network.
hth
Quentin
"Shaila" <Shailaja @.discussions.microsoft.com> wrote in message
news:03329249-66CC-4806-91A9-D5434C3130D9@.microsoft.com...
>I get the following error sometimes when I execute a store procedure from
>SQL
> Query Analyzer. After a few more attempts, the query succeeds... How can I
> troubleshoot this network error...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

ConnectionRead (InvalidParam()) error

Somtimes I get the following error in SQL query Analyzer when executing a
store procedure. After a few attempts the query succeeds but how can i
resolve this issue...
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broke
Hi,
This is due to the network that you are having. Due to network congestion u
might be facing this problem. Try to enhance the network and try again
"Shaila" wrote:

> Somtimes I get the following error in SQL query Analyzer when executing a
> store procedure. After a few attempts the query succeeds but how can i
> resolve this issue...
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broke

Tuesday, February 14, 2012

Connection String

I have SQL Server 2000 installed on my XP Pro PC and the Client Tools (SQL
Query Analyzer) installed on my 98SE PC. On the 98SE PC, when I start SQL
Query Analyzer, I get a window titled "Connect to SQL Server" but the SQL
Server line is blank and the drop-down arrow is also blank. How do I get the
SQL Server 2000 to show up here? Thanks in advance for any help on this. I
built the 98SE machine especially to access the database files that are on
the SQL Server 2000 but, so far, I have been unable to connect to the
server. Jim.The drop down shows what servers you have connected to not
necessarily what servers are available. Type the server name
in and try connecting.
-Sue
On Sun, 12 Jun 2005 14:15:42 GMT, "Jim Richards"
<JWRichards@.satx.rr.com> wrote:

>I have SQL Server 2000 installed on my XP Pro PC and the Client Tools (SQL
>Query Analyzer) installed on my 98SE PC. On the 98SE PC, when I start SQL
>Query Analyzer, I get a window titled "Connect to SQL Server" but the SQL
>Server line is blank and the drop-down arrow is also blank. How do I get th
e
>SQL Server 2000 to show up here? Thanks in advance for any help on this. I
>built the 98SE machine especially to access the database files that are on
>the SQL Server 2000 but, so far, I have been unable to connect to the
>server. Jim.
>|||Thank you Sue. You said: "Type the server name in and try connecting." The
name of the computer on which the Server resides is "JIMRIC" and is accessed
over a LAN. The name of the Server is "local". Do I type in:
\\JIMRIC\(local) , if not, what do I type in Please.
BTW, I also have the SQL Query Analyzer on the XP Pro PC and I have no
trouble connecting to the server there. The server is entered here as
(local). Jim.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8msqa1loi5kortnt885spitum19pof9rdj@.
4ax.com...
> The drop down shows what servers you have connected to not
> necessarily what servers are available. Type the server name
> in and try connecting.
> -Sue
> On Sun, 12 Jun 2005 14:15:42 GMT, "Jim Richards"
> <JWRichards@.satx.rr.com> wrote:
>
>|||When it's on the box where you are running the tools, you
can use (local) for the default instance. From other
computers, you need to specify the server name and from the
local server you can specify the server name.
ServerName\OtherName is used for connecting to named
instances.
If you are using (local) from another PC, it's not
connecting to another server in the network. It's connecting
to a SQL Server (or MSDE) instance on that PC.
-Sue
On Mon, 13 Jun 2005 15:26:58 GMT, "Jim Richards"
<JWRichards@.satx.rr.com> wrote:

>Thank you Sue. You said: "Type the server name in and try connecting." The
>name of the computer on which the Server resides is "JIMRIC" and is accesse
d
>over a LAN. The name of the Server is "local". Do I type in:
>\\JIMRIC\(local) , if not, what do I type in Please.
>BTW, I also have the SQL Query Analyzer on the XP Pro PC and I have no
>trouble connecting to the server there. The server is entered here as
>(local). Jim.
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:8msqa1loi5kortnt885spitum19pof9rdj@.
4ax.com...
>|||Thank you Sue and I will show my ignorance and ask then how do I know what
name to type in? TIA, Jim.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:1fgsa1db7tqfqdddqfs1d01510ggrn9m9i@.
4ax.com...
> When it's on the box where you are running the tools, you
> can use (local) for the default instance. From other
> computers, you need to specify the server name and from the
> local server you can specify the server name.
> ServerName\OtherName is used for connecting to named
> instances.
> If you are using (local) from another PC, it's not
> connecting to another server in the network. It's connecting
> to a SQL Server (or MSDE) instance on that PC.
> -Sue
> On Mon, 13 Jun 2005 15:26:58 GMT, "Jim Richards"
> <JWRichards@.satx.rr.com> wrote:
>
>

Connection String

I have SQL Server 2000 installed on my XP Pro PC and the Client Tools (SQL
Query Analyzer) installed on my 98SE PC. On the 98SE PC, when I start SQL
Query Analyzer, I get a window titled "Connect to SQL Server" but the SQL
Server line is blank and the drop-down arrow is also blank. How do I get the
SQL Server 2000 to show up here? Thanks in advance for any help on this. I
built the 98SE machine especially to access the database files that are on
the SQL Server 2000 but, so far, I have been unable to connect to the
server. Jim.
The drop down shows what servers you have connected to not
necessarily what servers are available. Type the server name
in and try connecting.
-Sue
On Sun, 12 Jun 2005 14:15:42 GMT, "Jim Richards"
<JWRichards@.satx.rr.com> wrote:

>I have SQL Server 2000 installed on my XP Pro PC and the Client Tools (SQL
>Query Analyzer) installed on my 98SE PC. On the 98SE PC, when I start SQL
>Query Analyzer, I get a window titled "Connect to SQL Server" but the SQL
>Server line is blank and the drop-down arrow is also blank. How do I get the
>SQL Server 2000 to show up here? Thanks in advance for any help on this. I
>built the 98SE machine especially to access the database files that are on
>the SQL Server 2000 but, so far, I have been unable to connect to the
>server. Jim.
>
|||Thank you Sue. You said: "Type the server name in and try connecting." The
name of the computer on which the Server resides is "JIMRIC" and is accessed
over a LAN. The name of the Server is "local". Do I type in:
\\JIMRIC\(local) , if not, what do I type in Please.
BTW, I also have the SQL Query Analyzer on the XP Pro PC and I have no
trouble connecting to the server there. The server is entered here as
(local). Jim.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8msqa1loi5kortnt885spitum19pof9rdj@.4ax.com...
> The drop down shows what servers you have connected to not
> necessarily what servers are available. Type the server name
> in and try connecting.
> -Sue
> On Sun, 12 Jun 2005 14:15:42 GMT, "Jim Richards"
> <JWRichards@.satx.rr.com> wrote:
>
|||When it's on the box where you are running the tools, you
can use (local) for the default instance. From other
computers, you need to specify the server name and from the
local server you can specify the server name.
ServerName\OtherName is used for connecting to named
instances.
If you are using (local) from another PC, it's not
connecting to another server in the network. It's connecting
to a SQL Server (or MSDE) instance on that PC.
-Sue
On Mon, 13 Jun 2005 15:26:58 GMT, "Jim Richards"
<JWRichards@.satx.rr.com> wrote:

>Thank you Sue. You said: "Type the server name in and try connecting." The
>name of the computer on which the Server resides is "JIMRIC" and is accessed
>over a LAN. The name of the Server is "local". Do I type in:
>\\JIMRIC\(local) , if not, what do I type in Please.
>BTW, I also have the SQL Query Analyzer on the XP Pro PC and I have no
>trouble connecting to the server there. The server is entered here as
>(local). Jim.
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:8msqa1loi5kortnt885spitum19pof9rdj@.4ax.com.. .
>
|||Thank you Sue and I will show my ignorance and ask then how do I know what
name to type in? TIA, Jim.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:1fgsa1db7tqfqdddqfs1d01510ggrn9m9i@.4ax.com...
> When it's on the box where you are running the tools, you
> can use (local) for the default instance. From other
> computers, you need to specify the server name and from the
> local server you can specify the server name.
> ServerName\OtherName is used for connecting to named
> instances.
> If you are using (local) from another PC, it's not
> connecting to another server in the network. It's connecting
> to a SQL Server (or MSDE) instance on that PC.
> -Sue
> On Mon, 13 Jun 2005 15:26:58 GMT, "Jim Richards"
> <JWRichards@.satx.rr.com> wrote:
>