I have an ism with few files and some executables.
It has a merge module which contains odbc entries and some normal non-executable files.

The ism contains file extensions in both tables 
and in registries,only progid I have shown below.
When I deleted the entries in Registries so as to remove redundancy, after installation whenever I click on the associated files, it is going to self heal everytime.

When I checked the root cause of self heal in event viewer, it is pointing to component in mergemodule and displays the error as those odbc registries are missing.But those are 64 bit registries and component also mentioned as 64 bit but windows installed tried to look in 32 bit hive and when I replicate the same in 32 bit registry(wow6432node) it is not going to self heal.

This self heal didn;t occur if I keep the file association registry keys.But If I remove them, it is checking for keys belonging to 64 bit component of mergemodule in 32 bit hive.

Can you suggest how to proceed.
2 Comments   [ + ] Show Comments


  • The above issue is because of the dsn entries.... All the components in the msm file are 64 bit and also the msm.And the msi is also contains all 64 bit components.ANd the target machine is 64 bit.

    When I install the msi, the dsn entries in the msm are coming in the 64 bit hive, which is as expected.

    But when I launch the advertised shortcut(created now to check) and the file association(with tables it is coming as advertised and with registries they are non-advertised).It is checking for the dsn entries in the 32 bit(instead of 64 bit as in component) hive and going to self-heal and as the component is 64 bit so it keeping 64 bit registries again.And this process is going on everytime we launch shortcut or file association.

    How to make it check for 64 bit registries only instead of 32 bit.
  • At present, as it is release time, I am removing keypath for the dsn component so that it won't trigger self heal. Please let me know if any suggestion so that I can incorporate the same.
Please log in to comment



If these are user DSNs - and I can't think why it's self-healing if they're not - just make them system DSNs.

Answered 06/30/2016 by: VBScab
Red Belt

  • Thy are System DSNs only.And these are created through ODBC Resources section in Installshield.Don't know why it is routing(during self-heal) to 32 bit wow6432node hive even it is 64 bit component and it is getting installed to Normal 64 bit hive.
Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja