Labview 2009 32 bit not running on xp 64 bit

Hi all,
I tried to upgrade to LabVIEW 2009 from LabVIEW 8.6 on 64-bit windows XP machine. Following about a 2 hour removal of 8.6 and subsequent installation of LV 2009 it turns out that the device drivers are not compatible with a 64-bit machine. On launching LabVIEW 2009 (32-bit) an error box appears stating that it is corrupt or missing files and to correct this using control panel etc. I have tried this and still the same error occurs and LV refuses to start.
All the license files are correct and the compnents are activated.
Anyone know how to fix this? Or should I go back to 8.6 and cancel my upgrade subscription?
Secondly, I am using a firewire camera and was informed that Ni-IMAQ legacy are no longer supported and to go to ni.com/ifo and enter legacy1394 to see how to download drivers etc for this. I end up on a page that says "not authorized".
Any help gratefully appreciated.
Solved!
Go to Solution.

Leeser wrote:
I agree that XP64 and LV 2009 are not compatible as I installed LV 2009 on another 32-bit machine with no problems. I was just surprised as there were no problems or issues that I came across for 8. on XP64. Ah well, a uninstallation and reinstallation lies in wait for me on Monday morning!!
As an aside why call it LV 2009 instead of LV 8.7 or even LV9.0...sounds reminiscent of an operating system!!
Regards,
Leeser
LabVIEW 2009 is according to the internal version scheme actually equivalent to LabVIEW 9.0. Why they changed the naming? I guess marketing told them to do so. Why then? Well marketing has some funny ideas sometimes. I guess since THE software provider in this world has started to do this since about Windows 2000 someone must have thought it to be the best idea since sliced bread and decided to do it for LabVIEW too.
Another guess is that in about 2010 there would have been something like 9.1, and 10.0 would then come out in 2011 and that sounded somehow to someone like a bad scheme so they decided to change it now. But maybe it will be forgotten and everybody returns to the old versioning at the begin of next year when 9.0.1 will come out, which would then otherwise be LV 2009.1??? Or maybe LV2009 SP1?
It has already happened with LabVIEW 6i (iMacs, iPhones, iAnything), LabVIEW 7 Express and LabVIEW 8.20 (following 8.0.1 and marking the 20th anniversary of LabVIEW, and being internally LabVIEW 8.2). All some marketing fun or hysteria.
Rolf Kalbermatter
Message Edited by rolfk on 08-17-2009 11:08 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

64 bit processor running on a 32 bit os

I have a laptop that has a 64 bit processor running on a 32 bit os. Can I upgrade my os to 64 bit? If so how? I have a compaq presario with AMD 64 Athlon X2 procssor (64-bit) running on windows vista premium 32-bit. Please help.

You do not HAVE to upgrade to a 64bit OS, although doing so will better utilize the dual core capabilities of your processor.
If you do not upgrade, the sky will not fall, your computer WILL still be usable, and your programs will ALL work.
If you do want to upgrade, head into a store or online, and look for an UPGRADE package as it's a LOT cheaper then buying a full out version.
If you like my post, or solution to your issue/question, go ahead and click on the little star by my name and/or accept the post as the Solution. It makes me happy.
I'm NOT an employee of Best Buy, or Geek Squad, though I did work as an Agent for a year 5 years ago. None of my posts are to be taken as the official stance that Best Buy will take on your situation. My advice is just that, advice.
Unfortunately, that's the bad luck of any electronic, there's going to be bad Apples... wait that's a horrible pun.

Support in LabVIEW 2009 for IMAQ legacy drivers on 64-bit windows

Hi,
I have been trying to use a VI that was created in LabVIEW 7.0 that makes use of IMAQ 1394 VI's in LabVIEW 2009. When I first tried to run the VI an error told me that the VI's in question were missing, to overcome this problem I thought I should attempt to replace them with legacy VI'. After downloading the legacy installer, I then realised that these VI's would not function on a 64-bit version of windows even though I have a 32-bit version of LabVIEW.
I was wondering if there is an alternative way of replacing these VI's or a way of implementing the lagacy VI's? Would it be suitable to replace the IMAQ 1394 VI's with IMAQdx VI's?
Thanks for your time,
Alistair Martin

Hi Alistair,
The following KB states that it should be possible to do what you require: http://digital.ni.com/public.nsf/allkb/3358528DF8648DC2862571F500586140?OpenDocument
The KB also links to some development articles for upgrading and using IMAQdx to acquire from 1394 cameras.
I hope this helps,
Kind Regards,
Applications Engineer

Labview 2009 .exe not working with windows 2000

