Added: November/15/2005 at 5:19am | IP Logged

My ASP page has script timeout of 900 seconds. The ADO command and connection timeout in the COM is also 900 seconds. Until last week, it seemed to be working fine. But since yesterday it gives me a timeout error well before 5 minutes. There seems to be an erratic behavior. It suddenly works fine and then it does not (all this happens without any code change).

I checked the IIS settings, it shows the timeout setting as 900 seconds. I even checked the SQL Query timeout which is 0.

I then tried changing the timeout to 0 in the COM. I had kept a WAITFOR DELAY '00:15:00' statement in my stored procedure used. It was working fine even despite the delay of 15 minutes. There was no timeout error.

Can anybody throw light on why such an erratic behavior? What can be the issue and how can I address the same?

The task is very critical on the business point of view and cannot throw a timeout error.

Kindly reply in this forum or reply to sriram_natesan@infosys.com

Thanks in Advance,

Sriram

Added: November/15/2005 at 6:25pm | IP Logged

to make it more clear for what I am looking for:

We know that override of default timeout can be done through having script timeout value overridden in the ASP page (set to 900)

And have commandTimeout and Connectiontimeout properties set in the Com layer (we are using ADO)

The problem is that this code works fine in some servers but does not in other servers.

All the articles/posts point to default timeout values being overridden by the setting done above but we don’t know what can override

These settings.

Obviously, this seems to be some server/IIS setting /environment issue rather than a code level issue since it should not have worked in one server and not on the other.