LabView 8.6 Installer Build Unsuccessful - "Error in action: [TagExists?]"

[Steve_S1]

Guys I have a similar problem, only I recieve the following errors:

CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_VerifyItemPresent.vi

Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
 
**************
*** Error: Input data from a source data file has errors. (Error code -33)
Error in ini file: D:\Distributions\MeasurementStudio 8.6\nidist.id
*** End Error Report
**************
 
 
**************
*** Error: Input data from a source data file has errors. (Error code -33)
Error in ini file: D:\Distributions\MeasurementStudio 8.6\nidist.id
*** End Error Report
**************
 
 
**************
*** Error: Input data from a source data file has errors. (Error code -33)
Error verifying distribution present: NI-DAQmx 8.7.1, Disk 1
Error in ini file: D:\Distributions\MeasurementStudio 8.6\nidist.id
*** End Error Report
**************
 
Done building deployment

The application runs fine and I have made instllation files on another machine. Any sugestions?

[Robbob]

I dont think this is related at all, it sounds like you have some corrupt files on your machine, specifically Measurement Studio.  Also, if you are including additional installers, than

"Error verifying distribution present: NI-DAQmx 8.7.1, Disk 1" Sounds like a clue..

[johnny_icon]

I also experienced this bug. My scenario was as follows:

- My Source Distribution and Installer build specifications were both working fine in LabVIEW 8.5.

I upgraded to LabVIEW 8.5.1, and that's pretty much when I think it broke my previously working build specifications.

- The source distribution build worked fine in LabVIEW 8.5 and in 8.5.1, but the Installer build specification does not, and gives me the following afore-mentioned error:

 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_PreBuild.vi >> CDK_Validate_BuildRules.vi >> CDK_TargetTree_FileFGTransfer.vi >> CDK_FGMgr_DirInfo.vi

- Other than upgrading from LabVIEW 8.5 to 8.5.1, the only other variable was moving several project libraries from the dekstop target to the PDA target and back. They recompiled fine, and there were no apparent errors, so my best guess is that there is that the build specification API may have deprecated some functionality between versions.

- I was able to circumvent the problem by using an installer build specification to distribute my  llb's and other resources (help, examples, etc.) by adding the llb as a file in a virtual folder rather than including the literal source distribution llb that appears in the Project Explorer.

This was a very strange problem. I'm still not certain what the root cause is, but I'm sure it will become evident. The workaroud above is OK for now.

[Jim West]

I am using LV2009 SP1. I am getting the error. Was it really fixed?

[ZachAttack]

Documentation showed that this error was fixed for LabVIEW 2009.  If you're still seeing this issue, please provide more details and screenshots of what is occuring.  Do the workarounds listed in this thread solve the problem?  Thanks.

[Jim West]

The work around adding the built LLB as files has fixed the problem. I don't understand why a screenshot will help. The problem occurs when the build tries to add the same file to the destination directory. Like lvsound.dll. I had failed attempts to add build results to a destination directory when the same file was specified. ll

[Jim West]

I am in a bit of quandry. If I use the workaround, I am not able to include some NI libraries. If I use the source distribution, I get the error.

Here are more details. One of my source distributions use the NIreport. LLB. This creates some folders in the built results called NI_HTML, NI_report, and NI_Standard report. The folders contain the VIs I used from the library. (I don't understand why the VIs are not in the source distribution llb, but that is another issue. ) If I use the source distribution and build, the folders are created, and the application that uses the llb works fine. However, the installer fails.

I used the workaround and tried to manually add the NI report VIs but the installer returns the error. "The project library does not share a common path to disk with the files the project library owns"

jim

[cbauer]

I have found that adding the LLBs with their support files in a group is causing this in my case.  It causes the installer build file to become corrupt.  Going back into it later it has folders missing that were there before.  I would also suggest adding the filders you want before hand instead of having them created by the items you add to the installer.  Adding them one at a time has resolved this issue for me.