IIS Worker Process stopped working and was closed and unmanaged code...

[wojski696969]

Hi.. i've got the serious problem..

In my ASP.NET 2.0 application I'm using COM dll file referenced by interop dll.
I'm using few properties from in one of the objects made from this library class.

Problem is that i get "IIS Worker Process stopped working and was closed" error on my server. The script is working too long and then the process is stoped.

I located wchich line of code causes the crash. It's invocation of one of the methods that i used, and it has following form:

int PerformInitTran saction(void)

This method connects to the Bank server and returns the status of the operation, so maybe its the problem with the permissions or sth?

This situation shows up on the IIS7, WindowsServer 2008, ClassicAppPool.
The problem didn't show up on my local IIS7 Vista server.

Please, help me with that issue.
Thanks..

PS. I'm also attached analyze of minidump made in windbg.

---------------- DUMP ANALYZE -----------------

FAULTING_IP: 
ntdll+23592
77e53592 f00fba3000      lock btr dword ptr [eax],0

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 77e53592 (ntdll+0x00023592)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000024
Attempt to write to address 00000024

PROCESS_NAME:  w3wp.exe

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 77710000 kernel32

DEBUG_FLR_IMAGE_TIMESTAMP:  3f7da237

MODULE_NAME: e24PaymentPipe

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000024

WRITE_ADDRESS:  00000024 

FOLLOWUP_IP: 
e24PaymentPipe+290ab
1b5a90ab ??              ???

MANAGED_STACK: !dumpstack -EE
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
            2) the file mscordacwks.dll that matches your version of mscorwks.dll is 
                in the version directory
            3) or, if you are debugging a dump file, verify that the file 
                mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
            4) you are debugging on the same architecture as the dump file.
                For example, an IA64 dump file must be debugged on an IA64
                machine.

You can also run the debugger command .cordll to control the debugger's
load of mscordacwks.dll.  .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.

If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.

FAULTING_THREAD:  00000900

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_ONE_BIT_INVALID_POINTER_WRITE_WRONG_SYMBOLS

PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_DEREFERENCE_ONE_BIT

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE_ONE_BIT

LAST_CONTROL_TRANSFER:  from 1b5a90ab to 77e53592

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
1c15d784 1b5a90ab 00000020 1c15d7a0 1b5a36bd ntdll+0x23592
1c15d790 1b5a36bd 00000000 00000000 1c15e818 e24PaymentPipe+0x290ab
1c15d7a0 1b5868d3 1c161630 00000001 00000138 e24PaymentPipe+0x236bd
1c15e818 1b586395 1c15f1a0 1c15f394 1c15f398 e24PaymentPipe+0x68d3
1c15f078 1b584ff6 1c15f1a0 1c15f394 1c15f398 e24PaymentPipe+0x6395
1c15f144 1b599c84 1c160080 1c15f1a0 1c15f394 e24PaymentPipe+0x4ff6
1c15f19c 773f43b6 1c1600fc 1c15f3a8 00000202 e24PaymentPipe+0x19c84
1c15f1b8 77480cc6 1b581de8 1c15f398 00000002 rpcrt4+0x243b6
1c15f5bc 77481968 0066f868 01b44100 01b38cd0 rpcrt4+0xb0cc6
1c15f604 773227f7 0066f868 01b38cd0 01b44100 rpcrt4+0xb1968
1c15f628 77a59759 01bdc638 01b38cd0 01b44100 oleaut32+0x127f7
1c15f670 77a596f3 01b38cd0 01c4c7ec 1bc4ec18 ole32+0x129759
1c15f6bc 77979d67 01b38cd0 01ba7648 01bdc638 ole32+0x1296f3
1c15f798 77979c5c 01b44100 00000000 01bdc638 ole32+0x49d67
1c15f7b4 7797aab0 01b38cd0 00000001 01bdc638 ole32+0x49c5c
1c15f7e0 77a5961b 01b38cd0 00000001 01bdc638 ole32+0x4aab0
1c15f814 77a59498 d0908070 01b44100 01bdc638 ole32+0x12961b
1c15f8f0 77a59aa2 01b38c78 01b5a0a8 00000000 ole32+0x129498
1c15f918 7797a8ea 01b38c78 00000400 01b7d910 ole32+0x129aa2
1c15f92c 7797a8a9 01b38c78 00000000 7797a80c ole32+0x4a8ea
1c15f970 775a8807 002f0066 00000400 0000babe ole32+0x4a8a9
1c15f99c 775a8962 7797a80c 002f0066 00000400 user32+0x18807
1c15fa14 775a8aad 00000000 7797a80c 002f0066 user32+0x18962
1c15fa78 775a8b00 7797a80c 00000000 1c15fabc user32+0x18aad
1c15fa88 7796ee5d 1c15faa0 00000000 77a60ba8 user32+0x18b00
1c15fabc 7796aaa7 00007530 777211e1 01c4bbf0 ole32+0x3ee5d
1c15fad8 7796a9e9 1c15fafc 7796e086 77a60ba8 ole32+0x3aaa7
1c15fae0 7796e086 77a60ba8 00000000 01c4bbf0 ole32+0x3a9e9
1c15fafc 7796e0e2 00000000 00000000 1c15fb18 ole32+0x3e086
1c15fb0c 7779e4a5 01c4bbf0 1c15fb58 77eacfed ole32+0x3e0e2
1c15fb18 77eacfed 01c4bbf0 7a97e633 00000000 kernel32+0x8e4a5
1c15fb58 77ead1ff 7796e0cc 01c4bbf0 ffffffff ntdll+0x7cfed
1c15fb70 00000000 7796e0cc 01c4bbf0 00000000 ntdll+0x7d1ff


STACK_COMMAND:  .cxr 00000000 ; kb ; ~31s; .ecxr ; kb

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  e24PaymentPipe+290ab

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  e24PaymentPipe.dll

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE_ONE_BIT_c0000005_e24PaymentPipe.dll!Unknown

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/w3wp_exe/7_0_6001_18000/47919413/ntdll_dll/6_0_6001_18000/4791a783/c0000005/00023592.htm?Retriage=1

Followup: MachineOwner

[Mike426]

Can you try the following:
1. Temporarily run your application pool under an account with administrative privileges and see if you can reproduce the error.
2. If you can reproduce the error, then write a quick Windows Application test app and run the same code interactively (i.e. clicking a button on a form, rather than invoking a web application).

If it works interactively, but not in a web app, then you may need to control the threading in the web app to make it more like a Windows form. You might need the ASPCOMPAT option, or you may need to make sure COM calls are serviced on the same thread that instantiated the COM object.