[TCP/IP Sockets] Specified SQL Server not found

Connections, using ODBC (version 3.520) and from a couple web apps, to one of
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOpen
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Server
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipes
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.com
On the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon

[TCP/IP Sockets] Specified SQL Server not found

Connections, using ODBC (version 3.520) and from a couple web apps, to one o
f
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOp
en
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Se
rver
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipe
s
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.comOn the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pk
There is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk
|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well :))
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
--
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well :)) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my PERL / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by PERL script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my PERL / ASP aplications seems to behave as if
> it were some.
> PERL script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by PERL script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so ther
e
> are definitely practical limitations. Make sure that all your code drops t
he
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk