|
Home > Archive > IIS Server > July 2005 > IIS 6 hang up !!!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hello,
I have moved my win2k server to win2003 server with IIS 6 since 10 days, but
since yesterday i have a big problem on my server, and he was come alone, i
haven't change anything before... Then, my server say this error... (bellow)
and he did not respond anymore, the page seems to be loaded but nothing
appear, only blank... all that every 25mn approx... do you have a good
solution ?? thanks
Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2262
Date: 28/06/2005
Time: 18:21:00
User: N/A
Computer: IK55165
Description:
ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy for
the following reason: 'ASP unhealthy because 93% of executing requests are
hung and 19% of the request queue is full.'.
| |
| Egbert Nierop \(MVP for IIS\) 2005-06-29, 7:52 am |
| Hi,
Mentioned it a lot today, you'll need IISState
http://www.iisfaq.com/default.aspx?view=P197
Maybe some script uses practices which never were recommended. But it is too
vague anyway to help you now. Please use IISState and let us know the
results by posting the log to this forum.
--
compatible web farm Session replacement for Asp and Asp.Net
http://www.nieropwebconsult.nl/asp_session_manager.htm
"David" <David@discussions.microsoft.com> wrote in message
news:4A8D703D-A10C-4C46-BD7D-1215FD99DFCD@microsoft.com...
> Hello,
>
> I have moved my win2k server to win2003 server with IIS 6 since 10 days,
> but
> since yesterday i have a big problem on my server, and he was come alone,
> i
> haven't change anything before... Then, my server say this error...
> (bellow)
> and he did not respond anymore, the page seems to be loaded but nothing
> appear, only blank... all that every 25mn approx... do you have a good
> solution ?? thanks
>
> Event Type: Warning
> Event Source: W3SVC-WP
> Event Category: None
> Event ID: 2262
> Date: 28/06/2005
> Time: 18:21:00
> User: N/A
> Computer: IK55165
> Description:
> ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy
> for
> the following reason: 'ASP unhealthy because 93% of executing requests are
> hung and 19% of the request queue is full.'.
>
| |
|
| This don't help me sorry, i think i have found something
Going to web site properties / home directory / configuration / cache
options and set
Do not cache ASP files
the server stop to block, but i get the same event message error
| |
| Egbert Nierop \(MVP for IIS\) 2005-06-29, 7:52 am |
| "David" <David@discussions.microsoft.com> wrote in message
news:CD02BA6A-98BB-451C-AF7B-84BD0FE8D750@microsoft.com...
> This don't help me sorry, i think i have found something
>
> Going to web site properties / home directory / configuration / cache
> options and set
>
> Do not cache ASP files
I think this is very bad. Just turning off options and hoping your errors go
away is not the good analyzis. Sorry.
You really need IISState to analyze your server +plus+ scripts. Because the
scripts within ASP can cause problems as well.
If you disable script caching, you will exhaust your CPU. Possibly some COM
objects you wrote or used, use their memory state in invalid way, so your
memory and threads get locked up.
Shortly, disabling script caching has never been the solution to lock-up IIS
problems.
> the server stop to block, but i get the same event message error
| |
|
| OK i will install IISTATE, i have already install debug tools for windows
(cdb.exe)
My memory and CPU hasn't increase, i turn approx 10% CPU usage and 300 MB
memory
"Egbert Nierop (MVP for IIS)" a écrit :
> I think this is very bad. Just turning off options and hoping your errors go
> away is not the good analyzis. Sorry.
> You really need IISState to analyze your server +plus+ scripts. Because the
> scripts within ASP can cause problems as well.
> If you disable script caching, you will exhaust your CPU. Possibly some COM
> objects you wrote or used, use their memory state in invalid way, so your
> memory and threads get locked up.
>
> Shortly, disabling script caching has never been the solution to lock-up IIS
> problems.
| |
|
| Hello, i have a log here
http://213.246.55.165/IISState-2696.txt
The problem now is that i can't grab error cause he said event like that and
this don't crash my system like event 2262 do (but i have the same error)
Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2273
Description:
Worker process could not access metabase due to disconnection error.
Marking process as unhealthy.
| |
|
| Hello, i have a log here
http://213.246.55.165/IISState-2696.txt
The problem now is that i can't grab error cause he said event like that and
this don't crash my system like event 2262 do (but i have the same error)
Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2273
Description:
Worker process could not access metabase due to disconnection error.
Marking process as unhealthy.
| |
|
| Hello, i have a log here
http://213.246.55.165/IISState-2696.txt
The problem now is that i can't grab error cause he said event like that and
this don't crash my system like event 2262 do (but i have the same error)
Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2273
Description:
Worker process could not access metabase due to disconnection error.
Marking process as unhealthy.
| |
|
| I have reboot again my server and i have this error, maybe the metabase is
wrong ? how i can correct it ?
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 29/06/2005
Time: 20:03:27
User: N/A
Computer: IK55165
Description:
Reporting queued error: faulting application inetinfo.exe, version
6.0.3790.1830, faulting module metadata.dll, version 6.0.3790.1830, fault
address 0x00028b37.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 6e 65 ure ine
0018: 74 69 6e 66 6f 2e 65 78 tinfo.ex
0020: 65 20 36 2e 30 2e 33 37 e 6.0.37
0028: 39 30 2e 31 38 33 30 20 90.1830
0030: 69 6e 20 6d 65 74 61 64 in metad
0038: 61 74 61 2e 64 6c 6c 20 ata.dll
0040: 36 2e 30 2e 33 37 39 30 6.0.3790
0048: 2e 31 38 33 30 20 61 74 .1830 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 32 38 62 33 37 00028b37
| |
| David Wang [Msft] 2005-06-29, 5:53 pm |
| It looks like SOMETHING started to open and lock up the metabase on your
server. This prevented ASP (and IIS) from reading necessary configuration
and causes the w3wp.exe to hang (waiting for the configuration to be
available). And now, something has corrupted your metabase so IIS6 will be
hosed.
I hope you have a backup of the metabase.xml or else you will have to
reinstall. Then, you need to find that bad application that is locking the
metabase. I would start with things like backup agents and virus scanners or
anything added to the machine -- because as you said, things ran fine for
over a week, so I do not think the problem is originating from IIS6 itself.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"David" <David@discussions.microsoft.com> wrote in message
news:F3457054-2365-406D-812D-2A41FB01C5F7@microsoft.com...
I have reboot again my server and i have this error, maybe the metabase is
wrong ? how i can correct it ?
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 29/06/2005
Time: 20:03:27
User: N/A
Computer: IK55165
Description:
Reporting queued error: faulting application inetinfo.exe, version
6.0.3790.1830, faulting module metadata.dll, version 6.0.3790.1830, fault
address 0x00028b37.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 6e 65 ure ine
0018: 74 69 6e 66 6f 2e 65 78 tinfo.ex
0020: 65 20 36 2e 30 2e 33 37 e 6.0.37
0028: 39 30 2e 31 38 33 30 20 90.1830
0030: 69 6e 20 6d 65 74 61 64 in metad
0038: 61 74 61 2e 64 6c 6c 20 ata.dll
0040: 36 2e 30 2e 33 37 39 30 6.0.3790
0048: 2e 31 38 33 30 20 61 74 .1830 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 32 38 62 33 37 00028b37
| |
| RsrAdministrator123 2005-06-30, 6:01 pm |
| I'm having a similar problem, do you have SP1. Error I get is:
Source: W3SVC
A process serving application pool 'DefaultAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '5392'. The data field contains the error number.
"David" wrote:
> Hello,
>
> I have moved my win2k server to win2003 server with IIS 6 since 10 days, but
> since yesterday i have a big problem on my server, and he was come alone, i
> haven't change anything before... Then, my server say this error... (bellow)
> and he did not respond anymore, the page seems to be loaded but nothing
> appear, only blank... all that every 25mn approx... do you have a good
> solution ?? thanks
>
> Event Type: Warning
> Event Source: W3SVC-WP
> Event Category: None
> Event ID: 2262
> Date: 28/06/2005
> Time: 18:21:00
> User: N/A
> Computer: IK55165
> Description:
> ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy for
> the following reason: 'ASP unhealthy because 93% of executing requests are
> hung and 19% of the request queue is full.'.
>
| |
| David Wang [Msft] 2005-06-30, 8:50 pm |
| No, your problem is most likely different than his problem. Completely
different event log entry, even. Please provide the entire event log entry,
including the "data field" since it contains the error number.
This event tells you that you ran some web application that crashed. You
want to use an IISState to catch the next time it crashes and post the crash
log with a Subject containing "IISSTATE LOG ANALYSIS"
http://www.iisfaq.com/default.aspx?view=P197
His error does not indicate a web application crashing. His error indicates
something locking the metabase and causing a backup/queuing of requests,
which eventually hang the server (a metabase lock can do this sort of thing,
easily).
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
in message news:81814AC6-540C-40DC-A2BD-5A03BC67F360@microsoft.com...
I'm having a similar problem, do you have SP1. Error I get is:
Source: W3SVC
A process serving application pool 'DefaultAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '5392'. The data field contains the error number.
"David" wrote:
> Hello,
>
> I have moved my win2k server to win2003 server with IIS 6 since 10 days,
but
> since yesterday i have a big problem on my server, and he was come alone,
i
> haven't change anything before... Then, my server say this error...
(bellow)
> and he did not respond anymore, the page seems to be loaded but nothing
> appear, only blank... all that every 25mn approx... do you have a good
> solution ?? thanks
>
> Event Type: Warning
> Event Source: W3SVC-WP
> Event Category: None
> Event ID: 2262
> Date: 28/06/2005
> Time: 18:21:00
> User: N/A
> Computer: IK55165
> Description:
> ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy
for
> the following reason: 'ASP unhealthy because 93% of executing requests are
> hung and 19% of the request queue is full.'.
>
| |
| RsrAdministrator123 2005-07-01, 7:53 am |
| Your right. Yesterday the developers from Promail gave us a patch to fix the
web interface.
The event ID is 1011 and the data field shows: 0000: 6d 00 07 80
"David Wang [Msft]" wrote:
> No, your problem is most likely different than his problem. Completely
> different event log entry, even. Please provide the entire event log entry,
> including the "data field" since it contains the error number.
>
> This event tells you that you ran some web application that crashed. You
> want to use an IISState to catch the next time it crashes and post the crash
> log with a Subject containing "IISSTATE LOG ANALYSIS"
>
> http://www.iisfaq.com/default.aspx?view=P197
>
>
> His error does not indicate a web application crashing. His error indicates
> something locking the metabase and causing a backup/queuing of requests,
> which eventually hang the server (a metabase lock can do this sort of thing,
> easily).
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
> in message news:81814AC6-540C-40DC-A2BD-5A03BC67F360@microsoft.com...
> I'm having a similar problem, do you have SP1. Error I get is:
>
> Source: W3SVC
>
> A process serving application pool 'DefaultAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The process
> id was '5392'. The data field contains the error number.
>
> "David" wrote:
>
> but
> i
> (bellow)
> for
>
>
>
| |
| David Wang [Msft] 2005-07-02, 2:47 am |
| Yeah, 0x8007006d indicates Win32 error (the 7 means Win32, the high order
bit=1 means "error") code of 109 (0x006d), which is basically "pipe
disconnected" and in the context of IIS, means that something crashed the
w3wp.exe. Attaching a debugger to grab stack trace to get more data is the
next step -- but you said that a patch has been applied to fix some issue,
so maybe that was causing the crash.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
in message news:012D1689-77ED-49D8-BD7D-788C61807BD4@microsoft.com...
Your right. Yesterday the developers from Promail gave us a patch to fix
the
web interface.
The event ID is 1011 and the data field shows: 0000: 6d 00 07 80
"David Wang [Msft]" wrote:
> No, your problem is most likely different than his problem. Completely
> different event log entry, even. Please provide the entire event log
entry,
> including the "data field" since it contains the error number.
>
> This event tells you that you ran some web application that crashed. You
> want to use an IISState to catch the next time it crashes and post the
crash
> log with a Subject containing "IISSTATE LOG ANALYSIS"
>
> http://www.iisfaq.com/default.aspx?view=P197
>
>
> His error does not indicate a web application crashing. His error
indicates
> something locking the metabase and causing a backup/queuing of requests,
> which eventually hang the server (a metabase lock can do this sort of
thing,
> easily).
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com>
wrote
> in message news:81814AC6-540C-40DC-A2BD-5A03BC67F360@microsoft.com...
> I'm having a similar problem, do you have SP1. Error I get is:
>
> Source: W3SVC
>
> A process serving application pool 'DefaultAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The
process
> id was '5392'. The data field contains the error number.
>
> "David" wrote:
>
> but
alone,[vbcol=seagreen]
> i
> (bellow)
> for
are[vbcol=seagreen]
>
>
>
| |
| RsrAdministrator123 2005-07-25, 6:06 pm |
| David, the problems is still occuring. The developers fixed a different
problem with their software, turns out it wasn't related to this IIS error.
Here are some details below that posted some time ago. How do I use the
debugger? Are there log files?
******Previous post******
I've been getting a pop up error every couple of days on my Win2003 server
with SP1. The pop up title says "GDI+ Window: w3wp.exe - Application Error"
The error says " The instruction at "0x38734bf9 referenced memory at
"0x38734bf9". The memory could not be "read". " Does anyone know what this
means? It this realated to service pack on or a certain application? Also,
one time I rebooted and got the following error 'IIS Worker Process
encountered a problem and needed to close."
"David Wang [Msft]" wrote:
> Yeah, 0x8007006d indicates Win32 error (the 7 means Win32, the high order
> bit=1 means "error") code of 109 (0x006d), which is basically "pipe
> disconnected" and in the context of IIS, means that something crashed the
> w3wp.exe. Attaching a debugger to grab stack trace to get more data is the
> next step -- but you said that a patch has been applied to fix some issue,
> so maybe that was causing the crash.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
> in message news:012D1689-77ED-49D8-BD7D-788C61807BD4@microsoft.com...
> Your right. Yesterday the developers from Promail gave us a patch to fix
> the
> web interface.
>
> The event ID is 1011 and the data field shows: 0000: 6d 00 07 80
>
> "David Wang [Msft]" wrote:
>
> entry,
> crash
> indicates
> thing,
> rights.
> wrote
> process
> alone,
> are
>
>
>
| |
| David Wang [Msft] 2005-07-26, 5:54 pm |
| You need to use a tool like IIS State (URL given earlier in this email
thread) to monitor the IIS w3wp.exe processes and catch crashes, produce a
log, and post the log here for analysis. Th elog will show what code is
crashing so that we can determine who is responsible for support.
The popup simply indicates that you are running some code on IIS that is
crashing by reading the wrong memory address. This is usually not caused by
IIS or a service pack.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
in message news:B5EB8CBD-5414-4602-9AC5-75E8B5D53230@microsoft.com...
David, the problems is still occuring. The developers fixed a different
problem with their software, turns out it wasn't related to this IIS error.
Here are some details below that posted some time ago. How do I use the
debugger? Are there log files?
******Previous post******
I've been getting a pop up error every couple of days on my Win2003 server
with SP1. The pop up title says "GDI+ Window: w3wp.exe - Application Error"
The error says " The instruction at "0x38734bf9 referenced memory at
"0x38734bf9". The memory could not be "read". " Does anyone know what this
means? It this realated to service pack on or a certain application? Also,
one time I rebooted and got the following error 'IIS Worker Process
encountered a problem and needed to close."
"David Wang [Msft]" wrote:
> Yeah, 0x8007006d indicates Win32 error (the 7 means Win32, the high order
> bit=1 means "error") code of 109 (0x006d), which is basically "pipe
> disconnected" and in the context of IIS, means that something crashed the
> w3wp.exe. Attaching a debugger to grab stack trace to get more data is the
> next step -- but you said that a patch has been applied to fix some issue,
> so maybe that was causing the crash.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com>
wrote
> in message news:012D1689-77ED-49D8-BD7D-788C61807BD4@microsoft.com...
> Your right. Yesterday the developers from Promail gave us a patch to fix
> the
> web interface.
>
> The event ID is 1011 and the data field shows: 0000: 6d 00 07 80
>
> "David Wang [Msft]" wrote:
>
> entry,
> crash
> indicates
> thing,
> rights.
> wrote
> process
days,[vbcol=seagreen]
> alone,
nothing[vbcol=seagreen]
unhealthy[vbcol=seagreen]
> are
>
>
>
| |
| RsrAdministrator123 2005-07-26, 5:54 pm |
| Thank you David, I was on the phone today with Microsoft support for about 4
hours. I installed two different plugins to anaylize dumps. One download
was from beta.microsoft.com just for IIS called DebugDiag.msi. After the
install, the debugger caught some dumps and I sent two log files, one on the
w3wp.exe process, and one was for first time exceptions; both totaled about
180mb size so I cant post it here.
The error occured twice today and while the engineer was in our system so he
has a clear picture of whats going on. He is going to follow up first thing
tomorrw.
"David Wang [Msft]" wrote:
> You need to use a tool like IIS State (URL given earlier in this email
> thread) to monitor the IIS w3wp.exe processes and catch crashes, produce a
> log, and post the log here for analysis. Th elog will show what code is
> crashing so that we can determine who is responsible for support.
>
> The popup simply indicates that you are running some code on IIS that is
> crashing by reading the wrong memory address. This is usually not caused by
> IIS or a service pack.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "RsrAdministrator123" <RsrAdministrator123@discussions.microsoft.com> wrote
> in message news:B5EB8CBD-5414-4602-9AC5-75E8B5D53230@microsoft.com...
> David, the problems is still occuring. The developers fixed a different
> problem with their software, turns out it wasn't related to this IIS error.
> Here are some details below that posted some time ago. How do I use the
> debugger? Are there log files?
>
> ******Previous post******
> I've been getting a pop up error every couple of days on my Win2003 server
> with SP1. The pop up title says "GDI+ Window: w3wp.exe - Application Error"
> The error says " The instruction at "0x38734bf9 referenced memory at
> "0x38734bf9". The memory could not be "read". " Does anyone know what this
> means? It this realated to service pack on or a certain application? Also,
> one time I rebooted and got the following error 'IIS Worker Process
> encountered a problem and needed to close."
>
>
> "David Wang [Msft]" wrote:
>
> rights.
> wrote
> days,
> nothing
> unhealthy
>
>
>
|
|
|
|
|