Uttecetbace
New Member
Good day!I'm experiencing an issue with an ASP classic application we have. We were working on the SQL connection management and everything was perfect, so we deployed on another environment for the users to test and one of the ASP page hungs for 90 sec and results in:\[code\]Active Server Pages error 'ASP 0113' Script timed out \[/code\]So, I tried adding some debug code. What I used is:\[code\]Response.End\[/code\]To check where it was hanging. I finally discovered that it was the new function we developed that was hanging, obviously! Here's a little extract:\[code\]Dim sqlConnSet sqlConn = SessionConnection("SQLConnection")set rsIDXMDL = SQLQuery(sqlConn, sQuery)\[/code\]If I put a Response.End just before the call to SessionConnection(), the process stops. If I put the Response.End after the call to SessionConnection(), the page hangs for 90 sec. That made me think: "Bingo! Something inside fails!" So, just for fun, I put a Response.End at the first line of the function, like:\[code\]Function SessionConnection(SessVarName) Response.End [...]\[/code\]I'm sure you can guess what happened!!! THE PAGE STILL HANGS!!! How is this possible?