IIS 500-13 : server too busy

"Performance" issue with IIS

[sparki_uk]

I hope someone can help. I am getting some angry emails from users of www.snipped.net -

The error:
IIS 500 - 13 : server too busy.
The request cannot be processed at this time. The amount of traffic exceeds the Web site's configured capacity.

I have been through some good Microsoft articles on performance tuning etc with no success.
Also, when i have this error, the server is definitely NOT BUSY and there are no ASP pages queued!

SOMEONE must have experienced this. I would appreciate help.

The site runs on a Win2K server with SQL Server 2000

[edited by: DaveAtIFG at 2:35 pm (utc) on Mar. 3, 2004]
[edit reason] No specifics please! TOS 13, 20, 25 [/edit]

[korkus2000]

Have you checked the amount of memory being used by SQL Server? Make sure the stored procedures are not killing the server. Also check to see if any executables or other file types maybe hogging the processes. Also are you using sessions to keep your login info. Sessions can bring a server to its knees.

[markus007]

98% of performance issues are due to poor coding....

[plumsauce]

exceeds the Web site's configured capacity.

do you have any limits set in mmc?

like bandwidth throttling or number of connections?

[sparki_uk]

Many thanks for your replies.

Time to put my hand up and admit something careless - I reviewed the VB DLLs used and found that the most utilized DLL was marked as "retained in memory".

(markus007 - don't forget - 86.52% of statistics are meaningless. In this case it appears to be careless configuration!)

This is instantiated 10's of 1000's of times a day and could explain why the server was down before Starbucks had even opened for business. Where was I that day when the teacher covered component services?

korkus2000 - I will check into this too, many thanks. I use SP's heavily and, although they seem to perform well, I will check them more carefully.
I have transferred large, rarely used ASP procedures into SP's as they don't need to be loaded each request.

No I DON'T use sessions for that very reason! However I have to open a DB connection on each page request to check user credentials. If there's an easier way let me know!

plumsauce - I checked and there are no limits.