LabVIEW 7.0 Build Error 26097

Hi All,
Blast from the past here.
I am working on resurrecting an old program (I work for a company where our products are in use for 30 to 50 years).
I have all of the vis assembled, the computer is a Windows XP running LabVIEW 7.0 professional with the build application.
When I try to build the program, the application chugs away, adding vis etc, but then it gets to this (see attachment):
Has anyone seen this before?
Thanks for any help.
Let me know if you have questions that I can answer.
Dan
Solved!
Go to Solution.
Attachments:
10-27-2014 2-56-07 PM.jpg ‏31 KB

Hi All,
I should have updated you all on this yesterday.
I did find my error. I missed putting in place a patch that NI had given us way back when we were putting all of this together. Once I installed that all was fine.
I do appreciate the time that you took to look into the issue and I'm sorry about the wild goose chase.
With a few particular programs it is better that we keep those in their original configurations, hence the use of 7.0 in this case. Rest assurred for any new projects we are using the latest and greatest of LabVIEW. It'll be interesting what others down the line have to say when they pick up new code that I'm developing now in 15 to 20 years!!!
Best Regards,
Dan

Similar Messages

Application Builder error in LabVIEW 7.0

I am maintaining some legacy code in LabVIEW 7.0. I have recently (perhaps within the last month or so) been getting Error 1003 in Dist Copy Non-VI Files.vi (part of App Builder) when building my code. I've done some testing, including trying to build much simpler VIs, and get the same error. Curiously, this occurs on multiple (Windows XP SP3) machines, both "real" and "virtual", including on two of three installations on a single PC (so it is not hardware-dependent).
I have a strong suspicion that the problem is neither my code nor LabVIEW itself, based on the following logic: 1) This problem arose on multiple PCs at about the same time (i.e. I don't recall seeing this a few months ago, now I see it on almost all of my PCs). 2) There are two PCs where I do not see this error -- when I check the LabVIEW installation files between a PC that "works" and one that doesn't, the differences seem (to me) to be small, more related to "what did I do most recently" or "how much of MAX did I install, which drivers". (3) Using or not using OpenG in my code mades no difference, nor does turning off Anti-Virus scans.
I tried two other things. First, I have a VM that I recently build (which I think is significant) that has both LabVIEW 7.0 and LabVIEW 7.1. The build fails with LabVIEW 7.0, but succeeds with LabVIEW 7.1. In addition, I found a VM, built a year ago and "sitting idle", with LabVIEW 7.0 on it. I fired it up, did not allow Microsoft Update to update anything, and tried the build with LabVIEW 7.0 -- it worked!
My current working hypothesis is that some "patch" installed by Microsoft (.NET? ActiveX?) has clobbered something in the LabVIEW 7.0 Build Application. Unfortunately, the VIs that make up this application are password-protected, so I can't see "inside" to discover what file or other condition is responsible for the error message.
Does anyone have any ideas or suggestions? [Don't suggest "Upgrade to 7.1" -- I'm the only "maintainer" of multiple PCs and multiple applications, some of which run on systems "belonging" to other people. I am in the process of rewriting the code in "modern LabVIEW" (2011) and will port it widely, but until then, it's not practical (or "politically correct") to make the 7.0 -> 7.1 shift ... Besides, my curiousity is piqued!]
Bob Schor
Solved!
Go to Solution.

Good point. The reason for my "laser beams" is several fold. First, I follow a written protocol (I wrote it!) whenever I install or re-install LabVIEW 7.0, so I'm pretty sure that all of the installations "should be consistent" (if not identical). Second, I compared two NI folders in Program Files between a version that worked and one that didn't, and while there were differences, it seemed "not likely" to be an explanation. Third, I'm 99% sure that at least one of the systems that now cannot build (of the eight installs, all by me, that I've checked, only three worked, and one was on a PC that hadn't been turned on in over a year, hence was certainly not updated) was able to build previously (i.e. I don't recall seeing this problem until about a week ago, when I started re-building an update to my legacy application). It is possible that this problem was always present on these systems, but doesn't seem likely.
Nevertheless, before the beginning of next week, I plan to take one of my "failing" systems, uninstall LabVIEW (but not change the OS in any way), reinstall it, and see if I can build. If this still fails, I'll take the "old" system I mentioned above and start bringing it "up to speed" until I "break" the App Builder. Note that it is possible that MicroSoft is not to blame -- I have other software (such as editors, utilities like WinZip, etc.) that have also been updated, and one of them might have clobbered the Builder.
Will let you all know what I find.
Bob Schor

C++ build error with LabVIEW DLL

Hi, I'm a student at UC Irvine learning to use LabVIEW. I am working on a practice project for which I have to use a PID system to control the temperature of an object. Things are starting to get a little messy with nested control statements, loops, etc., so I figured I'd export a LabVIEW DLL with all the hard to code stuff, such as interfacing with my instruments, and plotting data or whatever, and do the number crunching and keeping track of stuff in C++.
The DLL file I made in LabVIEW went off without a hitch as far as I can tell, but when linking it to my C++ test program (which at this point is just including the LabVIEW's .h file for the DLL and an empty main() function), I get a lot of build errors. I am using Dev-C++ which uses g++ to compile the code.
Here is a pic of my build errors:
Solved!
Go to Solution.
Attachments:
LabVIEW_compile_error.JPG ‏184 KB

Normal windows apps are not as forgiving about where you can put your DLL as LabVIEW. You have to have a DLL either in the direcotry where the executable file itself resides (that would be your build directory, not the source directory), the windows or system directory, or any directory that is set in the PATH environment variable. Anythin else will most likely not work, or at least not reliably.
No need to add the cintools directory into your include file paths nor the library file paths. you would only need that if you decided to let the DLL export native LabVIEW data types in which case you would need the LabVIEW manager functions to prepare the correct data buffers.
Rolf Kalbermatter
Message Edited by rolfk on 07-30-2009 07:49 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Tab Control Property Node gives a build error when used in a VI for LabVIEW PDA

Hello,
    Iam new to LabVIEW development & need help regarding this:
    We are trying to port a LabVIEW application from desktop to a Windows Mobile PDA. Please note that the LabVIEW application works fine on the desktop. In one of the VIs, a Tab control property node is used which gives a build error with LabVIEW PDA project. A sample VI which shows the problem & the error list snapshot is attached with this post. Can anyone please suggest an alternate approach to achieve the same functionality with LabVIEW PDA? Waiting for an early response from anyone...
Thanks & Regards,
Subhashini
Attachments:
VI_Error.zip ‏31 KB

Hello Ton,
    Am glad that i got a response, thanks. The following links indicate that Tab control is supported on PDA target:
http://digital.ni.com/public.nsf/allkb/CBA335641E27B858862571490015EA88?OpenDocument
http://forums.ni.com/ni/board/message?board.id=170&message.id=221507&requireLogin=False
    I feel that the Tab control property node that has been used in the VI (which is attached earlier) may not be supported on the PDA target. Can u (or any LabVIEW expert) suggest an alternate approach to achieve the same goal with LabVIEW PDA (changing colour of Tab control pages programatically)??
    I had missed out some details earlier: We are using LabVIEW 8.5 PDA module on a Windows Mobile PDA.
Thanks & Regards,
Subhashini

Build error in LabVIEW 8.5

Hi,
An error as follows has occurred when building the exe file:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1502 occurred at Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: Cannot save a bad VI without its block diagram.
Method Name: Save:Target Instrument
The code was built successfully in all previous version. Only a few minor changes to the latest code: a global variable was added and a few calculation algorithm were updated.
Does anyone have any idea about this error?
Thanks in advance,
Jean

Hello AOrtin,
Another possible workaround for this issue is to use the additional exclusions section of Application builder. Uncheck all of the items on this category as shown below.
Also, are you getting the exact same error as described above? There were two bug fixes in LabVIEW 8.5 for Error 1502 when building EXEs but you mentioned that you are already using LabVIEW 8.5.
Regards,
Jon S.
National Instruments
LabVIEW R&D

Report Generation Toolkit and Office 10 - build errors

Using LabView 2011 and Report Generation Toolkit 2011.
After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
Says it is unable to save a vi without a block diagram.
Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
Can't believe I could be the only one to experience this. Any workarounds?

Duplicate Post

Build error: an input parameter is invalid

I am looking for help with a build error. I am getting the following error message when I try to build a project in 8.5.1:
Error 1 occurred at Open VI Reference in AB_Source_VI.lvclasspen_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.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 @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
VI Path:
Tom Rhoads
Goodrich FUS
Vergennes, Vermont

Arducopter:
Did you check to see if the KB Hunter posted resolves the issue?
If you're opening a project in a newer version of LabVIEW, then there's a chance the mass compile tool might work. It will open and save all of the VIs within a specified folder. The tool is fairly self-explanatory, and you can access it from within LabVIEW by going to "Tools --> Advanced --> Mass Compile..."
Good luck!
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

Error 7 Build Error - File not found

I am trying to build my software to another computer over the network. I am able to access the directory I am installing to and the program is not indicating any build errors(all VI's are not broken). This error only occurs when building. Any suggestions would be great.
Thanks,
Nate
The Build was unsuccessful
Possible Reasons: An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
\\PAINESTORAGE\Engineering\Test & Manufacturing Software\AutoTest Software\Current Version\AutoTest ...
Extended 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 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File2.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Rule_Editor.vi -> EBUIP_Item_OnDoProperties.vi -> EBUIP_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Non-existent board.
-Nate
Solved!
Go to Solution.

Is there a way to see a report of the dynamically called VI's? I inherited this software and am relatively new to LabView...
-Nate

Why does labview generate Dr. Watson error "C0000005 access violation"

I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
*----> System Information <----*
Computer Name: ANDANTE
User Name: Administrator
Number of Processors: 2
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
When the crash occurs, I see a dialog appear with the error
labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
The Dr. Watson error log is generated and the error is
Application exception occurred:
App: (pid=1160)
When: 4/25/2004 @ 01:57:56.640
Exception number: c0000005 (access violation)
I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
State Dump for Thread Id 0x574
eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: StrLen
00748230 55 push ebp
00748231 8bec mov ebp,esp
00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
0074823b 84d2 test dl,dl
0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
0074823f 8a10 mov dl,[eax] ds:00000062=??
00748241 40 inc eax
00748242 84d2 test dl,dl
00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
00748246 2bc1 sub eax,ecx
00748248 48 dec eax
00748249 5d pop ebp
0074824a c3 ret
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
*----> Raw Stack Dump <----*
0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....

For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.

Application builder error 1041

Dear All,
I have a problem to build a application in Labview 8.5.
It's the first time that I try to build this application in fact it's the first application every I try to build.
I found the following problem.
Authentication: "Error Code Database.vi is password-protected. Enter the password to acces the block diagram."
I do not know the password for this file.
The building errors details I get are:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Incorrect password.
Method Name: Lock Stateet
When I start looking for the file that causes the problems I find that it is "Get File Type.vi" it's protected.
This is an NI file and I do not know the password and I do not know why it is locked.
The VI general properties of the file are:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\Get File Type.vi
File revision is 78
I tried to solve the problem as discribed in tread
http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=False
But that did not work for me. A build with a new file also gives the same error.
So I tried something else in the Build specification there is a menu "source file settings". There is a selection about passwords
You can choose 3 settings 1) No passord change 2) Remove password 3) Apply new password. I changed this setting from 2 to 1.
And I can build the project now. So I change back from 1 to 2 and I should get the error back again. And I did not. How can this happen?
What is going on?
Thanks in advance

