Error 1612 when uninstalling LabVIEW 2009

Hello,
I'm trying to uninstall LabVIEW 2009 from an Acer tablet running Windows 7. Whenever I attempt to uninstall it though, I receive error 1612. Also, I'm not doing any weird methods of uninstalling; I'm following what the NI website says to do! When looking at previous topics that discussed this issue, none really seemed to come to a clear solution and I'm not sure yet if using a 3rd party program is the way to go. Have any new solutions to this problem appeared? I need to uninstall LabVIEW 2009 so I can install the 2014 version on it. That way I can move a program that I wrote on my personal laptop to my lab's tablet.
Any help is much appreciated!
Amy

You don't need to uninstall 2009 to install 2014. That said, it sounds like something is corrupt. As counter-intuitive as it may sound, you might try installing 2009 from the command prompt using the command: setup.exe /reinstall
That will force the installer to overwrite registry entries and the such. After that's complete, you should be able to uninstall.

Similar Messages

Error 43 when accessing LabVIEW 2009 write/read file functions through the web server functionality

Is there any way around to avoid Error 43, "Operation cancelled by user" when using Web server?
I am using the example VI:s RemotePanelMethods-Server.vi and RemotePanelMethods-Client.vi to acces the MainGUI.vi from my workstation to a lab computer. * LabVIEW 2009 is installed in both machines.
* MainGUI.vi is wired to the VI access list in the Server VI but it also contains a hierarchy below that isn't, is this a problem?
* Several functions in MainGUI calls file read and write operations
The problem ocurrs when file read/write operations with no preselected path are selected through the Client. The traditional popup window requesting the file to read or write is never seen in the Client, but only the Error 43.
Thanks in advance

See this

Error 1722 when uninstalling Labview run-time engine 7.1.1

I have been trying to uninstall all NI software so I can start off with a clean slate. I have been going to the control panel under add/remove programs to remove the NI stuff. Everything is gone except the Labview run-time engine 7.1.1. Everytime i try to remove it, i get teh 1722 error followed by the 1603 error. I've tried repairing it but I still get the same results when i try to remove it agian. I've also tried removing it with MSI Blast. This did not work either. I've gone through the registry and manually deleted anything related to NI and that still didn't work. Is there anything else I could try?
Thanks,
Nick

Hey Steve,
I have tried repairing it through the control panel.
I tried reinstalling just the run-time engine and it said it was already installed. So I reinstalled Labview 7.1 and repaired the 7.1.1 run-time engine through the control panel. Then I uninstalled everything. Thanks for all your help
Thanks again,
Nick
Message Edited by Nick_C on 03-12-2007 03:57 PM

DLL causes error when quiting LabVIEW 2009 on WIN7

Hello,
I have reduced the problem in my EXE application to the following attached code (see attachment). Somehow the DLL (To User32.dll) calls are creating a problem when quiting Labview 2009. The Application stays resident in the Windows taskbar and after a while an error appears about that there was a problem closing the application and that it can be reported to Microsoft if desired. Then a second error message appears before the application dissapears from the taskbar. If I remove the DLL:calls from the code then the problems dissapear.
Should I unload the DLL calls on a special manner before quiting LabVIEW?
Solved!
Go to Solution.
Attachments:
DLL-WIN7 problem.jpg ‏35 KB

Another potential problem not mentioned in that article is that you have included your user32.dll explicitedly in your built application. Doing that creates 200% for sure trouble as the kernel32.dll, user32.dll and others are always residently loaded into memory anyhow and mapped into the system memory section of any process. If you tell an application to load this DLL again by explicit name, you end up having two copies of it mapped in your process memory space and that will cause very weird problems.
To avoid this problem make sure the library name inside the Call Library Node only specifies the DLL name without any path information. Then close the dialog and save it. If you reopen the dialog it will show the full path but still save the name only until you make a modification in the path control at which time you can end up having a full path again.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

MSVCR90.DLL Error when start LabVIEW 2009

Hi,
   My LabVIEW 2009 failed to start. It pops up a window says fault module MSVCR90.DLL. I have reinstalled LabVIEW but the problem is still there. Anybody has similar problem before?
   Thanks for help!
   Tom

