LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

msm custom action fails "nmdkTouchComponentFiles.0A12B0D3_94AF_489F_AA01_DDC6E268E50A"

I am tyring to create an installer (Using Installsheild) for my program using LabWindows 6.0. I did download the updated msms (at http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/36c5e45e15a6862d86256b79005f89bb?OpenDocument) and everything seems to merge okay, however when I run the installer at the end I recieve the error:

error 2721
nmdkTouchComponentFiles.0A12B0D3_94AF_489F_AA01_DDC6E268E50A

Upon further investigation I discoverd that this error means that the custom action could not be launched. I opened the installer in Orca and deleted the custom action (which ofcourse gets rid of the error) however the CVI RTE does not install with it, which leads me to be
lieve that the error must be tied to cvirte.msm.

Please Any Help will be greatly appreciated!!
0 Kudos
Message 1 of 6
(3,598 Views)
Hi,

The code 0A12B0D3_94AF_489F_AA01_DD C6E268E50A refers to the CVIRTE; What version of Installshield are you using?

One thing to try here would be to create a distribution kit with CVI and test it; this would verify that the msms are working properly, or you need to repair the installation. It could be that the msms are just not working.

Could you give me more details on how are you adding the CVI's msms? I only have the version of Installshild that comes with Visual Studio 6, but I'll try to replicate it here to see if I can encounter the same error.

Please keep me poeted!

Regards,

Juan Carlos
N.I.
0 Kudos
Message 2 of 6
(3,598 Views)
Thank you for your answer.

I am using Installshield Express 4.0 SP2.

A few notes on where I am at with this issue,

First I downloaded the CVIRTE installer (6.0) from ni's website and opened the msi in orca. It also contained the same custom action (literally the function its calling and everything is the same). Then I created a blank LabWindows project and created a distribution kit with install full rte selected (so it essentially just installs the rte) and this one also ran fine (in fact I am run this one in the background of my installer now). Again I opened the .msi file in Orca and the custom action is there, with the exact same settings as the downloaded and installshield version. Lastly I created a blank installshield project and the only
dependacey was cvirte.msm (and its dependacies such as nipaths.msm), again I opened the msi in Orca and the custom action is there as expected, but when you run the installer you recieve the error Internal Error 2721....

I am not exactly sure (thus the post) but it seems that for some reason the dll that contains the function _nmdkTouchFiles@4 (its close to that name) is not being pulled into the msi.

Question:
In what dll does this function reside? Is it a dll that I have access to? If so one possible solution would be to replace the custom action in orca with one created in the installer that would force the dll into the installers msi. Just a thought though this may not work but Im willing to try.

Thanks again for looking into this matter, I hope that I have provided you with all the information that you require.
0 Kudos
Message 3 of 6
(3,598 Views)
Thanks for the info!

I'll look into this, it sounds like a dependency may be missing where the troubling function resides.

I'll let you know as soon as I have any info.

Thanks,

Juan Carlos
0 Kudos
Message 4 of 6
(3,598 Views)
Hello,

The error 2721 is because the binary that contains the function can not be found in the Stream of the MSI that is built. This is usually do to a merge problem with your build tool, hence this problem only occuring in Insallshield.

I know of one thing that you may want to do as a test. I have seen InstallShield barf because there are tables that give it problems. In the CVI 6.0 timeframe we have one of these tables in the cvirte.msm that is being merged. I saw that you have Orca, use it to open the cvirte.msm found in [cvifolder]\redist and remove the "Complus" table. This table is empty and not used but seems to give InstallShield and VS.NETs MSI build tools issues.

If this doesn't work let me know and I can contiue to research (I don't have InstallS
hield so I may have to find a copy to solve this problem).

Jeff
NI
0 Kudos
Message 5 of 6
(3,598 Views)
Aha!! Success.

That seems to have done the trick. Thanks!!
0 Kudos
Message 6 of 6
(3,598 Views)