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

[Jace]

I have been getting this error:

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

for some time now and have contacted Microsoft Frontpage paid support. I
have been on the phone with a tech for about 5 hours and still do not have
an answer. I am using Frontpage 2002, IIS 4.0 and SQL Server 7.0 SP4.

The tech is forwarding the issue as a Request for Comment, whatever that is.
I think the answer is that Frontpage 2000 and 2002 are broken and not
setting the CommandTimeout line properly.

Has anyone else seen this issue?

 

[Guest]

CAUSE: the Query was timing out because the default command timeout of the
connection (30 seconds) was shorter that the amount of time the query needed to
execute
RESOLUTION:
- Add an index to the table and that speed the query up so that it did not time
out.
- Customer could also change the command timeout in front page by:
1. Select insert database results
2. Use a new database connection and click create
3. Select connection and hit modify button
4. Make sure system datasource name is selected. If not select it and hit browse
to select system DSN.
5. Click advanced and increase connection and command timeouts from 15 and 30
respectively
6. Hit OK, then OK again

 

[Jace]

Thanks for the reply, unfortunately, the command timeout setting in
Frontpage 2000 / 2002 are broken...

Thanks anyway.

 

[jon spivey]

Hi,
obviously it shoudn't take 30 seconds to connect to a SQL Server - even if
it was located at the other side of the planet. To try and narrow the
problem down can you put up a page with this code -
<%
set oConn = server.createobject("adodb.connection")
oConn.open
"provider=sqloledb;server=10.10.10.10;database=yourdb;uid=you;pwd=secret"
%>
replacing 10.10.10.10 with the ip of your sql server and the uid and pwd as
appropriate. This should help us establish if the problem is with your sql
server or fp or your network connection.

 

[Jace]

Thanks for the reply Jon.

I should have mentioned that the Frontpage tech that I am working with at
Microsoft has pretty much duplicated this issue on their system in that when
she sets the command timeout down to zero, it is ignored on her system as
well. (I don't think she had a query that would run longer than 30 seconds
so we couldn't duplicate the EXACT scenario on her system, but we have
established that the command timeout setting in Frontpage 2002 is broken)

Also, it's not the connection timeout that is a problem, my machine and the
sql server are on the same 100Mbit switch. It's the command timeout. I run
some tough datepart queries on a database that's about 1GB in size. If I use
an .asp file that I got from Microsoft (I think from their ASP department)
the query will run as long as it is set in the command timeout that is
specified within that file. However, if I let Frontpage build the .asp file
and the global.asa file, the command timeout specified in the global.asa
file is completely ignored.

You should be able to duplicate this issue on your own system by setting the
command timeout, in the Frontpage 2000/2002 GUI, for one of your databases
to be zero or 1 second, then try running a query that takes longer than 1
second, using an .asp page that Frontpage built, and you will see that it
will complete, when it should not. Also, if you have a query that takes
longer than 30 seconds, it will never complete due to the command timeout
setting being ignored.

Thanks for taking the time to reply.