Database Results Error Description: [Microsoft][ODBC SQL Server Driver]Timeout expired

[Jace]

Does anyone know why the database command timeout setting does not appear to work in Frontpage 2002?

This is the error that I get when I try to pull data from an SQL Server 7.0 SP4 database using one of the ASP pages I have developed using Frontpage 2002. Other pages work just fine as long as the query doesn't take longer than 30 seconds.

"Database Results Error
Description: [Microsoft][ODBC SQL Server Driver]Timeout expired
Number: -2147217871 (0x80040E31)
Source: Microsoft OLE DB Provider for ODBC Drivers"

I get this after about 30 seconds. If I re-submit the page enough times I can get the results because the SQL Server finally caches enough information in memory to beat the clock.

What is irritating is that in Frontpage, under Tools, Web Settings, Database under the connection settings I can modify the Command Timeout value to be 60, 90 or whatever, but it never has any effect. The query still times out at about 30 seconds.

My SQL Server Query Timeout value is 0, so running the query from Query Analyzer works fine.

Is the command timeout setting in Frontpage just broken? Is there some way around this?

TIA.

 

[Kevin Spencer]

Not sure what version of SQL Server you're using, but the following MS KB
article may be helpful:

http://support.microsoft.com/default.aspx?scid=kb;en-us;313661

HTH,

Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
http://www.takempis.com
Some things just happen.
Everything else occurs.

Does anyone know why the database command timeout setting does not appear to
work in Frontpage 2002?

This is the error that I get when I try to pull data from an SQL Server 7.0
SP4 database using one of the ASP pages I have developed using Frontpage
2002. Other pages work just fine as long as the query doesn't take longer
than 30 seconds.

"Database Results Error
Description: [Microsoft][ODBC SQL Server Driver]Timeout expired
Number: -2147217871 (0x80040E31)
Source: Microsoft OLE DB Provider for ODBC Drivers"

I get this after about 30 seconds. If I re-submit the page enough times I
can get the results because the SQL Server finally caches enough information
in memory to beat the clock.

What is irritating is that in Frontpage, under Tools, Web Settings, Database
under the connection settings I can modify the Command Timeout value to be
60, 90 or whatever, but it never has any effect. The query still times out
at about 30 seconds.

My SQL Server Query Timeout value is 0, so running the query from Query
Analyzer works fine.

Is the command timeout setting in Frontpage just broken? Is there some way
around this?

TIA.

 

[Jace]

??

Check my original post, SQL Server 7.0 SP4.

Unfortunately, that KB article doesn't apply since it says that that
particular problem was fixed in SP4 and since the problem I am having is a
different one anyway.

Thanks anyway.