Labview 2009 SP1 Installer build help needed

[TTran1]

Hello,

First time posting here.  I have a rather large project that I recently converted from Labview 7.0 to 9.0.  I am able to build an executable and it starts up Ok but I don't know for sure if it works.  Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1.  The executable then complains that it needs the full development version to work.  I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.

Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer.  Here's the Build Errors from the pop-up dialog:

CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi

Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
 
**************
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
**************
  
**************
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
**************

The build log file has slightly more info:

    [LOG ON]  Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1

    [NMDK BEGIN]  Mon May 31 20:55:07 2010
     Building developer part

> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>

> 
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024

> *** End Error Report
> **************
> 
Adding product dependencies to developer part

> 
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig::DoMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6

> *** End Error Report
> **************
> 
    [LOG OFF]  Mon May 31 20:55:07 2010

    [MDF END]  Mon May 31 20:55:07 2010
     Closing MDF.

I realize that I should post my project file but I can't do that until tomorrow.  From those 2 errors, can you tell me what the installer builder is looking for?  I have gone through all my dependencies and they look Ok at the moment.

Thanks for you time.

[MartinP]

I recently installed SP1 also, and suddenly got lots of problems when compiling into an executable, problems that was not

present before installing SP1. I received the attached tips from NI, and the first of them helped me get through. But 

I sure did not like what SP1 did to LabVIEW 2009, it must be loaded with new bugs.

Hope this helps you. Good luck.

Martin

[charris]

Hello TTran1,

Unfortunately, these errors can be difficult to track down, and they're often artifacts from the upgrade process. Would it be possible to simply create a new installer build in the later version of LabVIEW? This very often fixes the issue, since the errors occur most often with upgraded build specifications.

Good luck!

[TTran1]

Martin and Celeb,

Thanks for your suggestions.  I tried the hint on not disconnecting type definitions and not remove unused members of libraries or polymorphic VI instances but that didn't help.  Still got the identical errors.

I will probably need to create a new build.  I thought I did that already but because I tried so many different things, my memory is getting blurred.

Thanks again,
T.

[charris]

Hello TTran1:

Let me know if the error still persists after creating a new build specification. I'm fairly sure that should iron out the problem you're seeing.

Good luck!

[TTran1]

Hi Celeb,

I had to help out on another project and finally only getting back to looking at this issue yesterday.  As you suggested, I went ahead and created a new project and created new build specifications (exe and installer).  I was able to properly build both items but won't be able to check out the executable til later this week.

I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View.  I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder.  Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly.  This might have been the cause of my inability to build an installer with the converted project/build specs.

I hope NI could add in more details into the build error messages.  As it is, it's really difficult to know why a build failed because there's no details in those messages.

Thanks again,

T.