Vi converted to LabView 7.0 Error

I converted an application from LabView 6.02 to 7.0, and the conversion is fine.
However, when one particular vi is opened, Labview 7.0 asks and searches for the vi named ""
I continue (press ignore vi), and the vi is loaded .
I saved the vi, opened it again , and still get the same message. It is annoying.
I solved the problem by copying the block diagram of the vi to a new vi and then saved the new vi. The saved vi, if opened does not produce the message anymore (good news)
Attached is the vi (_stop.vi) with no block diagram. Open it to see the message displayed
Attachments:
load_debug_vi.jpg ‏36 KB
_Stop.vi ‏7 KB

Hi Dr. Imad,
another workaround is described here. Search for my answer. This is a conversion bug in LV 7.0 and the workaround is first load it into LV 7.0 then save it into the new location and then make your changes.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Similar Messages

Converting from LabView 4.0 to 8.5

I have a Pico Technology TC-08 thermocouple datalogger (RS232). It has drivers for Labview 4.0 but I use Labview 8.5, which says it can't convert the drivers. From the help pages I have understood that there is separate software that can convert from Labview 4.0 to 8.5. Can anyone tell me where I can download or otherwise obtain this software?

Hi EKY,
converted to LV7.1 - should be ok now
But: there's a "missing dll"-error. You have to check this in LV8.5.
There is also no guarantee the dll will work with LV8.5 or maybe new operating system (from Win95 to WinXP or Vista?)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
TC081_LV71.LLB ‏29 KB

Need to convert to labview 11 from labview 12

hello
I need to convert the following Labview 12 VIs to Labview 11.
thank you in advance
Attachments:
QAM Demodulation.vi ‏30 KB
QAM Modulation.vi ‏30 KB
rx QAM.vi ‏57 KB

The conversion was done here: http://forums.ni.com/t5/Version-Conversion/need-to-convert-from-Labview-12-VI-to-Labview-11/m-p/3021...
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

After writing an html report on a floppy disk and removing it, labview shows an error message window: disk not present

after writing an html report on a floppy disk and removing it, labview shows an error message window: disk not present.
My pc is based on asus motherboard. Labview 7 and Windows 2000 sp4 installed.
The error message continue also if i stop the application that generated report on a: .
I've got this problem only on a pc: on other machines i don't have this problem (Labview only continues to access floppy but it doesn't show any window).
Find below an example: first press the button to create a report on a: then remove the floppy, after 30-35 sec i've got the error message
Attachments:
prova.vi ‏55 KB

Hi,
I tried your vi: I don't get any error message after removing the disk but LV7 keeps on accessing the drive at regular intervals even if you stop the vi and close it!!! This is not supposed to happen.
The only way to stop it is exit LV7.
If you don't use the file dialog and you wire a full path, you don't get any problem.
I also created a very simple vi that conditionally writes a text file on a: and I got the same behaviour.
This problem occurs only with LV7, I tried the same examples in LV6.1 and everything was fine.
If anybody wants to try I attach this simple example,
Alberto
Attachments:
salva_testo1.vi ‏22 KB

Convert from LabVIEW 2011 to LabVIEW 9.0

Please convert from LabVIEW 2011 to LabVIEW 9.0
Attachments:
Watlow Vis.zip ‏76 KB

Looks like somebody forgot to attach the zip file. Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Watflow.zip ‏57 KB

The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Nickled and dimed once again by obscure errors. This is LabVIEW 10.0.1 on Redhat EL 5.5 32-bit.
I removed an enum from the project that is also used in a typedef control cluster. Since many VIs use this typedef I have to go to each VI and save in order to remove the phantom dependencies (i.e. popup can't find enum ctl when opening VIs). In the process of opening every VI and saving LabVIew is crashing on me reliably but not everytime just after I press cancel when it tries to find the enum ctl.
Here are the errors. Sometimes the address is null....I believe LabVIEW src code should check for null/bad pointers but does not in this case.
GenNAryOp_ArrayBase : naryop, setdef? ninp=1
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xFF
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x21
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt bool, csrc=0x30
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xA
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x50
LabVIEW caught fatal signal
10.0.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0xffffffff
Upon reopening LV I see this.
The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Hello wbdoyle,
I'm sorry you are seeing that error. Did you close and save the type def that included the enum? This should prevent you from having to go through and save each VI that includes the type def. Are you using the System Exec VI? Also, are you performing any data acquisition with the VI you are referencing? The error you are seeing indicates that the LV compiler isn't handling something in your VI and I want to pinpoint exactly what is happening.
Thanks!
Regards,
Anna L
Applications Engineer
National Instruments

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

How to Convert the Warning Message to Error Message in Standard Transaction

Hi,
I face one problem in Standard Transaction Code CS02. In that by entering the material Number, Plant, bomstatus press enter. it gives a warning message. How to convert the Warning message to Error. In abap how to do that. Please help me.

Mohan,
It appears that there is some configuration you can do for BOM Message types to change the message type. The IMG link for this function is:
Production->Basic Data->Bill of Material->General Data->Change Message Type
However you need to read the IMG documentation to see if this will work for you. There are only certain messages that can be changed with this configuration step.
Also, please do not double post questions in the forums.
Best Regards,
Chris H.

Converter Web Client: get compiler error when run URL

When I try to run the Converter's web client with the the URL:
http://localhost:8000/converter
I got a compiler error on the lines:
import Converter;
import ConverterHome;
The J2EE server wants to have a "." after the Converter and ConverterHome.
Any one has any idea?
The error messages are:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Compiling 1 source file
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:7: '.' expected
import Converter;
^
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:8: '.' expected
import ConverterHome;
^
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:20: cannot resolve symbol
symbol : class Converter
location: class org.apache.jsp.index_jsp
private Converter converter = null;
^
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:26: cannot resolve symbol
symbol : class ConverterHome
location: class org.apache.jsp.index_jsp
ConverterHome home = (ConverterHome)PortableRemoteObject.narrow(objRef, ConverterHome.class);
^
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:26: cannot resolve symbol
symbol : class ConverterHome
location: class org.apache.jsp.index_jsp
ConverterHome home = (ConverterHome)PortableRemoteObject.narrow(objRef, ConverterHome.class);
^
C:\app\j2sdkee1.4\web\repository\Standard-Engine\localhost\converter\index_jsp.java:26: cannot resolve symbol
symbol : class ConverterHome
location: class org.apache.jsp.index_jsp
ConverterHome home = (ConverterHome)PortableRemoteObject.narrow(objRef, ConverterHome.class);
^
6 errors
     at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:125)
     at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
     at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:387)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:410)
     at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:570)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.util.SecurityUtil$1.run(SecurityUtil.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:499)
     at org.apache.catalina.util.SecurityUtil.execute(SecurityUtil.java:210)
     at org.apache.catalina.util.SecurityUtil.doAsPrivilege(SecurityUtil.java:147)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:99)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:177)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:271)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2505)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:133)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:383)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
     at java.lang.Thread.run(Thread.java:536)
