How do I stop my e-mail subscription?
Active Server Pages error 'ASP 0113'
Hello Guest		   
  • Login
• Register…
• Start blog		   • Who, Where, When
• What can I do?
• What to Read?		   • Polls
• Avatars
• Interests		   • Cities and Countries
• Random blog
• Users search		   • Search
• Games
• Tests
• QAIX		   • Сообщества
• Talxy Chat
• Horoscope
• Online		  
Зарегистрируйся!
QAIX > ASP web-programming > Active Server Pages error 'ASP 0113' 3 October 2008 23:54:50
  Recent blog posts: 
_4_
…

mego day!
:-O­ yesss I today went for a walk from a 6 morning! it super! so merrily that pipec!

Everybody is a book
Everybody is a book, parents are our publishing houses, and our publication time on birthday, the ID…

boring..boring...boring :-|…
boring..boring...bor­­ing :-|­ where people? bitchs...not abandon me one…

here so quietly and boring! on…
here so quietly and boring! on beone merrier far! well but I can sit in a quiet.... and not who by the…

Transfer iTunes Library to Zune
If you have moved from Apple iPod to Microsoft Zune, you probably have some songs that you purchased&hellip­;

hello!
hello!I here new! interestingly me what people dwell on this site... I search friends from the command…

Routes on Sale!
Looking for great Quality/Competitive­­ Rates???? Breezecom FZC is offering: PAKISTAN! CLI…

Hello!
Hello!

How to rip DVD and convert…
You may have at hand many fantastic DVD movies and video files, which you definitely love very much…

  Forums:   
    topic feeds

• QAIX  all topics, blogs and comments

• PHP web-programming

• Perl web-programming

• ASP web-programming

• Visual Basic Programming

• .Net Development

• C/C++ Programming

• Java Programming

• Javascript web-programming

• Apache HTTP Server

• Web-design

• Web-hosting, dedicated, colocation

• HTML web-programming

• XML development

• General Web-programming

• Content Management Systems

• ColdFusion

• Search Engine Optimization

• Hardware

• Software, Computer Help

• MySQL database development

• PostgreSQL database development

• MS Access database development

• Oracle database development

• MS SQL database development

• Informix database development

• Buy / Sell

• Open discussion

• Anonymous
  Discuss: 
Select Records between…
I've built a Point-of-Sale using "classic" asp (it's what I know) and I'm trying to get daily…

Borwser prompts for…
I have put together a very simple internal web site that runs on Windows 2003 Server. Anonymous access…

Possible to include SSI in ASP…
Hi, We want to include some SSI in our ASP pages, but where the SSI is located on a different server…

text wait or hourglass
Hi Can someone please help me with the following: I have an ASP-page where a query runs, it…
  Recent forum topics: 
r24799 - docs/Perl6/Spec
Author: particle Date: 2009-01-07 20:53:32 +0100 (Wed, 07 Jan 2009) New Revision: 24799 Modified…

r24798 - docs/Perl6/Spec
Author: particle Date: 2009-01-07 20:42:33 +0100 (Wed, 07 Jan 2009) New Revision: 24798 Modified…

Writing to an iterator
I was just reading through S07, and it occurred to me that if one wanted to, one could handle stacks and…

ServiceController status…
This is a repost from CLR, doesn't seem like there is much activity over on that list. This isn't…
  Recent forum comments:
RE: NEW NEOPOINT GENERATOR v2…
Is it really that hard to hack neopets? I figure someone must of done something about that O:

RE: Re: What happened with…
$ svn info lib/Apache2/Reload.­pm Path: lib/Apache2/Reload.­pm Name: Reload.pm URL…

RE: Can I have multiple child divs?
I don't understand your question. The button bar appears stable to me. -- Murray MVP Expression Web…

RE: Can I have multiple child divs?
It is related to the white space issue at the bottom. If I try to move the tables up to get rid of the…

RE: Frustrated, Frontpage…
Sixbells;9207716 Wrote: I would use a decent package such as Dreamweaver or if you cant afford it go…

RE: Frustrated, Frontpage…
and that would fix it, eh? -- ~~~~~~~~~~~~~~~~~~ Rob Giordano Microsoft MVP Expression…

RE: Frustrated, Frontpage…
I will re-write it with nested tables, a good do over usually results in better code anyway. But one…

RE: Frustrated, Frontpage…
Don't use the draw table tool. That will add height attributes to everything (tables and table cells)…

RE: change text color
Use the Date Diff functionSee…

RE: Drop down is not displaying…
I have talked to my boss and we do not want the top frame larger, so we are going to re-develop the…
  Moderators:
 Administrator
 Protorioris

Active Server Pages error 'ASP 0113'

Justin Doh 3 October 2008 23:54:50
 "Active Server Pages error 'ASP 0113'
Script timed out"

I am still getting this error, and I am not sure how I could fix this.

When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through Database
Engine Tuning Advisor to put all the necessary indexes on the associated
tables.

It happens when I run this report on other new web server.

I already put this on the ASP web page for this report.

<% server.ScriptTimeou­t = 4000 %>

.ConnectionTimeout = 4800
.CommandTimeout = 4800

Any idea?
Thanks.

Add comment
Justin Doh 11 September 2008 21:46:09 [ permanent link ]
 "Active Server Pages error 'ASP 0113'
Script timed out"

I am still getting this error, and I am not sure how I could fix this.

When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through Database
Engine Tuning Advisor to put all the necessary indexes on the associated
tables.

It happens when I run this report on other new web server.

I already put this on the ASP web page for this report.

<% server.ScriptTimeou­t = 4000 %>

.ConnectionTimeout = 4800
.CommandTimeout = 4800

Any idea?
Thanks.

Add comment
Dave Anderson 11 September 2008 21:53:19 [ permanent link ]
 "Justin Doh" wrote:
"Active Server Pages error 'ASP 0113'
Script timed out"
...<% server.ScriptTimeou­t = 4000 %>...
.ConnectionTimeout = 4800
.CommandTimeout = 4800
Any idea?

Maybe it's not database-related. Are you in an endless loop, perhaps missing
a MoveNext() or something?



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Add comment
Bob Barrows 11 September 2008 22:06:31 [ permanent link ]
 Justin Doh wrote:
"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.
When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through
Database Engine Tuning Advisor to put all the necessary indexes on
the associated tables.
It happens when I run this report on other new web server.
I already put this on the ASP web page for this report.
<% server.ScriptTimeou­t = 4000 %>
.ConnectionTimeout = 4800
.CommandTimeout = 4800
Any idea?
Thanks.

Before setting ridiculous timeouts, verify that you need them.
1. use SQL Profiler to run a trace to verify that the stored procedure
is the problem
2. identify the bottleneck in your code if the stored procedure is not
the problem

<%
Response.Write "Code start: " & now & "<BR>"
...
Response.Write "Opening connection: " & now & "<BR>"
...
Response.Write "Calling procedure: " & now & "<BR>"

...
Response.Write "Processing results: " & now & "<BR>"
...


--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


Add comment
Old Pedant 11 September 2008 22:21:00 [ permanent link ]
 

"Bob Barrows [MVP]" wrote:

Before setting ridiculous timeouts, verify that you need them.
1. use SQL Profiler to run a trace to verify that the stored procedure
is the problem
2. identify the bottleneck in your code if the stored procedure is not
the problem
<%
Response.Write "Code start: " & now & "<BR>"
....
Response.Write "Opening connection: " & now & "<BR>"
....
Response.Write "Calling procedure: " & now & "<BR>"
....
Response.Write "Processing results: " & now & "<BR>"
....

But if the problem is an infinite loop of some kind, then you might want to
follow up each of the Response.Write calls with
Response.Flush
to be sure the output gets to the browser. Also, be sure to *NOT* output
your debug into the <TR> rows of a <TABLE>. Even with Response.Flush, the
browser will set there forever waiting for the terminating </TABLE> before
displaying anything.


Add comment
Evertjan. 11 September 2008 22:44:12 [ permanent link ]
 =?Utf-8?B?SnVzdGluIE­RvaA==?= wrote on 11 sep 2008 in
microsoft.public.in­etserver.asp.db:

"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.
When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through
Database Engine Tuning Advisor to put all the necessary indexes on the
associated tables.
It happens when I run this report on other new web server.
I already put this on the ASP web page for this report.
<% server.ScriptTimeou­t = 4000 %>
.ConnectionTimeout = 4800
.CommandTimeout = 4800

