Looking for Vision 7.1.1 runtime engine

Hi,
I have a vision application that has always been used on the development machine. Now I need to deploy it.
It's written in LabVIEW 7.1.1 maintainence release, with Vision development 7.1.1. I can't go newer on the development environment as the target machine is Win NT.
The application supports a linescan camera - allows adjustment, captures image, saves to disk.
I have a deployment license and deployment engine CD , version 7.0, so I need an update to 7.1.1.
I can't find it anywhere. Downloads available on NI.com jump from 7.0.1 to 8.0
I have searched the forumes for the answer without luck. Does anyone have any pointers?
Cheers.
Bandit

Hi,
just to tidy this up for others on the forum,
The Vision Run Time Engine for 7.1.1 was part of the Vision Deployment Engine and was a purchasable part, so not available for download.
If you require this, then we need to check with your internal sales engineer with regards to entitlement etc, and then we can burn the cd.
For each deployment of your Vision applications that uses this Run Time Engine you need to purchase a license, as the Run Time Engine for Vision is not freely distributable in the same was as the LabVIEW one is.
We've already spoken to "Bandit" and resolved this so a CD is on the way.
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Similar Messages

After reboot, Labview looks for RTE 7.1 (RTE 8.2 installed)

I started developing software using Labview 7.1. Mid way complete I decided to switch to Labview 8.2. Now everytime I reboot, I get a Windows installer asking for the Labview 7.1 runtime engine. I re-installed Labview 7.1 but I keep getting the installer asking for this runtime engine. Eventually after clicking cancel about 10 times, it finds an engine (not sure which one) and runs the exe. This exe is on a PC running Windows XP in a factory, controlling a machine. I need to fix this problem for the customer to be happy. Is it possible that one of the VIs I used in 7.1 is now in 8.2's code but needs the old engine to work? How can I fix this problem? Note that I'm not using any VIs in 8.2 that don't already exist in 7.1. (stupid mistake to use 8.2).
Hopefully someone can help me.
Matt Koebel
Technologist

Apparently Windows something got messed-up during the installation process. If it were me I think my first step would be to backup the source code and uninstall all National Instruments software. After the uninstall, reboot and run a registry cleaner like CCleaner (free download) to remove any remnants of old installations. Note that before it cleans up issues that it finds in your registry it will ask you if you want to back up the things that its removing - say "Yes". If necessary, run the scan repeatedly until it reports that it found no additional issues.
Finally, reboot again you should not get the message.
Now reinstall all the NI software. If the latest version of your code is in LV8.2 just install that (actually 8.2.1).
Oh yes, the most important thing: Be sure to do all of this from an administrator account.
Keep us posted on how you are getting on.
Mike...
PS: Looking back on what I wrote it occurs to me that perhaps it might be worth a try to download CCleaner and running it before you do the uninstall. It's probably a long shot, but it's clean-up process might fix whatever is causing the trouble. If it works you have saved a bunch of time. If it doesn't you haven't lost much.
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Distribution Builder looking for product installers

I'm having a problem building a distribution.
The builder is asking for product installers that were part of a different distribution and no longer
on the machine. Its looking for the NI-DAQmx Core Runtime 9.6.2 and the Ni-VISA Runtime 5.3 installers.
How do I remove the dependency of the previous distribution. In the Drivers & Components tab of the Installer
the change Source button is disabled how do enable it.
I'm running CVI 2012 on an XP machine. I appreciate any help .

Hello chetp
This might help:
http://digital.ni.com/public.nsf/allkb/E2D8B36AE74458C8862573A8005C4708?OpenDocument
Regards
Mart G

App is looking for old version of runtime engine

I have an app that came with a datalogger that was (presumably) written in Labview 7.X. Whe it runs, it wants me to point it to lvruntimeeng 7.1.1.
I have LV 8.2 already on the machine, and I can't find the file it's looking for.
I really need to use this datalogger.
Any ideas?

From what I can tell, the KB article is about "Executable Version (7.1.1) Doesn't Match Resource File (7.1) Check Your Configuration", while this thread is about the inability to install the 7.1.1 runtime if 8.2 is already installed on the same machine.
I don't think the KB applies in this case. Did you post the wrong link?
LabVIEW Champion . Do more with less code and in less time .

Why is the Microsoft Office Access Database Engine data source looking for a workgroup information file?

While trying to import to MSSQL2012 from SSDT using the wizard from an Access 2013 DB (.accdb) which is password protected, I get the following error with the username blank and the password field correctly populated:
Cannot start your application. The workgroup information file is missing or opened exclusively by another user. (MicrosoftOffice Access Database Engine)
But according to this link:
http://office.microsoft.com/en-us/access-help/what-happened-to-user-level-security-HA010342116.aspx
MSA10 and beyond shouldn't need workgroup information files, although it's not clear to me if they are
created/used or not.
I can point the wizard to some local version of system.mdw at Advanced -> All -> Jet OLEDB:System Database, and then the error becomes:
Not a valid account name or password. (Microsoft Office Access Database Engine)
for any username I can think of.
Questions:
1. Why does this data source insist on looking for a workgroup information file even though user-level security should be disabled?
2. Why does the Open dialog box for the Microsoft Access Database Engine have *.mdb as the only selectable filetype?
3. How can I get around these errors for an .accdb that is password protected?
Thanks!

Hi JordanPG,
To connect to Access 2007 or later database, we need the Microsoft ACE 12.0 OLE DB driver. SQL Server only installs the Microsoft Jet 4.0 OLE DB driver which can be used to connect to Access 2003 or earlier database. Besides, the Microsoft Jet 4.0 OLE DB
driver only has 32-bit version, but the Microsoft ACE 12.0 OLE DB driver has both 32-bit and 64-bit version. However, the 32-bit and 64-bit Microsoft ACE 12.0 OLE DB drivers cannot be installed on a single server.
According to your description, you can use the 64-bit SQL Server Import and Export Wizard to load data from the Access database, so the 64-bit Microsoft ACE 12.0 OLE DB driver is installed on your computer. Since the BIDS/SSDT is a 32-bit application, the
64-bit Microsoft ACE 12.0 OLE DB Provider is not visible in BIDS/SSDT. So, when you said that you select “Microsoft Access (Microsoft Access Database Engine)" in the SQL Server Import and Export Wizard (it is actually the 32-bit version) started by the SSDT,
I think it should be “Microsoft Access (Microsoft Jet Database Engine)”. Because the Microsoft Jet 4.0 OLE DB driver only supports Access 2003 or earlier format, it threw the error “Test connection failed because of an error in initializing provider. Unrecognized
database format 'C:\myDB.accdb'”.
In this situation, you have two approaches to avoid this issue:
Launch the SQL Server Import and Export Wizard (64-bit), and select “Save SSIS Package” to “File System” on the “Save and Run Package” page. Then, the package will be saved to a specified directory. After that, you can add this existing package to a SSIS
project. The status of the corresponding OLE DB Connection Manager should be Work Offline, or the OLE DB Source will throw an error about 32-bit driver if the Connection Manager is not in Work Offline status, you can ignore that and the package can run successfully
in SSDT as long as the project is set to run in 64-bit runtime mode.
However, for the SSDT 2012 integrated with Visual Studio 2012, the 64-bit runtime mode is disabled. In this situation, to run the package in SSDT, you have to uninstall the 64-bit Microsoft ACE 12.0 OLE DB drivers and install the 32-bit one. Here is the
download link:
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Regards,
Mike Yin
TechNet Community Support

Is there a .sld file for LabView runtime engine when creating Embedded XP image

I'm looking for a .sld file to aid inclusion of LabView runtime engine in my embedded XP image. Has anyone already written one?

Hi,
unfortunately, National Instruments doesn't have any sld files for embedded OS'es, however, please checkout the links from the Lookout discussion forum, where someone was trying to do something similar.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000AD5C0000&ECategory=Lookout
Although there's no definitive resolution to this thread, the person who answered has said he could be contacted.
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

The Distribution Kit Builder is Looking for the NI Variable Engine in an old distribution, cant find it and fails to build

I am unable to build a distribution kit because the builder appears to have saved a path to the NI Variable Engine which is not valid. I appear to have the NI Variable Engine installed. There are NI Variable Engine 2.5.0 .xml files loaded in on my computer (See attached for listing of drivers loaded). I do not seem to be able to break CVI's Link to my past installers for getting drivers. I've tried creating a new installer but had the same trouble.
I am running a 64 bit Laptop with Windows 7, building a 32 bit application, running CVI 2010.
Solved!
Go to Solution.
Attachments:
ATAHM Outline.ppt ‏61 KB

The default path is the path to whatever distribution installed NI Variable Engine on your machine. For example, if it was installed from a Driver Disk, the path would probably be D:\. However, from the images you originally posted, I can see that you were being prompted to provide the path to one of your earlier ATAHM distributions. It was looking for it at this path:
c:\Users\chill\Documents\Development\AATAS\ATAHM\distributions_ATAHM\ATAHM Oct 24 2011\
Do you still have that distribution? If you can point it to that distribuiton, you should be good.
Now back to the error you were seeing... Your version of that .NET manifest file matches (except for the version number) Revision A from the Knowledge Base, so you should try replacing it with Revision B (and rename it to NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml). Make sure you restart CVI after swapping the file. I would expect that to solve your problem. If it doesn't, you'll have to let me know what the new issue is, or if you're somehow still seeing the same error message.
Mert A.
National Instruments

Apps, civil and environmental any suggestions ? Thanks, Hello Folks I am currently looking for engineering apps, civil and environmental any suggestions ? Thanks

Hello folks I am currently looking for Apps for Civil and environmnetal engineering to help me at University and work any sugestions? Best wishes Bruno

How about "Truss Me!" ?
http://www.tuaw.com/2014/02/04/trussme-learning-a-bit-of-structural-engineering- while-having-f/

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Using LV2009 to produce EXEs for Runtime Engine 8.6

Hi,
I am currently running LabVIEW version 8.6. However, having purchased this less than a year ago, I think I am eligible to upgrade to v2009 for free.
At the moment, if I produce an EXE file using the Application Builder, my colleagues are able to run this on their machines using the LabVIEW Runtime Engine version 8.6.
If I upgrade to LabVIEW 2009, will all my colleagues who use the runtime engine also have to upgrade to the Runtime Engine 2009, or will I have the option to build an EXE file that is compatible with version 8.6 of the Runtime Engine.
Many Thanks,
Dan
Dan
CLD

There are no option for build "8.6" compatible application from LabVIEW 2009 (other than save for 8.6 and build in 8.6).
For LabVIEW 2009 - builded application you will need according version of the Run-Time Engine.
Important point, that Run-Time Engine version 2009 will not replace version 8.6. It means, if you have PC where Run-Time 8.6 installed, and after that on this PC you will install Run-Time 2009, then you can run both 8.6 and 2009 - builded applications.
Andrey.

Looking For Field Trial Customers to Test Audio & Video Using Cisco's Intercompany Media Engine (IME)

IntelePeer, Inc. (www.intelepeer.com) is a leading provider of on-demand cloud-based IP communications services, and is currently looking for a limited number of existing users of Cisco's CUBE, CUCM, or CME call processing systems to work with IntelePeer in testing our new hosted audio and video federation applications, including interworking with CUCM systems enabled with Cisco's Intercompany Media Engine (IME) platform. The specific supported Cisco call processing and audio/video specs mentioned above are as follows:
Call Processing:
Cisco Unified Border Element (CUBE) - preferred
Cisco Unified Communications Manager (CUCM) 6.X or higher
Cisco Unified CallManager Express (CUCME) 7.1 or higher
Audio Codecs Supported:
G.722
G.711
Video Codecs Supported:
H.264
H.263
IntelePeer will provide those willing to participate with a no cost SIP trunk, as well as free IME based voice and video usage during the trial. The specific details of the requested test case scenarios, as well as timeframes for testing, will be outlined in detail upon being approved for participation in the field trial program.
Those willing to participate are urged to notify us immediately, via response to this form.
Thank you in advance for your time and consideration. We very much look forward to working with you during this field trial.
Sincerely,
IntelePeer, Inc.

Hello there and yes I would be interested in learning more about your testing program. How can I share a little bit about my environment and we can see I'd we would be a good candidate. Please feel free to reach me at [email protected] or [email protected]
Sent from Cisco Technical Support iPhone App

Looking For Field Trial Customers to Test Audio & Video Using Cisco's Intercompany Media Engine

IntelePeer, Inc. (www.intelepeer.com) is a leading provider of on-demand cloud-based IP communications services, and is currently looking for a limited number of existing users of Cisco's CUBE, CUCM, or CME call processing systems to work with IntelePeer in testing our new hosted audio and video federation applications, including interworking with CUCM systems enabled with Cisco's Intercompany Media Engine (IME) platform. The specific supported Cisco call processing and audio/video specs mentioned above are as follows:
Call Processing:
Cisco Unified Border Element (CUBE) - preferred
Cisco Unified Communications Manager (CUCM) 6.X or higher
Cisco Unified CallManager Express (CUCME) 7.1 or higher
Audio Codecs Supported:
G.722
G.711
Video Codecs Supported:
H.264
H.263
IntelePeer will provide those willing to participate with a no cost SIP trunk, as well as free IME based voice and video usage during the trial. The specific details of the requested test case scenarios, as well as timeframes for testing, will be outlined in detail upon being approved for participation in the field trial program.
Those willing to participate are urged to notify us immediately, via response to this form.
Thank you in advance for your time and consideration. We very much look forward to working with you during this field trial.
Sincerely,
IntelePeer, Inc.

Hi, Stephen.
Yes, we would be more than happy to speak with you about becoming a test participant for IME. If you could please email me with your contact information, I will get in touch to set up a meeting to discuss.
Please advise.
Thanks much.
Regards,
Scott
Scott Davidson
Product Manager
http://www.voex.com/index.php
2300 15th Street
Suite 100
Denver, CO 80202
303.222-0090 Office
303-818-9183 Mobile
[email protected]

Small runtime engine for newer labview versions?

A few times in the past I have created simple LabVIEW standalone executibles. I did this in 8.6 and used the runtime engine minimal installer instead of the full version. This resulted in an installation package size of 30-35 Meg.
I agin need to create a simple executible but have not seen a minimum runtime installer for any LabVIEW version since 8.6
Are there any minimal runtimes for other versions?
The default 2014 runtime is 264 Meg!!! It is hard to explain to a customer why a simple "Hello World" program requires a 200+ Meg download.
Solved!
Go to Solution.

Jack Dunaway has documented a way of segmenting the run time engine, basically only including the pieces of it you need.
https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-run-time-engine
And here is an idea exchange item on it.
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Segment-the-LabVIEW-Run-Time-Engine-RTE-to-ONLY-Necess...
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.

Looking for Vision 7.1.1 runtime engine

Similar Messages

Maybe you are looking for