Apache Tomcat/5.0

I have exactly the same error.
Me too, I'm running on Win XP. And I have had lots of trouble to deploy the converter.
I cannot install J2EE 1.3 as I am supposed to write a report on how Web Services may help my company. By the moment I can only say it takes me much more time than expected to run the J2EE 1.3 tutorial. As SUN didn't deliver a tutorial one can use.
So by the moment if anyone can HELP me to finish this converter tutorial I will be thankful.
Bye
Manuel Acevedo

LabVIEW File Permissions Error (8) when trying to delete a .SVN checkout directory

This one has me stumped...
Our test platform: Windows XP SP2, LabVIEW 8.2.1, TortoiseSVN client 1.45 Build 10425
We would like to delete our checkout folder and download a clean version from our SVN server using LabVIEW.
When we try and delete the folder using the standard LabVIEW Delete VI (see attached snap) we always receive Error 8 - LabVIEW: File permission error. You do not have the correct permissions for the file. This is interesting because I've checked the entire directory hierarchy and I'm the sole owner under Windows XP - I'm also our domain admin.
In an effort to debug this further, we removed the contents of the directory, apart from the hidden .svn. We checked the .svn tree for any outstanding files and removed them. We then re-ran the LabVIEW code to delete the dir. Still no joy. We then looked at the Windows dialog for the attributes of the checkout folder. It appear that the folder has read-onlly attributes - with a greyed-out tick in the checkbox. Also trying to delete the folder under the Windows command line doesn't work either. It only seems to work when you delete the folder through the Windows GUI.
Any thoughts anyone?
-Chroma
Attachments:
LV Delete Code.png ‏27 KB

LabVIEW has the nasy habit of locking a directory where it opened a file in or just browsed.
Maybe this bug is biting you
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Converting from Deski to Webi - Error

Hi Everybody,
when I try to convert the DeskI report to WebI, it is partially converted because of the following error:
Failed: Page Setup Options : (Report Name)- Page setup options are not implemented in Web Intelligence (First page number, page order, scale, Fit to N pages)
Can anyone explain me how to fix this error?
Thanks for in advance
Swen
BusinessObjects Enterprise XIR2 SP4

Tulsi,
After importing the BIAR file, did you check to make sure all your DeskI reports work properly. Are you running latest version XI 3.1 w/ SP7?
Are all DeskI reports working properly prior to running the RCT.
Regards,
Ajay

Converting Warning Message 06434 into Error message

Hi Experts,
While creating PO with ref to RFQ systems gives warning message 06434. Kindly any one guide me how to convert this warning message to error message.
Thnxs
Harish

Hi,
To change the message category from Warning to Error,please follow the below path in SPRO:
Materials ManagementPurchasingEnvironment-- Define Attributes of System Messages------System Messages
Edited by: Manish Kumar Agarwal on Jun 15, 2009 12:59 PM

Pdf arabic text file unable to convert to word formate text error is coming.

Dear Sir,
Pdf arabic text file unable to convert to word formate text error is coming. The arabic text once converted to word language error is appearing.

Hi,
I am moving your posting at PDF Pack(CreatePDF) forum to Acrobat forum.
Hisami

Just purchased this, verified my email, payment taken etc., etc., but keep getting a message when trying to convert a doc saying an error occured when signing in. I have siged out and signed in again - no avail. Any help would be much appreciated. Than

Just purchased this product, verified my email, payment taken etc., etc., but keep getting a message when trying to convert a doc saying an error occured when signing in. I have siged out and signed in again - no avail. Any help would be much appreciated. Thanks

Hi there Katie,
I just checked your account, and see that it's active. Are you trying to sign in via Adobe Reader? If so, please choose Help > Check for Updates in Reader and make sure that it-s up-to-date. The most current version, 11.0.07, should alleviate that sign-in error.
Best,
Sara

What does LabVIEW mean by "Error 71: File Datalog Type Conflict"

What does LabVIEW mean by "Error 71: File Datalog Type Conflict" (Hex code:47)
Thank you.

Please provide us further information on when you are getting the error and what the functionality of the VI is. That would help us to troubleshoot your issue.
Is the error caused by a similar situation as the one descibed in this KnowledgeBase?
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

Vi converted to LabView 7.0 Error

Similar Messages

Maybe you are looking for