w3wp.exe exception
in [IIS]
|
From: GaneshBabu.CV on 2 Oct 2007 01:53 Dear Sir We found out the reason for the memory exception. The problem is we are generating a huge .html file at the server side. E.g The size of the file will be 900 MB. When we are trying to load the .HTML file from an .ASP file at the client side we are getting the exception at the server side. We have solved this problem also. But we are not able to find out the reason why the Exception has occurred. If you have any idea regarding please let us know. Thanks in advance On Sep 21, 2:18 pm, David Wang <w3.4...(a)gmail.com> wrote: > Neither. > > The event log entry indicates that something inside the worker process > prevented it from shutting down within its configured time limit when > IIS told it to recycle due to some other recycling metric. > > The appropriate values are all depending on your server's > configuration. > > I recommend running Application Verifier while you simulate using your > application to try and find the memory problem. > > Of course, since there was no clear reproduction steps, you have no > guarantee that what you are doing will actuall result in the memory > issue you are looking for. So, you could be just wasting time. Or not. > No one really knows. That's the unfortunate nature of bugs. > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > // > > On Sep 20, 9:26 pm, GaneshBabu...(a)gmail.com wrote: > > > > > Dear Sir > > In order to simulate the memory problem we executed our > > application for almost 48 hours continiously. We didnt get any memory > >exceptionbut after 48 hours the session was cut and the following > > message was logged in the event log > > > A process serving application pool DefaultAppPool exceeded time limits > > during shut down. The process id was process id. > > > Event ID - 1013 > > > Is it a problem or it is because our application ran for a long time > > the process was shutdown. > > > On Sep 18, 12:55 pm, David Wang <w3.4...(a)gmail.com> wrote: > > > > Following the strategy that I outline at:http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_... > > > > We are going after the issues one at a time, not all at once. > > > > We know there is memory corruption. I would use Application Verifier > > > and enable "Page Heap" onw3wp.exe, and then try to reproduce the > > > issue. > > > > When it happens, Application Verifier will break into the process. If > > > you happen to have a debugger attached, you can directly observe the > > > culprit. > > > > How to do this is beyond the scope of this newsgroup. You can either > > > learn on your own, pay someone else to learn, or pay someone else to > > > do it. > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > > // > > > > On Sep 17, 11:52 pm,GaneshBabu...(a)gmail.com wrote: > > > > > Yes Sir our code is ASP, but we do use COM DLLs for Database > > > > connectivity and Logging. When we analyzed the memory leaks we found > > > > out that the BSTR were not freed using SysFreeString(). When we called > > > > SysFreeString also the same problem persists. Sometimes we get an > > > >exceptiondialog fromw3wp.exe, it is an memoryexception. I > > > > downloaded Application verifier from micorosoft site but Iam not able > > > > to executew3wp.exeusing the verifier. When Debug diag is not > > > > runnning theexceptiondialog apperas and event log entries are > > > > created, but if Debug diag is executed then theExceptiondialog does > > > > not appear and only event log entries are created. Please help me in > > > > how to use Appverifier forw3wp.exeservice and suggest me some method > > > > through which i can identify the cause of the problem. > > > > > Thanks in Advance > > > > > On Sep 18, 1:23 am, David Wang <w3.4...(a)gmail.com> wrote: > > > > > > It *could*, but I consider it the last option to explore because if it > > > > > is a problem with IIS/Windows, the issue would be hit far more > > > > > frequently and honestly we haven't seen such a deluge. I realize that > > > > > users usually trust their own code and not Microsoft's, but history > > > > > has shown that to be an incorrect assumption. Put in another way -- if > > > > > your application gets used by 100 million people in countless > > > > > different ways, how likely do you think it'd have issues? > > > > > > ISAPI DLL is a common cause but not the only. Are you running *any* > > > > > third party code with your application. I see that your application is > > > > > ASP, so it is purely ASP which does not do *any* Server.CreateObject() > > > > > or new ActiveXObject() calls? Those calls would load other native > > > > > code into the web server that could crash, even if your web page is > > > > > pure ASP. > > > > > > I'm also going to have to check if that "crash" is one of the expected > > > > > exceptions -- there's a couple of internal Windows APIs that actually > > > > > use exceptions as a normal part of operation and should be ignored by > > > > > the debugger. I could have sworn ntdll! > > > > > ExpInterlockedPopEntrySListFault is one of them. > > > > > > Does this happen if you do not run DebugDiag to track memory leaks? > > > > > Because you have a crash, not memory leak, and they are tracked > > > > > differently > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > > > > // > > > > > > On Sep 16, 9:52 pm,GaneshBabu...(a)gmail.com wrote: > > > > > > > Thanks for the help. But we dont use any ISAPI DLLs in our > > > > > > application. We reviewed the code for memory leaks but didnt find any > > > > > > problem. This problem is occurring only in windows 2003 R2 SP2. Will > > > > > > it be a problem with 2003 R2? > > > > > > > On Sep 16, 12:14 pm, David Wang <w3.4...(a)gmail.com> wrote: > > > > > > > > Your application is running native code which is crashing the worker > > > > > > > process (that's what 0xc0000005 means). > > > > > > > > There is also signs of memory corruption in the worker process. It > > > > > > > *may* be the cause of the crash (in which case you have one issue), or > > > > > > > it may not (which means you have more than one issue within your > > > > > > > website). > > > > > > > > Please start by identifying all custom ISAPI Filter DLL and ISAPI > > > > > > > Extension DLL loaded on your server. > > > > > > > > When there is signs of memory corruption, the code that actually > > > > > > > crashed may *not* be the culprit but rather unfortunate victim of the > > > > > > > memory corrupting code. For example, the code that crashed in your > > > > > > > example was NTDLL, an internal Windows DLL, but what it was doing is > > > > > > > hardly the cause of the memory corruption -- it is clearly the victim > > > > > > > of some other memory corrupting code. It is usually beneficial to > > > > > > > enable PageHeap to catch many (but not all) code that corrupt memory > > > > > > > as it corrupts its, which is like catching a crook red-handed. > > > > > > > > Microsoft publishes free Application Verifier as well as Debugging > > > > > > > Tools which do all these things (and more), as well as general > > > > > > > instructions on how to use them. It would be beneficial in your > > > > > > > situation to use them to diagnose your issue. > > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > > > > > > // > > > > > > > > On Sep 14, 5:02 am,GaneshBabu...(a)gmail.com wrote: > > > > > > > > > Hi, > > > > > > > > > We are running ASP application in IIS 6.0. > > > > > > > > Butw3wp.execrashes unexpectedly with the following message. > > > > > > > > > Anexceptiondialog appears and one of the following message is logged > > > > > > > > in event log > > > > > > > > > And any one of the following are logged in the System log during the > > > > > > > >w3wp.exeexception: > > > > > > > > Message 1 > > > > > > > > > Event Type: Warning > > > > > > > > Event Source: W3SVC > > > > > > > > Event Category: None > > > > > > > > Event ID: 1009 > > > > > > > > Date: Date > > > > > > > > Time: Time > > > > > > > > User: N/A > > > > > > > > Computer: ComputerName > > > > > > > > Description: > > > > > > > > A process serving application pool 'DefaultAppPool' terminated > > > > > > > > unexpectedly. The process id was '1234'. The process exit code was > > > > > > > > '0xc0000005'. > > > > > > > > > Message 2 > > > > > > > > > Event Type: Warning > > > > > > > > Event Source: W3SVC > > > > > > > > Event Category: None > > > > > > > > Event ID: 1011 > > > > > > > > Date: Date > > > > > > > > Time: Time > > > > > > > > User: N/A > > > > > > > > Computer: ComputerName > > > > > > > > Description: > > > > > > > > A process serving application pool 'DefaultAppPool' suffered a fatal > > > > > > > > communication error with the World Wide Web Publishing Service. The > > > > > > > > process id was '1234'. The data field contains the error number. > > > > > > > > > Message 3 > > > > > > > > > Event Type: Warning > > > > > > > > Event Source: W3SVC > > > > > > > > Event Category: None > > > > > > > > Event ID: 1013 > > > > > > > > Date: Date > > > > > > > > Time: Time > > > > > > > > User: N/A > > > > > > > > Computer: ComputerName > > > > > > > > Description: > > > > > > > > The process where application pool 'DefaultAppPool' was offered > > > > > > > > exceeded the time limitation in the middle of the shutdown. Process id > > > > > > > > was two '41 ' > > > > > > > > > At times, only any of the above entry is found in the event log > > > > > > > > without thew3wp.exeexceptiondialog. > > > > > > > > > We have run Microsoft's debug tool(Debug Diag) and have captured the > > > > > > > > following > > > > > > > > > Analysis Summary > > > > > > > > Type Description Recommendation > > > > > > > > Error In > > > > > > > > w3wp__PID__4468__Date__09_11_2007__Time_10_30_53AM__0__Second_Chance_Exception_C0000005.dmp > > > > > > > > the assembly instruction at ntdll!ExpInterlockedPopEntrySListFault in > > > > > > > > C:\WINDOWS\system32\ntdll.dll from Microsoft Corporation has caused an > > > > > > > > access violationexception(0xC0000005) when trying to read from > > > > > > > > memory location 0x00000002 on thread 8 > > > > > > > > > Heap corruption was detected in heap 0x00080000, however pageheap was > > > > > > > > not enabled in this dump. Please follow the instructions in the > > > > > > > > recommendation section for troubleshooting heap corruption issues. > > > > > > > > > Current NTGlobalFlags value: 0x0 An access violationexceptionthrown > > > > > > > > by a heap memory manager function indicates heap corruption.. Please > > > > > > > > follow the steps outlined in the following Knowledge Base article: > > > > > > > > > 300966 Howto debug heap corruption issues in Internet Information > > > > > > > > Services (IIS) > > > > > > > > Warning 1 client connection(s) in > > ... > > read more »- Hide quoted text - > > - Show quoted text -
From: GaneshBabu.CV on 2 Oct 2007 02:37
Dear Sir The actual problem was the we write the entire contents of the .HTML file within a <table> and </table> tag. We understand that IE will display the contents only after the constructing the entire table. E.g It the file size is 900 MB then the entire contents will be written within a <table> and </table> tag. We have solved the problem by splitting the tables ie by rendering after every 100 records we close the table and open a new table and write the next set of records. On Oct 2, 10:53 am, GaneshBabu...(a)gmail.com wrote: > Dear Sir > We found out the reason for the memoryexception. The > problem is we are generating a huge .html file at the server side. E.g > The size of the file will be 900 MB. When we are trying to load > the .HTML file from an .ASP file at the client side we are getting theexceptionat the server side. We have solved this problem also. But we > are not able to find out the reason why theExceptionhas occurred. If > you have any idea regarding please let us know. > > Thanks in advance > > On Sep 21, 2:18 pm, David Wang <w3.4...(a)gmail.com> wrote: > > > > > Neither. > > > The event log entry indicates that something inside the worker process > > prevented it from shutting down within its configured time limit when > > IIS told it to recycle due to some other recycling metric. > > > The appropriate values are all depending on your server's > > configuration. > > > I recommend running Application Verifier while you simulate using your > > application to try and find the memory problem. > > > Of course, since there was no clear reproduction steps, you have no > > guarantee that what you are doing will actuall result in the memory > > issue you are looking for. So, you could be just wasting time. Or not. > > No one really knows. That's the unfortunate nature of bugs. > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > // > > > On Sep 20, 9:26 pm, GaneshBabu...(a)gmail.com wrote: > > > > Dear Sir > > > In order to simulate the memory problem we executed our > > > application for almost 48 hours continiously. We didnt get any memory > > >exceptionbut after 48 hours the session was cut and the following > > > message was logged in the event log > > > > A process serving application pool DefaultAppPool exceeded time limits > > > during shut down. The process id was process id. > > > > Event ID - 1013 > > > > Is it a problem or it is because our application ran for a long time > > > the process was shutdown. > > > > On Sep 18, 12:55 pm, David Wang <w3.4...(a)gmail.com> wrote: > > > > > Following the strategy that I outline at:http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_... > > > > > We are going after the issues one at a time, not all at once. > > > > > We know there is memory corruption. I would use Application Verifier > > > > and enable "Page Heap" onw3wp.exe, and then try to reproduce the > > > > issue. > > > > > When it happens, Application Verifier will break into the process. If > > > > you happen to have a debugger attached, you can directly observe the > > > > culprit. > > > > > How to do this is beyond the scope of this newsgroup. You can either > > > > learn on your own, pay someone else to learn, or pay someone else to > > > > do it. > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > > > // > > > > > On Sep 17, 11:52 pm,GaneshBabu...(a)gmail.com wrote: > > > > > > Yes Sir our code is ASP, but we do use COM DLLs for Database > > > > > connectivity and Logging. When we analyzed the memory leaks we found > > > > > out that the BSTR were not freed using SysFreeString(). When we called > > > > > SysFreeString also the same problem persists. Sometimes we get an > > > > >exceptiondialog fromw3wp.exe, it is an memoryexception. I > > > > > downloaded Application verifier from micorosoft site but Iam not able > > > > > to executew3wp.exeusing the verifier. When Debug diag is not > > > > > runnning theexceptiondialog apperas and event log entries are > > > > > created, but if Debug diag is executed then theExceptiondialog does > > > > > not appear and only event log entries are created. Please help me in > > > > > how to use Appverifier forw3wp.exeservice and suggest me some method > > > > > through which i can identify the cause of the problem. > > > > > > Thanks in Advance > > > > > > On Sep 18, 1:23 am, David Wang <w3.4...(a)gmail.com> wrote: > > > > > > > It *could*, but I consider it the last option to explore because if it > > > > > > is a problem with IIS/Windows, the issue would be hit far more > > > > > > frequently and honestly we haven't seen such a deluge. I realize that > > > > > > users usually trust their own code and not Microsoft's, but history > > > > > > has shown that to be an incorrect assumption. Put in another way -- if > > > > > > your application gets used by 100 million people in countless > > > > > > different ways, how likely do you think it'd have issues? > > > > > > > ISAPI DLL is a common cause but not the only. Are you running *any* > > > > > > third party code with your application. I see that your application is > > > > > > ASP, so it is purely ASP which does not do *any* Server.CreateObject() > > > > > > or new ActiveXObject() calls? Those calls would load other native > > > > > > code into the web server that could crash, even if your web page is > > > > > > pure ASP. > > > > > > > I'm also going to have to check if that "crash" is one of the expected > > > > > > exceptions -- there's a couple of internal Windows APIs that actually > > > > > > use exceptions as a normal part of operation and should be ignored by > > > > > > the debugger. I could have sworn ntdll! > > > > > > ExpInterlockedPopEntrySListFault is one of them. > > > > > > > Does this happen if you do not run DebugDiag to track memory leaks? > > > > > > Because you have a crash, not memory leak, and they are tracked > > > > > > differently > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang > > > > > > // > > > > > > > On Sep 16, 9:52 pm,GaneshBabu...(a)gmail.com wrote: > > > > > > > > Thanks for the help. But we dont use any ISAPI DLLs in our > > > > > > > application. We reviewed the code for memory leaks but didnt find any > > > > > > > problem. This problem is occurring only in windows 2003 R2 SP2. Will > > > > > > > it be a problem with 2003 R2? > > > > > > > > On Sep 16, 12:14 pm, David Wang <w3.4...(a)gmail.com> wrote: > > > > > > > > > Your application is running native code which is crashing the worker > > > > > > > > process (that's what 0xc0000005 means). > > > > > > > > > There is also signs of memory corruption in the worker process. It > > > > > > > > *may* be the cause of the crash (in which case you have one issue), or > > > > > > > > it may not (which means you have more than one issue within your > > > > > > > > website). > > > > > > > > > Please start by identifying all custom ISAPI Filter DLL and ISAPI > > > > > > > > Extension DLL loaded on your server. > > > > > > > > > When there is signs of memory corruption, the code that actually > > > > > > > > crashed may *not* be the culprit but rather unfortunate victim of the > > > > > > > > memory corrupting code. For example, the code that crashed in your > > > > > > > > example was NTDLL, an internal Windows DLL, but what it was doing is > > > > > > > > hardly the cause of the memory corruption -- it is clearly the victim > > > > > > > > of some other memory corrupting code. It is usually beneficial to > > > > > > > > enable PageHeap to catch many (but not all) code that corrupt memory > > > > > > > > as it corrupts its, which is like catching a crook red-handed. > > > > > > > > > Microsoft publishes free Application Verifier as well as Debugging > > > > > > > > Tools which do all these things (and more), as well as general > > > > > > > > instructions on how to use them. It would be beneficial in your > > > > > > > > situation to use them to diagnose your issue. > > > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David..Wang > > > > > > > > // > > > > > > > > > On Sep 14, 5:02 am,GaneshBabu...(a)gmail.com wrote: > > > > > > > > > > Hi, > > > > > > > > > > We are running ASP application in IIS 6.0. > > > > > > > > > Butw3wp.execrashes unexpectedly with the following message. > > > > > > > > > > Anexceptiondialog appears and one of the following message is logged > > > > > > > > > in event log > > > > > > > > > > And any one of the following are logged in the System log during the > > > > > > > > >w3wp.exeexception: > > > > > > > > > Message 1 > > > > > > > > > > Event Type: Warning > > > > > > > > > Event Source: W3SVC > > > > > > > > > Event Category: None > > > > > > > > > Event ID: 1009 > > > > > > > > > Date: Date > > > > > > > > > Time: Time > > > > > > > > > User: N/A > > > > > > > > > Computer: ComputerName > > > > > > > > > Description: > > > > > > > > > A process serving application pool 'DefaultAppPool' terminated > > > > > > > > > unexpectedly. The process id was '1234'. The process exit code was > > > > > > > > > '0xc0000005'. > > > > > > > > > > Message 2 > > > > > > > > > > Event Type: Warning > > > > > > > > > Event Source: W3SVC > > > > > > > > > Event Category: None > > > > > > > > > Event ID: 1011 > > > > > > > > > Date: Date > > > > > > > > > Time: Time > > > > > > > > > User: N/A > > > > > > > > > Computer: ComputerName > > > > > > > > > Description: > > > > > > > > > A process serving application pool 'DefaultAppPool' suffered a fatal > > > > > > > > > communication error with the World Wide Web Publishing Service. The > > > > > > > > > process id was '1234'. The data field contains the error number. > > > > > > > > > > Message 3 > > > > > > > > > > Event Type: Warning > > > > > > > > > Event Source: W3SVC > > > > > > > > > Event Category: None > > > > > > > > > Event ID: 1013 > > > > > > > > > Date: Date > > > > > > > > > Time: Time > > > > > > > > > User: N/A > > > > > > > > > Computer: ComputerName > > > > > > > > > Description: > > > > > > > > > The process where application pool 'DefaultAppPool' was offered > > > > > > > > > exceeded the time limitation in the middle of the shutdown. Process id > > > > > > > > > was two '41 ' > > > > > > > > > > At times, only any of the above entry is found in the event log > > > > > > > > > without thew3wp.exeexceptiondialog. > > > > > > > > > > We have run Microsoft's debug tool(Debug Diag) and have captured the > > > > > > > > > following > > > > > > > > > > Analysis Summary > > > > > > > > > Type Description Recommendation > > > > > > > > > Error In > > > > > > > > > w3wp__PID__4468__Date__09_11_2007__Time_10_30_53AM__0__Second_Chance_Exception_C0000005.dmp > > > > > > > > > the assembly instruction at ntdll!ExpInterlockedPopEntrySListFault in > > ... > > read more »- Hide quoted text - > > - Show quoted text - |