Please do not multipost on usenet


--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
Add comment
Bob Barrows 11 September 2008 22:55:02 [ permanent link ]
 Old Pedant wrote:
"Bob Barrows [MVP]" wrote:
Before setting ridiculous timeouts, verify that you need them.
1. use SQL Profiler to run a trace to verify that the stored
procedure is the problem
2. identify the bottleneck in your code if the stored procedure is
not the problem
<%
Response.Write "Code start: " & now & "<BR>"
....
Response.Write "Opening connection: " & now & "<BR>"
....
Response.Write "Calling procedure: " & now & "<BR>"
....
Response.Write "Processing results: " & now & "<BR>"
....
But if the problem is an infinite loop of some kind, then you might
want to follow up each of the Response.Write calls with
Response.Flush
to be sure the output gets to the browser.

I did mean to put that in - sorry

Also, be sure to *NOT*
output your debug into the <TR> rows of a <TABLE>. Even with
Response.Flush, the browser will set there forever waiting for the
terminating </TABLE> before displaying anything.

I didn't think that needed to be said, but thanks for saying it.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.


Add comment
Jeff Dillon 11 September 2008 23:12:05 [ permanent link ]
 
"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.

Try with a very simple query first to verify connectivity, etc.

Jeff


Add comment
Dave Anderson 11 September 2008 23:31:29 [ permanent link ]
 "Old Pedant" wrote:
...Also, be sure to *NOT* output your debug into the <TR> rows of a
<TABLE>. Even with Response.Flush, the browser will set there forever
waiting for the terminating </TABLE> before displaying anything.

It has been years since I saw a browser other than Internet Explorer that
exhibits this behavior. Certainly both Firefox and Opera will display table
rows before </table> is reached.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Add comment
Justin Doh 11 September 2008 23:36:01 [ permanent link ]
 Thank you very much for the feedback.

My output is:
I have the error message on the top of web page

Active Server Pages error 'ASP 0113'
Script timed out

And then, there is output (report with data)..

It retrieved the data fine, but why do I have the error message on the top?

Thanks.



"Jeff Dillon" wrote:

"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.
Try with a very simple query first to verify connectivity, etc.
Jeff
Add comment
Old Pedant 12 September 2008 00:08:02 [ permanent link ]
 
"Justin Doh" wrote:

My output is:
I have the error message on the top of web page
Active Server Pages error 'ASP 0113'
Script timed out
And then, there is output (report with data)..
It retrieved the data fine, but why do I have the error message on the top?

Well, this is a pure guess. But one way it *could* happen would be for you
to have an infinite loop AFTER all of the reporting is done but before the
final </TABLE> tag was written.

And if your reporting is done into a <TABLE> then the error message, since
it wouldn't be output with <TR><TD>...</TD></T­R> surrounding it, then indeed
the browser might show the error message *before* the incomplete <TABLE>.

As Dave Anderson might comment, this would likely only happen with MSIE (and
possibly only with pre-MSIE 7 versions), but I have seen it happen with MSIE
6, for sure. (Well, not timeout...but other errors.)

You can find out the truth of my guess by inspecting the HTML. Do a
VIEW==>>SOURCE in the browser and look at the HTML (in Notepad, if using
MSIE, by default). See if the error message really is at the bottom of the
HTML text and is simply displaying at the top becuz of MSIE peculiarities.


Add comment
Justin Doh 12 September 2008 00:56:18 [ permanent link ]
 You know what.
When I looked at the SOURCE of HTML (notepad), I see the error message on
the bottom.
How do I fix this?
Thanks.

"Old Pedant" wrote:

"Justin Doh" wrote:
My output is:
I have the error message on the top of web page
Active Server Pages error 'ASP 0113'
Script timed out
And then, there is output (report with data)..
It retrieved the data fine, but why do I have the error message on the top?
Well, this is a pure guess. But one way it *could* happen would be for you
to have an infinite loop AFTER all of the reporting is done but before the
final </TABLE> tag was written.
And if your reporting is done into a <TABLE> then the error message, since
it wouldn't be output with <TR><TD>...</TD></T­R> surrounding it, then indeed
the browser might show the error message *before* the incomplete <TABLE>.
As Dave Anderson might comment, this would likely only happen with MSIE (and
possibly only with pre-MSIE 7 versions), but I have seen it happen with MSIE
6, for sure. (Well, not timeout...but other errors.)
You can find out the truth of my guess by inspecting the HTML. Do a
VIEW==>>SOURCE in the browser and look at the HTML (in Notepad, if using
MSIE, by default). See if the error message really is at the bottom of the
HTML text and is simply displaying at the top becuz of MSIE peculiarities.
Add comment
Dave Anderson 12 September 2008 01:08:50 [ permanent link ]
 "Justin Doh" wrote:
