EDN Admin
Well-known member
Can someone help with an exception that is being experienced by one of our customers?
The customer is getting the following exception generated.
Problem Event Name: APPCRASH
Application Name: iAM_esrv.exe
Application Version: 8.2794.0.1
Application Timestamp: 48fdb68e
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a76d
Exception Code: e06d7363
Exception Offset: 000442eb
OS Version: 6.0.6001.2.1.0.272.7
Locale ID: 1033
Additional Information 1: e51a
Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433
Additional Information 3: e51a
Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433
The system is hosted on VMWare ESX 3.5. As well as this problem being reported on a Windows 2008 Server, they have experienced it also on a Windows 2003 Server as well.
The application is compiles as C++ native code under VS 2005 SP1. The same code works when compiled under Visual Studio 6.
I understand the exception code e06d7363 , identifies it as a C++ exception code.
The executable does not stop, but continues, which suggests the exception is being handled.
We have tried to duplicate this problem on one of our in house systems, but are not able to reproduce it.
I have had access to one of their systems that exhibits this problem and have been able to trace the problem down by using depends.exe and running under profile.
00:00:09.531: DllMain(0x3D690000, DLL_PROCESS_ATTACH, 0x0012FD24) in "c
rogram filesitheoniambinRULE_VERIFY.DLL" returned 1 (0x1) by thread 1.
00:00:09.531: DllMain(0x3D4C0000, DLL_PROCESS_ATTACH, 0x0012FD24) in "crogram filesitheoniambinRNT.DLL" called by thread 1.
00:00:09.547: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "c:windowssystem32KERNEL32.DLL" at address 0x764F42EB by thread 1.
00:00:52.531: First chance exception 0x80000003 (Breakpoint) occurred in "c:windowssystem32NTDLL.DLL" at address 0x77867DFE by thread 1.
00:00:52.531: LoadLibraryW("rpcrt4.dll") called from "c:windowssystem32RPCRT4.DLL" at address 0x765FA927 by thread 1.
00:00:52.531: LoadLibraryW("rpcrt4.dll") returned 0x765C0000 by thread 1.
This suggests the problem occurs when the DLLMAIN function in the RNT.DLL is executed after it is attached to by the process. I cannot find any problem with the code in the DLLMAIN function. In fact by checking registry and file access it looks as though it never gets executed. I have placed a try catch block around the code, but it does not catch any exceptions and the exception occurs regardless. It looks like the exception is occurring event before the DLLMAIN code is executed.
Does anyone have any idea what could be causing this exception?
View the full article
The customer is getting the following exception generated.
Problem Event Name: APPCRASH
Application Name: iAM_esrv.exe
Application Version: 8.2794.0.1
Application Timestamp: 48fdb68e
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a76d
Exception Code: e06d7363
Exception Offset: 000442eb
OS Version: 6.0.6001.2.1.0.272.7
Locale ID: 1033
Additional Information 1: e51a
Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433
Additional Information 3: e51a
Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433
The system is hosted on VMWare ESX 3.5. As well as this problem being reported on a Windows 2008 Server, they have experienced it also on a Windows 2003 Server as well.
The application is compiles as C++ native code under VS 2005 SP1. The same code works when compiled under Visual Studio 6.
I understand the exception code e06d7363 , identifies it as a C++ exception code.
The executable does not stop, but continues, which suggests the exception is being handled.
We have tried to duplicate this problem on one of our in house systems, but are not able to reproduce it.
I have had access to one of their systems that exhibits this problem and have been able to trace the problem down by using depends.exe and running under profile.
00:00:09.531: DllMain(0x3D690000, DLL_PROCESS_ATTACH, 0x0012FD24) in "c
rogram filesitheoniambinRULE_VERIFY.DLL" returned 1 (0x1) by thread 1.00:00:09.531: DllMain(0x3D4C0000, DLL_PROCESS_ATTACH, 0x0012FD24) in "c
rogram filesitheoniambinRNT.DLL" called by thread 1.00:00:09.547: First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "c:windowssystem32KERNEL32.DLL" at address 0x764F42EB by thread 1.
00:00:52.531: First chance exception 0x80000003 (Breakpoint) occurred in "c:windowssystem32NTDLL.DLL" at address 0x77867DFE by thread 1.
00:00:52.531: LoadLibraryW("rpcrt4.dll") called from "c:windowssystem32RPCRT4.DLL" at address 0x765FA927 by thread 1.
00:00:52.531: LoadLibraryW("rpcrt4.dll") returned 0x765C0000 by thread 1.
This suggests the problem occurs when the DLLMAIN function in the RNT.DLL is executed after it is attached to by the process. I cannot find any problem with the code in the DLLMAIN function. In fact by checking registry and file access it looks as though it never gets executed. I have placed a try catch block around the code, but it does not catch any exceptions and the exception occurs regardless. It looks like the exception is occurring event before the DLLMAIN code is executed.
Does anyone have any idea what could be causing this exception?
- [Broken External Image]:[URL]http://i4.social.microsoft.com/Forums/resources/images/trans.gifReply[/url]
- [Broken External Image]:[URL]http://i4.social.microsoft.com/Forums/resources/images/trans.gifQuote[/url]
View the full article