runtime error while running the setup on vista

Hi everybody,

I am getting the following runtime error while running the setup on vista. If anybody has faced similar error, Pls help me. The error is as follows:

Problem signature:
Problem Event Name: APPCRASH
Application Name: propglue.exe
Application Version: 12.0.1.161
Application Timestamp: 452c8925
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.5744.16384
Fault Module Timestamp: 452358e5
Exception Code: c0150002
Exception Offset: 000089f3
OS Version: 6.0.5744.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 9d13
Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3: 9d13
Additional Information 4: 1abee00edb3fc1158f9ad6f44f0f6be8

Read our privacy statement:
http://go.microsoft.com/fwlink/ linkid=50163&clcid=0x0409

Error in the event viewer is as follows:

faulting module ntdll.dll,
exception code 0xc0150002,
fault offset 0x000089f3,

version 6.0.5744.16384,
time stamp 0x452358e5,
process id 0xad4,
application start time 0x01c6eddacd528727.

TIA,

Regards,

bharath .k



Answer this question

runtime error while running the setup on vista

  • Cory.Isakson

    bharath-k wrote:

    D:\Propglue.exe /Regserver. The error is "The Application has failed to start because MFC80D.dll was not found. Re-Installing the application may fix the problem". Firstly, I am using release exe, why it has to depend on a debug dll . I had checked it in the dependency walker, it is highlighting on MFC80.dll not the debug dll

    This error indicates that this exe depends on debug MFC. If dependency walker does not show it, perhaps this is only bogus dependency in manifest of this EXE. Open this EXE in Visual Studio and check what is in RT_MANIFEST file. It should not have any dependency on Microsoft.VC80.DebugMFC assembly. If you do see this dependency, the most likely reason for this dependency pulled in is a fact that one or more of libraries that are part of this EXE are built with Debug MFC. Check that every object, static library and import library that are used by the EXE are built as Release, not Debug.

    Second question is when do you run this /regserver command during installation. On Vista you cannot use VC++ assemblies any time before InstallFinalize action of MSI that installs them. If you have parts of your install that you would like to start while MSI installing, you need to build two phase commit of MSI, when you first finalize install of VC++ assemblies into WinSxS folder, then start services or apps that depend on these assemblies.

    Hope this helps,

    Nikola

    VC++



  • dakerson

    Hi,

    Is two phase commit is required in xp and is it mandatory for Vista Pls guide & help me

    Thanks and Regards,

    Bharath .k


  • learnerplates

    Hi Nikola and David,

    Thanks for the help, Now I am able to register the exe. and setup goes through fine, if visual c++ 2005 redistributable is already installed. It shows that if I make two phase commit, the installation will go through fine. can you tell me how to make two-phase commit

    TIA,

    Regards,

    bharath .K


  • Chuff

    Yes David,

    I think there are lot of dependent dll's for that exe. I think I can fix it up,with some trail and error effort.

    Thanks for the help.

    Regards,

    bharath .k


  • ABS_BEG

    It is actually required on both XP and Vista. But in some scenarios it may work on XP with single phase commit due to a way of how MSMs are installed on XP.

    I am not expert of MSI. As far as I know you can use Commit custom action to commit isntallation of some part of MSI before other parts are executed. http://msdn.microsoft.com/library/default.asp url=/library/en-us/msi/setup/custom_action_in_script_execution_options.asp Some other documentation mentions 2-phase commit process for global assemblies. This can be found here http://msdn.microsoft.com/library/default.asp url=/library/en-us/msi/setup/msiassembly_table.asp. See around this paragraph:

    The assemblies are not committed until successful execution of the InstallFinalize Action. This means that if you author a custom action or resource that relies on the assembly, it must be sequenced after the InstallFinalize Action. For example, if you need to start a service that depends on an assembly in the Global Assembly Cache (GAC), you must schedule the starting of that service after the InstallFinalize Action. This means you cannot use the ServiceControl Table to start the service, instead you must use a custom action that is sequenced after InstallFinalize.

    For more guidances on MSI, check out WIndows Installer docs and newsgroups.

    Nikola



  • Tom De Cort

    Hi David,

    I had found out the reason for this error, it is that Propglue.exe is not getting registered. When i do

    D:\Propglue.exe /Regserver. The error is "The Application has failed to start because MFC80D.dll was not found. Re-Installing the application may fix the problem". Firstly, I am using release exe, why it has to depend on a debug dll . I had checked it in the dependency walker, it is highlighting on MFC80.dll not the debug dll . If you have any Idea, pls throw some light on it.

    Thanks and regards,

    Bharath .K


  • Doraemon_1

    We've been doing some testing on Vista and I don't think we've run into this problem at all...

    What's interesting about your setup



  • danadanny

    I've asked someone from the VC++ team to help out.

    This sounds loosely familiar, but I don't remember the specifics. How are you deploying MFC80 There's a bootstrapper package that I think should install anything you need.

    Also, are you building and deploying "release" bits



  • runtime error while running the setup on vista