LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

duplicate error

In a build application process, using old NT version, Labview begins to build the exe, but stops maybe a 1/3rd of the way...How do I find the problem if I cant even understand what DLLs are used in the build process..? Is there a way of tracking down the duplicate error? Is it related to DLLs or duplicate *.VIs?
0 Kudos
Message 1 of 3
(2,748 Views)
I probably can't help you, but here are a few questions:
Which version (LV & Windows)?
What do you mean "stops"? Does it freeze? Does it stop and return an error?
Is this happening only with one VI or with all your apps?

___________________
Try to take over the world!
0 Kudos
Message 2 of 3
(2,743 Views)
Well, this is LAbview ver.4.0.1 with NT 3.5 and I can't get help from NI, so thx for responding..The build *.exe file I am referring to is a file size about 1.3Meg and to compare to a past *.exe file compiled in the past was about 4.3Meg. So, I assume the Labview build is compiling to a point...Now, I look at a another thread saying::::::::::::

Labview : Duplicate Path
Why do I receive this error and how can I resolve this issue?

Solution: This error occurs when the LabVIEW Application Builder is supplied with two paths to the same external library which is referred to by [filename] in the error message above. This typically happens when users include a DLL as a support file in the Application Builder, but it is also loaded by one of the VIs in their application. For instance, if you build a Data Acquisition VI and you also include lvdaq.dll as a support file, you have actually provided the path to this DLL twice, once through the support files and once through the DAQ VIs. To resolve this, remove the DLL or external library from support files and run Application Builder again.

The error could also occur if a DLL is called by two different paths within the LabVIEW program itself (using the Call Library Function Node). In this case, the code will run fine, but the Application Builder won't know where to take the file from. In this case, make sure that all instances of the DLL or library are called by the same path. Then you should be able to build the executable

But, where I am I to approach this in Labview ,, to identify where a "DLL" is associated or to know where "Call Library Function Node" path is in a VI? My code is extensive and has gone through many changes and any advice is helpful...Thx
Message 3 of 3
(2,732 Views)