Installshield merge module problem
I am having a problem when I run my install on a clean machine everything is working fine.
When I run a major upgrade install it upgrades as it should, but when I try and run the application it fails, because either the Microsoft.crt90 and/or atl90 merge module hasn't installed correctly. If I then run a repair the application runs as it should. I am unable to see anything unusual in the msi logs.
The event viewer shows the following error:
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xe0434f4d
Fault offset: 0x0000b727
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
I do have the verbose log files but I can't see anything unusual.
I am using installshield 2009 and this only happens on Vista 32 bit and Windows 7 64 bit.
Does anyone have any ideas how to fix this? Don't really want customers to have to run the install then the repair.
Thanks in advance
When I run a major upgrade install it upgrades as it should, but when I try and run the application it fails, because either the Microsoft.crt90 and/or atl90 merge module hasn't installed correctly. If I then run a repair the application runs as it should. I am unable to see anything unusual in the msi logs.
The event viewer shows the following error:
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xe0434f4d
Fault offset: 0x0000b727
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
I do have the verbose log files but I can't see anything unusual.
I am using installshield 2009 and this only happens on Vista 32 bit and Windows 7 64 bit.
Does anyone have any ideas how to fix this? Don't really want customers to have to run the install then the repair.
Thanks in advance
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
The log produced by the repair must contain detail about which component(s) got repaired, surely?
Posted by:
timmsie
14 years ago
when you authored the upgrade did you move RemoveExistingProducts up the InstallExecuteSequence?
You may find that the clever installer engine decided that a component didn't need to be reinstalled but removed it first so it's missing?
You may find that the clever installer engine decided that a component didn't need to be reinstalled but removed it first so it's missing?
Posted by:
mutchie
14 years ago
The repair log shows the merge modules being reinstalled.
The upgrade log has an return value 0 Action completed sucessfully. But the product state is not installed not installed when the installation was run.
I am puzzled.
The upgrade log has an return value 0 Action completed sucessfully. But the product state is not installed not installed when the installation was run.
I am puzzled.
Posted by:
timmsie
14 years ago
So get yourself an install log, look for the components that get repaired and see what it says about the install state
The line will look something like this
Component: xxxx; Installed: Absent; Request: Local; Action: Local
Where is RemoveExistingProducts in the InstallExecuteSequence?
The line will look something like this
Component: xxxx; Installed: Absent; Request: Local; Action: Local
Where is RemoveExistingProducts in the InstallExecuteSequence?
Posted by:
mutchie
14 years ago
RemoveExistingProduct is between installValidate and installinitialise.
I have found the following in the repair log and they are all merge modules:
uplevel.30729.4148.Microsoft_VC90_ATL_x86.QFE.0901F145_82C9_3BF6_A91B_31F6791950EA; Installed: Local; Request: Local; Action: Null
uplevel.30729.4148.Microsoft_VC90_MFCLOC_x86.QFE.1D3B0A01_2635_3323_932D_3D66D5C4B0FD; Installed: Local; Request: Local; Action: Null
uplevel.30729.4148.Microsoft_VC90_MFC_x86.QFE.1B1242B0_08E9_3D59_826D_ADAA4BB763B5; Installed: Local; Request: Local; Action: Null
None of the files in the log have the installed as none.
I have found the following in the repair log and they are all merge modules:
uplevel.30729.4148.Microsoft_VC90_ATL_x86.QFE.0901F145_82C9_3BF6_A91B_31F6791950EA; Installed: Local; Request: Local; Action: Null
uplevel.30729.4148.Microsoft_VC90_MFCLOC_x86.QFE.1D3B0A01_2635_3323_932D_3D66D5C4B0FD; Installed: Local; Request: Local; Action: Null
uplevel.30729.4148.Microsoft_VC90_MFC_x86.QFE.1B1242B0_08E9_3D59_826D_ADAA4BB763B5; Installed: Local; Request: Local; Action: Null
None of the files in the log have the installed as none.
Posted by:
timmsie
14 years ago
Just noticed your problem is on Windows Vista and 7 (should have read the post properly [;)] )
this is an interesting article that say's these modules don't install in these environments:
http://www.symantec.com/connect/forums/v9-atlcrtmfc-merge-modules-are-not-installed-vista
this is an interesting article that say's these modules don't install in these environments:
http://www.symantec.com/connect/forums/v9-atlcrtmfc-merge-modules-are-not-installed-vista
Posted by:
mekaywe
14 years ago
sequence your "RemoveExistingProducts" CA at 750 sequence and give a try. This should work probably
Posted by:
notuenmc
13 years ago
I'm having the same problem using Wise.
How can i solve this on Wise?
I cannot understand how i apply the mekaywe solution on wise.
How can i solve this on Wise?
I cannot understand how i apply the mekaywe solution on wise.
Posted by:
anonymous_9363
13 years ago
No offence intended but seriously, if you don't know how to re-sequence a standard action in an MSI, you should leave the task to someone who does.
Posted by:
notuenmc
13 years ago
Sorry i'm new to this area, and yes i don't know how to re-sequence a standard action in an MSI.
Thanks for the answer.
Thanks for the answer.
ORIGINAL: VBScab
No offence intended but seriously, if you don't know how to re-sequence a standard action in an MSI, you should leave the task to someone who does.
Posted by:
anonymous_9363
13 years ago
I don't know what happened to the rest of the text I posted :(
It was something like: "Before you embark on editing tables and potentially breaking the MSI, you should get yourself on a Windows Installer training course or, at worst, read from cover to cover Phil Wilson's tome 'The Definitive Guide to Windows Installer'.
It was something like: "Before you embark on editing tables and potentially breaking the MSI, you should get yourself on a Windows Installer training course or, at worst, read from cover to cover Phil Wilson's tome 'The Definitive Guide to Windows Installer'.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.