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

Similar Messages

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

What can I do about "LabVIEW load error code 38: Failed to uncompress part of the VI."

While attempting to load an executable LabVIEW application for LabVIEW 2009 SP1 on a Windows-XP machine when the following pop-up message occurs. "LabVIEW: Memory or data structure corrupt. An error occurs in loading VI 'NI_Gmath.lblib: Backward Bracket Search.VI'. LabVIEW load error code 38: Failed to uncompress part of the VI. The VI is most likely corrupt." What seems odd is that the same LabVIEW application loads fine when logged on as a privileged user account, but fails to load on a private user account.
Attachments:
2012-07-18 LabVIEW Load error code 38.jpg ‏1314 KB

Here's a thought:
So when something is decompressed, a temp folder is often used.
I have no idea why LabVIEW would be decompressing anything, but I suspect it is trying to put the decompressed file into a temp folder where the user does not have write permissions.
In the .ini file for your executable, you can add a line that specified the location of the temp folder to use:
tmpdir=C:\Temp
On my Win7 machine, the location is:
C:\Users\MyUserName\AppData\Local\Temp
On WinXP, it is probably:
C:\Documents And Settings\YourUserName\local settings\temp
Try changing the tmpdir key in your ini file to something to C:\Temp and see if that helps.
- john

Installer LV7.1 - LabVIEW load error code 21: An external subroutine required for execution could not be found.

Bonjour,
Je cherche à créer un installer portatif utilisant les drivers NI-DAQmx 8.7.1 et NI-CAN 2.6.0.
Je dispose d'un code LV 7.1 et j'ai installé l'application builder 7.1.
Mais une fois l'application installé sur un PC vierge de Labview, j'obtiens le message suivant:
load error code 21: An external subroutine required for execution could not be found.
Ce message est répété plusieurs fois (pour différents VIs) puis le programme ne se lance pas.
J'ai bien veillé à installer les drivers NI-CAN et NI-DAQmx correspondant au préalable sur la machine cible.
En chercant sur le forum, plusieurs pistes m'ont été proposé:
La version NI-DAQ
L'intégration du Run time Engine
Un problème de DLL
J'ai vérifié ces 3 points mais cela n'a pas règlé mon problème.
Résolu !
Accéder à la solution.

Bonjour,
Merci de ta réponse.
En fait, j'ai bien inclu le runtime engine de Labview qui était effectivement la source de l'erreur.
L'installation de NI-DAQmx v 8.7.1 provoque la mise à jour de la version du runtime engine (passage de 7.1 à 7.1.1).
J'ai donc désinstallé Le runtime engine 7.1.1 (ce qui a provoqué la désinstallation de labview et NI-DAQ).
Puis je suis passé par une version plus ancienne de NI-DAQ (7.2) que j'ai adapté (inclusions de DLL et de VIs).
Les messages d'erreurs ont alors tout simplement disparus!

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!

LabView 6.0 Evaluation version load error (20)

Hi,
I wrote three vi files in LabView 6.0 evaluation version. Afte instaling the 6.1 full version the vi could not be load, giving a code 20 load error. All other vi files loaded normally.
I could not find any special instructions in these files.
Any ideas?
Yossi
Attachments:
Bessel_Function_j(x)-Spheric-011009.vi ‏146 KB
Read_From_V8_File.vi ‏58 KB
Read_File+_[V8].vi ‏67 KB

Yossi,
Refer to the following KnowledgeBase on our website:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/5654f94cdf5954ff86256b37006758c0?OpenDocument
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

LabVIEW load error 21

I get a LabVIEW load error 21 when running an exe built with LV6.1 on Win2000
The full message is "A dynamic link library initialization routine failed. An error loading DIO Config.vi". The lvdaq.dll has been installed by the installer in the expected location and the file and subdirectory permissions have been set to "everyone". NIDAQ version is 6.9.3.
This only happens when the user is logged in with "User privileges". Accounts with Power User privileges run the app just fine.
What can I change to allow accounts with normal user privileges to run my LabVIEW exe?

Hi,
DAQ is intended to be run under Administrative priveledges. This is because it is necessary to install and configure device drivers (which is an administrative priveledge). You may be able to get around this issue by giving the National Instruments folder read/write permission to everyone.
This is not a sure solution but it has worked for people in the past.
-Sal

Labview 8.2 application builder gives load error 3

Hi,
I have been developing a Labview application that I am compiling to an executable for others to run. It has been working fine until I recently made an update to the VI, but not the build settings, and now the executable generates a load error 3 for several of the sub vi's.
I am using labview 8.2 professional. I've tried using the advice in support doc 33CDL8QX but I cannot change any of the sub vi settings - everything is greyed out as shown in this image:
I've tried toggling the 'Remove Panel' option globally but this has no effect.
I'd be grateful for any help, this is driving me mad!
Cheers,
Pete

Hey there pete,
Is it possible to post your project or a shinked version of it that generates the error? I would have recomended having a look at the knowledge base you mentioned but you cannot change any of the sub vi settings. Could you attach the screenshot to your reply as I cannot see it.
Did you have a backup of your application? Do you get the same error if you try and build an installer?
Best Regards,
CLA | LabVIEW 7.1... 2013
www.renishaw.com