Mike, you can't change the password if you don't know the old one. Why do you want to change the password? I do't wanna change the password. The application builder is asking for it and I do not have it. The same problem occured at thread http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=FalseIt looks almost the same but the solutions there did not work. The problem kept occuring. So I tried someting else:
In the Build specifications there is a menu "source file settings" for your project files. I only have 1 main.vi project file
There is a selection about passwords for your source file settings. See attachment 3. You can choose 3 settings
1) No passord change
2) Remove password
3) Apply new password.
I changed this setting from 2 to 1.And I can build the project now. So problem solved.
Then I changed back from 1 to 2 and I should get the error back again. And it did not.
I do not understand why it works and I would like to.
What is going on?
Attachments:
Authentication.JPG ‏13 KB
VIPropertiesProtection.JPG ‏131 KB
SourceFileSettings.JPG ‏52 KB

Application builder error 1055

ed. cross-post: http://lavag.org/topic/18047-application-builder-error-1055/
Hello everyone
I have a big problem with building applications lately. The build is running fine until the end, when it throws:
Error 1055 occurred at Property Node in VISL_findDependentVISvr.vi->VISL_findAndProcessVISvrList.vi->VISL_detectAndCopyVISvr.vi->AB_Engine_Copy_CustomIOServer_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
Has anyone seen this error in app builder? Does anyone have any idea how can I resolve this problem?

