I´ve a page working perfectly when the query requested for it is small, but when it´s a large query (working with SQL Server Connection), after approximaticly 90 minutos I get the message error "The page cannot be displayed.". The point here is that I have the scriptTimeout unlimited and the problem continuous.. do you have any idea what it can be?!
The page also has Response.buffer true and I can see the page working without problem until the message error appears.
I´m sure that I don´t have any problem with my query and anything similar with the code.
It looks like IIS "problem" to me... do you have any idea?
Thanks for your help unatratnag, but the point is that the page is working perfectly when running with a small query, the query created depends of the a session variable. I´m sure the code isn´t getting looping. Take a look at the bit code:
'it executes the mdxQuery (A simple query)
cst.Source = mdxQuery
set cst.ActiveConnection = cat.ActiveConnection
In the page I do a looping with N queries openning and closing each one and so one.
The problem here isn´t the connection or query because with n queries getting less than 90 minutes, it is working without any problem but if the page has N queries getting more than 90 minutes, the IIS returns the message error as the subject.
Each loop done, I show in the page a message to see if it is working correctly and it is... the page gets the process step by step correctly. (Sure I´m using response.buffer true for it)
Another thing is that I´m using a Relational and Multidimensional connection in the page, but again, it is working perfectly when running with less 90 minutes approximately.
I couldn´t see any timeout attribute like it at IIS Configurations.
Hi johnny, I see/understand your point, but my point was that maybe when you started getting to bigger queries that maybe you messed upsomething or where joining this and that creating long load times, but if you're confident it works i'll go with you.
In the page I do a looping with N queries openning and closing each one and so one
You have an active connection so I don't think you're actually opening and closeing the database each time. It's just one constant connection.
This has to be one hell of a query / program to have an active connection open for 90 minutes. I've never heard of an autoshut off of 90 minutes in IIS but I don't understand how that would be an IIS issue.... I'd look into your SQL settings to see if it autoshuts off connections of greater then 90 minutes to preserve resources. I'd also look at your analysis services, i've never used it / even heard of it so i'm not sure exactly what it does but it might autoclose the connection to after 90 minutes.
In the off chance it is IIS, it will write it to the logs. If it's closing for this or that reason. And if not, check the event logs to make sure, If something's autoclosing your connection of failing, it will be in there.
hope this can get you looking in the right direction