|
|
#1 (permalink) |
|
Guest
Posts: n/a
|
I’m using wise For Windows Installer 6.2 to create Application Server
installation. The installation uses external dll (C# dll) called “GeneralFunctions.dll” that include general functions. In order to use these functions from the installation I used call custom dll. The call custom dll cannot call C# dlls therefore I wrapped the dll with C++ dll called “GeneralFunctionsInterface.dll”. The C++ dll call the functions from C# dll. The installation copy both dlls to system32 folder, register com registration - the C# dll and use ‘call custom dll’ to call the C++ dll functions. The problem is after installation ended and a reboot performed the following error message appears: ‘Reporting queued error: faulting application msiexec.exe, version 3.1.4000.3959, faulting module GeneralFunctionsInterface.dll, version 1.0.0.1, fault address 0x0000adec.’ What this error means? What can I do to avoid this error? |
|
|
|
#2 (permalink) |
|
Guest
Posts: n/a
|
It means you've completely crashed msiexec.exe. You should give up calling managed code in custom action Dll calls, not because it's a mess (which it often is) but because the Windows Installer team doesn't support it. http://robmensching.com/blog/posts/2...-way-and-heres Calling managed code in custom actions is one of those things that everyone wants and whines about, but the fact is that what you're seeing is exactly the kind of mess that happens, and so you're asking how to debug a system process, which isn't exactly a Windows Installer question. You'd need a crash dump etc. -- Phil Wilson The Definitive Guide to Windows Installer http://www.apress.com/book/view/1590592972 "LimorTT" <LimorTT@discussions.microsoft.com> wrote in message news:FBF08849-E859-44AA-A4EC-B92A24E77D55@microsoft.com... > I’m using wise For Windows Installer 6.2 to create Application Server > installation. The installation uses external dll (C# dll) called > “GeneralFunctions.dll” that include general functions. > In order to use these functions from the installation I used call custom > dll. > The call custom dll cannot call C# dlls therefore I wrapped the dll with > C++ > dll called “GeneralFunctionsInterface.dll”. > The C++ dll call the functions from C# dll. > The installation copy both dlls to system32 folder, register com > registration - the C# dll and use ‘call custom dll’ to call the C++ dll > functions. > The problem is after installation ended and a reboot performed the > following > error message appears: > ‘Reporting queued error: faulting application msiexec.exe, version > 3.1.4000.3959, faulting module GeneralFunctionsInterface.dll, version > 1.0.0.1, fault address 0x0000adec.’ > What this error means? What can I do to avoid this error? > |
|
|
|
#3 (permalink) |
|
Guest
Posts: n/a
|
even though there is more than one DLL do not pluralize it in its actual
spelling "LimorTT" <LimorTT@discussions.microsoft.com> wrote in message news:FBF08849-E859-44AA-A4EC-B92A24E77D55@microsoft.com... > I’m using wise For Windows Installer 6.2 to create Application Server > installation. The installation uses external dll (C# dll) called > “GeneralFunctions.dll” that include general functions. > In order to use these functions from the installation I used call custom > dll. > The call custom dll cannot call C# dlls therefore I wrapped the dll with > C++ > dll called “GeneralFunctionsInterface.dll”. > The C++ dll call the functions from C# dll. > The installation copy both dlls to system32 folder, register com > registration - the C# dll and use ‘call custom dll’ to call the C++ dll > functions. > The problem is after installation ended and a reboot performed the > following > error message appears: > ‘Reporting queued error: faulting application msiexec.exe, version > 3.1.4000.3959, faulting module GeneralFunctionsInterface.dll, version > 1.0.0.1, fault address 0x0000adec.’ > What this error means? What can I do to avoid this error? > |
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|