Self heal on including Merge Modules.
Hi Everyone ,
I am facing a strange problem with on the applications i am packaging. The application is a legacy exe application which i captured using Wise package 5.5. There were around 6-7 common files like comdlg32, comctl232, comct32 , oleaut 32 for which i included the respective merge modules. On launching the shorcut the application goes on never ending sefl heal , i check in the event-viewer and the Warning there points to the component of that merge module. I am unable to figure out why is it pointing to the mm component. Please help .
I am facing a strange problem with on the applications i am packaging. The application is a legacy exe application which i captured using Wise package 5.5. There were around 6-7 common files like comdlg32, comctl232, comct32 , oleaut 32 for which i included the respective merge modules. On launching the shorcut the application goes on never ending sefl heal , i check in the event-viewer and the Warning there points to the component of that merge module. I am unable to figure out why is it pointing to the mm component. Please help .
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
16 years ago
I think that it could be due to the registry entries associated with these com components is still left behind in the MSI.
Go through the Registry table and remove any related registry entry as these will be added from the merge modules instead.
Go through the Registry table and remove any related registry entry as these will be added from the merge modules instead.
Posted by:
Inabus
16 years ago
Might want to also try, if the hint given by AngelID doesnt work, not using the merge modules and manually adding the files to the package. Not having used Wise I would assume it will ask you if you want to use the modules when you drag and drop the files into your package, just say no.
Also it would be worth fixing the merge modules of all errors anyway so that you remove these types of problems. Just remember to keep the same GUID as the Microsoft versionl.
Paul
Also it would be worth fixing the merge modules of all errors anyway so that you remove these types of problems. Just remember to keep the same GUID as the Microsoft versionl.
Paul
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
