Built is not executing in Runtime

Hello,
i have to PCs. One with LV 2013 to develop and create exe-files and a second PC with only Runtime installed.
Just now i tried the first time to execute a fresh built exe-file and got this popup:
But in my Windows 7 64bit under software i see that it is installed:
What is the problem?
I installed "LVRTE2013_64bitstd.exe" or is this the wrong runtime as my Labview-version is LabVIEW 2013 SP1 (32-bit)
Thanks for help
Solved!
Go to Solution.

All that said, the error message in the first picture should mention the word "32bit" to avoid confusions like this!
Why doesn't it???
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Mapping is not executed in runtime

Hi All,
i am doing a scenario
1)file to idoc
2)idoc to idoc
in the two scenarios we are geeting the same idoc error 56.
partner profiles are maintained and ports and rfc destinations are also maintained.
but why this error is coming we are not understanding.
2)when i run the message mapping ,it is executed in IR, but in end to end scenario it is not executed.
Please suggest.
Regards,
reddy

Hi
This error generally happens when we dont properly maintain below details.
Please check you have defined Sender System port in Receiver System.
Tcode WE21 - give port name and give RFC destination(i.e connect your Sender System)
then send IDOC
Regards
Pothana

Badi does not execute at runtime

Hello All,
We are having a problem trying to implement BADI BBP_CATALOG_TRANSFER with method ENRICH_ITEM_DATA / interface IF_EX_BBP_CATALOG_TRANSFER
We have created a new implementation for this BADI that has generated a new class (in se19). The implementation is visible in V_ext_act and the class and implementation is visible in SXC_CLASS.
The implementation is active, the class is active and the class has the correct method IF_EX_BBP_CATALOG_TRANSFER~ENRICH_ITEM_DATA
However
When performing a where used list for this BADI our new implementation does not appear. Instead we are still seeing an old implementation that has been deleted. In addition the source code that we have implemented as part of the exit is not being executed during run time.
We think that we have covered all the steps required but may be missing something vital ???
I know this is a tricky one but any help would be greatly appreciated.
Thanks very much in advance
Regards
Ketan

Hello
Just wanted to add that in addition to our custom implementations, the class implementation
CL_EX_BBP_CATALOG_TRANSFER
is also associated with this BADI in the where used list.
When I look at this in our QA environment this class is not associated only the custom developed classes are associated.
Not sure why?
Any ideas would be appreciated..
Regards

XSLT for adding Namespace is not being executed at runtime

Hi Gurus,
I am trying to add a Namespace to inbound xml and I wrote a simple XSLT mapping as below, when I execute this using XML spy or in Operation mapping manually it is working fine and giving me output as expected but at runtime it is not executing, I am getting same input xml as output xml and receiver agreement is failing...
Appreciate your thoughts..
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:output method="xml" encoding="UTF-8"/>
 <xsl:template match="*">
 <ns0:SalesXmlExtended xmlns:ns0="urn:/company.com/H/sndr">
 <xsl:copy-of select="//SalesReportInfo"/>
 </ns0:SalesXmlExtended>
 </xsl:template>
</xsl:stylesheet>
input xml is as below....
<?xml version="1.0" encoding="UTF-8"?>
<SalesXmlExtended>
 <SalesReportInfo>
 <SalesReport>
 <Detail>
 <deptNum>0270</deptNum> etc...
output I am getting in XMLSpy and OM is as below, this is exactly what I need...
<?xml version="1.0" encoding="UTF-8"?>
<ns0:SalesXmlExtended xmlns:ns0="urn:/company.com/H/sndr">
 <SalesReportInfo>
 <SalesReport>
 <Detail>
 <deptNum>0270</deptNum>
Thanks...
Sukarna...

Hi Baskar,
Yeah, that is what my issue is , it shouldn't be failing but it is...
I tried by manipulating the required namespace in the input file and it is working fine with out any errors....so I am guessing the XSLT is not being executed...
I am getting below error which is valid because the transformation is not happening
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_HOUSE_OF_FRASER_DEV</SAP:P1><SAP:P2>-BD1_100,urn:.com/HoF/POS/EOD/sndr.SI_Out_HoFSales_XML</SAP:P2>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText>No standard agreement found for , BS_HOUSE_OF_FRASER_DEV, , BD1_100, urn:/HoF/POS/EOD/sndr, SI_Out_HoFSales_XML</SAP:AdditionalText
><SAP:Stack>Problem occurred in receiver agreement for sender -BS_HOUSE_OF_FRASER_DEV to receiver -

Runtime.exec not executing the command !

