09-03-2010 05:39 AM
Hi there,
I have a question concerning a source distribution that I am trying to build. The source distribution contains my graphical user interface pages for a large project. These pages are called dynamically from the main exe.
I build the project in LV2009SP1 and there everything was OK.
I deinstalled LV2009SP1 and did a clean install of LV2010.
First I mass compiled all VIs from the project, to be sure that there are no LV2009SP1 'left overs' in the project, which would possibly result in a build failure.
Nonetheless, I have the following build error:
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 2010\menus\Categories\Programming\plat-nireport.mnu
Destination: D:\projecten\Active Projects\Alpha Test System\GUI Pages\GUI.llb\plat-nireport.mnu
Unknown LLB file type.
Error Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1 occurred at AB_Dest_LLB.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Item_OnDoProperties.vi -> AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
The reason for this error is that I MUST check 'include files from vi.lib'. If I uncheck this option, then the build is succesfull but however, the main application doesn't find the necessary VIs, since the graphical user interface pages must be 'standalone' and thus contain all needed VIs.
Therefore, I MUST include all vi's from vi.lib, which previously worked in LV2009SP1, and now in LV2010 this fails?!?
anybody has any ideas? thanks!
09-03-2010 06:59 AM
After some more research, the root cause is the report generation toolkit (not the microsoft office toolkit, the standard LV report toolkit).
If I leave out the VIs that use this toolkit, the builder doens't include the report toolkit and the compilation is succesful.
If I include 1 single VI with ie "open report.vi" inside, it crashes giving this error.
Every now it also gives me the same error but then for another *.mnu file, from the SMTP palette...
In any case, I temporary solved the problem by moving these VIs to the application and calling those VI's from the LLB via a queue commander. Note however, this is NOT a solution to my problem, so please react if you have a solution.