Problem executing a stored proc, please help

Hi All,
I have stored proc that processes about 60,000 rows using a cursor. When I
call the SP from Query Analyzer, I get the following error message after
processing about 12,000 records :
Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
12614 records
What can i do to make this SP run sucessfully ? I even tried using a table
variable instead of a cursor, but got the same result. Please suggest .
THE output from SP_CONFIG on database server is
Option
config_value
------
affinity mask 0
allow updates 0
awe enabled 0
c2 audit mode 0
cost threshold for parallelism 5
Cross DB Ownership Chaining 0
cursor threshold -1
default full-text language 1033
default language 0
fill factor (%) 0
index create memory (KB) 0
lightweight pooling 0
locks 0
max degree of parallelism 0
max server memory (MB) 2147483647
max text repl size (B) 65536
max worker threads 255
media retention 0
min memory per query (KB) 1024
min server memory (MB) 0
nested triggers 1
network packet size (B) 4096
open objects 0
priority boost 0
query governor cost limit 0
query wait (s) -1
recovery interval (min) 0
remote access 1
remote login timeout (s) 20
remote proc trans 0
remote query timeout (s) 0
scan for startup procs 0
set working set size 0
show advanced options 1
two digit year cutoff 2049
user connections 0
user options 0
Hi
It would help if you posted DDL and example data such as
http://www.aspfaq.com/etiquettXXe.asp?id=5006 and
example data as insert statements
http://vyaskn.tripod.com/code.XXhtm#inserts
Connection broken implies a network failure/disconnection, possibly a
timeout but you do not indicate how long this process takes.
Check your SQL server version and service pack level, you may also want to
check MDAC version and consistancy along with the SQL Server log and event
log to see if there is any more information that may help.
Other posts on this http://tinyurl.com/4ebus may be helpful.
John
"rajeshlh" <rajeshlh@.discussions.microsoft.com> wrote in message
news:F1F399D6-BB17-4FC9-BF10-4F7D3A31F7B1@.microsoft.com...
> Hi All,
> I have stored proc that processes about 60,000 rows using a cursor. When I
> call the SP from Query Analyzer, I get the following error message after
> processing about 12,000 records :
>
> Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> ODBC: Msg 0, Level 16, State 1
> Communication link failure
>
> Connection Broken
>
>
> 12614 records
>
> What can i do to make this SP run sucessfully ? I even tried using a table
> variable instead of a cursor, but got the same result. Please suggest .
>
> THE output from SP_CONFIG on database server is
> Option
> config_value
> ------
> affinity mask 0
> allow updates 0
> awe enabled 0
> c2 audit mode 0
> cost threshold for parallelism 5
> Cross DB Ownership Chaining 0
> cursor threshold -1
> default full-text language 1033
> default language 0
> fill factor (%) 0
> index create memory (KB) 0
> lightweight pooling 0
> locks 0
> max degree of parallelism 0
> max server memory (MB) 2147483647
> max text repl size (B) 65536
> max worker threads 255
> media retention 0
> min memory per query (KB) 1024
> min server memory (MB) 0
> nested triggers 1
> network packet size (B) 4096
> open objects 0
> priority boost 0
> query governor cost limit 0
> query wait (s) -1
> recovery interval (min) 0
> remote access 1
> remote login timeout (s) 20
> remote proc trans 0
> remote query timeout (s) 0
> scan for startup procs 0
> set working set size 0
> show advanced options 1
> two digit year cutoff 2049
> user connections 0
> user options 0
>
>
>

Problem executing a stored proc, please help

