By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,269 Members | 1,519 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,269 IT Pros & Developers. It's quick & easy.

IIS 6.0, ASP pages, HTTP Error 500.13 - Server error

P: n/a
Hello,
we have a website in ASP , the pages connected to .mdb access database
by ODBC there is a big traffic on this site, so after 9-10 hour the
server show this error to visitors :

HTTP Error 500.13 - Server error: Web server is too busy.
Internet Information Services (IIS)
BUT only .asp pages on all domains make this error, all images or aspx
or html
pages work correctly.
now! to resolve this problem, i should restart ther server or IIS evry
9-10 hour!! so it is not a good idea!
i search the internet to resolve this problem, microsoft tell me :
"ASP requests are executed by threads from a pool of threads whose size
is
limited to 25 threads per processor, by default. If more ASP requests
arrive
than there are threads available to execute them, ASP places the extra
requests in a queue, where they wait until a thread becomes available.
By
default, this queue is limited to 3000 requests. If the queue becomes
full,
the next ASP request, instead of being queued, causes a 500.13-Web
server
too busy error. The number of requests that can wait in the queue is
controlled by the AspRequestQueueMax metabase property. Change the
AspRequestQueueMax property to produce the desired user experience -
a
smaller queue allows users to more quickly see the 500.13 error when
ASP
requests are backed up."
i edit the MetaBase, first i set the "AspRequestQueueMax" to 5000! so
visitors did not get the 500.13 error but they think the server is not
response them becouse they was in the queue.!!
then i set the "AspRequestQueueMax" to 3500, and i think this is not
the best solutoin! becouse after all users will recive the 500.13
error, but when it was on 3000 they recived after 8-9 hour and now will
recive after 10-12 hour!
1) do you think server upgrade is a good sulotion ?
2) the cpu usage of our server is not full! , do i need better cpu ?
3) the memory is busy! when users get that error! do i need more memory
(currently it is 1 GB)?
thank you becouse of your help.
best regards

Aug 13 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
re*******@gmail.com wrote:
we have a website in ASP , the pages connected to .mdb access
database by ODBC there is a big traffic on this site, so after
9-10 hour the server show this error to visitors :

HTTP Error 500.13 - Server error: Web server is too busy.
Internet Information Services (IIS)
Honestly, MS Access (not to mention the use of ODBC) is more likely the
cause:
http://aspfaq.com/show.asp?id=2195

BUT only .asp pages on all domains make this error, all images or
aspx or html pages work correctly.
....which shows that the server itself is not overtaxed. Among the MANY
possibilites is failure to close your connections and destroy your objects.
now! to resolve this problem, i should restart ther server or IIS
evry 9-10 hour!! so it is not a good idea!
Since you are in IIS 6, you can partition into application pools and let IIS
restart them as needed. Check out the [Recycling] and [Performance] tabs on
your application pool properties in the IIS console.

Note that this does not fix the root cause of your problem.

--
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.
Aug 13 '06 #2

P: n/a

<re*******@gmail.comwrote in message
news:11*********************@p79g2000cwp.googlegro ups.com...
Hello,
we have a website in ASP , the pages connected to .mdb access database
by ODBC there is a big traffic on this site, so after 9-10 hour the
server show this error to visitors :

HTTP Error 500.13 - Server error: Web server is too busy.
Internet Information Services (IIS)
BUT only .asp pages on all domains make this error, all images or aspx
or html
pages work correctly.
now! to resolve this problem, i should restart ther server or IIS evry
9-10 hour!! so it is not a good idea!
i search the internet to resolve this problem, microsoft tell me :
"ASP requests are executed by threads from a pool of threads whose size
is
limited to 25 threads per processor, by default. If more ASP requests
arrive
than there are threads available to execute them, ASP places the extra
requests in a queue, where they wait until a thread becomes available.
By
default, this queue is limited to 3000 requests. If the queue becomes
full,
the next ASP request, instead of being queued, causes a 500.13-Web
server
too busy error. The number of requests that can wait in the queue is
controlled by the AspRequestQueueMax metabase property. Change the
AspRequestQueueMax property to produce the desired user experience -
a
smaller queue allows users to more quickly see the 500.13 error when
ASP
requests are backed up."
i edit the MetaBase, first i set the "AspRequestQueueMax" to 5000! so
visitors did not get the 500.13 error but they think the server is not
response them becouse they was in the queue.!!
then i set the "AspRequestQueueMax" to 3500, and i think this is not
the best solutoin! becouse after all users will recive the 500.13
error, but when it was on 3000 they recived after 8-9 hour and now will
recive after 10-12 hour!
1) do you think server upgrade is a good sulotion ?
2) the cpu usage of our server is not full! , do i need better cpu ?
3) the memory is busy! when users get that error! do i need more memory
(currently it is 1 GB)?

Use performance monitor to watch the number Requests Executing in Active
Server Performance object. If the after a while it never drops to zero and
over time the minimum value increases you most likely have threads which are
hanging.

Use IISState to get a dump the executing pages this will tell you the pages
'running' in the hung threads.

thank you becouse of your help.
best regards

Aug 14 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.