I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
Thanks
Solved!
Go to Solution.
Attachments:
Serial Number Reset Cell 2.vi ‏15 KB

There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
George M
National Instruments

LabSQL can not run with MySQL 64-bit ODBC connector

I have developed a small piece of LabVIEW program to retrieve the data from MySQL database and displayed as curve with XY-Graph. The bridge between database and the program is the MySQL ODBC connector and the LabSQL VIs (which is quite useful). The program runs properly in my 32-bit computer for developing while a error caused in LabSQL part and stated that there is a architecture mismatch:
Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application in ADO Connection Open.vi->WeatherDataRetrive.vi
Is there anyone encountered similar problem and would you please provide some help?
Many thanks in advance.
Harry

Are you using LabVIEW 32 Bit? Even if you run on Windows 64 Bit any DLL loaded on behalve of an application has to have the bitness of that application, not the bitness of the OS. And I'm pretty sure that the ADO/DAO interface that LabSQL is using will not provide any bridging if the ODBC driver is not in the same bitness as the calling application.
So if you are using LabVIEW 32 Bit, install the 32 Bit MyODBC driver or change to using 64 Bit LabVIEW instead, although there might be other problems with ADO/DAO not working properly for a 64 Bit application.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

6i Reports Not Running in Windows 64 Bit PC

Hi All,
We have installed 64 bit version of Windows in some PC’s. We are running Forms and Reports 6i from that PC. But only forms are running fine reports are not running. Have any one of you encountered this problem and got that resolved.
Please share with us the resolution for the same.
Thanks in advance

Hello - I have been able to get the AIP installed.
Turns out that the installation was hanging because a previous version of Acrobat was already installed. On other machines with Acrobat, I would get a window stating that I had to remove the old software but on W7 x64, the installation simply failed. After removing the old version and trying again, the new installation succeeded.
Thanks to everyone for their help.

ITunes latest up-date will not run on Vista 64 bit system

Downloaded and installed latest iTunes version Friday 21/1/14 but program would not run. Error message 'MSVCR80.Dll is missing. Repeat download.' Repeated downloads give the same message. Tried to uninstall and reload my original iTunes download from 2011 but that now gives the same error message. I'm running 64 bit Vista. Does anyone have a suggestion???

Hi, here are a couple of links that should help.
http://support.microsoft.com/kb/827218
http://kb2.adobe.com/cps/000/6b3af6c9.html
This one is the MS forum, sort of hard to follow, but the info is there.
http://social.answers.microsoft.com/Forums/en-US/InternetExplorer/thread/3c12694b-0e3d-417 e-bf3f-6ba53b9a8253
Hope these will help.
Thanks,
eidnolb

I need to know how to run Flash Player in a Vista 32-bit browser running on a 64-bit O.S.

Help please ! I have been reading for days, trying everything to find the answer to my dilemma, which BTW is making it impossible to use our new computer now. Every other minute it seems I get the message that I need to run Flash Player in a VISTA 32-bit browser which is actually running on a 64-bit operating system. Do I have to uninstall a program (what and where is it) and then instal something else (from where etc.)?
Give me back our XP! I get the idea that Adobe keeps SAYING they are developing a platform for Adobe Flash to run on a 64-bit, but I fear that is only a stall. Who is responsible for helping neophytes? No matter how many times I have tried to contact Adobe, it is a joke. One time, even though I do not have a subscription for service, the poor man took pity on me. But his Indian accent was so severe I have ZERO idea what he was saying. Can one of you wonderful, erudite, helpful people out there give me the solution in computer language 101?? I will be forever grateful. I wish our computer "guru" had been smart enough to give us the pros and cons when he suggested Vista and 64..... When I am asked for a serial number even I have no earthly idea how to get that either. I feel completely HELPLESS and SLEEPLESS in Tucson. Thanks SOOOO much to whomever can get me going in the right direction. (Forgive my LONG message. I had to vent. I feel better.) CLOWG

Hi Clowg,
Sorry to hear that you are having trouble. Unfortunately, I don't believe the folks here on this forum will be able to help you with your issue. Have you tried posting on the Flash Player forum?
http://forums.adobe.com/community/webplayers/flash_player
Regards,
Fang

Labview project does not run on different computer

I have some problems with a lvproj file containing an application. The application used to work with as long as I had all subvis inside a llb file. With the very same VIs I now created a lvproj file on Labview 8.6. I can successfully load and run the program on 2 windows machines, but I get very odd error messages on a third Windows machine.
The error seems to be related to a mathscript node I'm using but I don't understand why this is a problem. I get an error code -90001 "Error in function path at line 1. A problem occured in a subvi call".
As said before, this works perfectly find with the old llb file, but not with the lvproj file. How can I fix this?
I tried the obvious things like rebooting the computer & restarting Labview, but no I had no success so far to get this running.
Message Edited by kandreas on 01-02-2009 08:30 PM

Hi Kandreas,
Thanks for the post and I hope your well today.
Sorry for stating the obvious first off - but clearly the three computers are not the same.
You could run a MAX System Report to see what differences there are...
Let me know what you think,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

SSIS 2005 not running after upgrading (32 bit, Windows XP to 64 bit Windows 7)

I really need some help. Recently I went from using Visual Studio and SQL 2005 on a laptop (32bit system - Windows XP) to a desktop unit 64bit processor with Windows 7). SSIS on the laptop worked just fine and I could execute and open packages in SSIS; however,
my new desktop unit will not even allow me to open a new package or run an existing package. As soon as I attempt to create a new SSIS project, I receive the following error: "An error prevented the view from loading. The specified module could not be
found. (Exception from HResult:0x8007007E)(System Windows Forms).
SSIS won't allow me to view the control flow or data flow screens and if I attempt to run an existing package created with the SSIS wizard I receive the following error: SSIS package "Package1.dtsx" starting.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Error: 0xC0202009 at Package1, Connection manager "SourceConnectionExcel": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC020801C at Data Flow Task, Source - Without_Sample$ [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code
0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "Source - Without_Sample$" (1) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
SSIS package "Package1.dtsx" finished: Failure.
I have tried changing the properties in the package to run in 32-bit mode; however, this does not work. I can run queries and import data in SQL Server Management Studios just fine, as well as run queries and reports in Visual Studios; however, I can't execute
or create any package in Visual Studio with the new machine. Am I missing a needed system file in the new sysWOW64 folder? The IT person who installed the software isn't familiar with the program and doesn't know how to fix it either. I'm relatively new with
using SSIS and really need some help on how to get this fixed. Any help you can offer would be greatly appreciated.

If the Development Studio environment does not even open then it is probably an installation issue. Possibly a DLL did not register properly. Could you take a look at the following forums where a similar issue is being discussed? You can also look for more
responses by searching for "0x8007007e visual studio on windows 7" in your search engine.
http://support.microsoft.com/kb/978714
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bcf22d6-adab-4595-b0d8-3a37ce7fbff3/2008-ssis-designer-stops-working-after-installing-vs11-dev-preview?forum=sqlintegrationservices
http://stackoverflow.com/questions/10460118/the-specified-module-could-not-be-found-exception-from-hresult-0x8007007e
- Aalamjeet Rangi | (Blog)

LabVIEW 2009 sp1 not responding / crash

Hi,
I seem to have developed an issue with LabVIEW whereby it freezes at a random point during execution. It is not a case of a VI freezing, rather the LabVIEW application itself ceases to work and needs to closed by task manager. What I have running at the time is a host VI that sends and receives data over a TCP connection to a real-time target on a PXI. The real-time application keeps running after the crash. The host system is also running 3D picture control showing some basic graphics. The whole system is controlled at a top level by a program written in C# over a TCP connection but can run stand alone. When running stand alone the problem does not occur.
The communication between the C# and LabVIEW works fine, yet at a random point during operation, LabVIEW freezes while the C# continues to work. This doesn't seem to correspond to a particular action by the C# program. I guess my question is, is there any likely culprit by which LabVIEW can be crashed by an exernal program where the only communication is via TCP that seems to work fine and where there doesn't appear to be excessive memory or CPU usage?
Cheers.
Solved!
Go to Solution.

Having further investigated it appears to only occur as TCP exchange is taking place and the full LabVIEW application doesn't appear to have crashed, but several VIs hang and can't be closed. There are three total TCP connections running, one that links to the PXI unit, one to the C# application and one from the C# to the visual display VI that is idle when this event occurs. Does anyone know of any reason why a TCP connection can cause LabVIEW to hang? The same connection has worked numerous times before the error occurs. Appears to only happen when the 3D picture control is running.

Labview 2009 would not close properly

Hi everyone!
I have been having problems with our recent upgrade from LabView 7.1 to 9. I have removed 7.1 completely and have installed everything that came with the installation DVD's in LabView 9. When I went to my old VI's and continued to work on them, after I have saved the VI and exited LabView, Labview would still linger in the background and do nothing. This prevents me from opening LabView again. I then would have to go to Task Manager to terminate the process. As soon as I do this and re-open LabView, I would get the pop-up window asking to investigate the recent crash.
I am currently in contact with [email protected] as well, but they have not solved the issue so far. This is why I am seeking help with the rest of the community. I am hoping that somebody out there knows anything about this issue. I am attaching the most recent lvfailurelog I have encountered.
I have currently installed the most recent patch to LabView 9 and the only thing it's done is to illiminate the logging of the failure because it's no longer asking me to investigate after terminating the application from Task Manager.
Marcos
March 25, 2009
Update: The problem has retuned and I have attached the most recent logfile. Please help.
Attachments:
lvlog2010-03-25-13-35-08.txt ‏190 KB

I don't know about old VIs specifically, but quite often, when I exit LV 2009 (and I think 8.6 did this as well) it takes a long time until the process dies and during that time the memory consumption of the process rises considerably. Eventually it does quit, but it just takes a while before it does (roughly two or three minutes).
Try to take over the world!

LabVIEW program will not run on Windows 2000

I need to run parts of a LabVIEW program on a PC which does not contain all the hardware required to run the full version. This used to work on Windows 95/98 but on Windows 2000 I get error message 'Capabilty not supported. VI was stopped at node 0x1BC of subvi "Out Port.vi"'. This program is very large and full of references of this type, is there an easy way around this problem?

Hi,
I might be barking up the wrong tree here, but Windows 2000 is built on top of the architecture of Windows NT. Win NT/2000 treats direct memory access differently to Win95/98.
Have a look at the following link and see if that helps - unfortunately it involves re-writing (well, re-linking) the .vi's that are calling the out port.vi. The link is in reference to writing to the parallel port through direct memory access, but the .vi's are based on writing to any memory location.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c80752c53094c296862565f3007ac765?OpenDocument
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000110A0000&ECategory=LabVIEW.LabVIEW+General
As you don't say wh
at version of LV you're using, the following link might also prove useful (if you're using LV 6.0.2+)
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000102F0000&ECategory=LabVIEW.LabVIEW+General
Hope that helps
S.
// it takes almost no time to rate an answer

Needing help with Bootcamp Drivers on my late 2009 27" iMac running windows 7 64-bit.

Hey, installed Windows 7 on my late 2009 27" iMac (Have previously done so and worked flawlessly, magic mouse could scroll etc) but had to remove the partition as I required more of my hard drive than anticipated, so I removed the partition and went to install Windows, everything worked fine until I wanted to install the bootcamp drivers, to which it said that my Mac doesnt support 64-bit... which it does as I've been running it for months with no problems whatsoever. Would appreciate if someone could tell me which version of bootcamp would be best to install and how to do so if the procedure isn't that simple. Also I get no sound from the Windows partition, as I get a red light from the audio Jack, which is clearly from the lack of drivers as it works fine on the OS X partition.
I have snow leopard install discs handy although the version of bootcamp on that differed from the one I had, which was much better.

Did you download the correct drivers for your Mac? The Late 2009 iMac needs these drivers > http://support.apple.com/kb/DL1630

LabVIEW 7.1 reports an application error 'instruction adresses memory at 0x00000000 - ... could not be written' when finishing LabVIEW, even when not running any private code

Hi there,
I have found similar Qs here, but this one is _somehow_ different.
My quite large app (>600 VIs) uses some DLL calls to communicate with medical devices. It runs OK, AFAIK, even when started several times. BUT I get an error message each time I when finishing LabVIEW 7.1 (even when just having loaded the app!!!). The error message states that "The instruction at 0x778cca36 adresses memory at 0x00000000. The process 'written' could not be done on that memory. Click to close the app".
Any clues?
My system: Athlon64 3000+ with 1GB of RAM running W2k German with all availabel SPs, LabVIEW 7.1 English with all support files from the devellopr suite May05 edition. System was set up 2 days ago on a fresh PC. The old system showed the very same behavior.
My opinion is, that simply loading an app and than removing it should not cause such an error??!!
Greetings from Germany!
Uwe
Attachments:
Application_Error_LabVIEW_when_finishing.jpg ‏20 KB

I can't look at your code because I don't have LV 7.1, but I would recommend searching on the side of the DLL.
Do you have the source for the DLL? Can you be sure that the DLL doesn't somehow have a memory addressing bug? The DLL will be loadsd as soon as the program is loaded AFAIK, so maybe when unloading the DLL an error occurs because something isn't initialised properly. I've never programmed a DLL, so I may be way wrong, but my instinct tells me that the problem will most likely be with the DLL.
Hope this helps
Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

Labview 2009 32 bit not running on xp 64 bit

Similar Messages

Maybe you are looking for