Hi All,
I have stored proc that processes about 60,000 rows using a cursor. When I
call the SP from Query Analyzer, I get the following error message after
processing about 12,000 records :
Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
12614 records
What can i do to make this SP run sucessfully ? I even tried using a table
variable instead of a cursor, but got the same result. Please suggest .
THE output from SP_CONFIG on database server is
Option
config_value
------
affinity mask 0
allow updates 0
awe enabled 0
c2 audit mode 0
cost threshold for parallelism 5
Cross DB Ownership Chaining 0
cursor threshold -1
default full-text language 1033
default language 0
fill factor (%) 0
index create memory (KB) 0
lightweight pooling 0
locks 0
max degree of parallelism 0
max server memory (MB) 2147483647
max text repl size (B) 65536
max worker threads 255
media retention 0
min memory per query (KB) 1024
min server memory (MB) 0
nested triggers 1
network packet size (B) 4096
open objects 0
priority boost 0
query governor cost limit 0
query wait (s) -1
recovery interval (min) 0
remote access 1
remote login timeout (s) 20
remote proc trans 0
remote query timeout (s) 0
scan for startup procs 0
set working set size 0
show advanced options 1
two digit year cutoff 2049
user connections 0
user options 0Hi
It would help if you posted DDL and example data such as
http://www.aspfaq.com/etiquett­­e.asp?id=5006 and
example data as insert statements
http://vyaskn.tripod.com/code.­­htm#inserts
Connection broken implies a network failure/disconnection, possibly a
timeout but you do not indicate how long this process takes.
Check your SQL server version and service pack level, you may also want to
check MDAC version and consistancy along with the SQL Server log and event
log to see if there is any more information that may help.
Other posts on this http://tinyurl.com/4ebus may be helpful.
John
"rajeshlh" <rajeshlh@.discussions.microsoft.com> wrote in message
news:F1F399D6-BB17-4FC9-BF10-4F7D3A31F7B1@.microsoft.com...
> Hi All,
> I have stored proc that processes about 60,000 rows using a cursor. When I
> call the SP from Query Analyzer, I get the following error message after
> processing about 12,000 records :
>
> Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> ODBC: Msg 0, Level 16, State 1
> Communication link failure
>
> Connection Broken
>
>
> 12614 records
>
> What can i do to make this SP run sucessfully ? I even tried using a table
> variable instead of a cursor, but got the same result. Please suggest .
>
> THE output from SP_CONFIG on database server is
> Option
> config_value
> ------
> affinity mask 0
> allow updates 0
> awe enabled 0
> c2 audit mode 0
> cost threshold for parallelism 5
> Cross DB Ownership Chaining 0
> cursor threshold -1
> default full-text language 1033
> default language 0
> fill factor (%) 0
> index create memory (KB) 0
> lightweight pooling 0
> locks 0
> max degree of parallelism 0
> max server memory (MB) 2147483647
> max text repl size (B) 65536
> max worker threads 255
> media retention 0
> min memory per query (KB) 1024
> min server memory (MB) 0
> nested triggers 1
> network packet size (B) 4096
> open objects 0
> priority boost 0
> query governor cost limit 0
> query wait (s) -1
> recovery interval (min) 0
> remote access 1
> remote login timeout (s) 20
> remote proc trans 0
> remote query timeout (s) 0
> scan for startup procs 0
> set working set size 0
> show advanced options 1
> two digit year cutoff 2049
> user connections 0
> user options 0
>
>
>

Problem executing a stored proc, please help

