[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

[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

[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

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi,
Our web applications are using COM objects to call sps in
SQL server. We are getting a lot of timeout errors. If
you know why this happens and any fixes pls let me know.
The error looks like following:
[Microsoft][ODBC SQL Server Driver]Timeout expiredhi
I also face to that prob.At last i found the solution for the "timeout
expired" problem. what we
have to do is, we have to edit two windows files calld
,"c:\winnt\system32\drives\ect\hosts.txt"
and "c:\winnt\system32\drives\ect\Lhosts.txt"
we should enter sql server IP and name like this
169.192.2.100 sqlserverName
in both files
Thanks,
indika
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJ
hi
goto the server properties.then there is a property called connection time.
check it and give the appropiate time on this

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas

"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.
|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:

> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>
|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.

:confused:

Could you please help me with that?
Thanks
DJCheck out this page.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313661|||The link in the previous post is for a connection timeout using SQL Server 7. It does not apply to running a query on SQL Server 2000.|||SQL Server 2000's default timeout period it 600 seconds (10 minutes). If you change it to zero (0), that's infinite. How long is it taking to timeout?

If you run a long query through the Enterprise Manager, it will timeout after 30 seconds. MS's answer to this is to use the Query Analyzer (which should not timeout). I've run a 14-hour query through SQL Query Analyzer before.

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a vie
w
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subjec
t
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:

> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will contin
ue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the Vie
w
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In t
he
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably bein
g
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
[vbcol=seagreen]
> Unfortunately, there is no error number, and the error message is the subj
ect
> line of this post. Also, I am not specifying any parameters at all, as th
is
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
>|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
[vbcol=seagreen]
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably be
ing
> blocked by current processes and are getting a LOCK TIMEOUT (which is real
ly
> a Lock Wait timeout). You do not have the ability to modify the Lock Timo
ut
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selecte
d
> database, but that property is a timeout setting for RPC queries, not SQLE
M
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
>

[Microsoft][ODBC SQL Server Driver] Timeout expired

I am getting this error when I try and look at the Top 1000 records of a view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.What is the exact error number and message? There are several types of
timeouts. If you are not specifying the correct parameter, it will continue
to timeout on that type.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
I am getting this error when I try and look at the Top 1000 records of a
view
that I have created, in Enterprise Manager. If I copy the SQL for the View
into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
Enterprise Manager Properties Advanced window, I have set Query timeout to
both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
suggestions would be greatly appreciated.|||Unfortunately, there is no error number, and the error message is the subject
line of this post. Also, I am not specifying any parameters at all, as this
is happening in Enterrpise Manager, Views, right-click on view, Open View,
Return Top.
"AnthonyThomas" wrote:
> What is the exact error number and message? There are several types of
> timeouts. If you are not specifying the correct parameter, it will continue
> to timeout on that type.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> I am getting this error when I try and look at the Top 1000 records of a
> view
> that I have created, in Enterprise Manager. If I copy the SQL for the View
> into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> Enterprise Manager Properties Advanced window, I have set Query timeout to
> both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> suggestions would be greatly appreciated.
>
>|||If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
value to 0 and you are still getting the message, then you are probably being
blocked by current processes and are getting a LOCK TIMEOUT (which is really
a Lock Wait timeout). You do not have the ability to modify the Lock Timout
setting through EM; however, you can through Query Analyzer.
The Properties, Advanced Window does not exist for SQLEM. There is a
Properties, Connections, Remote Connections area for the currently selected
database, but that property is a timeout setting for RPC queries, not SQLEM
DMO.
Sincerely,
Anthony Thomas
"Gary W. Hinkel" wrote:
> Unfortunately, there is no error number, and the error message is the subject
> line of this post. Also, I am not specifying any parameters at all, as this
> is happening in Enterrpise Manager, Views, right-click on view, Open View,
> Return Top.
> "AnthonyThomas" wrote:
> > What is the exact error number and message? There are several types of
> > timeouts. If you are not specifying the correct parameter, it will continue
> > to timeout on that type.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > I am getting this error when I try and look at the Top 1000 records of a
> > view
> > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > suggestions would be greatly appreciated.
> >
> >
> >|||Thanks for all your assisstance Anthony. This has cleared things up for me
as far as SQLEM is concerned (ie: I won't use it to display views, I'll use
QA instead).
I had initially thought that if I could resolve the timeout issue in SQLEM,
then the same issues in getting data into MapPoint, Excel, etc. through an
ODBC connection could be resolved as well.
Now at least, I can focus my efforts on getting the View data into
MapPoint/Excel etc.
Thanks again Anthony.
Sincerely,
Gary W. Hinkel
"AnthonyThomas" wrote:
> If you've changed the SQLEM, Tools, Options, Advanced Tab, Query Timeout
> value to 0 and you are still getting the message, then you are probably being
> blocked by current processes and are getting a LOCK TIMEOUT (which is really
> a Lock Wait timeout). You do not have the ability to modify the Lock Timout
> setting through EM; however, you can through Query Analyzer.
> The Properties, Advanced Window does not exist for SQLEM. There is a
> Properties, Connections, Remote Connections area for the currently selected
> database, but that property is a timeout setting for RPC queries, not SQLEM
> DMO.
> Sincerely,
>
> Anthony Thomas
>
> "Gary W. Hinkel" wrote:
> > Unfortunately, there is no error number, and the error message is the subject
> > line of this post. Also, I am not specifying any parameters at all, as this
> > is happening in Enterrpise Manager, Views, right-click on view, Open View,
> > Return Top.
> >
> > "AnthonyThomas" wrote:
> >
> > > What is the exact error number and message? There are several types of
> > > timeouts. If you are not specifying the correct parameter, it will continue
> > > to timeout on that type.
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > --
> > >
> > > "Gary W. Hinkel" <GaryWHinkel@.discussions.microsoft.com> wrote in message
> > > news:E43E35ED-809B-4DF4-8869-0EE3A49F9EEF@.microsoft.com...
> > > I am getting this error when I try and look at the Top 1000 records of a
> > > view
> > > that I have created, in Enterprise Manager. If I copy the SQL for the View
> > > into Query Analyzer, it returns results fine (in approx. 2 minutes). In the
> > > Enterprise Manager Properties Advanced window, I have set Query timeout to
> > > both 0 (never times out?) and 60000 (100 minutes?) to no avail. Any
> > > suggestions would be greatly appreciated.
> > >
> > >
> > >

[Microsoft][ODBC SQL Server Driver] Timeout Expired

Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro PC. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
Could you please help me with that?
Thanks
DJhi
goto the server properties.then there is a property called connection time
.
check it and give the appropiate time on this

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users &
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.
Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.
|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post the
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>
|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users
&
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post th
e
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in messa
ge
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft] [ODBC SQL Server Driver] Timeout Expired

I've tried every websearch possible to try and get a solution for this problem but can't.

Development Software:
SQL Server 2000
Enterprise Manager 8.0
Query Analyzer 8.00.194

Error:
When I run a mildly complex view in Enterprise Manager I get the error:[Microsoft][ODBC SQL Server Driver]Timeout Expired
after about 30 seconds.

When I copy and paste and run the exact same code in Query Analyzer the Query runs for longer than 30 seconds and runs until completion. Now my question is since this apparently seems to be an Enterpise Manager problem and not on the server end, where do I go in Enterprise Manager to change that setting? I've looked everywhere in Enterpise manager and can't find a "command timeout" setting.

Thanks!http://vyaskn.tripod.com/watch_your_timeouts.htm|||http://vyaskn.tripod.com/watch_your_timeouts.htm

Thanks for the link. Am I looking at the COM+ section on that webpage because the other two don't look like they apply to Enterprise Manager? I see the default timeouts for the COM+ settings are 60 seconds when Enterprise Manager is timing out at about 30 seconds. I tried upping the first setting in the COM+ section to 10 minutes to no avail. I can't locate the "common" folder to up the second setting under the COM+ section (DB.StoredProcedure).|||a quick search netted me this little tidbit:
QA has no time limit on how long you can inspect results, and you cannot adjust the timeout in Enterprise Manager.

Hence, do what you are trying to do in QA, and save yourself the headache.|||Here's one place to check (from BOL) ... open QA & run sp_configure:



query wait Option

In Microsoft SQL Server, memory-intensive queries, such as those involving sorting and hashing, are queued when there is not enough memory available to run the query. The query times out after a set amount of time calculated by SQL Server (25 times the estimated cost of the query) or the time amount specified by the non-negative value of the query wait.
Use the query wait option to specify the time in seconds (from 0 through 2147483647) that a query waits for resources before timing out. If the default value of -1 is used, or if 1 is specified, then the time-out is calculated as 25 times of the estimated query cost.

http://www.dbforums.com/mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/Basics/important.gif
Important A transaction containing the waiting query may hold locks while the query waits for memory. In rare situations, it is possible for an undetectable deadlock to occur. Decreasing the query wait time lowers the probability of such deadlocks. Eventually, a waiting query will be terminated and the transaction locks released. However, increasing the maximum wait time may increase the amount of time for the query to be terminated. Changes to this option are not recommended.

query wait is an advanced option. If you are using the sp_configure system stored procedure to change the setting, you can change query wait only when show advanced options is set to 1. The setting takes effect immediately (without a server stop and restart).
To set the query wait option
http://www.dbforums.com/mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/plus.gifTransact-SQL (http://javascript<b></b>:hhobj_1.Click())
http://www.dbforums.com/mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/plus.gifSQL-DMO (http://javascript<b></b>:hhobj_2.Click())

See Also


RECONFIGURE (http://javascript<b></b>:hhobj_3.Click())
Setting Configuration Options (mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\adminsql.chm::/ad_config_3wmr.htm)
sp_configure (http://javascript<b></b>:hhobj_4.Click())
Thread and Fiber Execution (http://javascript<b></b>:hhobj_5.Click())

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[Microsoft] [ODBC SQL Server Driver] Timeout expired

Hi, Everyone,

I have a SQL 2000 cluster with sp4. I used SQL QUERY Analyzer to running DBCC CHECKDB for 2 of user’s databases (one is 110 GB and other 5 GB) and get the following message: [Microsoft] [ODBC SQL Server Driver] Timeout expired.I am running same DBCC CHECKDB against system databases or other small users’ databases are fine.

I can get resulted back from T-SQL (DBCC CHECKDB) against these 2 user databases and I checked sp_configure with other server, I can not find the difference.

Can someone help me out?

KT

Are you executing CHECKDB against 2 of those databases at the same time?

Also check event viewer and SQL error logs for any sort of slow performance with any of the hardware or components on this server.

Have you tried scheduling the same using a SQLagent job?

Have you applied or tested the sp4 hotfix?

|||

I ran dbcc checkdb agaist each database at each time. There has no information logon at even view and SQL log when I got time out message.

I haven't schedule this dbcc checkdb at SQL agent job yet.

I only applied hot fix -KB903086 and brought SQL server level to v8.00 2140.

|||ODBC Sql server drive Timeout expires error message getting when I connect to sql200 server data base with query analyzer

[165]ODBC Error 0 Timeout expired[SQLSTATE HYT00]

sql server 2000 8.00.194
Microsoft Windows 2000 Service Pack 2

I looked into my sqlserver agent log and found the following

ODBC Error 0 Timeout expired[SQLSTATE HYT00]
logon to server local '( failed)' (Job manager)

I have no idea what that means but it did keep out users for a minute or more.
The threads found on this forum almost all point to reccuring situations
mine is a sporadic one time issue.
Is it Ok to conclude it is a network error as I did?

TIA
VinceVincento Harris (wumutek@.yahoo.com) writes:
> sql server 2000 8.00.194

That's an SQL Server with no service pack. I strongly encouarge you to
download and install Service Pack 3.

> I looked into my sqlserver agent log and found the following
> ODBC Error 0 Timeout expired[SQLSTATE HYT00]
> logon to server local '( failed)' (Job manager)
> I have no idea what that means but it did keep out users for a minute or
> more. The threads found on this forum almost all point to reccuring
> situations mine is a sporadic one time issue.
> Is it Ok to conclude it is a network error as I did?

This may be a correct conclusion in the end, but it is not the most likely.

The ODBC error "Timeout expired" means that a query did not start to
return rows with the timeout period, which by default is 30 seconds.
The reason for this could be that the query itself needed longer time
to execute, because of large amounts of data to search and/or poor
indexing. It could also be that the query was blocked by another query,
and that query was long-running. In fact it does not have to be a query
as such that was blocking, but a process holding locks because of
an earlier abandoned query, which was not properly handled.

All this could have been started by some abnormal event like a
network glitch. However, it is much more likely that there was
some inappropriate SQL statement somewhere.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp