Variant config : Run time Version

Hi All,
During run time version generation in Variant configuration, in R/3 using Tcode CU34 , errors like two characteristics are pointing to same table and field name and structure is not defined.
Process is like this : We created configuration profile, checked the consistency in CU50 and then created KB object using CU31 and then executed run time version in CU34...here we are getting error messages and unable to generate run time versions.
Further, these run time versions will be used in CRM system....
It is understand that CRM doesnt support multiple characteristics pointing to same table field....
My question is whether the R/3 will check the consistency of profile/run time version in CRM also at the time of run time version generation?
Suggest me solution.....
BR,
Krishna

No.
But for the inhouse use of your NCo-based application you just distribute your app with the needed runtime DLLs:
- SAP.Connector.DLL (deploy to app-dir or GAC)
- SAP.Connector.Rfc.DLL (deploy to app-dir or GAC)
- LIBRFC32.DLL (deploy to app-dir or System32)

Similar Messages

Error in generating Run time version of the KB Object of a VC Product

Hi All
There is a VC Product which needs to be transported to the CRM server via Middleware.
Hence I need to create a Knowledge Base (KB Object) and generate a Run-Time version of the same.
I am getting an error while generating the Run Time version. The description of the error is as follows:
Object characteristic COSTING_LOT_SIZE is supported in IPC scnearios 3,5
and
Object characteristic PRICE_LIST is not supported in IPC scnearios.
The exceptions raised are STPO-MENGE (Component Quantity) and SDCOM-VKOND (Variant Condition)
Please provide your inputs and suggestions in this regard.
P.S: Once I generate the run time version successfully, the CRM Middleware Consultant needs to download the VC Product to CRM.
Thanks in Advance
Regards
Chaitanya

Hi Mike,
It likely is the viewer causing the problem. 2008 now has cascading parameters and the activex viewer does not support them.
All I can suggest is you try CR XI R2 which you can upgrade for free, you have to contact CIC to get a keycode to deploy your app, and test again.
R2 is out of support now so no fixes available...
http://downloads.businessobjects.com/akdlm/crystalreports/crxir2_sp4_full_bld_0-20008684.exe
http://downloads.businessobjects.com/akdlm/crystalreports/CRYSTALREPORTS06_0-20008684.EXE
Thanks
Don

Labview run time version

My CVI application needs to have the LabVIEW run-time engine installed to run so I would like to programmatically check it is installed at program start.
Now, the question is not simply "how can I retrieve the LV runtime version?", as differently from CVI there may be more than one LVRTE in the system, so I must either check for all RTEs installed or at least discover the latest (and this makes another question come to my mind: may a module developed on a specific LV rersion can be run with a newer RTE? If so, why having more than one RTE installed?)
Thanks to anyone who can help me in this matter,
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?
Solved!
Go to Solution.

Hi Roberto,
first of all, LabVIEW RunTime Engine (differently from CVI) is not backwards compatible (as explained here), thus an application requires a RTE version exactly matching the LV development environment one, in order to run properly.
If you need to programmatically check which LV RTE versions are installed on the PC, you could list the folders contained in C:\Program Files\National Instruments\Shared\LabVIEW Run-Time, as a folder for each version exists.
Otherwise, you could access the registry keys from your application checking in HKEY_LOCAL_MACHINE>>SOFTWARE>>National Instruments>>LabVIEW Run-Time for the installed versions.
I hope this suggestions could help!
Bye!
Licia

Saved default Parameter values not appearing in Run Time version of report

I've created a report in Crystal 2008 and set up a number of parameters. I supplied each of them with a default value. I check it out in Crystal Reports and a nice looking window opens up that shows all my parameters with the default values. I save the report and open it within our application and upon pressing print, a plain looking box appears that lists my parameters but none of the saved values are included. Is this a problem with my version of Crystal Reports (ver. 12.2.0.290) that I can get an update for to fix; Or, is this a problem with the crviewer.dll that we are running in our application (ver 11.0.0.1282, dated March 8, 2005)?
I'm worried about updating to the latest Crystal 2008 crviewer.dll because I've read where it is only for reports with Saved Data and that won't work for us. We need the ability to refresh the data on the reports.

Hi Mike,
It likely is the viewer causing the problem. 2008 now has cascading parameters and the activex viewer does not support them.
All I can suggest is you try CR XI R2 which you can upgrade for free, you have to contact CIC to get a keycode to deploy your app, and test again.
R2 is out of support now so no fixes available...
http://downloads.businessobjects.com/akdlm/crystalreports/crxir2_sp4_full_bld_0-20008684.exe
http://downloads.businessobjects.com/akdlm/crystalreports/CRYSTALREPORTS06_0-20008684.EXE
Thanks
Don

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

NI-DAQmx Run-time Engine

Is a run-time version of the NI-DAQmx v8.6 driver available yet? I'm distributing an application from LV 7.1 that requires DAQmx and want to include this as part of the installation. I found run-time packages for v8.3 but I'm using v8.6 in my development work so hate to switch to an older version. Are there any compatibility issues in using v8.3? Thanks.
Art

HI Paul,
Thanks for your suggestions. Just prior to receiving your response, I had in fact tried to build just an installer for the daq driver from LV 8.5. The problem is that it forces the project to be saved before it will create and installer and then proceeds to include the empty project and the LV runtime engine. In my case, I named the project test and the installer created c:\test on the target and installed the LV runtime as well as the daq driver. I also ended up with a regiestered application - test. Once I manually uninstalled test, I had the result I wanted, but too long a path to get there.
I bit the bullet and migrated the code from LV 7.1 to LV 8.5 so that I could build a comprehensive installer. Generally, things turned out well. My biggest question is why the application builder / installer insists on putting both LV 8.2 and 8.5 RTE on the target. I want, and expect, only LV 8.5 RTE. I'm have installed and am running off of the 3rd Q release for the NI developer suite. Why is 8.2 RTE loading and how do I correct this?
Another strange result is that my daq device and channels do not show up in MAX. I included the level 5 daq driver and MAX in my installer as well as the hardware configuration. The application works ok, and if I manully import from my *.nce file then I get a warning that my device will be replaced. Is this normal? The GPIB controller shows up as normal. The only thing that seemed odd during installation was that the daq driver didn't complete installation after restart because I forgot to plug in the daq device cable. Afterward it seemed ok.
I also have a couple of bugs with the application builder / installer. I converted my LV 7.1 build script and made needed changes. I see the following behaviors.
1) I have setup a file to install into a subdirectory. Every thing works ok except when I subsequently go back into the Installer Properties window and go to the Source Files. I see two problems. First, in the Project View my files are in the correct locations, but the icon for the one in the sub-directory is switched with the very last one in the list. Second, in the Destination View the next-to-the-last file from the Project View is the one shown in the sub-directory while the file that should be in there is listed directed below it in the list (but not in the sub-directory). Everything installs to the correct location, but this maked it very confusing to edit the installer.
2) Whenever I use the Build All command, the application builder fails with the following error. If I start the build individually from the Properties window, then the build completes successfully.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\McPherson-errors.txt
Thanks again for help.
Art

Get Layout details during run time of the report

Hi floks,
          We are downloading the ALV ouput data through a customised button. Presently, it downloads all the data from the Internal table that is passing to the function module. But the requirement is it should download only those fields which are in that particular layout selected....Could you please let me know how to get the various fields assigned to that variant at run time...is there any function module to do so..
                                Thanks in advance,
                                    Shyam.

Hi shyam,
                  The layouts are stored in the table LTDX. The function module 'LT_DBDATA_READ_FROM_LTDX' gives the info about the fields displayed in the using the layout. In the tables paremeter T_DBFIELDCAT the field key1 is populated with the the fields used in the layout. you just have to poplulate the exportin parameter IS_VARKEY with the report name and variant name . it is similar the entries in the table LTDX. All these related info about the Layouts can be found in the function group SKBS . you have to code accordingly once you have the fields used in the layout and download the data.
Hope this helps you.
Cheers,
Ravi.

Unable to locate run-time engine

Hello all!
Sometimes we must upgrade some of our customer machines. Those machines where developed in Labview, but they only have the executable and the run-time.
Several times I have the a problem, we upgrade the Labview version on our PC's and we can not send them only the executable. We must make a new installer with the new version and install all that.
There is the possibility to create an EXE to a previous Labview run-time version?
Thanks in advance, best regards,
Paulo Carmo

Hi Paulo,
Thank you for posting.
You are only able to create .EXE for and with the version of LabVIEW you build it. You can choose the version of run-time.
For example, if you have LV 2010 and you want to deploy your application on Windows 2000 (not compatible with LV run-time 2010), you have to create your EXE with at least LV 2009 SP1, and the run-time version will be the same as LV.
I advise you to follow this link to know the compatibility between LabVIEW (and the run-time) and Windows : here.
Regards,
Romain P.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

Deux run time différents pour deux applications différentes sur un PC

Bonjour,
Je suis actuellement en stage et je possède la version 2010 étudiante de Labview sur mon protable. Mon centre de recherche possède également la version complète 2010. Je cherche à créer un exécutable dans cette version pour qu'il soit exécuter sous un autre PC qui possède un run-time de la version 5.1 et 6.0. Je voudrais savoir si je peux installer le run-time version 2010 sur ce PC pour que toutes les applications puissent fonctionner normalement ( et en même temps) ou si simplement les applications de version 5.1 et 6.0 utilisent leur propre run-time indépendamment du fait que j'utilise une autre application nécessitant le run-time 2010.
Prévenez-moi s'il vous plait si je n'ai pas été suffisamment clair.
Merci pour votre aide d'avance.
Olivier.

Bonjour
chaque runtime peut s'installer indépandement l'un des autres.
Le runtime Labview 2010 ne devrait pas perturber les autres.
Par contre , attention : avec une appliccation il n'y a pas que le run time labview mais aussi (et surtout) les runtime des autres composants qui sont souvent moyée dans le runtime.
fait ne particulier allusion à DataSocket, daq, daqmx, mathlib, visa, max, ect...
Cela est d'autant plus complexe, que les versions 5 et 6 de LV ne faisait pas la différence.
Donc méfiance lors de la mise à jour des PCs.
Un conseil, faite un backup avec des outils commes Norton Ghost ou easeus todo backup. Si toutefois ils sont compatibles avec des machines faisant tourner du LV 5 et 6.
bon courrange !
EricC
Ingénieur d'Application / Développeur LabVIEW Certifié (CLD)
Application Engineer / LabVIEW Certified Developer (CLD)

Using full development system on customized test setup that normally uses run-time - How to do?

I have 8.2 Full Development System (2 copies as there are two of us who write code).
I develop testing systems, each on an individual computer, each customized with a custom built (by me) interface to test and measure perfomance of motors produced on the production line.
In order to modify the program and test it, I have to replace the production set-up computer with my developmental computer, make the changes (and check that they work) and then make the run-time version for the production computer. THEN switch computers. Since I have nearly a dozen different setups, I cannot just make two production test sets of each (one for development and one for production).
Is there an easier way?
Perhaps with HDD in a drawer? But then I'd have driver and version issues.
Is it possible to run the full development system remotely (from the production setup)?
What about a site-license?
Thanks,
Tim K

From the 8.2 Release Notes:
Single-Seat and Multi-Seat Licensing
LabVIEW supports both single-seat and multi-seat licenses. Single-seat
licensing is the use of LabVIEW on up to three computers but by only one
user. Multi-seat, or volume, licensing is the use of LabVIEW on several
computers or by several users. Each seat using LabVIEW must have a valid
license from a license server. Refer to the National Instruments Web site at
ni.com/license for more information.
You are permitted to install LabVIEW on the the pc with the hardware, do the changes and debug, and re-build the app for production.

