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

Similar Messages

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.

How to uninstall MAX (Ver 2.0) after uninstall Labview 6.0

I have deleted the Labview 6.0 as well as NI-488.2. However, MAX 2.0 is still remaining and would like to know how to uninstall it. There's no program shown in Control Panel-Add/remove programs. And the remaining MAX doesn't work properly because missing some component.

You should not be deleting files like that beause those are MSI based installers. Even if you delete the files, MSI stores a lot of information in the registry.
The only easily way for you to install everything that MAX 2.0 came with and then uninstall them all from ControlPanel>>Add/Remove programs. That should take away MAX as well.
hope this works!

Full uninstall labview 2009

i have installed labview2009 evaluation version in my laptop. Now I want to uninstall it. but how to uninstall its registry entry? what are the keys introduced NI?

What kind of registry entries are you worried about. Just uninstalling the application should be enough for all practical purpose.
(Are you possibly trying to be able to get another evaluation period out of this exercise? )
LabVIEW Champion . Do more with less code and in less time .

Run-time engine problem in Labview 2009 and Labview 2010

I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation related to Labview is not permitted and the same error came up every time. it is very annoying.
So, What is the deal?
I attached the error here. Any comments or advice are welcomed and appreciated.
Attachments:
error.docx ‏2305 KB

By chance is this machine's language set to any non-English locale? You would check the locale setting by:
Opening Control Panel.
Opening "Regional and Language Options".
Looking Under "Regional Options" >> "Standards and Formats"
If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
Regards,
- WesW

Font size on Windows 7 with LabVIEW 2009

Hello,
after installing labview 2009 on windows7, I have a problem with the font size of my old application written in 8.6.
the Application Font has seemed to default to another style under windows7 so I searched the forum for the default font under XP when I used lv 8.6. Tahoma 13pt seemed to the correct choice, however when i changed all default fonts to Tahoma 13pt it helped and they look very similar, but the Tahoma under windows7 is slightly longer that the original and it looks like there is some sort of font smoothing going on... perhaps windows is doing its "cleartype" thing by default and influencing its length (thou i thought this shouldnt be the case).
This small difference is causing havoc in my GUI as objects are being resized in a bad way.
Please see the screenshot for an example of my concerns
Another question on the side... is there a Font I can use that will keep the appearance and size over all OSs?
Any help would be appreciated...
Best Regards
Alex.
:. LV2010 SP1 ... W7 .:
Attachments:
Font Difference.png ‏3 KB

Actually this problem affect LabVIEW itself even while editing!
Many of NI's screens suffer from the same problem. Configuring events is one of the most obvious cases. Since teh edit events screen does not allow for resizing, there are some events that you can only guess what they are.
I tried reporting this but the AE wanted me to spoon feed screen shots and ....
I think what really irks me over this problem is that I purchased a laptop with the biggest screen available just to let me do LV and in the end LV can't handle the laptop.
Double -
Ben
Message Edited by Ben on 05-06-2010 10:13 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

My compiled program crashes after first run (LabVIEW 2009)

I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly.
The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM). On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's. Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running. The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down. The program is then gone from memory as far as I can tell. There are no processes in memory or anything.
Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once.
In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see. Also, when I run my program in the development environment the program does not behave this way. It has no problems at all.
I have used this style of architecture before in LV8.6 with out any problems. Can anyone suggest some possible solutions or even some debugging tips? I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue.
Thanks for any help.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!
Solved!
Go to Solution.

I have solved the problem I think (at least as far as testing to this point has revealed). After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher. My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI. My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories. What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down. This is my supposition about what may be happening any way. I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running. This fixed the problem, or at least worked around it. If someone out there can explain to me exactly what is happening I sure would appreciate it.
Thanks for all the help those of you who responded. Your advice was very beneficial and certainly led me to a resolution faster.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing. Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO. I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
So far, so good. After much fighting with Windows 7 network location settings, I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
Any advice will be greatly appreciated.
Kevin
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
Export the variables from the master library as a csv file and copy that to the remote machine.
Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
Find the network path column (it was "U" in my file).
replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
NOTE the single quotes around the process name; they are required.
The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
Once the formula worked on line 2, I could copy it into all the other lines.
Save the CSV file.
Import the CSV into the remote library to create the variables.
Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
Open the properties for the first imported variable.
There is probably an error message at the bottom saying the alias is invalid.
In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
Change the setting to "PSP URL" with the same path and the error message should disappear.
Close the properties box, save the library, and then export the variables to a new CSV file.
Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
The first one is NetworkingleWriter; it should already be FALSE for all lines.
The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
Save the edited CSV file.
Go back to the remote library, and import variables from the just-edited remote library CSV file.
Once you have imported them and the Multiple Variable Editor opens, click on done.
You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
It actually took longer to write out the process here than to perform these steps once I figured it out.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Labview 2009 SP1 crashes when moving large selection with arrow key

