When opening PT Assembler, Windows tries & fails to open NI Run-Time engine

I am using PT Assembler, a front-end for the Panorama Tools software bundle, to stitch microscope images taken by LabVIEW using the QCam Suite. Whenever I attempt to open PT Assembler, Windows informs me that it needs to configure the NI LabVIEW Run-Time Engine 7.1.1, which it cannot as it is not installed. After cancelling the configuration 4-5 times, my program opens and runs without errors.
PT Assembler has absolutely nothing to do with with NI or Labview as far as I can determine, so why does Windows try to open it with the run-time engine? I attempted to install the 7.1.1 engine from ni.com but was informed that it was unavailable. Is there any way I can keep Windows from attempting to use the engine? I could install a later version of the engine and hope it works, but I am a bit leery about how it might affect my program.

Hi rhazelton,
If this program hasn't been created in LabVIEW, then I'm not sure why it would be doing this.. However, you should be able to download the 7.1.1 run-time here. Give it a try and see what happens!
Regards,
Brian A.
National Instruments
Applications Engineer

Similar Messages

Open API App (Windows based) fails to open FMB on Unix file system

My Open API, Windows based app, can successfully open and 'get' properties of FMBs stored in the Windows file system. However, it fails to load the FMB when the FMB resides on a networked Unix server. The same FMBs on Unix can be opened by the Windows based FormBuilder (over the network). I can copy the FMB down to Windows and without re-compiling the FMB, my Open API app can 'load' the FMB and 'get' all the properties. What suggestions can you give for debugging / resolving this? I need to be able to 'Load' the FMBs (through the Open API), that reside in the Unix file system, from Windows.
JJ

Generally, this is why we will tell you that accessing net shares is not supported and in places where it might even be supported, we would still suggest that it is not recommended. Accessing via net shares (especially through Windows) is often problematic. There are various performance and connectivity issues that, unfortunately fool you into believing that the product you are using is flawed when the problem is really a connection issue with the share.
In your case, because you are not exactly using an Oracle product (initially), Oracle can't offer much anyway, but I would recommend against using shares whenever possible. If you need to access a file, copy it locally first, perform whatever task on it, then return the updated file to its origin. This method protects you from things like net failure and instability as well as the performance issues associated with accessing files remotely.

Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly). I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine. Is this a bug in the installer, or is there something else I need?

LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular). However, many people have had success installing to various flavors of Ubuntu. You can search these forums using the key Ubuntu and find the problems they had and how they solved them. If you cannot find an answer to your problem, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

NI Vision Run-Time Engine 8.2 - Error user is now getting when attempting install of built software

I've built an installer for an application using LabVIEW 8.2 and Vision8.2. I have sent this installer to someone for 6 months and they have had no problems completing the install.
Now the last time that I sent the installer, the user is getting the attached error during install.
"NI Vision Run-Time Engine 8.2
Error: Another installer or uninstaller is running.
Finish that installer or uninstaller and try again."
When the user clicks OK to this error, the user is then told to restart or finish uninstall. Since we do not know what uninstall is being asked for, the user restarted the computer and attempted running the software - to which he was prompted for LVWA.dll file and he did not know what to do from there.
I gave the installer to a second beta-tester - the same thing occurred.
The only thing 'of significance' that has changed in my software that I can think of that is Vision related is the inclusion in the software of the ability to read/write .TIF files. I have no clue whether that might have anything to do with the error.
Any help is appreciated. NI - I can post the installer ZIP to your ftp site if you want.
Sincerely,
Don
Attachments:
error.jpg ‏30 KB

Hello Don,
Have you tried uninstalling the previous Vision run-time
engine on the deployed computer before running the new installer? You
might also want to try running the Vision RTE separately from the installer to
see if you are able to manually run it on the target. Here is a document which explains the
procedure for both manually installing the RTE as well as how to include it in
the LabVIEW installer:How do I
Deploy LabVIEW 8.0 and 8.20 Applications with NI Vision 8.0 and 8.2?
I also found
a Knowledge Base that may be helpful addressing the error you mention in your
first post. I hope this helps.
How Do I
Correct the "Another Installer Is Already Running" Error Message?
Regards,
Vu D

Windows setup failed to open distribution share d:\ds when trying to run the windows embedded standard 7 image builder wizard

The wizard fails with: windows setup failed to open distribution share d:\ds (..etc)
I am running it from a USB disk that has over 4GB free space, all the other files and folders are shown in the DS folder ok
Please advise what i should do here?
Does the drive need to be a certain format? its FAT32 at the moment (not NTFS, so no security)
I have tried copying the contents of the wes7-ibw iso to another USB drive and the same thing happens.