I'm running Pages version 5.2 on a Desktop Mac version 10.9.2. with the Pages app open how do I use the Time Machine to go back five hours to see the work?

I'm running Pages version 5.2 on a Desktop Mac version 10.9.2. With the Pages app open how do I use the Time Machine to go back five hours to see my page? Can I access Time Machine within an app like Pages? How do I enter Time Machine within the application? It always takes me to the Finder. I apolgise for the mumbo jumbo. I simply do not know how to use Time Machine. It makes sense when I follow the Tutorial but then I lose it.

OK. You've kind of skipped over the reason why you want to go back five hours, but my assumption would be that you've made changes to a Pages file that you want to revert.
There are two ways to tackle this. From Pages itself, open the current version of your document, and from the File menu, click Revert To, and Browse All Versions. You'll then be in the Time Machine interface for that file, and can browse back to the version you want.
Or, outside of Pages, you can select the file (or the folder it was originally in, if you've since deleted it) and enter Time Machine from the TM menu (it sounds like you've already tried this?)
best
Matt

Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC? I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
Thanks!
Solved!
Go to Solution.

I'm guessing this is a bug that NI needs to fix. I see no reason you shouldn't be able to install the run-time engine of an older version. I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine. There are some command line switches for NI installers as mentioned here:
http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
I wonder if there is a force install option.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

How to create a variant to a report from another program at run time

Hi experts,
when i am using FM : /OSP/REPORT_CREATE_VARIANT to create a report variant from a program then i am getting an error 'For object /OSP/ERPNR , number range interval 01 does not exist ', how should i avoid it or can any one help me out to create a report variant from another program at run time with the results of the program.so that i can execute the report from here with this variant

If i understand you,
- You can use a FM like [RS_CREATE_VARIANT|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=rs_create_variant+&adv=false&sortby=cm_rnd_rankvalue] to create a variant and then use it in the [SUBMIT|http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/096d67543b11d1898e0000e8322d00/frameset.htm] statement USING SELECTION-SET.
- But you may also use SUBMIT with WITH parameters which doesnt require variant creation and with much less programming efforts.
- You can mix the two solutions also.
So what is you actual requirement, also look at some documentation like [ Scheduling a Job: Full-Control Method|http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/096ce5543b11d1898e0000e8322d00/frameset.htm]
Regards

JRE run-time arguments in deployment.properties file all versions of PlugIn

G'day,
A user can specify the run-time arguments for the JRE via the Java Plug-In's control panel. This results in a (property, value) pair being written to the user's deployment.properties file. I'm trying to compile a list of the property names used by various versions of the Plug-In. Here's what I have so far:
1.4.2_*
javaplugin.jre.params
i.e. one set of run-time arguments for all JREs known to the plug-in.
1.5.0_*
deployment.javapi.jre.V.args
where V is a JRE version number, e.g. 1.5.0_16, i.e. custom run-time arguments for all JREs known to the plug-in.
1.6.0_00 .. _07 ("classic")
deployment.javapi.jre.V.args
where V is a JRE version number, e.g. 1.6.0_07, i.e. custom run-time arguments for all JREs known to the plug-in.
1.6.0_10 .. ("next generation")
deployment.javaws.jre.N.args
where N is an index into the list of JREs known to the plug-in, i.e. custom run-time arguments for all JREs known to the plug-in.
These have been determined by sampling a couple of updates for each of the X.Y.Z versions listed above, i.e. not an exhaustive test by any means. Therefore, if you could expand on this, esp. pre-1.4.2, post 1.6.0, assuming they use the same deployment.properties mechanism, it'd be appreciated.
Thanks,
Chris.

Read U area of process.
You can get argument list from U area.
Though U area is not kerenl, you may be careful to read data using copyin() functions.
Good luck,
Chun-Mok Chung

Variant config : Run time Version

Similar Messages

Maybe you are looking for