You know what.
When I looked at the SOURCE of HTML (notepad), I see the error message on
the bottom.
How do I fix this?

Fix what? That the error message is at the bottom?

If I were trying to find the moment this timeout occurs, I would put a
Response.Flush() after every Response.Write(), and load the whole thing in
Firefox, watching to see the timing of the page as it progresses toward the
error. Is it all loading quickly, then doing nothing for a while, or do the
rows load at a constant pace until the error?

For IE-specific troubleshooting, you could also insert a </table><table>
every few rows in order to force rendering.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Add comment
Old Pedant 12 September 2008 01:51:02 [ permanent link ]
 

"Justin Doh" wrote:

You know what.
When I looked at the SOURCE of HTML (notepad), I see the error message on
the bottom.
How do I fix this?

So now you have to find out what is going into an infinite loop after all
the data has been reported.

At this point, I don't think we can help you until/unless you show some
source code.

We know that the problem occurs after the last </TR> is written, or you
wouldn't see *all* of the data.

We also know the problem occurs before the </TABLE> is written, or the error
message would appear after the table in the browser.

SO... What ASP code occurs between those two points in time in your code???

Add comment
Old Pedant 12 September 2008 01:58:02 [ permanent link ]
 

"Dave Anderson" wrote:

If I were trying to find the moment this timeout occurs, I would put a
Response.Flush() after every Response.Write(), ...

But I think that the problem is occurring at a point in time when he isn't
*doing* any Response.Write calls. Possibly even when he is trying to close
the connection. It would be silly, but if he had something like:
While Err.Number > 0
DB.Close
Wend
and if "DB" was already closed at that point...well, kablooey!

So I really think we have to see some code.

Add comment
Justin Doh 12 September 2008 02:03:00 [ permanent link ]
 I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.

Thank you!

"Old Pedant" wrote:

"Dave Anderson" wrote:
If I were trying to find the moment this timeout occurs, I would put a
Response.Flush() after every Response.Write(), ...
But I think that the problem is occurring at a point in time when he isn't
*doing* any Response.Write calls. Possibly even when he is trying to close
the connection. It would be silly, but if he had something like:
While Err.Number > 0
DB.Close
Wend
and if "DB" was already closed at that point...well, kablooey!
So I really think we have to see some code.
Add comment
Justin Doh 12 September 2008 02:18:02 [ permanent link ]
 Oops. I am still getting error.
The error disappeared and then now it appears again.
I got to dig again..

"Justin Doh" wrote:

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.
Thank you!
"Old Pedant" wrote:
"Dave Anderson" wrote:
If I were trying to find the moment this timeout occurs, I would put a
Response.Flush() after every Response.Write(), ...
But I think that the problem is occurring at a point in time when he isn't
*doing* any Response.Write calls. Possibly even when he is trying to close
the connection. It would be silly, but if he had something like:
While Err.Number > 0
DB.Close
Wend
and if "DB" was already closed at that point...well, kablooey!
So I really think we have to see some code.
Add comment
Old Pedant 12 September 2008 02:26:01 [ permanent link ]
 

"Justin Doh" wrote:

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.

This has *NOTHING* to do with the cause of the error. This only has to do
with what the Response.Write's are showing you. The debug info. Not the
cause of the orginal problem.

Add comment
Old Pedant 12 September 2008 02:28:00 [ permanent link ]
 

"Justin Doh" wrote:

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.

Response.Buffer=Tru­e is the *default* for all modern versions (since 2003 at
least, maybe before that) of IIS. So I doubt that you actually changed
anything.


Add comment
Ted Dawson 12 September 2008 04:35:40 [ permanent link ]
 
