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
Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts
Tuesday, March 20, 2012
[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
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
Thursday, March 8, 2012
[ODBC SQL Server Driver]Timeout expired
We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
[ODBC SQL Server Driver]Timeout expired
We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e r"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e r"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
[ODBC SQL Server Driver]Timeout expired
We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied)
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expire
If anyone has any ideas as to possible reasons, it would be immensely appreciated
Any help would be greatly appreciated
Thank you
- A l p e"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
SP3a applied)
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expire
If anyone has any ideas as to possible reasons, it would be immensely appreciated
Any help would be greatly appreciated
Thank you
- A l p e"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
[ODBC SQL Server Driver]Timeout Error
Hi,
I receive this intermmitent "[ODBC SQL Server Driver]
Timeout Error" eventhough i have set the Query Timeout in
Enterprise Manager to '0' (unlimited). However when
running the query in Query Analyser, it returns a result
in just a few seconds.
Is there someplace else that i need to change the timeout
setting? Or is there some other reason that this error
occasionally comes out?
Any help is much appreciated, thx!!
JaclynWhen it's intermittent, it can often be related to activity
on the server at the time the query is running. You'd want
to check locking, blocking and also check for data, log file
size changes that can contribute to timeouts (e.g. with
autogrow, autoshrink, manually growing or shrinking files)
-Sue
On Wed, 9 Jun 2004 01:45:05 -0700, "Jaclyn"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>I receive this intermmitent "[ODBC SQL Server Driver]
>Timeout Error" eventhough i have set the Query Timeout in
>Enterprise Manager to '0' (unlimited). However when
>running the query in Query Analyser, it returns a result
>in just a few seconds.
>Is there someplace else that i need to change the timeout
>setting? Or is there some other reason that this error
>occasionally comes out?
>Any help is much appreciated, thx!!
>Jaclyn
I receive this intermmitent "[ODBC SQL Server Driver]
Timeout Error" eventhough i have set the Query Timeout in
Enterprise Manager to '0' (unlimited). However when
running the query in Query Analyser, it returns a result
in just a few seconds.
Is there someplace else that i need to change the timeout
setting? Or is there some other reason that this error
occasionally comes out?
Any help is much appreciated, thx!!
JaclynWhen it's intermittent, it can often be related to activity
on the server at the time the query is running. You'd want
to check locking, blocking and also check for data, log file
size changes that can contribute to timeouts (e.g. with
autogrow, autoshrink, manually growing or shrinking files)
-Sue
On Wed, 9 Jun 2004 01:45:05 -0700, "Jaclyn"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>I receive this intermmitent "[ODBC SQL Server Driver]
>Timeout Error" eventhough i have set the Query Timeout in
>Enterprise Manager to '0' (unlimited). However when
>running the query in Query Analyser, it returns a result
>in just a few seconds.
>Is there someplace else that i need to change the timeout
>setting? Or is there some other reason that this error
>occasionally comes out?
>Any help is much appreciated, thx!!
>Jaclyn
[ODBC SQL Server Driver]Timeout Error
Hi,
I receive this intermmitent "[ODBC SQL Server Driver]
Timeout Error" eventhough i have set the Query Timeout in
Enterprise Manager to '0' (unlimited). However when
running the query in Query Analyser, it returns a result
in just a few seconds.
Is there someplace else that i need to change the timeout
setting? Or is there some other reason that this error
occasionally comes out?
Any help is much appreciated, thx!!
Jaclyn
When it's intermittent, it can often be related to activity
on the server at the time the query is running. You'd want
to check locking, blocking and also check for data, log file
size changes that can contribute to timeouts (e.g. with
autogrow, autoshrink, manually growing or shrinking files)
-Sue
On Wed, 9 Jun 2004 01:45:05 -0700, "Jaclyn"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>I receive this intermmitent "[ODBC SQL Server Driver]
>Timeout Error" eventhough i have set the Query Timeout in
>Enterprise Manager to '0' (unlimited). However when
>running the query in Query Analyser, it returns a result
>in just a few seconds.
>Is there someplace else that i need to change the timeout
>setting? Or is there some other reason that this error
>occasionally comes out?
>Any help is much appreciated, thx!!
>Jaclyn
I receive this intermmitent "[ODBC SQL Server Driver]
Timeout Error" eventhough i have set the Query Timeout in
Enterprise Manager to '0' (unlimited). However when
running the query in Query Analyser, it returns a result
in just a few seconds.
Is there someplace else that i need to change the timeout
setting? Or is there some other reason that this error
occasionally comes out?
Any help is much appreciated, thx!!
Jaclyn
When it's intermittent, it can often be related to activity
on the server at the time the query is running. You'd want
to check locking, blocking and also check for data, log file
size changes that can contribute to timeouts (e.g. with
autogrow, autoshrink, manually growing or shrinking files)
-Sue
On Wed, 9 Jun 2004 01:45:05 -0700, "Jaclyn"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>I receive this intermmitent "[ODBC SQL Server Driver]
>Timeout Error" eventhough i have set the Query Timeout in
>Enterprise Manager to '0' (unlimited). However when
>running the query in Query Analyser, it returns a result
>in just a few seconds.
>Is there someplace else that i need to change the timeout
>setting? Or is there some other reason that this error
>occasionally comes out?
>Any help is much appreciated, thx!!
>Jaclyn
[ODBC SQL Server Driver]Connot generate SSPI Context Anybody ...
We get the following error: Connection Failed:
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : Windows 2000 sql server 7.x
but on Windows XP it goes very well.
any ideas ?Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:
>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : Windows 2000 sql server 7.x
>
>but on Windows XP it goes very well.
>any ideas ?
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : Windows 2000 sql server 7.x
but on Windows XP it goes very well.
any ideas ?Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:
>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : Windows 2000 sql server 7.x
>
>but on Windows XP it goes very well.
>any ideas ?
[ODBC SQL Server Driver]Connot generate SSPI Context Anybody ...
We get the following error: Connection Failed:
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : windows 2000 sql server 7.x
but on windows xp it goes very well.
any ideas ?
Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:
>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : windows 2000 sql server 7.x
>
>but on windows xp it goes very well.
>any ideas ?
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : windows 2000 sql server 7.x
but on windows xp it goes very well.
any ideas ?
Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:
>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : windows 2000 sql server 7.x
>
>but on windows xp it goes very well.
>any ideas ?
[ODBC SQL Server Driver]Communication Link Failure
I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?
You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL server
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?
|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?
You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL server
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?
|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
[ODBC SQL Server Driver]Communication link failure
This error is being generated from a SQLServer2000 database being accessed
via ASP over the web, any suggestions for fixing it?
THANKS
--
John9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John
via ASP over the web, any suggestions for fixing it?
THANKS
--
John9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John
[ODBC SQL Server Driver]Communication link failure
This error is being generated from a SQLServer2000 database being accessed
via ASP over the web, any suggestions for fixing it?
THANKS
John
9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John
via ASP over the web, any suggestions for fixing it?
THANKS
John
9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John
[ODBC SQL Server Driver]Communication Link Failure
I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regardsIs there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott
Originally posted by attinder
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regards|||We might have used DTS but we are using the same socket with different applications. They may or may not use SQL server|||Hi Hugh,
You indicated that connecting to AS 400 requires quite a bit of configuration. Can you please elaborate on this point? I need it urgently.
Thanks
Originally posted by hmscott
Is there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott|||Okay, here is what I remember:
1. We used the IBM Client Access Express drivers. We are using V5R1M0 with SP SI02795. The SP is critical, since there is a bug in the original release which won't let you connect to a database w/ more than 9 characters in the name (thanks IBM!).
2. The main hassle is that the driver always prompts you for a user name/password unless you config it appropriately. The prompt is not visible when the DTS package runs as a job (since it appears on the virtual desktop of the SQL Agent service account).
If that doesn't make sense to you, stop. Read up on SQL Service accounts and make sure that SQL Agent is set up to run under a service account.
3. Okay, proceeding ahead:
a. The SQL Agent account must be set up with 10 characters or less (SQLAdmin is okay, SQLAgentAccount is not).
b. Set up an account on the AS/400 with the same name as the SQL Agent account.
c. Set the password for both accounts to be identical (and again, no more than 10 characters)
4. Use the ODBC Administration GUI to set up a new connection. Specify that the connection should use the Windows user name/account information. It is helpful to do this set up while logged in as the SQL Agent Service account. It's not critical, but it is helpful.
Some additional notes:
1. We are using MS W2K SP4 (Advanced)
2. We are using MS SQL 2K (SP3a + MS03-031)
3. To verifiy that you have everything working correctly, log in to the server as the SQL Service account. Open a DTS package. Create a connection object for the AS/400. Create a destination connection object. Add a data pump task. When you specify the details of the data pump task, you should never be prompted for the password.
Alternatively: A friend of mine has had good success with the Hit Software OLE DB drivers for AS/400. I have never used them/don't know anything about them. But they may be worth trying. www.hitsw.com.
HTH,
hmscott
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regardsIs there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott
Originally posted by attinder
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regards|||We might have used DTS but we are using the same socket with different applications. They may or may not use SQL server|||Hi Hugh,
You indicated that connecting to AS 400 requires quite a bit of configuration. Can you please elaborate on this point? I need it urgently.
Thanks
Originally posted by hmscott
Is there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott|||Okay, here is what I remember:
1. We used the IBM Client Access Express drivers. We are using V5R1M0 with SP SI02795. The SP is critical, since there is a bug in the original release which won't let you connect to a database w/ more than 9 characters in the name (thanks IBM!).
2. The main hassle is that the driver always prompts you for a user name/password unless you config it appropriately. The prompt is not visible when the DTS package runs as a job (since it appears on the virtual desktop of the SQL Agent service account).
If that doesn't make sense to you, stop. Read up on SQL Service accounts and make sure that SQL Agent is set up to run under a service account.
3. Okay, proceeding ahead:
a. The SQL Agent account must be set up with 10 characters or less (SQLAdmin is okay, SQLAgentAccount is not).
b. Set up an account on the AS/400 with the same name as the SQL Agent account.
c. Set the password for both accounts to be identical (and again, no more than 10 characters)
4. Use the ODBC Administration GUI to set up a new connection. Specify that the connection should use the Windows user name/account information. It is helpful to do this set up while logged in as the SQL Agent Service account. It's not critical, but it is helpful.
Some additional notes:
1. We are using MS W2K SP4 (Advanced)
2. We are using MS SQL 2K (SP3a + MS03-031)
3. To verifiy that you have everything working correctly, log in to the server as the SQL Service account. Open a DTS package. Create a connection object for the AS/400. Create a destination connection object. Add a data pump task. When you specify the details of the data pump task, you should never be prompted for the password.
Alternatively: A friend of mine has had good success with the Hit Software OLE DB drivers for AS/400. I have never used them/don't know anything about them. But they may be worth trying. www.hitsw.com.
HTH,
hmscott
[ODBC SQL Server Driver][SQL Server]Transaction (Process ID X) was deadlocked
I am not concerned about seeing an occasional deadlock. I am wondering
why I am seeing unprintable characters now when SQL is trying to tell
me what it deadlocked with. This did not happen in our old environment
and our SQL DBA was unable to explain.
Thanks.
-Jeff-Hi
Check that sysmessages is not corrupted and that the languages installed are
ok (both OS and SQL Server). You may also want to see what the sessions
language is.
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130674174.697516.35360@.g43g2000cwa.googlegroups.com...
>I am not concerned about seeing an occasional deadlock. I am wondering
> why I am seeing unprintable characters now when SQL is trying to tell
> me what it deadlocked with. This did not happen in our old environment
> and our SQL DBA was unable to explain.
> Thanks.
> -Jeff-
>
why I am seeing unprintable characters now when SQL is trying to tell
me what it deadlocked with. This did not happen in our old environment
and our SQL DBA was unable to explain.
Thanks.
-Jeff-Hi
Check that sysmessages is not corrupted and that the languages installed are
ok (both OS and SQL Server). You may also want to see what the sessions
language is.
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130674174.697516.35360@.g43g2000cwa.googlegroups.com...
>I am not concerned about seeing an occasional deadlock. I am wondering
> why I am seeing unprintable characters now when SQL is trying to tell
> me what it deadlocked with. This did not happen in our old environment
> and our SQL DBA was unable to explain.
> Thanks.
> -Jeff-
>
[ODBC SQL Server Driver] Timeout Expired - How to fix
I am running SQL (Selects and Deletes) against a large
table in a database and am getting Timeout Expired. I am
using Enterprise Manager (Right Click on Table and select
Query). Is there a setting that I need to change to allow
a long running query? It works fine in the SQL Query
Analyzer.
SELECT COUNT(*) AS Expr1
FROM CallDetailThe timeout is a property of the connection to the server. Select your
instance in the Enterprise manager, select properties. Then on the
connection tab change the timeout. (Zero means infinite)
Bruce
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail|||Better indexing / design so that the query doesn't take so long? Use Query
Analyzer rather than Enterprise Manager (see http://www.aspfaq.com/2455)?
You could kludge it up by increasing your timeouts, but this is like
bandaging a fever.
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail
table in a database and am getting Timeout Expired. I am
using Enterprise Manager (Right Click on Table and select
Query). Is there a setting that I need to change to allow
a long running query? It works fine in the SQL Query
Analyzer.
SELECT COUNT(*) AS Expr1
FROM CallDetailThe timeout is a property of the connection to the server. Select your
instance in the Enterprise manager, select properties. Then on the
connection tab change the timeout. (Zero means infinite)
Bruce
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail|||Better indexing / design so that the query doesn't take so long? Use Query
Analyzer rather than Enterprise Manager (see http://www.aspfaq.com/2455)?
You could kludge it up by increasing your timeouts, but this is like
bandaging a fever.
"Michael Orechoff" <anonymous@.discussions.microsoft.com> wrote in message
news:0ee701c39d6b$f0e86750$a401280a@.phx.gbl...
> I am running SQL (Selects and Deletes) against a large
> table in a database and am getting Timeout Expired. I am
> using Enterprise Manager (Right Click on Table and select
> Query). Is there a setting that I need to change to allow
> a long running query? It works fine in the SQL Query
> Analyzer.
> SELECT COUNT(*) AS Expr1
> FROM CallDetail
Tuesday, March 6, 2012
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi:
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi:
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)