This topic is locked

Export Results

2/9/2007 2:11:01 PM
ASPRunnerPro General questions
Alberto author

Sergey
I got some time now to troubleshoot this.
My environment is:

Server

-------------

Dell Box

4 GB RAM

Windows 2003
Database

--------------

MS SQL Server 2000 Standard Edition
Version:

-----------

Built # 221
Situation:

-------------

Exporting: Trying to export to excel

Number of Record: 52383

Number of columns: 8 small fields

SQL Table dedicated only for this export.
Having made this recommended changes

-------------------------------------------------------

Changed on the server the TcpTimedWaitDelay to 600

Disabled what you have recommended to me "Friendly HTTP error messages"

Server.ScriptTimeOut=3600 on top of Export.asp after <%
Error text:

------------------

Response object error 'ASP 0251 : 80004005'

Response Buffer Limit Exceeded

/olr/SchdIniConsultTimeRange/BT_SANDP_SCHED_INITIAL_CONSULTS_IN_TIME_RANGE_export.asp, line 0

Execution of the ASP page caused the Response Buffer to exceed its configured limit.
THANKS

Alberto author 2/9/2007

Sergey,
I did a search in internet and found a suggestion to add this code to the asp file.

Response.Buffer = False
By just testing I put it on the top of my BT_SANDP_SCHED_INITIAL_CONSULTS_IN_TIME_RANGE_export.asp file and it worked ok with the 52 thousand to excel.

I don't really know if this will affect the rest of the design of this page or not.
With 100 Thowsands to CSV. I get this error in the bottom of the text file.
error 'ASP 0113'

Script timed out

/olr/SchdIniConsultTimeRange/BT_SANDP_SCHED_INITIAL_CONSULTS_IN_TIME_RANGE_export.asp

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.
The server has Connection Time Out 1,200 Secondsand HTTP Keep alivechecked
Thanks

Alberto author 2/9/2007

Sergey,
More info: Most of the time it stops at
around 5 minutes

arround 60 and 70 thousand records

around 5 and 6 MB
Thanks

C
clig 2/11/2007

Sergey,

More info: Most of the time it stops at
around 5 minutes

arround 60 and 70 thousand records

around 5 and 6 MB
Thanks


how about adding to your export page
<%

Session.Timeout = 480 ' minutes

%>

<%

Server.ScriptTimeout = 0 ' 0 for never - max 2147483647

%>

Alberto author 2/12/2007

Thanks clig,
I played a litle bit more with this today but it keeps failing arround 5 minutes and at record#

63,092

66,364

60.161
Also tryied something else: I have eliminated some fields to export and this is the sequence and results of my tests;
1 Fields Worked ok in 40 seconds

4 Fields 4.76 MB worked ok in 5 minutes 8 sec

5 Fields 4.36 MB failed in 4 minutes 46 sec

5 Fields 4.27 MB failed in 4 minutes 58 sec

4 Fields 4.76 MB worked ok in 5 minutes 11 sec

5 Fields 4.62 MB failed in 5 minutes 32 sec

C
clig 2/18/2007

Thanks clig,

I played a litle bit more with this today but it keeps failing arround 5 minutes and at record#

63,092

66,364

60.161
Also tryied something else: I have eliminated some fields to export and this is the sequence and results of my tests;
1 Fields Worked ok in 40 seconds

4 Fields 4.76 MB worked ok in 5 minutes 8 sec

5 Fields 4.36 MB failed in 4 minutes 46 sec

5 Fields 4.27 MB failed in 4 minutes 58 sec

4 Fields 4.76 MB worked ok in 5 minutes 11 sec

5 Fields 4.62 MB failed in 5 minutes 32 sec


Odd... Curious on this - under 5MB in 5 minutes - Is there throttling?
Tried:
Response.Clear

Response.Buffer = True

Response.ContentType = "application/vnd.ms-excel"
?

Sergey Kornilov admin 2/19/2007

If the error you currently getting is "Script timed out" setting Server.ScriptTimeout to some value greater than 300 should solve the issue.
Put the following somewhere in the beginning of export page.

Server.ScriptTimeout = 600
Alberto author 8/2/2007

I was able to fix this problem by adding this on the top of the _export.asp file as follows:
<%

Server.ScriptTimeOut=3600

Session.Timeout = 1440

Response.Buffer = False
It works fine now with big exports.
Thanks