Hi All,
I have stored proc that processes about 60,000 rows using a cursor. When I
call the SP from Query Analyzer, I get the following error message after
processing about 12,000 records :
Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidP
aram()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Connection Broken
12614 records
What can i do to make this SP run sucessfully ? I even tried using a table
variable instead of a cursor, but got the same result. Please suggest .
THE output from SP_CONFIG on database server is
Option
config_value
----
---
affinity mask 0
allow updates 0
awe enabled 0
c2 audit mode 0
cost threshold for parallelism 5
Cross DB Ownership Chaining 0
cursor threshold -1
default full-text language 1033
default language 0
fill factor (%) 0
index create memory (KB) 0
lightweight pooling 0
locks 0
max degree of parallelism 0
max server memory (MB) 2147483647
max text repl size (B) 65536
max worker threads 255
media retention 0
min memory per query (KB) 1024
min server memory (MB) 0
nested triggers 1
network packet size (B) 4096
open objects 0
priority boost 0
query governor cost limit 0
query wait (s) -1
recovery interval (min) 0
remote access 1
remote login timeout (s) 20
remote proc trans 0
remote query timeout (s) 0
scan for startup procs 0
set working set size 0
show advanced options 1
two digit year cutoff 2049
user connections 0
user options 0Hi
It would help if you posted DDL and example data such as
http://www.aspfaq.com/etiquett__e.asp?id=5006 and
example data as insert statements
http://vyaskn.tripod.com/code.__htm#inserts
Connection broken implies a network failure/disconnection, possibly a
timeout but you do not indicate how long this process takes.
Check your SQL server version and service pack level, you may also want to
check MDAC version and consistancy along with the SQL Server log and event
log to see if there is any more information that may help.
Other posts on this http://tinyurl.com/4ebus may be helpful.
John
"rajeshlh" <rajeshlh@.discussions.microsoft.com> wrote in message
news:F1F399D6-BB17-4FC9-BF10-4F7D3A31F7B1@.microsoft.com...
> Hi All,
> I have stored proc that processes about 60,000 rows using a cursor. When I
> call the SP from Query Analyzer, I get the following error message after
> processing about 12,000 records :
>
> Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (InvalidParam()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> ODBC: Msg 0, Level 16, State 1
> Communication link failure
>
> Connection Broken
>
>
> 12614 records
>
> What can i do to make this SP run sucessfully ? I even tried using a table
> variable instead of a cursor, but got the same result. Please suggest .
>
> THE output from SP_CONFIG on database server is
> Option
> config_value
> ----
---
> affinity mask 0
> allow updates 0
> awe enabled 0
> c2 audit mode 0
> cost threshold for parallelism 5
> Cross DB Ownership Chaining 0
> cursor threshold -1
> default full-text language 1033
> default language 0
> fill factor (%) 0
> index create memory (KB) 0
> lightweight pooling 0
> locks 0
> max degree of parallelism 0
> max server memory (MB) 2147483647
> max text repl size (B) 65536
> max worker threads 255
> media retention 0
> min memory per query (KB) 1024
> min server memory (MB) 0
> nested triggers 1
> network packet size (B) 4096
> open objects 0
> priority boost 0
> query governor cost limit 0
> query wait (s) -1
> recovery interval (min) 0
> remote access 1
> remote login timeout (s) 20
> remote proc trans 0
> remote query timeout (s) 0
> scan for startup procs 0
> set working set size 0
> show advanced options 1
> two digit year cutoff 2049
> user connections 0
> user options 0
>
>
>

Problem executing a stored proc

Hi All,

I have stored proc that processes about 60,000 rows using a cursor. When I call the SP from Query Analyzer, I get the following error message after processing about 12,000 records :

Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).

Server: Msg 11, Level 16, State 1, Line 0

General network error. Check your network documentation.

ODBC: Msg 0, Level 16, State 1

Communication link failure

Connection Broken

12614 records

What can i do to make this SP run sucessfully ? I even tried using a table variable instead of a cursor, but got the same result.

THE output from SP_CONFIG is

Option config_value

---------------------------------------

affinity mask	0
allow updates	0
awe enabled	0
c2 audit mode	0
cost threshold for parallelism	5
Cross DB Ownership Chaining	0
cursor threshold	-1
default full-text language	1033
default language	0
fill factor (%)	0
index create memory (KB)	0
lightweight pooling	0
locks	0
max degree of parallelism	0
max server memory (MB)	2147483647
max text repl size (B)	65536
max worker threads	255
media retention	0
min memory per query (KB)	1024
min server memory (MB)	0
nested triggers	1
network packet size (B)	4096
open objects	0
priority boost	0
query governor cost limit	0
query wait (s)	-1
recovery interval (min)	0
remote access	1
remote login timeout (s)	20
remote proc trans	0
remote query timeout (s)	0
scan for startup procs	0
set working set size	0
show advanced options	1
two digit year cutoff	2049
user connections	0
user options	0

Try rewriting the sproc, only without the cursor...

Problem Displaying Japanese Characters

