IIS uses worker processes (w3wp.exe file in Windows) to handle client requests. If w3wp.exe crashes, your users cannot access to your application until the process starts again. In Event Viewer, you may see the exception codes 0xc0000005 and 0xe0434352 recorded during crashes.
Exception descriptions from Event Viewer are below. “Faulting module name” refers to the component that causes the crash.
Event ID: 1000
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2608, time stamp: 0x5bd1340d
Exception code: 0xe0434352
Event ID: 1000
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: OraOps12.dll, version: 2.121.1.0, time stamp: 0x52002676
Exception code: 0xc0000005
Based on the logs above, there are two exception codes that lead to the root cause:
0:000> !err 0xC0000005
0xc0000005 = STATUS_ACCESS_VIOLATION
OraOps12.dll
. This is a part of Oracle Data Access Components (ODAC). Upgrading or repairing the related module could fix the issue.System.NullReferenceException
or System.ArgumentException
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.