IIS Stop responsing problem

Hi all,

I have an application written by ASP running in my win2003 + IIS 6 box. I
found that the IIS sometimes stop responsing and when I check the log file, I
find that there is an error message like the following:

ASP_0241|CreateObject_Exception|42|80020009

And in the win2003 event viewer, I found the following error message:

production/show_all_item.asp CreateObject exception. '(null)'
CreateObject(exception C0000005)

I have checked the show_all_item.asp, there is 1 createobject statement in
it and the object is a com server written in VFP. The statement well fine
most of the time, but I don't know why sometimes the IIS will crash because
of that statement.

Anyone have idea ?
Is it related to the loading problem ? since the application work fine in my
development box, however, this problem appear when I move the application to
the production environment

Thank you very much

Regards,
On

David
Wed Dec 08 23:03:40 CST 2004

Actually, IIS is not crashing -- the COM server in VFP is crashing the IIS
process -- so you will need to debug and get that COM server code fixed.

If IIS stops responding, then you are likely still running in IIS5
Compatibility Mode. If you run the application in IIS6 Worker Process
Isolation Mode, then the crash of w3wp.exe will simply be noted in the event
log and IIS will start up a new worker process to handle requests. IIS6
runs in IIS5 compatibility mode if you upgraded or explicitly chose the
mode -- otherwise, it runs in Worker Process Isolation Mode, which is far
more resiliant to user code errors.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"ong" <ong@discussions.microsoft.com> wrote in message
news:117059AF-4CD5-49EE-9F99-9D149B2365EB@microsoft.com...
Hi all,

I have an application written by ASP running in my win2003 + IIS 6 box. I
found that the IIS sometimes stop responsing and when I check the log file,
I
find that there is an error message like the following:

ASP_0241|CreateObject_Exception|42|80020009

And in the win2003 event viewer, I found the following error message:

production/show_all_item.asp CreateObject exception. '(null)'
CreateObject(exception C0000005)

I have checked the show_all_item.asp, there is 1 createobject statement in
it and the object is a com server written in VFP. The statement well fine
most of the time, but I don't know why sometimes the IIS will crash because
of that statement.

Anyone have idea ?
Is it related to the loading problem ? since the application work fine in my
development box, however, this problem appear when I move the application to
the production environment

Thank you very much

Regards,
On

ong
Sat Dec 11 03:19:01 CST 2004

Hi David,

Thank you for your reply.

Yes, I am wrong that the IIS is not crash, because I have 2 application
running on the same IIS server (run in 2 virtual directory and 2 application
pool). The problem only occur in one of the application, and when the problem
occur, I still can browse the other one.
However, when the problem occur, that application is totally malfunction,
and it seems that the IIS does not start a new work thread to handle further
request. Do I need to explicit set anything in order to run IIS worker
process isolation mode ?

It is very hard for me to debug the application since the application does
not crash frequently, instead, it crashes after running for 2-3 days.
Therefore, I cannot know which function/module is going wrong. Any tools
which can tell what function/module the application is running when the crash
occur ?

Thanks

ong


"David Wang [Msft]" wrote:

> Actually, IIS is not crashing -- the COM server in VFP is crashing the IIS
> process -- so you will need to debug and get that COM server code fixed.
>
> If IIS stops responding, then you are likely still running in IIS5
> Compatibility Mode. If you run the application in IIS6 Worker Process
> Isolation Mode, then the crash of w3wp.exe will simply be noted in the event
> log and IIS will start up a new worker process to handle requests. IIS6
> runs in IIS5 compatibility mode if you upgraded or explicitly chose the
> mode -- otherwise, it runs in Worker Process Isolation Mode, which is far
> more resiliant to user code errors.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "ong" <ong@discussions.microsoft.com> wrote in message
> news:117059AF-4CD5-49EE-9F99-9D149B2365EB@microsoft.com...
> Hi all,
>
> I have an application written by ASP running in my win2003 + IIS 6 box. I
> found that the IIS sometimes stop responsing and when I check the log file,
> I
> find that there is an error message like the following:
>
> ASP_0241|CreateObject_Exception|42|80020009
>
> And in the win2003 event viewer, I found the following error message:
>
> production/show_all_item.asp CreateObject exception. '(null)'
> CreateObject(exception C0000005)
>
> I have checked the show_all_item.asp, there is 1 createobject statement in
> it and the object is a com server written in VFP. The statement well fine
> most of the time, but I don't know why sometimes the IIS will crash because
> of that statement.
>
> Anyone have idea ?
> Is it related to the loading problem ? since the application work fine in my
> development box, however, this problem appear when I move the application to
> the production environment
>
> Thank you very much
>
> Regards,
> On
>
>
>

David
Mon Dec 13 20:33:50 CST 2004

If you upgraded, IIS6 will be running in IIS5 Compatibility Mode by default;
otherwise, it is running in IIS6 Worker Process Isolation Mode. You can
configure this setting in the IIS Manager UI. IF you do not know how,
please search for it in F1 help.

A debugger is the only way to catch a process before it crashes and allow
you to examine the function/module where the exception happened. You need
to have the right symbols for your VPF COM Server to do any debugging.
Depending on the IIS6 process model, you should follow different debugger
setup instructions. For IIS5 Compatibility, follow existing IIS5 debugging
steps. Otherwise, follow IIS6 debugging steps.

I suggest you first determine what process your VFP COM Server is loaded in,
and then make sure debuggers are attached to that process and waiting for a
crash to happen. If you do not know how, I suggest searching for it because
you will need to know how to do this to debug anything else on Windows. It
is not hard once you learn the idea -- so I want you to learn the steps and
am not going to spoon feed you any details other than "it's possible".

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"ong" <ong@discussions.microsoft.com> wrote in message
news:3AA1E4D5-05FF-406F-A958-B206EB5331A7@microsoft.com...
Hi David,

Thank you for your reply.

Yes, I am wrong that the IIS is not crash, because I have 2 application
running on the same IIS server (run in 2 virtual directory and 2 application
pool). The problem only occur in one of the application, and when the
problem
occur, I still can browse the other one.
However, when the problem occur, that application is totally malfunction,
and it seems that the IIS does not start a new work thread to handle further
request. Do I need to explicit set anything in order to run IIS worker
process isolation mode ?

It is very hard for me to debug the application since the application does
not crash frequently, instead, it crashes after running for 2-3 days.
Therefore, I cannot know which function/module is going wrong. Any tools
which can tell what function/module the application is running when the
crash
occur ?

Thanks

ong


"David Wang [Msft]" wrote:

> Actually, IIS is not crashing -- the COM server in VFP is crashing the IIS
> process -- so you will need to debug and get that COM server code fixed.
>
> If IIS stops responding, then you are likely still running in IIS5
> Compatibility Mode. If you run the application in IIS6 Worker Process
> Isolation Mode, then the crash of w3wp.exe will simply be noted in the
event
> log and IIS will start up a new worker process to handle requests. IIS6
> runs in IIS5 compatibility mode if you upgraded or explicitly chose the
> mode -- otherwise, it runs in Worker Process Isolation Mode, which is far
> more resiliant to user code errors.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers n