Load errror code 11: VI version 6.1 cannot be converted to 7.1

I have several vi's that were working with labview 6.1/7.0. Now I have installed 7.1 and does not run the program showing the error; "An error occured....... load error code 11: VI version (6.1) can not be converted to the current version labview (7.1) because it has no block diagram."
what should i do to make it run?
Thanks for your help.

If you have saved a VI without a block diagram, you cannot load it in any version of LabVIEW other than the version you used to remove its diagram. You will need to find the original source VIs (that still have their diagrams) and load them in LabVIEW 7.1.
-D
P.S. - Unless you have a really good reason, you should not save VIs without their block diagrams.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

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.

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?

Load error code 9: VI version (9.0) is newer than version (8.2.1)

I have a VI that was working just last week, I returned to use it today only to find I get this error. It was written in a legal version of Labview 8.2. We don't even have 9.0 so I don't know what is causing this. Is there a way to recover it somehow?
Might I be able to post the VI here and someone with 9.0 revert it back to 8.2? Thanks in advance.
Attachments:
FlapperMotors2.vi ‏134 KB

Here's the 8.2 version. (next time ask in the downconvert thread).
It was in 9.0, so somebody must have saved it in the higher version...
LabVIEW Champion . Do more with less code and in less time .
Attachments:
FlapperMotors2.vi ‏297 KB

Load error code 11 when attempting to open .vi from library

Hello,
Recently a colleague sent me a .llb containing a VI and sub-VIs of a program needed for my research. The VI opens correctly but none of the sub-VIs can be found by it and when I attempt to open the sub-VIs I get load error code 11: VI version (6.0) cannot be converted to the current Labview verstion (8.5.1) because is has no block diagram.
I am running Vista with 8.5.1 and attempting to open a library of version 6.0. I do not know what OS the library was compiled on. (Linux is a possibility) The colleague who sent me the program does not know either, as he recieved it from another colleague whom he is no longer in contact with.
I am fairly certain the library was saved with block diagrams, so I do not think that is the source of the error.
Does anyone know what might be a way to get these sub-VIs working?

Okay,
File posted. Someone please tell me if this has a block diagram on it.
Attachments:
Find First Error.vi ‏24 KB

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

Could not load file or assembly 'log4net, Version=1.2.10.0

Server Error in '/' Application.
Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match
the assembly reference. (Exception from HRESULT: 0x80131040)
Source Error:
Line 13: public partial class ReportViewer : System.Web.UI.Page
Line 14: {
Line 15: ReportDocument rptDocument = new ReportDocument();
Line 16: ParameterDiscreteValue crtParamDiscreteValue = new ParameterDiscreteValue();
Line 17: protected void Page_Load(object sender, EventArgs e)
Source File: d:\WEBDATA\sriramcollege.com\Reports\ReportViewer.aspx.cs Line:
15
Stack Trace:
[FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
CrystalDecisions.Shared.SharedUtils..cctor() +0
[TypeInitializationException: The type initializer for 'CrystalDecisions.Shared.SharedUtils' threw an exception.]
CrystalDecisions.Shared.SharedUtils.get_CurrentControl() +18
CrystalDecisions.Shared.SharedUtils.GetEffectiveCulture() +8
CrystalDecisions.CrystalReports.Engine.CREngineRes.GetString(String name) +10
CrystalDecisions.CrystalReports.Engine.ReportDocument.CheckForCrystalReportsRuntime() +143
CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor() +159
[TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.]
CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor() +0
ReportViewer..ctor() in d:\WEBDATA\sriramcollege.com\Reports\ReportViewer.aspx.cs:15
ASP.reports_reportviewer_aspx..ctor() in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\e63cc5e2\46d2498\App_Web_bvplj1td.0.cs:0
__ASP.FastObjectFactory_app_web_bvplj1td.Create_ASP_reports_reportviewer_aspx() in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\e63cc5e2\46d2498\App_Web_bvplj1td.2.cs:0
System.Web.Compilation.BuildResultCompiledType.CreateInstance() +30
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) +100
System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +31
System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +64
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +191
System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +145
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

hi,
this is not even c# question.
anyhow, you have the same case as this one.
https://social.msdn.microsoft.com/Forums/en-US/9223655f-0cbd-441e-86a6-d53f3fb37d48/could-not-load-file-or-assembly-log4net-version12100?forum=netfxbcl
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

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!

Is Cisco Nexus 5596UP support vlan base Policing and traffic shaping on code NX OS version: 5.1(3)N1(1)

Is Cisco Nexus 5596UP support vlan base Policing and traffic shaping on code NX OS version: 5.1(3)N1(1)
where i couldn't see any police command under the policy map

I have tested this issue on another 5548UP with L3 running the same NX-OS version and get the same problem. Show CDP from the switch is not discovering devices, but the neightbors can see the 5K in question. Reboot sometimes will fix it, but not always. I suspect a problem with the software since that doesn't happen in NX-OS 5.2. The one I am using is
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 5.1(3)N2(1)
system:    version 5.1(3)N2(1)

Could not load file or assembly 'CrystalKeyCodeLib, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

I am getting following error message when I publish my code on server. I am using VS 2010 as development tool and we are using framework 2.0.
Could not load file or assembly 'CrystalKeyCodeLib, Version=9.1.5000.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies.
The system cannot find the file specified.

I was the error from my side I was refering wrong DLL.

Reg:Could not load file or assembly 'crdb_adoplus, Version=9.2.3300.0'

Hi
Am getting below error while setting the datasource to the report using craxddrt9.dll.My main task is to export the crystal report to text file.
{"Could not load file or assembly 'crdb_adoplus, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)":"crdb_adoplus, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"}
Can anyone help me.
Thanks in advance.
Thanks
Madhavi Goud

There are multiple reasons why this isnt working:
CR9 was never designed to work with VS.NET 2008
The craxddrt is not meant to work in .NET and there are quite a few issues with using it.
You need special licensing to use the craxddrt.
You need to move to CR 2008 along with VS.NET 2008 and you can export to text using the appropriate CR .NET code.
Here is a code snippet showing this:
++++++++++++++++++++++
' First we must create a new instance of the diskfiledestinationoptions class and
' set variable called crExportOptions to the exportoptions class of the reportdocument.
crDiskFileDestinationOptions = New DiskFileDestinationOptions()
crExportOptions = crReportDocument.ExportOptions
'Export to TXT.
'append a filename to the export path and set this file as the filename property for
'the DestinationOptions class
crDiskFileDestinationOptions.DiskFileName = "c:\<yourdesinationpath>\TextFormat.txt"
'set the required report ExportOptions properties
With crReportDocument.ExportOptions
     .ExportDestinationType = ExportDestinationType.DiskFile
     .ExportFormatType = ExportFormatType.Text
     .DestinationOptions = crDiskFileDestinationOptions
End With
++++++++++++++++++++++
Jason

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

Labview load error code 15 preventing me from opening the VI

I'm having some problems opening a particular VI. I get an error called: "Labview Load Error Code 15; cannot load default data." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 6.1 and the system is on a Macintosh G3 with OS 8. Thanks in advance.

It sounds like the VI is corrupt. Are you able to open it another machine or a different version of LabVIEW?

Load errror code 11: VI version 6.1 cannot be converted to 7.1

Similar Messages

Maybe you are looking for