I solved it : setup failed to open distribution share d:\ds ... error 0x8007000 /0x8007003
the cause I assume there is something strange about the CD file format on that disk.
I first created a bootable usb (diskpart) then as i didnt had software to do it all in once
i converted the original CD to iso, and used other software to burn an ISO as bootable CD on usb.
( i used iso to usb for that its free )
i ve tried it with the usb as fat32 and (using convert converted fat32 to NTFS (stayed bootable).
I even tried different hard disks no difference same error.
Each time same error.
Then in the end i noticed the folder content of the DS folder on USB and CD wasn't equally.
So then i copied directories one by one over their existing USB counterparts
After that it worked...
Maybe the CD isnt folowing some CDrom standards, or uses a rarely used format; not wel recognized by common CDrom tools

I am having problems when i have minimized windows and try to open a new window it will open all minimized windows along with the new window. It just changed when mozzilla updated. It did not do this before the update.

I am having problems when i have minimized windows and try to open a new window it will open all minimized windows along with the new window. It just changed when mozzilla updated. It did not do this before the update. Before the update if i had minimized windows they would stay minimized when i opened a new window. Please help ,I would guess it is just a setting somewhere but i cannot figure out where the setting is. Thanks jason

This issue can be caused by the ASK.com Toolbar.
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

I can't play movie downloads. I've tried opening them with Windows Media Player, i-tunes, and Quick time but they don't work.

I can't play i-tunes downloaded movies. I've tried opening them with Windows Media Player, i-tunes, and quick time. Nothing works.

If after you download the movie, you navigate away and do something else with your Apple TV the content you have downloaded will be overwritten and you'll need to download it again. It's a pain in the neck for many who have slow downloads but it's something that comes with using volatile memory rather than a hard drive for storage.
Perhaps you're not doing this, but I thought it worth mentioning.

If Firefox is set as the default browser, and any application attempts to open a new window, this fails and I get the error "Firefox is already running..."

Here is what I am running:
Microsoft Windows 7, Service Pack 1, Fully updated to 4/10/2012
Fresh Install of Firefox 11. No add-ons enabled as a result of troubleshooting.
I am a user with administrator rights
UAS is disabled.
To begin, this has been going on Since Firefox 10 or so. A few months now.
I am able to open Firefox. My add-ons worked (ABP, Flashblock, ABP Element Hiding Helper, IETAB2, Downthemall, Greasemonkey, 4chan extension) had no problems. Firefox is set and has been set for the last two years as my default web browser.
However Since approximately Firefox 10 or so, maybe before that, If I have a Firefox session open, and any other application attempts to open a session in a new window, I get the Firefox is already running, but not responding error."
I attempted to follow troubleshooting advice already posted (look for parent.lock files left behind [none present], multiple sessionstore.js files [none present], create a new user profile, attempted to clear out the "read-only" permission in windows 7, however as soon as it is cleared, the read only permission returns.)
As a last resort, I deleted the Firefox folder, the %APPDATA%/Mozilla directory in its entirety, then utilized CCleaner to remove any and all references to Firefox in the windows registry, then did a full re-install, no extensions installed right now.
I checked preferences and have the option "open new windows in a new tab" checked off. The problem persists regardless if this option is checked on or off. This problem persists in or out of safe mode, even with the brand new install.
Test Cases:
All cases:
Firefox is selected as the default browser for windows 7
Case 1: Open a firefox session. Utilize any other program that attempts to open a link to their website in a new browser window or new browser session. Experience "Firefox is already running" error
Case 2: Open a firefox session. Right click on Firefox on the task bar. Select "open in new window". Experience "Firefox is already running" error
Case 3: Open a firefox session. Select the Firefox Menu > New tab > New Window. A new window will actually open.
This is the only method of opening a new window in the same browser session or profile that actually works on my system. Attempting to open a browser session from the task bar "open new window dialog" or opening a new window while a current window/session is running will not open firefox in a new window or a new tab in the current session. The "Firefox is already running, but is not responding" error will occur every time.

Cor-el's suggestion resolved my problem. Apparently the MOZ_NO_REMOTE variable was set to 1 on my system variables. I never made it, and really have no idea how it got there, but deleting this variable and restarting firefox has resolved the issue. Thanks Cor-el!
Marking case: Solved
Solution: Verify the MOZ_NO_REMOTE variable is NOT set to 1. This can be achieved by simply deleting this variable.

Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
Attachments:
windows.jpg ‏26 KB

Hi,
There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
Zvezdana S.
NAtional Instruments

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs. This happens near the beginning. Is there a compatibility issue? The window does not have any error messages. It says: "Updating System, The features you selected are currently being installed." The progress indicator blinks periodically, but does not move forward. Please help. Thanks!

I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE

What's going on here? I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer. When I open VB6, I always get what looks like a Windows Installer error:
First, it asked me for the location of "lvruntimeeng.msi", which I located for it. The next progress-window says:
NI LabVIEW Run-Time Engine 7.11
Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
Finally it fails with this error-message window:
NI LabVIEW Run-Time Engine 7.11
Error 1334. The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
[OK]
The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay. What can I do to prevent this error?
Message Edited by citizenDAK on 04-23-2008 01:34 PM

Yes it occurrs every time I launch VB6.
For a long time now, at least many months. It's not every day that I need to open good old VB6. I was hoping it'd just 'go away' but it hasn't.
I don't know what changes lead up to it. LOTS of things have been updated, security-patched, etc... (It is XP.) I've even un-installed the runtime, then re-installed it when I kept getting the same prompt. Don't have any idea why, I was hoping you could tell me from the specific file named in the error. (Google didn't find it for me, and neither did searching ni.com)
p.s., Sorry I left out a decimal and copy/pasted it several times... should've said "NI LabVIEW Run-Time Engine 7.1.1"

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

When opening PT Assembler, Windows tries & fails to open NI Run-Time engine

Similar Messages

Maybe you are looking for