Error 7 - LabView

hello.
i have a problem. i'm using labview 2009 and i'm trying to capture a picture and then save it. till block of saving is everythink OK, but from block for saving i get this error 7 (file not found). Do i have to enable my path or what? I dont know where is the problem here, because in tools-->options-->path i add this path where i want that data save.
Please help me what i have to do, that i will save my data. i need this funcion for my project at work.
Matjaz
Attachments:
ekran1.jpg ‏269 KB
Direktorij.jpg ‏297 KB

hei.
i tried to change \ with / and its still same. but then i tried to just load some picture from disk and i get error File I/O Error (Picture: ekran2.jpg). It is possible that, that its not working, because i have at Project explorer wrong settings(picture splosno.jpg)? I get error when i was working at Smart camera and not on My Computer. Because when i tried to load from disk some picture it was working normal at my computer. it is possible that i add this smart camera to my computer? I will need camera for my later project, because i will have to capture and save picture. When I try now to capture picture with camera at my computer wrote me an error 1074360311(with IMAQ snap). I tried to right click on my computer -->new-->target and device, but there i could not add camera.
regard,
Matjaz
Attachments:
ekran2.jpg ‏201 KB
splosno.jpg ‏191 KB

Similar Messages

Error installing LabVIEW 2011 on Win 7

I'm getting an error installing LabVIEW 2011 Professional:
I found a thread concerning missing MSIs, which suggested that one run setup.exe with the /log function, so I did, but I don't think it actually says anything useful.
I also found a Microsoft download page for WindowsInstaller-KB893803-v2-x86.exe, which is the thing that's supposed to be missing. This seems to be an old version of the installer (most recent compatible OS = WinXP SP2), so I don't really feel like installing this on my Windows 7 system.
Help!! Thanks in advance.
-- Philip

Hi Keller,
I'm Jamie an Applications Engineer at NI UK.
It does seem that you are missing some of the necessary support files required for the installer to run correctly, the details of which are available in the KnowledgeBase article here. Did you download the install files or are you installing from disk?
In addition to the setup.exe file, ensure that you have copied the following folders to the target PC or destination folder when creating an installer with LabVIEW.
bin
license
supportfiles
Hope this helps get you up and running with LabVIEW 2011, let me know if you experience any further issues.
Thanks
Jamie
Jamie S.
Applications Engineer
National Instruments

Run-time error "5010": Labview: VI execution ...

I get Run-time error "5010": Labview: VI execution terminated by server. This error occurs sporatically. I am running Visual Basic 5.0 application that communicates to Labview 6.1 VIs. It is using NI-Imaq to do vision analysis of parts. I just need to know what to look for that may be causing this error. I am also running it on a PXI system with 64 MB of memory.

Hello,
I recommend you to do direct function calls to NI-IMAQ and NI Vision function libraries from Visual Basic as this will be a lot more efficient and improve rubustness of your application. During the installation of both software, you have the option to include support files for Visal Basic. Once these components are installed you should see the shipping examples in the following directories (if installed in the default path):
(NI-IMAQ) C:\Program Files\National Instruments\NI-IMAQ\Sample\VB
(NI Vision) C:\Program Files\National Instruments\MeasurementStudio\VB\Samples\IMAQ
There are additional examples that can be found in the Code Library (see the link on the left sidebar).
Let me know if you have further questions regarding this issue.
Regards,
Yusuf C.
Applications Engineering
National Instruments

Intrument Gives error when Labview VI is loaded