We are a software developer here and ran into a problem trying to get SQL
Server Query Analyzer to display Japanese Characters fetched through a linked
server properly. Can someone comment on the situation?
The following configurations were able to display Japanese characters
properly:
================================================== ===
1. Write a C# application to get Japanese characters from an AS400 table
containing Japanese texts. The Japanese text was displayed on the DataGrid.
The provider used was HiT OLEDB Server/400. A 30 day eval copy can be
obtained from the following link:
http://www.hitsw.com/products_servic...b_svr_400.html
2. Create a table containing Japanese text on SQL Server A and create a
linked server on SQL Server B linking to SQL Server A. Change the font type
of SQL Server B's query analyzer to a font that is compatible with Japanese
character. (See the bottom of this message for the code used to create the
table on SQL Sever A)
3. On a new PC, install Japanese edition of Windows 2000 plus Japanese
Edition of SQL Server 2000. Create a linked server pointing to a Japanes
table on the AS400 using the HiT OLEDB provider.
The following configurations were not able to display Japanese characters
properly:
================================================== ===
i. On a PC with English version of Windows 2000 Professional and English
version of SQL Server, change the query analyzer font to a font that is
compitable with Japanese text and then use the HiT OLEDB provider to create a
linked server pointing to the Japanese table on the AS400.
ii. On the same PC above, install IBM Client Access and make a new linked
server pointing to the same Japanese table on the AS400 using Client Access.
A Japanese compitable font was selected in the query anaylzer.
The odd thing is that in configuration (1), we were able to see the Japanese
characters correctly which suggests that the HiT OLEDB provider has passed
the information back to the PC correctly. And in configuration (2) and (3),
we were able to show that SQL Server Query Analyzer has no problem displaying
Japanese characters regardless of its language edition.
We are not sure why it is behaving this way. Does anybody have any thought?
Here is the code used to generate the table on SQL Server:
Code Sample One
===============
The following code was used on an English version of SQL Server 2000 running
on an English version of Windows
2000 professional
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblJap]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[tblJap]
GO
CREATE TABLE [dbo].[tblJap] (
[CID] [int] IDENTITY (1, 1) NOT NULL ,
[Jap] [nchar] (30) NOT NULL ,
[Eng] [char] (30) NOT NULL
) ON [PRIMARY]
GO
INSERT INTO tblJap (Jap, Eng) VALUES ('織田信長','Oda Nobunaga')
INSERT INTO tblJap (Jap, Eng) VALUES ('豊臣秀吉','Toyotomi Hideyoshi')
INSERT INTO tblJap (Jap, Eng) VALUES ('徳川家康','Tokugawa Ieyasu')
--See note below
GO
SELECT * FROM tblJap
Note
====
Another odd thing was that if I run the code
INSERT INTO tblJap (Jap, Eng) VALUES ('織田信長','Oda Nobunaga')
from query analyzer, the Japanese characters showed up as ? in Enterprise
Manager. But if I edit the information again from Enterprise Manager, it
shows up properly in both Enterprise Manager and Query Analyzer.
Fabio,
Probably a problem with the way the HiT driver handles DBCS characters.
I suggest you try with StarSQL (www.starquest.com), it is another quite
reliable driver for DB2 and the support is pretty good.
Good luck,
Bob
Fabio Boscaini a =C3=A9crit :
> We are a software developer here and ran into a problem trying to get SQL
> Server Query Analyzer to display Japanese Characters fetched through a li=
nked
> server properly. Can someone comment on the situation?
> The following configurations were able to display Japanese characters
> properly:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> 1. Write a C# application to get Japanese characters from an AS400 table
> containing Japanese texts. The Japanese text was displayed on the DataGri=
d=2E
> The provider used was HiT OLEDB Server/400. A 30 day eval copy can be
> obtained from the following link:
> http://www.hitsw.com/products_servic...db_svr_400.ht=
ml
> 2. Create a table containing Japanese text on SQL Server A and create a
> linked server on SQL Server B linking to SQL Server A. Change the font ty=
pe
> of SQL Server B's query analyzer to a font that is compatible with Japane=
se
> character. (See the bottom of this message for the code used to create the
> table on SQL Sever A)
> 3. On a new PC, install Japanese edition of Windows 2000 plus Japanese
> Edition of SQL Server 2000. Create a linked server pointing to a Japanes
> table on the AS400 using the HiT OLEDB provider.
> The following configurations were not able to display Japanese characters
> properly:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> i. On a PC with English version of Windows 2000 Professional and English
> version of SQL Server, change the query analyzer font to a font that is
> compitable with Japanese text and then use the HiT OLEDB provider to crea=
te a
> linked server pointing to the Japanese table on the AS400.
> ii. On the same PC above, install IBM Client Access and make a new linked
> server pointing to the same Japanese table on the AS400 using Client Acce=
ss.
> A Japanese compitable font was selected in the query anaylzer.
> The odd thing is that in configuration (1), we were able to see the Japan=
ese
> characters correctly which suggests that the HiT OLEDB provider has passed
> the information back to the PC correctly. And in configuration (2) and (3=
),
> we were able to show that SQL Server Query Analyzer has no problem displa=
ying
> Japanese characters regardless of its language edition.
> We are not sure why it is behaving this way. Does anybody have any though=
t?
> Here is the code used to generate the table on SQL Server:
> Code Sample One
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> The following code was used on an English version of SQL Server 2000 runn=
ing
> on an English version of Windows
> 2000 professional
> if exists (select * from dbo.sysobjects where id =3D
> object_id(N'[dbo].[tblJap]') and OBJECTPROPERTY(id,
> N'IsUserTable') =3D 1)
> drop table [dbo].[tblJap]
> GO
> CREATE TABLE [dbo].[tblJap] (
> [CID] [int] IDENTITY (1, 1) NOT NULL ,
> [Jap] [nchar] (30) NOT NULL ,
> [Eng] [char] (30) NOT NULL
> ) ON [PRIMARY]
> GO
> INSERT INTO tblJap (Jap, Eng) VALUES ('=E7=B9=94=E7=94=B0=E4=BF=A1=E9=95=
=B7','Oda Nobunaga')
> INSERT INTO tblJap (Jap, Eng) VALUES ('=E8=B1=8A=E8=87=A3=E7=A7=80=E5=90=
=89','Toyotomi Hideyoshi')
> INSERT INTO tblJap (Jap, Eng) VALUES ('=E5=BE=B3=E5=B7=9D=E5=AE=B6=E5=BA=
=B7','Tokugawa Ieyasu')
> --See note below
> GO
> SELECT * FROM tblJap
> Note
> =3D=3D=3D=3D
> Another odd thing was that if I run the code
> INSERT INTO tblJap (Jap, Eng) VALUES ('=E7=B9=94=E7=94=B0=E4=BF=A1=E9=95=
=B7','Oda Nobunaga')
> from query analyzer, the Japanese characters showed up as ? in Enterpr=
ise
> Manager. But if I edit the information again from Enterprise Manager, it
> shows up properly in both Enterprise Manager and Query Analyzer.

Problem connecting to SQL Server via Query Analyzer

SQL 2000/SP3
I recently ran into an issue where I receive an error whenever I try
to connect to my database on a particular server via the Query Analyzer.
The error I receive is
ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
SQLAllocHandle on SQL_HANDLE_ENV failed.
Anyone else run into this before?Do you only have problem connecting to this particular
server? Your ODBC driver may be messed up somehow. See if
you can update your MDAC.
Linchi

quote:

---

>--Original Message--
>SQL 2000/SP3
>I recently ran into an issue where I receive an error

---

whenever I try

quote:

---

>to connect to my database on a particular server via the

---

Query Analyzer.

quote:

---

>The error I receive is
>ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver

---

Manager]Driver's

quote:

---

>SQLAllocHandle on SQL_HANDLE_ENV failed.
>Anyone else run into this before?
>
>.
>

---

|||I can't connect to any of our servers and only my machine seems to be
having this issue. I am guessing, that yes, the drivers are fried. I
had
installed some internal application software and then ka-boom... I can't
connect anywhere.
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:16a801c3df9b$3fb1d5d0$a601280a@.phx.gbl...[QUOTE]
> Do you only have problem connecting to this particular
> server? Your ODBC driver may be messed up somehow. See if
> you can update your MDAC.
> Linchi
>
> whenever I try
> Query Analyzer.
> Manager]Driver's|||Hi Simon,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From your information, when connecting to a database on a particular
server byQuery Analyzer, you got the error message as follows:
ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
SQLAllocHandle on SQL_HANDLE_ENV failed.
and you mentiond that you install some other softwares and after that, you
encounter this problem, right?
I wonder if you could login with system administrator account and
re-install the MDAC then reboot your system. You could download MDAC2.8 at:
http://www.microsoft.com/downloads/...0fe3-c795-4b7d-
b037-185d0506396c&DisplayLang=en
Hope this helps and I am looking forward to your response! Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Yes, this corrected it!
Thanks!!
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:M$wbGO83DHA.568@.cpmsftngxa07.phx.gbl...

quote:

---

> Hi Simon,
> Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
> your issue.
> From your information, when connecting to a database on a particular
> server byQuery Analyzer, you got the error message as follows:
> ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
> SQLAllocHandle on SQL_HANDLE_ENV failed.
> and you mentiond that you install some other softwares and after that, you
> encounter this problem, right?
> I wonder if you could login with system administrator account and
> re-install the MDAC then reboot your system. You could download MDAC2.8

---

at:

quote:

---

>

---

http://www.microsoft.com/downloads/...0fe3-c795-4b7d-

quote:

---

> b037-185d0506396c&DisplayLang=en
> Hope this helps and I am looking forward to your response! Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>

---

|||Hi Simon,
Thank you for using MSDN Newsgroup!
I would like to follow up on this issue and see if you still have questions
about this issue. Should you have any questions, please feel free to post
here. Looking forward to your reply!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi there, I see this thread is back from 2004. I am having an issue connecti
ng to a sql server located on another machine on my Intranet. I recieve the
following error:
unable to connect to server ...
server: Msg 17, Level 16, State 1
Microsoft odbc sql server driver odbnetlib sql server does not exit or acces
s
I tried to connect to other sql servers, and I got no problem, except for th
is particular server. any ideas'
From http://www.developmentnow.com/g/118...ry-Analyzer.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com|||1. Server does exist (server name spellign corrcet)?
2. You sure you have permission to access it?
3. Network library compatible?
"Efrain Juarez" <stranger_tepa@.hotmail.com> wrote in message
news:1bf20371-0394-4c54-a975-764a23b202d5@.developmentnow.com...
> Hi there, I see this thread is back from 2004. I am having an issue
> connecting to a sql server located on another machine on my Intranet. I
> recieve the following error:
> unable to connect to server ...
> server: Msg 17, Level 16, State 1
> Microsoft odbc sql server driver odbnetlib sql server does not exit or
> access
> I tried to connect to other sql servers, and I got no problem, except for
> this particular server. any ideas'
> From
> http://www.developmentnow.com/g/118...ry-Analyzer.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Problem connecting to SQL Server via Query Analyzer

SQL 2000/SP3
I recently ran into an issue where I receive an error whenever I try
to connect to my database on a particular server via the Query Analyzer.
The error I receive is
ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
SQLAllocHandle on SQL_HANDLE_ENV failed.
Anyone else run into this before?Do you only have problem connecting to this particular
server? Your ODBC driver may be messed up somehow. See if
you can update your MDAC.
Linchi
>--Original Message--
>SQL 2000/SP3
>I recently ran into an issue where I receive an error
whenever I try
>to connect to my database on a particular server via the
Query Analyzer.
>The error I receive is
>ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver
Manager]Driver's
>SQLAllocHandle on SQL_HANDLE_ENV failed.
>Anyone else run into this before?
>
>.
>|||I can't connect to any of our servers and only my machine seems to be
having this issue. I am guessing, that yes, the drivers are fried. I
had
installed some internal application software and then ka-boom... I can't
connect anywhere.
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:16a801c3df9b$3fb1d5d0$a601280a@.phx.gbl...
> Do you only have problem connecting to this particular
> server? Your ODBC driver may be messed up somehow. See if
> you can update your MDAC.
> Linchi
> >--Original Message--
> >
> >SQL 2000/SP3
> >
> >I recently ran into an issue where I receive an error
> whenever I try
> >to connect to my database on a particular server via the
> Query Analyzer.
> >
> >The error I receive is
> >
> >ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver
> Manager]Driver's
> >SQLAllocHandle on SQL_HANDLE_ENV failed.
> >
> >Anyone else run into this before?
> >
> >
> >.
> >|||Hi Simon,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From your information, when connecting to a database on a particular
server byQuery Analyzer, you got the error message as follows:
ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
SQLAllocHandle on SQL_HANDLE_ENV failed.
and you mentiond that you install some other softwares and after that, you
encounter this problem, right?
I wonder if you could login with system administrator account and
re-install the MDAC then reboot your system. You could download MDAC2.8 at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-
b037-185d0506396c&DisplayLang=en
Hope this helps and I am looking forward to your response! Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Yes, this corrected it!
Thanks!!
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:M$wbGO83DHA.568@.cpmsftngxa07.phx.gbl...
> Hi Simon,
> Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
> your issue.
> From your information, when connecting to a database on a particular
> server byQuery Analyzer, you got the error message as follows:
> ODBC: Msg 0, Level 16, State 1 [Microsoft][ODBC Driver Manager]Driver's
> SQLAllocHandle on SQL_HANDLE_ENV failed.
> and you mentiond that you install some other softwares and after that, you
> encounter this problem, right?
> I wonder if you could login with system administrator account and
> re-install the MDAC then reboot your system. You could download MDAC2.8
at:
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-
> b037-185d0506396c&DisplayLang=en
> Hope this helps and I am looking forward to your response! Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Hi Simon,
Thank you for using MSDN Newsgroup!
I would like to follow up on this issue and see if you still have questions
about this issue. Should you have any questions, please feel free to post
here. Looking forward to your reply!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi there, I see this thread is back from 2004. I am having an issue connecting to a sql server located on another machine on my Intranet. I recieve the following error:
unable to connect to server ...
server: Msg 17, Level 16, State 1
Microsoft odbc sql server driver odbnetlib sql server does not exit or access
I tried to connect to other sql servers, and I got no problem, except for this particular server. any ideas?
From http://www.developmentnow.com/g/118_2004_1_0_0_468284/Problem-connecting-to-SQL-Server-via-Query-Analyzer.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||1. Server does exist (server name spellign corrcet)?
2. You sure you have permission to access it?
3. Network library compatible?
"Efrain Juarez" <stranger_tepa@.hotmail.com> wrote in message
news:1bf20371-0394-4c54-a975-764a23b202d5@.developmentnow.com...
> Hi there, I see this thread is back from 2004. I am having an issue
> connecting to a sql server located on another machine on my Intranet. I
> recieve the following error:
> unable to connect to server ...
> server: Msg 17, Level 16, State 1
> Microsoft odbc sql server driver odbnetlib sql server does not exit or
> access
> I tried to connect to other sql servers, and I got no problem, except for
> this particular server. any ideas'
> From
> http://www.developmentnow.com/g/118_2004_1_0_0_468284/Problem-connecting-to-SQL-Server-via-Query-Analyzer.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Problem connecting to SQL Server via Query Analyzer

