ASP timeout errors

[mimivdg2002]

I have an ASP page that is accessing a SQL Server database to display data. Everything works fine on the development box. When I move this to production, I got the following error:

"Active Server Pages error 'ASP 0113'

Script timed out

The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools. "

I then used Server.ScriptTimeout = 180 to increase the timeout to 3 min. I now get a different error:

"error '8004e002'
The root transaction wanted to commit, but transaction aborted."

Does anybody have any idea why I'm getting these errors? As I said, everything works fine on the dev box, the errors only appear on the production even though the database on dev is identical to the database on production.

Thanks
M

 

[Sheco]

What differences might you have between the dev and live box?

Does your code need to perhaps use a different ADO ConnectionString?

Perhaps there is a difference in permissons between the two environments? Either account permissions or database permissons might be the cause.

Also do both environments have the same version external objects used in your code? Perhaps a different version of the MDAC for example?

 

[mimivdg2002]

It's not a problem with ADO ConnectionString, other ASP pages on the production box use it to connect the database and fetch data. Account or database permissions are not the cause either, as I said other ASP pages connect to the database fine. The problem is only with this one ASP page.

 

[Sheco]

Well, something is obviously different...

 

[yankinoz]

How long does this transaction run for in both environments? Are you using COM+ transactions, ADO, ASP or Database?
Some things to consider:
If running a COM+ transaction check the Transaction timeout value in Component Service.
If running a transaction via ADO or in a stored proc check the command.timeout setting. I think it is 15 seconds by default.

The problem is not in the ASP but in the length of the transaction. It is exceeding the time alloted.