InstallAware

Hello,

A Win7 (64-bit) customer has this error when trying to run our installer. Here is the part of the log containing the error:

MSI (s) (74:68) [11:45:29:138]: Note: 1: 1402 2: UNKNOWN\Components\A8CD4AD91379E0F3B85DCF71AC8684DA\14900E58FFDF69743A8BA3CC67F6CF5A 3: 5
MSI (s) (74:68) [11:45:29:161]: Note: 1: 2205 2: 3: Error
MSI (s) (74:68) [11:45:29:180]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1402
Error 1402. Could not open key: UNKNOWN\Components\A8CD4AD91379E0F3B85DCF71AC8684DA\14900E58FFDF69743A8BA3CC67F6CF5A. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.
MSI (s) (74:68) [11:47:32:012]: Note: 1: 2205 2: 3: Error
MSI (s) (74:68) [11:47:32:034]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

We have tried to run it from the adminstrator account. The error seems related with ditributing MSVC merger modules.

Dear KevinTX,

In order to allow us to better assist you, could you attach (or send to support@installaware,com) your installation script?

Best,
Aviv Giladi
InstallAware Support

Was this issue resolved? I think I have the same problem with the MergeModule in my setup project.

I can only solve this by send a setup without the merge module to the customer but would be great to know what the real problem is and how I can correct it.

Hi,

We never heard back from Kevin unfortunately.

Do you have a clue what could be the error? The component has something to do with Merge Module of VC 2005. But I do not understand how the error arise. I think it is a problem with the customer PC and not with the setup in general. But is there anything I can do to eliminate or prevent the problem?

Hi,

You can try running a logged install (/l) and examining the log file.

That is what I already did and the output was similar to the log-Output above.

But I have no clue what this means, that is my problem....

Could you please attach a reproducing project here? Thanks!

Sorry but this is not possible since the error is not reproduceable for me.

Only few customers have this problem...

The most time the merge module installs correct but I think in few upgrade scenarios (don't know exactly which) this error occurs.

Sorry this is all I have...I know it is not much

alibaba,

Please let us know if you are able to get more information on this - I am not sure there enough here for us to help you.

Hey,

You can also use the InstallAware runtime instead of the merge module.
Furthermore, if you are using Studio Admin, you can go ahead and use the Database Import Wizard to convert the merge module to an InstallAware script, and then install that natively using the Native Engine (instead of the Windows Installer engine) which will let you most likely prevent the error
on ALL affected systems (or at the very least provide detailed troubleshooting information).