Hello all - we have a serious problem as described below. Can anyone please
help ?

Hardware / Software setup:

- Three servers in Microsoft Application Center 2000 SP1 cluster running
Window 2000 Server SP4.

- SQL Server 2000 SP3 cluster with failover mechanism.

The solution is implemented with standard ASP and all database
communications goes through COM and COM+ objects programmed in Visual Basic
6.

The problem:

When running the web application in Internet Explorer we get a "HTTP 500 -
Internal server error" in pages that we know works fine. When the problem
arises it will occur at all three servers in large numbers. One way to stop
the error is to kill the dllhost.exe containing our COM-components in one of
the machines manually. A weird thing is that if the service is killed in one
machine the errors will stop in all three servers in the cluster.

It has been observed that when the server is parsing the ASP-page, the
number of lines processed is decreasing the longer the error has existed (in
time). To clarify: In the start of the error cycle the ASP-parser is able to
process ASP files with a large number of lines, but the number of lines it
can parse decreases during the error cycle and at the end the parser cant
even process an ASP-file with just a few lines of code.

The problem only exists in the productive system and neither in development
nor test, so it must be related to load on the system?

Best Regards
Torben

RE: Error 500 by timcof

timcof
Tue Sep 30 02:50:08 CDT 2003

You will want to debug. Sounds like it is stress related:
Try running IISstate from either the IIS6 Res Kit, or from www.iisfaq.com and post a new thread back with IISstate Log in the subject line.

Thank you. I hope this information is helpful.

Tim Coffey [MSFT]

This posting is provided ?AS IS? with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.
--------------------
| From: usenet_mail@yahoo.dk (Torben)
| Newsgroups: microsoft.public.inetserver.iis
| Subject: Error 500
| Date: 23 Sep 2003 13:25:37 -0700
| Organization: http://groups.google.com/
| Lines: 35
| Message-ID: <84c33f95.0309231225.3f982b3c@posting.google.com>
| NNTP-Posting-Host: 195.249.80.194
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1064348738 31416 127.0.0.1 (23 Sep 2003 20:25:38 GMT)
| X-Complaints-To: groups-abuse@google.com
| NNTP-Posting-Date: 23 Sep 2003 20:25:38 GMT
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!
sn-xit-06!sn-xit-08!sn-xit-09!supernews.com!postnews1.google.com!not-for-mail
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:276810
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| Hello all - we have a serious problem as described below. Can anyone please
| help ?
|
| Hardware / Software setup:
|
| - Three servers in Microsoft Application Center 2000 SP1 cluster running
| Window 2000 Server SP4.
|
| - SQL Server 2000 SP3 cluster with failover mechanism.
|
| The solution is implemented with standard ASP and all database
| communications goes through COM and COM+ objects programmed in Visual Basic
| 6.
|
| The problem:
|
| When running the web application in Internet Explorer we get a "HTTP 500 -
| Internal server error" in pages that we know works fine. When the problem
| arises it will occur at all three servers in large numbers. One way to stop
| the error is to kill the dllhost.exe containing our COM-components in one of
| the machines manually. A weird thing is that if the service is killed in one
| machine the errors will stop in all three servers in the cluster.
|
| It has been observed that when the server is parsing the ASP-page, the
| number of lines processed is decreasing the longer the error has existed (in
| time). To clarify: In the start of the error cycle the ASP-parser is able to
| process ASP files with a large number of lines, but the number of lines it
| can parse decreases during the error cycle and at the end the parser cant
| even process an ASP-file with just a few lines of code.
|
| The problem only exists in the productive system and neither in development
| nor test, so it must be related to load on the system?
|
| Best Regards
| Torben
|