Hi there, I see this thread is back from 2004. I am having an issue connecting to a sql server located on another machine on my Intranet. I recieve the following error:
unable to connect to server ...
server: Msg 17, Level 16, State 1
Microsoft odbc sql server driver odbnetlib sql server does not exit or access
I tried to connect to other sql servers, and I got no problem, except for this particular server. any ideas?
From http://www.developmentnow.com/g/118_2004_1_0_0_468284/Problem-connecting-to-SQL-Server-via-Query-Analyzer.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
1. Server does exist (server name spellign corrcet)?
2. You sure you have permission to access it?
3. Network library compatible?
"Efrain Juarez" <stranger_tepa@.hotmail.com> wrote in message
news:1bf20371-0394-4c54-a975-764a23b202d5@.developmentnow.com...
> Hi there, I see this thread is back from 2004. I am having an issue
> connecting to a sql server located on another machine on my Intranet. I
> recieve the following error:
> unable to connect to server ...
> server: Msg 17, Level 16, State 1
> Microsoft odbc sql server driver odbnetlib sql server does not exit or
> access
> I tried to connect to other sql servers, and I got no problem, except for
> this particular server. any ideas?
> From
> http://www.developmentnow.com/g/118_2004_1_0_0_468284/Problem-connecting-to-SQL-Server-via-Query-Analyzer.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com