If I select a lot (10 or 15) of Block Diagram components and try to move them some distance with the arrow key, I will frequently get a program crash. Since a smaller number of components seems to crash after a longer travel distance, it looks like some kind of buffer overflow error. I do not see this problem when using the mouse to move selections.
I have checked to be sure I have the latest video driver for my NVIDIA Quatro FX570. I have also tried working with no hardware acceleration and no combined writes. This is happening on Windows XP SP3 with all the current updates.
It has become so bad that I have to do a Save As every fifteen minutes to keep from losing data.
Why don't I use my mouse for all movements? Because it is not as accurate and not so easy to restrict to one dimension of movement. My hand is not as steady as it once was.
I hoping someone will have a suggestion that will clear up this problem.
Solved!
Go to Solution.

As I indicated, I had the same problem with 8.5 and just DID a new installation of Labview 2009.
Since it is possible my three-monitor setup, which obviously requires more video memory, may be at the root of the problem, I am satisfied with the workaround of dragging the objects near their final destination and then using the arrow keys.
Three monitors are ideal for front panel, block diagram and Help/Internet/Probe Window. When I had to work in the field with only one monitor, I felt severely handicapped.
You may consider the matter closed.
Thanks for attempting to duplicate the failure.

How do I sync my Ipod to a new library after my computer has crashed?

How do I sync my Ipod to a new library after my computer has crashed?

iTunes Store: Transferring purchases from your iOS device or iPod to a computer - http://support.apple.com/kb/HT1848 - only media purchased from iTunes Store
Sync transfer is one way, matching the device content to the content on the computer, except purchased content as mentioned above. For transferring other items from an i-device to a computer you have to use third party commercial software. Examples (check the web for others; this is not an exhaustive listing):
- Senuti - http://www.fadingred.com/senuti/
- Phoneview - http://www.ecamm.com/mac/phoneview/
- MusicRescue - http://www.kennettnet.co.uk/products/musicrescue/ - Mac & Windows
- Sharepod (free) - http://download.cnet.com/SharePod/3000-2141_4-10794489.html?tag=mncol;2 - Windows
- Post by Zevoneer: iPod media recovery options - https://discussions.apple.com/message/11624224 - this is an older post and many of the links are also for old posts, so bear this in mind when reading them.
Syncing to a "New" Computer or replacing a "crashed" Hard Drive - https://discussions.apple.com/docs/DOC-3141
In general do not regard your i-device as a reliable unique storage for your media. It is not a backup device and everything is structured around you maintaining a backup of your media on a computer backup.

I have lost my itunes library after updating it and keep getting a message saying MSVCR80.dll is not installed when I try to uninstall/reinstall it???

I have lost my itunes library after updating it. Have tried uninstalling/reinstalling it and it gets so far then tells me that it cannot be installed because MSVCR80.dll is not installed on my pc. I have no idea what this is and have googled it, followed links to sites that say they can fix it, only for them to scan, tell me I have 3 thousand issues and then want me to pay $30 dollars to fix it for me. This message also appears on firing up my pc too.
Can anyone help please?

I've been through the exact same thing and cannot seem to get an answer here. When you go to Manage Storage, does it have something at the top like "19.1 GB of 25 GB available"? I only have a Mail account with 5.3 GB in it and a Backups account with 553 MB in it. Obviously, these don't add up to 19.1 GB. There was no change in any of these numbers when I deleted all the same files you mention. With the free Mobile Me storage expiring next month, this is something I'm pretty concerned about.

Tried to upgrade and after uninstalling and reinstalling several times, keep getting "procedure entry point could not be located in dynamic link library" followed by "iTunes was not installed properly" Error 7.....Help, please??

Tried to upgrade as instructed and after uninstalling and reinstalling (even back to the former iTunes which I was happy with)several times, keep getting message "Procedure entry point could not be located in dynamic link library" followed by "iTunes was not installed properly" "Error 7". Help, please??

Entry point errors can usually be fixed by deleting the offending dll, then repairing the component it is part of from the programs and features control panel. Unfortunately you neglected to include the detail of which dll is mentioned.
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
The further information area has direct links to the current and recent builds in case you have problems downloading, need to revert to an older version or want to try the iTunes for Windows (64-bit - for older video cards) release as a workaround for installation or performance issues, or compatibility with QuickTime or third party software.
Your library should be unaffected by these steps but there are also links to backup and recovery advice should it be needed.
tt2

Switch executive stops working after labview 2009 installation

Hi, After I've installed labview 2009 my old switch executive virtual device routes stop working in such a way even if I try to set a route from switch executive test panel the attached error message pops up.
I am using:
Labview 9.0.1
TestStand 4.2.1
Switch Executive 4.6.2
Many Thanks in advance
Mehran Fard
Mehran Fard
Attachments:
niSE.png ‏11 KB

Hi Fardm,
I might try doing a repair on LabVIEW, TestStand and Switch as it sounds like a dll might have become corrupt.
Kind Regards,
Owen.S
Applications Engineer
National Instruments

Crash deploying library after uninstalling LabVIEW 2009

Similar Messages

Maybe you are looking for