"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.
When I execute the query at SQL 2005, it only takes 8 seconds.



Obviously IUSR is connecting to the database, but the script times out? IUSR
may not have adequate permission to run the query.

Add comment
Dave Anderson 12 September 2008 17:22:41 [ permanent link ]
 "Old Pedant" wrote:
Response.Buffer=Tru­e is the *default* for all modern versions (since
2003 at least, maybe before that) of IIS.

Value Description
===================­====================­====================­==========
FALSE No buffering. The server sends output to the client as it is
processed. This is the default value for versions of IIS 4.0
and earlier. For version 5.0 and later, the default value is
TRUE.

http://msdn.microso­ft.com/en-us/library­/ms526001.aspx



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Add comment


Old Pedant 12 September 2008 22:16:15 [ permanent link ]
 

"Dave Anderson" wrote:

"Old Pedant" wrote:
Response.Buffer=Tru­e is the *default* for all modern versions (since
2003 at least, maybe before that) of IIS.
===================­====================­====================­==========
FALSE No buffering. The server sends output to the client as it is
processed. This is the default value for versions of IIS 4.0
and earlier. For version 5.0 and later, the default value is
TRUE.
http://msdn.microso­ft.com/en-us/library­/ms526001.aspx

Yes, and this page
http://support.micr­osoft.com/kb/224609
says IIS 5 shipped with Windows 2000. So my "maybe before" was more than
true. It would be pretty surprising to find a shop still running IIS 4,
today. They'd presumably still be running WindowsNT version 4.

Or were you agreeing with me? Hmmm...I guess you were. Okay. Great.


Add comment
Dave Anderson 12 September 2008 22:37:31 [ permanent link ]
 "Old Pedant" "wrote":
http://msdn.microso­ft.com/en-us/library­/ms526001.aspx
[snip]
Or were you agreeing with me? Hmmm...I guess you were. Okay.
Great.

Documentation takes no sides.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Add comment


Old Pedant 13 September 2008 00:03:01 [ permanent link ]
 
"Dave Anderson" wrote:
Documentation takes no sides.

LMAO!

Only tops and bottoms, huh?


Add comment
MikeR 13 September 2008 15:40:14 [ permanent link ]
 Old Pedant wrote:
"Dave Anderson" wrote:
Documentation takes no sides.
LMAO!
Only tops and bottoms, huh?
Kinky!
Mike
Add comment


Ken 3 October 2008 23:54:50 [ permanent link ]
 It's probably not in the connection to SQL or the query but some loop
in the code that is running so long that it's timing out.

Check the loops ie where your moving through the record set.


On Sep 11, 12:45pm, Justin Doh <Justin...@discussi­ons.microsoft.com>
wrote:
"Active Server Pages error 'ASP 0113'
Script timed out"
I am still getting this error, and I am not sure how I could fix this.
When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through Database
Engine Tuning Advisor to put all the necessary indexes on the associated
tables.
It happens when I run this report on other new web server.
I already put this on the ASP web page for this report.
<% server.ScriptTimeou­t = 4000 %>
.ConnectionTimeout = 4800
.CommandTimeout = 4800
Any idea?
Thanks.

Add comment
 

Add new comment

As:
Login:  Password:  
 
 
  
 
Пожалуйста, относитесь к собеседникам уважительно, не используйте нецензурные слова, не злоупотребляйте заглавными буквами, не публикуйте рекламу и объявления о купле/продаже, а также материалы нарушающие сетевой этикет или УК РФ.

QAIX > ASP web-programming > Active Server Pages error 'ASP 0113' 3 October 2008 23:54:50
see also:
Php 4.3.2 "stream does not support…
Basic counter & users online..
Linux vs. Windows
пройди тесты:
What is Your Temperament?
see also:
MelodyCan YouTube Ripper
Convert video (AVI, WMV, MOV) to iPod
How to convert files from iTunes Music…
  Copyright © 2001—2008 QAIX
Idea: Miсhael Monashev
Помощь и задать вопросы можно в сообществе support.qaix.com.
Сообщения об ошибках оставляем в сообществе bugs.qaix.com.
Предложения и комментарии пишем в сообществе suggest.qaix.com.
Информация для родителей.
Write us at:
If you would like to report an abuse of our service, such as a spam message, please .