Labview load error code 10:VI version (8.2b23) is too old to convert to the current

trabajo en la version de LabVIEW 8.2, 20th aniversary edition, Professional y cuando intentaba abrir la parte de examples en la primera ventana me aparecia el siguiente error:
LABVIEW:VI version is too early to convert to the current labview version.
An error occurred loading VI "find examples.vi".
Labview load error code 10:VI version (8.2b23) is too old to convert to the current
labview version (8.2.1f4)
luego de la primera intaslacion de la version 8.2b23 tambien me salia el mismo error, desintale y reinstale pero igual, asi que probe instalar un parche que actuliza a la version 8.2.1f4, pero como ven sigo con el mismo problema ademas de intentar mass compile pero no me funcina al parecer son muchos VIs que hay que compilar... tambien busque el LabVIEW conversion kit, pero son para versiones demasiado anteriores agradeceria me ayudaran a solucionar este problema.
MUCHAS GRACIAS
ATT: Carlos Andres Rosero, Colombia

According to this, 8.2b23 is an illegal, bootlegged copy of LabVIEW.

LabVIEW load error code 10?

Hello..
I have received an .llb file from support at Anritsu, for a Wiltron 56100a Scalar network analyzer. It contains numerous priceless VI's. Unfortunately, when I try to open it, I get an error..
"An error occurred loading VI ''. LabView load error code 10: VI version (3.1) is too old to convert to the current LabView version (6.1)"
Is there any way I can convert this code at all? It would be most valuable! Would it be possible to get ahold of an older labview version, perhaps 4 or 5, convert to that version, then convert to 6.1? We really need these drivers..
Thanks for any suggestions!

Go here
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=0
Click on "become an Enthusiats".
Write a short bio,
Indicate what catagory,
Submit!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Load error code 9: VI version (8.2) is newer than the LabVIEW version (8.2b23).

I am getting the error...
VI version is later than the current LabVIEW version. An error occurred loading VI 'CleanupCallback.vi'. LabVIEW load error code 9: VI version (8.2) is newer than the LabVIEW version (8.2b23).

This is true. the 'b' indicates that it is a beta version of labview 8 (.2 in this case). I am surprised your beta version is still working. You need to upgrade to 8.2 or have the vi downgraded to 8.0
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

An error occurred loading VI. LabView load error code 1: LabView load error code %ld: %p"

I have been developing a VI file that has
been working fine, until now. I am using 8.6.
Every time I attempt to open this file
I keep getting:
How do I fix the error code:
Labview: Memory is
full.
An error occurred loading VI. LabView load error code 1:
LabView load error code %ld: %p”
On a separate dialog:
“Not enough memory to complete this
operation.”
I ran VI analyzer which told that the
VI:
One or more errors occurred during
analysis.
Testing errors tab – Vi not loadable
and my file name. At the bottom in the error description I got:
“Error 74. Memory or data structure
corrupt. <my file path> and <file name>.”
Could not be opened.
Is there anything I can do to recover
the file?

Hi kevin_khan,
I went ahead and tried to open it and got the error attached.
Peter T
Applications Engineer
National Instruments
Attachments:
test.png ‏14 KB

LabVIEW load error cod %ld: %p

All of the sudden, when I tried to open a VI, I got an error message that said, "LabVIEW: Resource not found. An error occured loading VI 'VI name.vi". LabVIEW load error code 1: LabVIEW load error code %ld: %p". I tried to revert that particular VI to the previous version through source control, but that didn't help. Does anyone know what I need to do to fix this? Thanks!
Kudos and Accepted as Solution are welcome!

It was fine, and now I can't open the VI. It is possible that I forcefully closed the VI a few times with ctrl+alt+del. The name.vi is the host vi for an fpga application. It interacts with user, calls .NET DLL to communite with a DUT, pass data to/from FPGA, etc.
I had already looked at the link that you posted. Not sure does it apply to me.
Kudos and Accepted as Solution are welcome!

Why I get Labview load error code 16?

"Labview load error code 16 preventing me from opening the VI"
"I'm having some problems opening a particular VI. I get an error called: "Resource not found"; "Labview Load Error Code 16; Could not load data space link information." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 7, the size of vi is about 1.08 Mb, and the system is on a Windows 98. Thanks in advance."

Hello James,
Thank you for contacting National Instruments.
Try opening the VI with another version of LabVIEW. You can also try placing the VI as a subVI and then viewing its block diagram.
You're also welcome to post your VI, and we can try to open it up here.
I hope this helps!
Matthew C
Applications Engineer
National Instruments

LabVIEW load error code 1: LabVIEW load error code %Id: %p

One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
This is a huge problem for me, hope someone can help...
Regards
Jesper

Hi Jesper
For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
Extending Virtual Memory Usage for 32-bit Windows
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
To use Source Code Control on your computer you will need:
1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
Software Configuration Management and LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/4114
3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
Bisides the advantage of being able to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Load error in LabVIEW communications

Similar Messages

Maybe you are looking for