I have a minor issue with one of my instruments that i control with labview. I can control it via Serial or GPIB control. When i load up my vi for the first time and my instrument is set to GPIB address 1 there is a slight delay loading up the program and I get an error light on my instrument. This means some info is being sent on the GPIB bus. After the slight delay the program finishes loading and the error light goes off telling me something else was sent to my instrument. This error occurs ONLY when my instrument is set to address 1. Any other address and everything works as expected. To combat this error in my vi i just send a *cls to clear everthing before i write again because the error seems
to send something that will mess up my first sent command. I ran NI spy to see what is happening when i load my VI's.
This is what NI SPY shows labview is doing on the GPIB card when i load up my VIs
1. viOpenDefaultRM (0x00154348)
2. viGetAttribute (0x00154348, 0x3fff018f, VI_TRUE)
3 viGetAttribute (0x00154348, 0x3fff0190,2 (0x0))
4 viSetAttribute (0x00154348, 0x3fff0190,2 (0x0))
5 viFindRsrc (0x00154348, "?*INSTR", 0x00157108,3 (0x3), "COM1")
6 viFindnext (0x00157108, "LPT1")
7 viFindNext (0x00157108, "GPIB0::1::INSTR")
8 viClose (0x00157108)
9 viSetAttribute (0x00154348, 0x3FF0190,0 (0x0)
Step 5 is where i get the error and labview hangs for a second. After it passes my error light goes off and it will continue to load. This issue only occurs when i have my instrument set to GPIB address 1. There seems to be some kind of conflict that occurs. Could it possibly be the software used in the instrument?

The viFindRsrc VISA call finds all VISA resources connected to your computer. Line five is where LabVIEW polls the Serial Port, not your instrument, so I'm not sure why you would get an error there.
Since the error only occurs when your device is at PAD 1, I'd suggest checking for address conflicts. Is your GPIB0 device at address 1? Do you have any other devices connected to you system?
Also, what are all of the getAttribute and setAttribute commands? I don't get those when I run VISA Resources VI.
I hope this helps!

Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it

Hi
Everybody ,
I am working with pci-6723 and labview 7.1 yesterday when iwas testing , the programme was running , suddenly the power has gone , since i have not connected my system to UPS system got shutdown , and when i booted pc its higlighted this error , now to what extent this problem affects to my software, and how to fix it.
"Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it"
Thanks in advance
Rajesh

Hello Rajesh,
Do you get this error frequently or you got it only once after the power shutdown? Are you making a call to a DLL in multithreaded environment? Try mass compiling the VI by going to Tools->Advanced->Mass Compile. Also please follow the suggestions provided in this knowledge base entry regarding thread.cpp and see if that will fix the problem:
http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument
If you continue to have this error, is there any way you can send me a pared-down example demonstrating what your program does, so I can at least investigate to see if I can narrow down the cause of the thread.cpp failure?
Thanks and good luck!
Shakhina P.
National Instruments

Load error in LabVIEW communications

Hello Everyone,
I am using LabVIEW Communications System Design suite. I connected USRP 2953R using PCI interface to the laptop. 802.11 WLAN framework is being used for the project. I had to check channel estiomation using antennas and it was done. Today, I am stuck with a load error while opening the project. It is saying that the project includes following featrues thta are not supported in this version of LabVIEW-
LabVIEW FPGA SystemDesigner plugin
USRP SystemDesigner plugin
FlexRIO SystemDesigner plugin
LabVIEW FPGA
I attached a screenshot of it. Please have a look and help me in sorting this.
Best Regards,
Ramya

Hi Everyone,
This was a problem due to communications suite license. I contacted the sales department and they gave me an activation key to extend the license(as I am using the suite on a trial period). There was a loading error because LabVIEW communications software was loaded instead of Suite which is not suitable for the respective plugins. The issue is resolved when I used the activation key to reinitiate LabVIEW suite. And I thank everyone who tried to help me.
Best Regards,
Ramya

Installer Error of LabView Run Time Engine 6.0.2 "premature"

I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
Does anyone know what to do is ?
Thanks for Help

It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
J.R. Allen

File permission error in LabVIEW, but what file?

I am in the process of smoothing out the wrinkles in a large LabVIEW program that I've converted from LV 7.0 to LV 2011SP1. I've also moved from WinXP to Windows 7. I get why there are file permission errors and I understand what the issues are in regard to moving from XP to 7. What I would really like, is for the error message to tell me WHAT file is having the issue. There are entirely too many file accesses in this program, I am not the originator, and it's been painful. A more explicit error message, a log file, or some other cool trick to find what file is having the issue would be super. While I'm asking for stuff, a call stack or at least the name of the VI this code calls would be wonderful, as nothing at all calls New File directly.
Certified LabVIEW Developer
NI-VLM Administrator

How are you currently handling the error? The file you tried to access should be part of the string in the error cluster.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

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

How to eliminate advapi32.dll error in Labview RT

Hi all,
I am having a problem deploying a RT application to the remote machine. I get an error stating Error loading 'WS2Help '.dll: Missing
export 'AllocateAndInitializeSid' from ADVAPI32.DLL' After searching the internet for a while I know that this is a dll that the labview realtime os cannot use. However I do not know if there is a tool/debugger that I can use that will tell me what vi's are calling this dll. If I know what is calling it I figure I can figure out an alternative to that function. Any help is appreciated. Thanks.

Hi KidMoe,
In addition to the information (and the program) from the thread that mathan linked, here is a little more about that dll. WS2Help.dll is used by Internet and network applications. Specifically, the file contains functions used by the Windows Sockets API.
Regards,
Charlie Piazza
Staff Product Support Engineer, RF
National Instruments

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

Winsockread Error in LabVIEW PDA

Hi all. I am currently trying out the VI server example given in the LabVIEW PDA toolkit but i keep getting this error "WinsockRead error Error Code: 10054.
The LabVIEW example project I am using is "VI Server- Pocket PC.lvproj" and I have loaded the "CallByRef Wave - Pocket PC.vi" into the PDA. I have a WIFI connection to a PC and have manually assigned IP address to both the PDA (192.168.100.101) and PC (192.168.100.100). I have verified my WIFI connection is working by using the "ping 192.168.100.101" command on my PC.
Also, I am configured my VI server correctly by selecting the enabling the TCP/IP protocol and ActiveX under the VI Server Configuration. The port number I used is 3363. I have also added the PDA IP address (192.168.100.101) to the Machine Access List.
When I try to run the example program on the PDA with the IP address "192.168.100.100" and a port number of 3363, I will get the error. Can anyone give advice on what I have missed out or done wrongly?
I forgot to mention that the remote program "TargetWave.vi" on the PC is loaded in memory and opened in LabVIEW also.
Thanks in advance.

D.Com,
I just thought of something else to try. You said you are using port 3363. The program was initially set up to use Port 3865. Did you change the VI server properties (From the project, right click on the my computer icon>>properties>>VI server: Configuration) to port 3363 or just the control on the front panel of the CallByRef Wave.vi? Both must be set to the same port.
Secondly, you may have to open a port in your firewall if you are using WindowsXP SP2. Initially I would completely disable the firewall and see if that solves the problem. If it does, then enable the firewall and create an exception of the port you've specified (3363).
As for using the trial version, this should have no impact on the performance of the toolkit.
Best Regards,
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

Errors in LabVIEW because Max is not ready

I'm having an unusual problem with Max and LabVIEW.
I need to have a LabVIEW program launch auotmatically on startup and run unattended. I put a shortcut in the Startup folder, use automatic logon, and generally things work. However, I have had some issues doing this with 8186 and 8187 PXI controllers. The 8186 was running WXP. When it started up and launched my program, often times LabVIEW could not talk to various NI hardware in the PXI chassis. I would get errors doing D/A, A/D, DIO, reading Max settings, whatever. If I quit the program, exit LabVIEW, then launch the program again without rebooting, everything usually works.
The 8187 is similar, but the problems aren't as severe. Most of the time, the program works right away when it boots up and runs. However, once in a while, the digital output doesn't work. It doesn't return an error, but the DO bits don't work. It's as if the DIO mapping is wrong, and it's setting a different DIO port or something. If I quit LabVIEW and restart it, it is fine. So I'm guessing that it has to do with MAX. I believe LV reads the Max database when it launches. If Max isn't ready or something goes wrong, it won't work until LabVIEW is restarted and rereads Max. I'm using traditional Daq, by the way. Also, I'm configuring the DO channels in LabVIEW, not in Max, so all that Max should be doing for the DO is registering which Device is which.
I' playing with putting a delay in the startup before launching LabVIEW. That seems to help. A 10 second delay reduced the chance of the DO error somewhat. So far, a 20 second delay seems to have eliminated the error. But that is a poor kludge.
Summary: PXI-8187, PXI E-series multifunction card, LV 7.1, Max 3.1, Traditional NI-Daq, W2K, DO. Has anyone seen a situation wherein Max does not appear to be ready by the time LabVIEW has launched and started? If so, is there a fix? Has anyone seen a situation wherein Max does not appear to be ready by the time LabVIEW has launched and started? If so, is there a fix?
Thanks,
Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Nick,
Thanks for the idea. I had considered trying this, but haven't gotten around to it yet. I've done this before with other systems. The reason I did it then is that it loads faster. In this case, I was going to try it just because it was something different, but I wasn't expecting much. In fact, loading the LV software faster would, according to my current theory, just make things worse. It seems that the LV program is starting before the low-level drivers are really ready. So how would making the LV program (in .exe form) load faster help?
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Error in LabView.exe after each start

I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
1) Reinstalling
2) updating video card driver and ActiveX
3) installing on a different drive
none of these help.
Any help you may have would be appreciated.
Attachments:
LabVIEWlog.txt ‏1 KB