Hi,
unfortunately I can't do anything in c:\windows\... because I'm not an adnministrator. I have to wait at least a week before he comes back and maybe do it for me. There are 2 Versions of Microsoft Visual C+ installed on this comuter: 2008 and 2010. When LabView crashes and I select "Debug" there are 2 possibilities: 2008 and 2010. The msvcr90.dll which is marked as "failure" in an error message referres to Microsoft RunTime Engine 2008 (according to its properties).
I had made another experiment: set "runTime Engine" as VI server by Test Stand. In this case VIs are marked as "erroneus" (with a red button on the module panel). I have to reload every VI (the red button stays, but the picture is loaded), then start execution and ingnore the message, that there are errors. The sequence works OK. When I close TestStand I get an error message "TestStand doesn't work any more-> SeqEdit APPCRASH".
I think it shows, that RunTime Engine (I select the option "Recognize the version automatically") loads VIs in another way than LabView Development Environment does.

Error 1612 when installing Acrobat 9 update

I am running Acrobat 9.0 Pro on a Windows XP SP3 system. According to my control panel, the most recent update that has been installed is 9.3.2.
Every time I boot the system, I get a message saying that an Acrobat update is ready to be installed. When I attempt to install it, I receive an Error 1612 which says that the installation file is not present or not accessible.
I have attempted updating with the original installation disk in the DVD drive. Same result.
I have attempted uninstalling the 9.3.2 update or the basic program from the control panel. Same result. (In other words, I can't uninstall either of them, but get Error 1612 instead.)
I have attempted copying the .MSI file from the insallation disk to my hard drive (both the C:\ root directory and the Acrobat directory in C:\Program. Same result.
Has anyone else found a solution for this problem?

Don't you get a little dialog when update is being installed, where you can point to the original installation package?
If not, use original CD from which you installed your application and run installer - do not try to repair or uninstall using ARP or Help\Repair menu.
It seems like Windows Installer Service lost track of where the original installer file got cached on the system.
One copy is saved (renamed) under Windows\Installer folder.
Another copy is under application installation folder.
They both registered by Windows during initial installation, but occasionaly get corrupted.
Good luck

Crash deploying library after uninstalling LabVIEW 2009

I have been running LabVIEW 8.6 with the DSC module. Recently I briefly installed LabVIEW 2009 for evaluation, then uninstalled it. Now version 8.6 crashes every time I deploy a library. I have tried repairing, uninstalling and re-installing 8.6 with no success. The crash message says the problem is in msvcr71.dll. There are many copies of various versions of msvcr*.dll all over my computer and I am not sure where the problem lies. Can anyone help?

Hi Richard,
Can you please upload a screenshot of the exact error message? I would advise emailing or calling in at National Instruments through this link.
Ipshita C.
National Instruments
Applications Engineer

Intstall error 1612 during uninstall

Hi,
I would like to uninstall several old piece of Labview found a a Pc I will use now before going to LV8 and some cannot be removed. If I press the remove key in windows add/remove sofware, the installer says that some pieces remains not linked to a product, and if i say I want to uninstall them, I have the error 1612 for each of them. How can I remove these old things? there are
NI-PAL 1.5.5f0 Engine
NI-RPC 2.2.1f0 Engine
NI-RPC 2.2.1f0 Engine for LVRT
NI IVI Engine 1.83
NI-488 2.1.70
Thanks for your help

In case it helps, here are some step-by-step instructions for how to use the MSI blast utility in conjunction with unistalling software on systems that require a clean re-installation...I hope this helps!!
Attachments:
MSI Blast instructions.txt ‏4 KB

Error 1305 when installing LabVIEW 7.1 app built with app builder

I have built an executable with installer from LabVIEW 7.1 app builder. The app installs/works fine, however 1 user reported 'Error 1305' when installing the app from a DOS subset on a WinXP machine. For example, a virtual drive is created using the DOS 'subst' command (see http://www.easydos.com/subst.html for more info), e.g. 'subst z: c:\temp'. Now when running z:\setup.exe, the error 1305 is encountered. If the same app is run from c:, e.g. 'c:\temp\setup.exe', it works fine. Is this a bug in the installer, or in the OS...?

Greetings,
This is an architectural issue with the Microsoft Windows Installer and Windows, and will occur with any MSI (not just those from the app builder). Under XP, a MSI cannot install from OR install to a location created by the "subst" command. My understanding of why is that installSequence runs in the context of the MSI engine, which is running as "system" user. But the subst command is a per-user setting (local to your account) so the MSI engine doesn't see it.
The only workaround is to run the MSI from a non-subst drive, or instead use network file shares (you can simulate what "subst" does by mounting an exported file share from the same machine).
Regards,
- WesW / NI

Error 1706 when installing LabVIEW 7.1

Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob

Robert_Deschambault wrote:
Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob
Hello Robert,
You can find out more information about this error at the following post.
what does Error 1706 mean during LabView 6.1 installation
This error is not specific to the install of LabVIEW but with the upgrade of the IMAQ device driver.
Please let me know if you have any other questions
Regards,
Matt F
Keep up to date on the latest PXI news at twitter.com/pxi

Error -1612 when installing iTunes.

Hi, yet again I am experiencing problems when trying to install iTunes for the hundreth time..
And it still doesn't work..
Now there's Error -1612 something about my installation source or whatsoever.. Now the cd is perfectly fine, so can somebody help me solve this, please?
I'm going nutss here! x

okay. let's try working through the general advice from the following document:
Trouble installing iTunes or QuickTime software in Windows

Error Message When Uninstalling Old iTunes for 7.7

When uninstalling (as a natural part of the process of installing 7.7) a message comes up saying that it cannot find iTunes.msi and asks me to find the file. I have no idea where it is. It isn't in either of the two suggested locations.
Any help is much appreciated.

a message comes up saying that it cannot find iTunes.msi and asks me to find the file.
With that one, let's try the following procedure.
First, head into your Add/Remove programs and uninstall your QuickTime. If it goes, good. If it doesn't, we'll just attend to it when we attend to iTunes.
Next, download and install the Windows Installer CleanUp utility:
Description of the Windows Installer CleanUp Utility
Now launch Windows Installer CleanUp ("Start > All Programs > Windows Install Clean Up"), find any iTunes and/or QuickTime entries in the list of programs in CleanUp, select those entries, and click “remove”.
Next, we'll manually remove any leftover iTunes or QuickTime program files:
(1) Open Local Disk (C:) in Computer or whichever disk programs are installed on.
(2) Open the Program Files folder.
(3) Right-click the iTunes folder and select Delete and choose Yes when asked to confirm the deletion.
(4) Right-click the QuickTime folder and select Delete and choose Yes when asked to confirm the deletion. (Note: This folder may have already been deleted if QuickTime was successfully removed using Add/Remove Programs earlier.)
(5) Delete the QuickTime and QuicktimeVR files located in the C:\Windows\system32\ folder. Click Continue if Windows needs confirmation or permission to continue. (Note: These files may have already been deleted if QuickTime was successfully removed using Add/Remove Programs earlier.)
(6) Right-click on the Recycle Bin and on the shortcut menu, click Empty Recycle Bin.
(7) Restart your computer.
Now try another iTunes install. Does it go through properly now?

Error 10401 when running LabView

To start, I am using a PCI 6032E, SC-2345, SCC-SG04, and load cell as my means of DAQ. I have configured a VI for this both in traditional and DAQmx using the example on this site. I can also run a test in MAX and if I push on the load cell, the reading changes. However, when I try to run the strain.vi LabView program found on this site, I get an error 10401. I tried closing the programs and opening them again, but I still get the error. I even have tried restarting the computer, but I still receive the error. Any suggestions? Thanks.

After looking at the program I think I might know why you were receiving the 10401 error with the program. By default, the program doesn't give a channel to acquire from. The array of channels is empty (grayed out) initially and you will get the 10401 error until to enter a channel number or select a virtual channel.
With regards to the new problem, what OS do you have? If you have Windows 2000/XP, then here is what I would try. Go to the device manager in Windows and choose to uninstall the device. Then go into MAX and refresh (press F5) and make sure that the device doesn't appear in Traditional NI-DAQ folder (you may have to delete the device in NI-DAQmx). Close MAX. Then, go back to the device manager and choose Action>>Scan for hardw
are changes and let Windows reinstall the device. Now, go to MAX and test the device in Traditional NI-DAQ and NI-DAQmx.
Let me know if this doesn't get things working.
Regards,
Todd D.

When uninstalling Labview I lose control of my network connection

For some strange reason when i uninstall completely labview and reboot my computer and that i want to access my network connection i get a message that and unexpected error occured.
I had the student version installed and for a project at school my teacher lend me is full version of NI motion. Everything was fine till I decided to remove it.
I tried uninstalling a couple of thing, but only labview causes this problem.
Thank You in Advance!
M.

Hi Hawk,
This is a LabVIEW related problem. Please post this thread to LabVIEW discussion board.
Thanks.
Feilian (Vince) Shen

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Error 1612 when uninstalling LabVIEW 2009

Similar Messages

Maybe you are looking for