unable to build installer in LV 8

[JLS]

Hello again,

This looks like a problem with the installer builder.  I have filed a corrective action request to R&D and attached the log file.  Although I can't find explicit evidence to support that 8.0.1 will solve this problem, you could attempt the upgrade to 8.0.1 and see if that helps.  In any event, I'll keep this thread posted with any information which may help work around the problem in the short term, or any other relevant information I can post here no the matter.

I apologize for the inconvenience!

Best Regards,

JLS

Message Edited by JLS on 04-19-2006 12:37 PM

[daveu]

I installed 8.0.1, but still received the same error. At this point, I'm at a stand still until NI finds a solution.

Thanks for all the help everyone!

Dave

[JLS]

Hello,

We can try to work from an application standpoint to get around the problem, but any formal fix will have to come through R&D (I cannot change the source and send you fixed version, for many reasons actually).  I know this may seem a bit arduous, but can you try removing files from your project and building the installer, in an effort to narrow down the problem?  Possible (purely speculative) culprits could be:

1. Large file or folder names

2. Deep file hierarchy

3. Many VIs at a given level of the hierarchy.

You can get an idea for those factors by looking at the Preview in your application build specification.  Again, that is purely speculative, but perhaps breaking your project in half and working in either direction will lead to some clues so that we can find a way to work around the problem without waiting for a formal fix!

Best Regards,

JLS

[daveu]

JLS,

Our application is 10 years old, with around 500-600 VI's. I am simply attempting to upgrade the application to LabVIEW 8. We have large file/folder names, a deep heirarchy, AND many VI's at many levels. I will begin attempting to narrow down the problem, but it being an arduous task is an understatement. However, what other choice do I have, right?

Again, thanks for the help.

Dave

[JLS]

Hello,

Wow, yes that would make "arduous" a bit of an understatement!  Unfortunately for now that seems to be the only choice, but hopefully the CAR will yield some positive results from R&D on the matter.  For future reference, the CAR number is: 3WIBGNSQ.  I want to emphasize that I was purely speculating on what could be going wrong.  I would think the installer building process is less sensative to things like hierarchy depth than the application building process in LV, but it seems the exe builds ok.

I sincerely apologize for the inconvenience, and understand how frustrating such circumstances can be!

Best Regards,

JLS

Message Edited by JLS on 04-21-2006 10:46 AM

[JLS]

Hello again,

I presume this issue is persistent, and I received word from R&D that they are not able to make progress with the current information, but are still willing to explore the problem with more information.  More specifically, is there any way we could get your code in an attempt to reproduce this?  It would be particularly helpful if you have a hardware independent version of your code which reproduces the issue.  If you can post your email address here, I will send you an email and we can discuss how to handle this.  If you have made progress or have found a way around the problem, definitely post your latest findings!

Thank you,

Best Regards,

JLS

[cking]

Dave,

I encountered the same error messge (with its possible reasons) and was able to overcome it.  In my case, for some reason in the installer build specifications, the LVWUTIL32.dll file in the "data" folder was missing.  This file is normally included in the application build and was physically there in the build folder but its inclusion or specification in the installer build was missing.  I noticed it was there for all the previous successful builts but not in this one (check "Installer Properties - Source Files - Destination View" and see if yours - or any of the .dll files that was supposed to be ther - is there). 

Anyway, I removed all the files & folders associated with that application from the "Installer Properties - Source Files - Destination View" pane (.aliases, .exe, .ini files, & data folder) and then select the application from the "Project View" pane and click the arrow to include the application build again. 

The Installer build was successful after this...  I hope you've already solved your installer building problem.  If not, I hope this would give you some clue as where to look for the "missing" path.

C.King

[daveu]

CKing,

Thanks for the post! I will definitely give that a look. I've been tending to other responsibilities as of late, so I've been unable to fiddle. However, as soon as I get chance I will look into it and post my findings.

Thanks again to everyone for the help!

Dave

[olivier66]

Hi,
 I do have the same error when building  the installer of my application ie: I can build an exe but when I want to build an installer it give me this error:
LabVIEW cannot locate some components necessary to build the installer. The components are from the following distribution(s):

Distribution name: Drivers de périphériques National Instruments - Novembre 2005
Last known distribution path: F:\

DETAILS:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> CDK_Engine_PromptForMissingDist.vi

Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
Creating installer files...
Build complete successfully.
Copying additional setup files
Done building deployment

exept that I don't have the error when I only include run time engine lv8 and not traditionnal NIdaq 741
And if I try too assign a path for the requested drivers de peripheriques NI the error turn into:

CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> CDK_Engine_PromptForMissingDist.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi


Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Reading distribution information from path: "F:\"
Reading distribution information from path: "G:\"
Reading distribution information from path: "H:\"
 
**************
*** Error: Improper function call or command line argument. (Error code -30)
*** End Error Report
**************
 
Reading distribution information from path: "G:\"
Copying distribution 'Drivers de périphériques National Instruments - Novembre 2005' from: G:\ to: C:\Documents and Settings\Olivier\Bureau\installer\
Reading distribution information from path: "G:\"
Reading distribution information from path: "F:\"
Reading distribution information from path: "H:\"
 
How can I fix the problem

Thanks
Olivier

[JLS]

Hello,

Is your project, or better yet a subset of it, small enough to post?  The idea here is that if this can reproduced, it can be passed to R&D and hopefully fixed in a future version.  Also, did you try the last suggestion (a couple of posts up) which seems to have worked around the problem in one case?

Sorry you're having this inconvenience, and I hope we can track down the problem soon!

Thank you,

JLS