Hello,
The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
There are two types of log files. There are those created by LabVIEW and those created by Windows.
The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
hidden files and folders.
If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
ther dlls with the VIs that cause LabVIEW to crash?
Zvezdana S.
National Instruments

Fix overlapping controls in error cluster (LabVIEW 2013)

In LabVIEW 2013, the "Error In.ctl" and "Error Out.ctl" have overlapping controls. If you run the VI Analyzer, you get an error from this arrangement. That shouldn't happen in something that's built-in.

Has an answer been determined for this?
I am getting this error for a few objects, but the error is not consistent and there doesn't seem to be alot of information on it.
See the attached images.
The Standard "error out" cluster is reporting 2 overlapping errors,
Status indicator
code indicator.
My "BioSig Control" is reporting 3 overlapping errors,
Bump/Offset F3
Yoke Connection Control
Programmer Connection
My question, are these really errors? or is this a defect in the analyzer and these indicators pose no threat to VI performance?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Attachments:
Overlapping control error labview.PNG ‏56 KB
Overlapping control error labview error output.PNG ‏5 KB

-18002 error after Labview 7.1.1 upgrade

Hi All,
It seems like LV 7.1.1 upgrade is very dangerous when you use with Teststand. The existing system runs fine with LV 7.0 and TS 3.1. Now we have upgraded to LV 7.1.1. The LabVIEW adapter was set as LV 7.0 runtime engine previously. Now I could see only LV 7.0 and LV 7.1 even after I upgraded to LV 7.1.1. I have mass compiled my source code folder and also LV 7.1 folder. But I couldn’t see LV 7.1.1 listed in the runtime engine adapter list.
I could see some support link which explains about the registry changes (copying LV 7.1 (runtime) key to LV 7.1.1 (runtime)). After doing so, I could see LV 7.1.1 in the adapter list. But then it is of No use. As even if I select the LV 7.1.1 runtime engine as my adapter, it changes back to LV 7.1 run time engine (when I check the adapter option again). It gives error when we run with LV 7.1 runtime engine.
I have attached the sample error message!
Thank you,
Sasi

Hi DWeiland and Schwede,
Thanks for your replies. Yes I did the runtime engine registry change and also mass compiled the LV7.1 folder and my sourcecode. I still see the problem as I have set the LV adapter as Lv 7.1.1 runtime engine. Now I have changed it to LV7.1 development system. With this setting, it is not giving any error. Thus I don’t see any problem now. The older version of the code had the adapter as the runtime engine for some reason, now I have changed the setting to the development system. I hope that it shouldn’t be a problem.
Thanks again!
Thank you,
Sasi

Error 7 - LabView

Similar Messages

Maybe you are looking for