Lennard, Valko
I'm using LV 2013 f2. Let me give you some more details and... The story how I fixed it:
The project is pretty big (~1500 VIs) and highly object-oriented (~300 classes). It has RT (PXI) and PC part. Some of the classes are shared between PC and RT. The problem with build was present only on PC - build for RT was ok.
I had DSC module installed, but it was not used in this project at all. Despite that, when I found information from Lennards link, I've tried to build it using "Enable Enhanced DSC Run-Time support". It didn't help. I started to wonder if the sharing of classes between RT and PC has something to do with the problem. So I refactored the project, splitted it into two projects (one for PC, one for PXI) and reduced number of shared classes (especially some specific classes, which implement "threads"). Afterwards, the build could be done just fine, but only in those refactored projects.
Now for the plot twist: before refactoring, I've tried to build the project on another computer. It was build without any problems! So I started to look for the differences. First of all, just before the build I've updated one of our internal libraries in VIPM and changed its name - so it was my main suspect (I needed to update dependencies in project as the change of VIPM package name changed it folder in vi.lib). This + disconnecting code from VIs and I though that I've just found another way of destroying LV compiler completely. Still, I couldn't fix it in any way...
As per Valko suggestion I've uninstalled DSC module completely. Once again - my project does not explicitly use this module at all! Removing the module didn't broke anything in the project. And guess what? The build was done without problems! I've even tried to do this build again on the code revision before refactoring, and the build was done!
tl;dr: REALLY NI!!?!? REALLY!? YOU'VE BROKEN SOMETHING IN THE MODULE WHICH I DON"T EVEN EXPLICITLY USE AND MADE ME LOSE FEW DAYS OF WORK JUST TO FIND IT OUT? REEEEAAAAALYYYYY!?

Installer Build Error

Hi,
I am rebuilding an existing Labview application (originally done in LV8.6) using LabVIEW 2011. The application works in LV2011 as stand alone but when I try to build the installer, I get the error for which the details are in the attached text file.
Please help figure out the issue.
Thanks
Jeet
Solved!
Go to Solution.
Attachments:
Installer builder error.txt ‏4 KB

The issue with installer build is fixed. It wasn't able to read the drivers from the CD drive because the CD drive had gone bad.
We replaced the CD drive and it started working.

PDA build error when using a 'value change' event on two controls

I get a build error when I use a 'value change' event on controls of a different type or even a different numeric representation. I'm using LV 7.1 PDA with no other modules installed. Attached is a picture of the entire code and the error message.
Try to take over the world!
Attachments:
PDA Error.jpg ‏48 KB

Hi,
I verified the error that you are seeing. It appears to be a bug hence I have reported it to our developers. Hopefully this bug would be fixed in the next relaese of the PDA module.
Thank you for pointing this to us. It is through feedback that we can make LabVIEW PDA module even better.
Regards,
Ankita A.
National Instruments

*.exe build error, files not on system error

I have recently had to rebuild my laptop meaning a full instal of 8.5.1.
I have just got to the stage of building an existing project that has been live for a number of months and built a number of times.
The *.exe builds no problem but the installer comes up with a build error
Has anyone saw this before?
Any ideas anyone???

your some guy.
Worked a treat!
Will that be that the previous build was from a previous version of labview & a previous version of laptop and just got its knickers in a twist?
Thanks for your help, I did search but obviously not good enough

LabVIEW 7.0 Build Error 26097

Similar Messages

Maybe you are looking for