Hi all,
I'm connecting to Progress Db thru JDBC trying to execute a stored procedure
which has a statement
Runtime.exec("ksh -c aa") where aa is aunix script which i'm trying to run from java snippet .
when i run this code as a seperate java program it executes the script
"aa" but thru JDBC connection it does not execute the command
what could be the reason ???
thanx in advance,
Nagu.

Hi Rick,
"aa" is the shell script which is lying in the user DIR .
It is returning a non-zero value. what kind of permissions be there for to execute the Shell command?
Regards,
Nagarathna.

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

UWL Task does not execute.........Gives Portal Runtime Error

Hi,
I completed UWL configuration.Some tasks execute properly but some tasks not execute it shows error like...
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapLaunch
Component Name : com.sap.portal.appintegrator.sap.Transaction
Exception in SAP Application Integrator occured: Application URL ':///sap(ZT1qRnRCaDZMVzlyX2llTjRJZTRGcXp3LS1NTzJqNlpibU42bkFwTzZaejdObTZ3LS0=)/bc/gui/sap/its/webgui' is not valid! Please check the protocol and host entries for system 'B07CLNT100_GB'..
Exception id: 05:50_27/12/07_0020_7205750
See the details for the exception ID in the log file
Please help me out to correct this problem.
Regards,
Gurprit Bhatia

Activate below services in ur back end systems
With transaction SICF and locate the services by path
sap/bc/gui/sap/its/webgui
Activate the full path to these services
with the context menu.
goto SE80
Locate the Internet Services
SYSTEM
Publish these services with the Context
Menu -> Publish -> Complete Service
and also WEBGUI
Publish these services with the Context
Menu -> Publish -> Complete Service
Regards
Krishna.

VI seen as not executable from LV runtime, correct in LV development

My current problem is the following:
On the same PC, having TestStand 4.0 & LabVIEW Development 8.5, I try running a sequence with both adapters: LV development 8.5 and LV runtime 8.5.
My sequence steps call VIs that call subVIs in a full hierarchy (let's say 1500 VIs are involved in a test sequence).
The sequence runs with the development adapter, and with the runtime, I got a -18002 LabVIEW error: Vi not executable, broken, etc.
Of course, when I open the VI within the development environment, everything is correct.
As I'm testing both adapters on the same PC, the full hierarchy, including LV libraries provided with LV development are at the same location.
Due to the large amount of VIs I use, I cannot guess which LLB could be missing or not inaccessible.
Is there a way to investigate the cause, despite the fact that everything is correct under the development environment?
Is it possible to tell the LV runtime where it should search for LLBs or other required dependencies that the LV development seams able to find?
Thanks in advance for your help,
JJD
Solved!
Go to Solution.

Hello,
I've seen this error when two VIs withthe same name were loaded in memory; this VI was called from a TestStand sequence and from the user interface (very poor design of a customer that I will not mention ^^).
I'm not sure to understand youy problem: everything works fine when you are using Developpment system (Active Version 8.5) but, do you have this error when you set the adapter to LabVIEW Run-Time Engine 8.5, right? Are LabVIEW and/or VIs used in your sequence open when you run your sequence in Run-Time mode?
Cordially,
.mrLeft{float:left} .mrInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898}
Mathieu R.
  CTD - Certified TestStand Developer / Développeur TestStand Certifié
  CLAD - Certified LabVIEW Associate Developer

"vi is not executable" built app - product feature request

OK, here's what I want for the next version of LabVIEW. Forget a real implementation of OO. Forget about making XControls so that you don't need a PhD to program them. Forget about a real polymorphic control (down all you who say "variant!"). Here's what I want for the next feature of LabVIEW.
I want the run-time engine to give me a better idea of why a built application won't run. The generic "This VI is not executable. The full development version of LabVIEW is required to fix the errors..." is meaningless. If the VI works just fine in the development environment, and it builds without errors, why does it not run? If there's so many reasons, how is one supposed to track it down?
I've been using LabVIEW since version 2 on a Mac, so I like to think that I know what I'm doing with it. Yet, whenever I run into this I feel helpless because I have NO information! This is frustrating beyond my ability to put into words. And please don't tell me to look at this article or this other article in your KnowledgeBase. Been there, done that. In one situation I tracked the problem down to a VI. Couldn't find ANYTHING wrong with it. So, I created a new VI, copied the block diagram over, and saved the new VI over it. Rebuilt the app, and presto, the app worked. Do you know how long it took me to track it down to that VI? About half a day. Was there ANYTHING that gave me a clue as to the problem? Can you say rhetorical question?
I'm posting this here in the hopes that enough people get my grief, and head over to the Product Suggestion Form to hopefully make this pipe dream a reality. Power to the people!
Now, back to figuring out why my latest built application won't run. Guess what I'll be doing for the next half-day or so.

smercurio, i can't help you, but i'm with you, maybe that makes you feel better.
i upgraded a LV-app i created originally with 7.1 (this was the best LV ever, in my opinion) to 8.20. i was forced to do that because of the 64bit feature of ms tickers. it took me about 4hrs to create a project to generate an executable, after several LV-crashes during editing. finally i managed to get the project working (compiling took about 10 mins, with the 7.1 app builder about 1 min!! same code!!!), and then there was this error message: "error blabla in VI blubblub", and the VI was part of the vi.lib! so what to do?
KB: no answer!
discussion forum: no hits!
i found a post in the forum about another error code, but the same scenario. workaround was to disable the "remove as much as possible" option in the advanced project settings.
result: size of executable increased about 100%, while execution speed decreased about 50% compared to the 7.1 version, though all of the "code enhancement features" of 8.20.
now i'm thinking of switching back to 7.1 and to workaround the limits of long execution times with 32bit tickers.
i'm a big fan of LV, and i'm dealing with it since 1998, not for fun, but as a professional programmer. but 8.2 is a real step backwards in quality in my opinion. i think this has to be said to make 9.0 better!
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

SSIS Script task not executing macro through SQL Agent (but it does through bids)

Hello everyone,I am having an issue with SQL Agent when executing a macro contained in a script task component. The script task actually opens an excel file, runs the macro, save and closes the file. When
I execute the package via BIDS/Visual studio, it works like a charm. However, when i execute the package with SQL agent, the package runs successfully but it seems that the macro is not executed as the excel file has not been modified as it should have. Also,
the history log does not show any error messages. Could 

Thanks!I did create a credential and a proxy too but still the macro is not executed.I have searched online for solutions but no one has experimented this kind of issue before it seems. Please have a look at the script task code:
Imports
Excel = Microsoft.Office.Interop.Excel
Imports
System
Imports
System.Data
Imports
System.Math
Imports
Microsoft.SqlServer.Dts.Runtime
<System.AddIn.AddIn(
"ScriptMain", Version:="1.0",
Publisher:="", Description:="")>
<System.CLSCompliantAttribute(
False)> _
Partial
Public
Class ScriptMain
Inherits Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase
Enum ScriptResults
Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success
Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure
End
Enum
Public
Sub Main()
Dim Macro_name
As
String
Dim ExcelObject
As
New Microsoft.Office.Interop.Excel.Application
Dim oBook
As Microsoft.Office.Interop.Excel.Workbook
Dim oBooks
As Microsoft.Office.Interop.Excel.Workbooks
Try
Macro_name =
"Macro001"
ExcelObject =
CType(CreateObject("Excel.Application"),
Excel.Application)
ExcelObject.Visible =
True
ExcelObject.UserControl =
False
ExcelObject.DisplayAlerts =
False
oBooks = ExcelObject.Workbooks
oBook =
CType(oBooks.Open("C\Book1.xls"),
Excel.WorkbookClass)
ExcelObject.Run(Macro_name)
Catch ex
As Exception
ExcelObject.Application.Quit()
ExcelObject.DisplayAlerts =
True
ExcelObject =
Nothing
End
Try
Dts.TaskResult = ScriptResults.Success
End
Sub
End
Class

Interface mapping Object does not exist in runtime cache

I am getting the following error after importing IR into our test system (PI7.0 SP10).
Interface mapping Object ID 19C3AC9D13B03787AEEB85169D0B6900 Software Component 8C51B2209F3C11DB94CEEB180DDF0074 does not exist in runtime cache Exception of class CX_XMS_SYSERR_MAPPING
You want to execute interface mapping Object ID 19C3AC9D13B03787AEEB85169D0B6900 Software Component 8C51B2209F3C11DB94CEEB180DDF0074 . However,the data of this interface mapping is missing in the runtime cache. Activate the interface mapping in the Integration Repository.
I cannot change the mapping and reactivate - as this cannot be changed.
I have run SXI_Cache, Cleared SLD caches on IR and ID and run cacherefresh=full, but no luck!
The mapping is there and I can test it in the IR.
Any thoughts?

I had this problem today, maybe this helps someone when searching about this (at least this is the first hit at a very big search engine when searching for interface mapping does not exist...)
I have a RFC => PI => File scenario. I was aware that this would need to be asynchronous so I set up the message interface (service interface for PI > 7.0) as asynchronous inbound. This is the file receiver part of the interface.
Hints on the error: Audit Log in message details of RWB showed a line like this: RFC adapter received sRFC for ZMY_FM from <sender SID>/<sender client>. Attempting to send message synchronously. This of course could not work as file is asynchronous by default.
Bottom line however was, to make the call of the sender RFC asynchronous by using "in background task" like so:
CALL FUNCTION 'ZMY_FM'
 IN BACKGROUND TASK
 DESTINATION 'PI_DEST'
 EXPORTING
 t_file = lt_file.
COMMIT WORK.
Don't forget the commit work here.
Hope this helps.
Cheers
Jens

Error message "VI is not executable"! Need help with Application Builder

Hello,
I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
To get a better idea from my project, here a little description of it:
In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
So, i hope to get an answer soon (the deadline for the project is not soooo far away )
If you need more information, please let it know...
I would be very grateful if there is someone with a working solution...
Kind regards from the Netherlands,
Sebastian

Sebastian,
Your architecture makes it very difficult to debug this and other problems. Does the error message mention which VI is causing the problem? It is very important to wire your error clusters everywhere. In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute. At the end, place an error cluster indicator that you can see on your front panel. When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
This is a start, but you really need to push this into a queued-state machine before this gets any more complicated. As it were, if anything in your loop hangs, your whole application hangs. See attached for a queued-message handler (not advisable for actual applications, but you get the point. You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
-Jason
Message Edited by LabBEAN on 01-20-2009 08:36 AM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
State Machine.vi ‏18 KB

Flex Application showing no errors in Eclipse but not executing either

Hello,
I am trying to develop an application in flex/BlazeDS/Java in eclipse and my problem is since my changes in the code are not reflected anymore during runtime of the application. There is no error received from eclipse when I try to clean the project. It is deployed correctly but it seems to be working with the old code and not reflecting the changes. I tried to put the breakpoint too but it says, 'breakpoint cannot be placed here because there is not executable code in this line'
Please advice.
Best Regards,
Jai Kishan Shah

Hello,
Well, i never re-install the FlexBuilder (stand-alone, or eclipse-plugin) because any error.
Your output folder in Flex Build Path on your Project Properties is correct? Other question, you are working with Java ? Many times the project have a "error" on configuration and the directory to deploy is not listen by web-server.
Exemple:
If i work with Java and my CATALINA_HOME is: C:\tomcat\ - My webapps is localizated on: C:\tomcat\webapps\MYWEBAPP\ but my output folder on FlexProject is: C:\MyProject\Flex\bin-debug, and i run the application, the application dont work...
So.. can you show your configuration? Its more easy to understand your problem and help you.
Regards

The VI is not executable. The full development version...

"The VI is not executable. The full development version of LabVIEW is required to fix the errors." That is the error I've been dealing with all day. Actually it is repeated 3 to 4 times in the error message, seen when first launching the EXE. Also of note is that the run-arrow is broken. This is in an EXE that was developed well before version 2013, but I recently upgraded it to 2013 to hopefully fix some random LVRT crashes. There is obviously no issue running the code on my development machine, only once it's deployed.
The good news is I've been able to solve the problem (mostly). My EXE now runs without the errors. I found that the problem wasn't actually in the EXE.
We have a separate project with no files, but in the build specification we have the LabVIEW 2013 Run-Time Engine, as well as NI-VISA for serial support. We then bundle the deployment in a self-extracting RAR and it does its business. In the past this has worked just fine, but with LV2013, it seems that there is a component missing from the deployment.
I found that if I download the Run-Time Engine directly from NI.com and run it, the only things I need to install are the Run-Time Engine, and the DEPLOYABLE LICENSE. If I do this, my EXE runs great, but with the custom installer, it is not included for some reason!
Putting aside the fact that I don't know why the Deployable License package is needed (we aren't connecting to remote panels), I can't seem to modify my custom installer to install the Deployable License. There are versions for LabVIEW 2009 and 2011 SP1 in the Additional Installers list, but I don't see 2013.
Can anyone explain why this is??? For now I will just distribute the 257MB Run-Time Engine and the NI-VISA installers separately I guess. But I'd really like to get back to a single, simple package to install all the prerequisites we need. HELP!

iannicholson wrote:
Yes, but then every installer I build will contain the runtime engine. That gets very large very quick. So I have an installer for JUST the runtime engine and VISA runtime.
Just remove them from the "Additional Installers" tab of the Installer dialog.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Built is not executing in Runtime

Similar Messages

Maybe you are looking for