Upgrading from LabVIEW 6.1 to 7.1, get a MS C++ Runtime Error

After upgrading from LabVIeW 6.1 to 7.1, I get a Microsoft Visual C++ Runtime Error
It states:
Runtime Error!
Program:...ogram Files\National Instruments\LabVIEW 7.1\LabVIEW.exe
abnormal program termination
I am using Windows NT, ver 4.0 SP 6.

I assume you get this error message everytime LabVIEW starts. This is not normal behavior. It is not even a common error. Have you tried reinstalling?

Similar Messages

  • Problems with IMAQ Vision after upgrading from Labview 6i to Labview 6.1

    Hi,
    We just upgraded from Labview 6i to 6.1.To do this,we uninstalled the 6i version as was suggested by NI and then installed the 6.1 version.Later when we tried to run the old vi's written using Imaq vision, we ran into different problems.Has anyone experienced any similar problems with IMaq vision after upgrading?If so please help me solve this issue.
    Thanx
    deepak

    What kind of problems?
    I would strongly suggest that you uninstall IMAQ (all elements) and reinstall them. They register with Windows, probably docked to 6i, and also must be recompiled, which I believe is done in installation.
    This is your best bet.
    If you still have problems, contact NI and ni.com/ask and start a support inquiry.

  • Good day I need the solution to the problem presented my iphone with ios upgrade from 7 to access any app, I get a message that says "log on to itunes to receive notifications"

    Good day I need the solution to the problem presented my iphone with ios upgrade from 7 to access any app, I get a message that says "log on to itunes to receive notifications"

    After the iOS 7.0.2 update words with friends is not working for me either. When I attempt to open the app it just closes itself after a few seconds of being open. This happens every time I attempt to open it.

  • After trying to upgrade from 4.3.4 to 5.0 stuck on recovry and giving error every time im trying to restore

    after trying to upgrade from 4.3.4 to 5.0 stuck on recovry and giving error every time im trying to restore
    what to do ?
    tried tiny umberlla dost do anything

    What OS is on the Install/Restore DVD that came wit your G5? If Tiger 10.4.x, you will need a black, retail Leopard install DVD. There is no free download of Leopard, only free updates once you have installed the base OS.
    First use your Mac's Install/Restore DVD to install an OS & apps. Then upgrade the OS.
    Leopard is no longer available at the Apple Store *but may be available by calling Apple Phone Sales @ 1-800-MY-APPLE (1-800-692-7753)*.
    Installing Mac OS X 10.5 Leopard
    http://support.apple.com/kb/HT1544
    Mac OS X 10.5 Leopard Installation and Setup Guide
    http://manuals.info.apple.com/en/leopard_install-setup.pdf
    After you install the base 10.5, download & install the 10.5.8 combo update at http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update
     Cheers, Tom

  • I have an IAMc 4.1 with intel core duo.  Upgraded from tiger to snow leopard but cannot get safari to run in 64 bit.  Is this because my older IMac won't support 64 bit?

    I have an IAMc 4.1 with intel core duo.  Upgraded from tiger to snow leopard but cannot get safari to run in 64 bit.  Is this because my older IMac won't support 64 bit?

    Hi,
    the Intel Core Duo processor is a 32-bit only processor and not capable of 64-bit.
    Only the Core 2 Duo and later processors are capable of 64-bit.
    Sorry
    Stefan

  • Can not access serial port while upgrading from LabVIEW 6.1 to 7.0

    Hi,
    I built an application under LabVIEW 6.0.2. few years ago. This application uses LabVIEW serial features. When I upgraded to LabVIEW 6.1, my application was still working correctly.
    Today, I upgraded to LabVIEW 7.0, mass compile all VIs and now my application can not communicate with my peripheral !!!
    The program is sending the command to the peripheral. The peripheral answers but LabVIEW serial driver does not see any datas on buffer even if datas are available ... "Bytes At serial port.vi" always returns 0. I am sure that datas are available, using a COM port psy.
    Does anyone has an idea?
    I saw a lot of solutions in the forum, but I would like to know the best solution with minimum work, te
    st, and so on ... on my program.
    Regards,
    Pascal.

    Hi Pascal,
    Which is your version of NI-VISA?
    Please see the link bellow :
    http://digital.ni.com/manuals.nsf/websearch/E8D86CD680B0753D86256D2C005D8EA0
    The first test to be made is to test the communication with your serial port using MAX (Measurement and Automation Explorer) :
    Open MAX, Go to "Devices and Interfaces", then "Ports", select COM1 (or ASRL1::INSTR). Right clic on it and select "Open VISA Session" the go the "Basic I/O" then Write data, execute, Read data, execute.
    Be sure that the communication is OK. Be sure that you use the same Alias existing in MAX in your LabVIEW program.
    Now, if all is OK, try to use Serial communication examples existing in LabVIEW Help>>Examples Finder. These examples use NI-VISA VIs.
    If all above is OK and you
    still have the same problem, try to follow these instructions :
    "In order to use the old Serial Compatibility VIs in LabVIEW 7.x, you must copy the following files from a previous version of LabVIEW to the LabVIEW 7.x directory:
    Replace the serial.llb in LabVIEW 7.x with the serial.llb from a previous version of LabVIEW. This file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
    Replace the _sersup.llb file in LabVIEW 7.x with the _sersup.llb from a previous version of LabVIEW. In LabVIEW 6i and 6.1 this file is located in C:\Program Files\National Instruments\LabVIEW\vi.lib\platform. In LabVIEW 7.x (and 5.x) this file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
    Copy the file serpdrv to the C:\Program Files\National Instruments\LabVIEW 7.x directory. This file is not installed with LabVIEW 7.x, so it only needs to be copied from a previous version of LabVIEW, not replaced."
    I hope that my answer will help you.
    Sa
    naa T
    National Instruments

  • Has anyone encountered a Microsoft Visual C++ Runtime error in Windows 2000 when upgrading from Labview 6.0i to 6.0.2?

    When I try to upgrade Labview 6.0i to 6.0.2 by running the setup.exe file I downloaded from the NI site, I immediately get a dialog box with the header "Microsoft Visual C++ Runtime Library" and it says "Runtime Error! Program: C:\setup.exe abnormal program termination."
    I'm running Windows 2000, but I've successfully installed it on another computer with the same setup. I'm guess some of the DLL files in system32 has been corrupted or mismatched versions. But I don't know which one...
    Anyone know what this means?

    Hello,
    You can probably solve this problem by going to Start >> Run and typing the following:
    Regsvr32 \msi.dll
    Where is the folder where the msi.dll file resides on your computer (you can use Start >> Find to find the exact location). Once you do this, the installation of the 6.0.2 update should work properly.
    Please let me know if you continue to have any problems. Thanks for your patience on this issue, and have a pleasant day.
    Sincerely,
    Darren Nattinger
    Applications Engineer
    National Instruments
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Upgrading from LabVIEW 4

    I'm currently upgrading an application from LabVIEW 4 to 2010 by way of 7.1.  After opening the VIs in 7.1, I have several orphaned local variables and no idea what they might have been attached to.
    Does anyone know how local variable behavior might have changed between 4 and 7.1 to cause this?  I'm probably going to load 4 in a VM to check it out but thought this might be a known artifact that pops up when doing these types of upgrades.
    Thanks!

    as part of the evolution, so has the desire to use wires instead of Locals...  (I hear shouts already )
    If you know the control that it came from, is it within a section of the code where a wire would do the trick?  Or if in a Loop, a nice Shift Register will carry the data.  If within a Stacked Sequence Structure, then you may have to flatten it first..  Then clean up the code..

  • What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

    OK.  Just to be clear.  I am a complete newb to ANYTHING LabVIEW or LabWindows related.  I am a programmer, but I have never used any version ever.  That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date.  The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1.  You can just imagine how ancient this is by today's standard.
    Have I set the stage properly?  I hope so.  Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
    Now here is what I "think" I know about what is required.  Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle.  I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
    Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.  
    What exactly do I need to zip up and what can I leave out? 
    Are there LabVIEW vi and llb files in a "project" that are not needed? 
    Are there any setup/configuration/project specific files I need to include? 
    Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
    Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date.  Is there any way I can send my files to a specific NI guru via email instead of just posting them?
    Solved!
    Go to Solution.

    So if I understand you correctly,  all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
    Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this?  Once done, LabVIEW 2012 will then allow me to open them and do what I need to do?  Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
    When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files?  Based on what is installed on that NT v4.0 system, we have the following items installed:
    NI VISA
    NI ComponentWorks 3D Graph
    NI DataSocket
    NI LabVIEW 5.1.1 Advanced Analysis Library
    NI LabVIEW RTE 5.1.1
    NI LabVIEW v5.1.1
    NI Measurement and Auto Explorer 1.1
    NI-488 2.1.60
    NI-DAQ 6.6
    NI-PAL 1.3.110
    NI-Reports
    NI-VXI/VISA
    You mention DAQ.  Our program uses NI DAQ v6.6 now.  I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now? 
    Thanks for your help so far.  If we had a support contract in place, this wouldn't be an issue.  However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest.  However, I am specifically not allowed to just place the files on a public forum for all to see.  It just isn't done.  We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.   
    I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself.    Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

  • Upgrade from LabView 5.0 to 5.0.1

    I´m currently using LabView 5.0. I have some problems using GPIB and asynchronous access calls. These issues are solved in Version 5.0.1.
    Now, how can I upgrade to Version 5.0.1? I seems that there is no way to download a corresponding patch from the NI website..?
    Thanx.

    Hello,
    As I recall, the 5.0.1 update was not available as a web download because it was too large. I believe you must contact NI in order to get the 5.0.1 update CD sent to you, if it is still available.
    Might I recommend upgrading to LabVIEW 7.0? I first started using LabVIEW with version 5.0.1 (back in January 99), and looking back, I feel like I was programming with an abacus, what with all the great new features introduced in LabVIEW since then (my favorite probably being the Event Structure). Of course, I am a bit biased, since I work for NI...
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • What issues are there in upgrading from LabVIEW 4.0 up to LabVIEW 6.1?

    I am "inheriting" a LabVIEW 4.0 application that is running on an old (133MHz) Pentium PC with the Windows95 OS. I would like to upgrade the PC to a more recent CPU running Windows2000. I also want to upgrade LabVIEW to version 6.1. Are there any issues in performing the LabVIEW upgrade? Will I need to rework most of the application or is the transition from LabVIEW 4.0 to 6.1 fairly painless and transparent?
    Any help is appreciated. I've never been through a LabVIEW upgrade before and am treading in uncharted water.
    Thanks.

    Boy, it seems I can't stick my head above water without this topic coming up. I've had thr exact same upgrade question come up on two different contracts--in the past week!
    In any case, the code itself should come across without major problems, unless you are using CINs. The only real trouble I'v had are with things like serial I/O as the drivers have changed dramatically over the years.
    Now the code that you translate will be (by comparison) very inefficient thanks to the makor enhancements that have taken place over the last two major revisions.
    For the most part, I would have to vote for "fairly painless".
    Mike...
    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

  • Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installati​on package for Run-Time Engine 7.0

    I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit).  The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading.  I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013.  Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0.  If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
    I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected).  How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0?  Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    Are you running your VI from a Project?  If so, you can look at Dependencies and get an idea what "dependent" VIs you might have.  There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
    If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it.  If all of your relevant VIs are in a single folder, add the entire folder.  Now look in Dependencies.
    BS
    Yes I am running the VI from within a LV Project.  After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
    1.  Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
    2.  Restart the PC
    3.  Open the project, close the project choosing to "save all"
    4.  Restart the PC
    5.  Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
    6.  Restart the PC
    7.  Open the project, close the project choosing to "save all"
    8.  Open the project and run the VI.  No more messages about LabVIEW trying to find Run-Time Engine 7.0.

  • UDP Error when upgrading from Labview 8.6 to Labview 2009

    I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

    How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

  • Is there anything in particlar that I need other than the installati​on disk when upgrading from Labview 8 to 2010

    I have a Labview program that ran fine when I had Labview 8 installed. I recently upgraded to Labview 2010 and now my program will not work. When I run the program, none of my instruments read out and after about 5 seconds, the whole Labview program closes with no error messages. Can someone please help? I am a new Labview user and I don't really know how to troubleshoot this problem.

    If you have the installation disks that should be all you need. You will need a connection to the internet to register your product.
    Tim
    Johnson Controls
    Holland Michigan

  • I'm getting a cwinstr error after upgrading from labview 7.0 to labview 2010

    Hello
     recently upgraged a PC from Labview 7.0 pro to Labview 2010 pro. Now I can not open a calibration executable we been using for a xantrex xfr power supply (unfortunately I don't have source code). The only error I get is "cwinstr-can't load program" pop-up when trying to run the executable. The calibration SW will run on multiple platfroms, Win 95, Win 200 0 and XP and this is the first time getting this error. The calibration SW ran fine until the Labview 2010 install. My question is does LV 2010 change the registry files when loaded? Visa and MAX still run fine on this PC and were loaded when LV 7.0 was installled. I know the calibration SW uses the VISA drivers so this is what's confusing. i don't want to downgrade back to LV 7.0  unless I have to.
    Thanks

    Hello Tanya,
    I'm a little confused here. i only started having issues with the executable (it ran previously with the visa drivers from 7.0) after I loaded LV2010. After the install, the exectuable started giving me the cwinstr error. As best I can tell, this may be an activex issue, but since I only have the executable it hard to tell.
    My question id do i have to install both labview 7.0 in addition to labview 2010 on the pc. Fom the the readme file, it looks like Labview 2010 won't support certain vi's older than 8.0. But since I'm dealing with an exectuable only here, I thought I  should be able to open it at least.
    So instead of updating the visa drivers, should i re-install the old visa drivers (Ni-Max) for 7.0 instead? would this even work without removing LV2010.
    Thanks Again

Maybe you are looking for