03-07-2008 03:48 PM
03-07-2008 05:33 PM
03-10-2008 09:01 AM
03-10-2008 05:37 PM
03-06-2011 09:02 AM
I have this same problem with LabVIEW 2010 on multiple PC, all of which have the latest version of Windows Installer.
I am using the report generation toolkit but there are no dynamic VIs. However, there are some class functions that are called dyanamically. LV Run-time isntstaller is included in the installer but no others.
The exe build works correctly in all instances but the installer gives teh MSI error.
Test on Win 7 Office 2010 Dell x64 machine with LV2010. Running setup.exe on same machine gives an error.
Tested on WinXP Office 2003 IBM x86 with LV2011. Running setup.exe on same machine gives an error.
The above setup.exe when built without the application inluded (i.e. on LV2010 RT installer and support files) doe run without error.
Running a simlary setup.exe file that was built in LV2010 SP1 on the win7 machine does not give this error. Have not confirmed that the build are identical but they are very similary and use the same source code/project/ and. applications but built in SP1
03-07-2011 05:42 PM
Hi Bob,
Are you getting the exact same MSI error code (1627) that was included in the above post? If not, which MSI error are you getting and could you include a screenshot?
Thanks,
Austin S.
03-13-2011 01:31 PM
Here's the image.
03-13-2011 01:38 PM
03-14-2011 06:39 PM
I am getting the same error with LV 2010 SP1. Was this ever resolved? I am using Report generation toolkit and also have 3rd party msi installer that I included in the build.
MsiError 1627: 1: 2727 2: .
03-14-2011 06:54 PM
Bob,
From what I can tell, you have done some extensive testing on your project. Thank you! It really helps to rule out some possibilities.
First off, have you tried opening the project in LabVIEW 2010 SP1 and building it there? I haven't found any documentation, but your mention that a similar project built in SP1 works may indicate that something was fixed or changed that overcame your problem.
The other suggestion I would have is that sometimes the Application Builder can get a little wonky, and it sometimes helps to create a new project, copy the files into it, and build the installer from the new project. This has been shown to work in the past with issues similar to yours.
Good luck!
Drew Terry
Applications Engineer