LabVIEW 9.0f2

Installation of LabVIEW 9.0 from the Third Quarter 2009 software was successfull and I was able to run any version of LabVIEW from v7.1 to v8.6.1 and the new 9.0 version.  I installed Fourth Quarter 2009 software and the f2 software and now I can only run LabVIEW v9.0f2.
When I run other versions other than 9.0f2 I get an error message:
"LabVIEW 8.6.1 Development System has encountered a problem and needs to close. We are sorry for the inconvenience."
How can I be run my lower version software packages?  Has this been reported before? 
Solved!
Go to Solution.

pallen wrote:
This is definitely not expected behavior, and it's the first time I've seen it reported.
Did your installation of 9.02f replace your previous installation of 9.0? 
I too would like to see confirmation on this before proceeding with my own upgrade. 
Me too.
Especially someone with a lot of version (7.0 and up) could comment.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

  • LabVIEW 13.0f2 crashes when cutting text from certain free labels on the block diagram

    While revising the documentation of a VI, I faced a LabVIEW crash. I can reproduce it in LabVIEW 13.0f2 with the following code.  Can anyone confirm that cutting the content "def" from the free label and trying to paste it in the free label with "ghi" produces error 0xBC0BF185?
    I cannot reproduce this issue by any other cut/paste between the free labels on the left-hand part of the BD.  The crash solely occurs when cutting "def" and trying to paste to "ghi".
    Solved!
    Go to Solution.

    I'm not reproducing it from the snipette. LabVIEW 2013.0f2x32 on Win7 enterprise. Heap Peek your copy, there is something insane with your label.
    Whoops.... I take that back.
    Crash report sent- d77e8fae-e15f-45d7-9bc5-d125970a4119
    Jeff

  • Bug: Windows 7 DLL call to turn off monitor message crashes LabVIEW 10.0f2

    Hi,
    I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 286873
    I was trying to find a way to turn off a laptop lcd
    monitor during measurements. I was trying to replicate this
    http://codereflect.com/2009/04/03/how-to-programmatically-turn-onoff-your-monitor/
    which uses windows messaging.
    I found the attached Monitor-1.vi somewhere on the forum that seems to do the above.
    However when I run the VI it crashes LabVIEW 10.f2 on Windows 7 32-bit.
    cheers
    David
    Solved!
    Go to Solution.
    Attachments:
    Monitor-1.vi ‏13 KB

    Hi Cosmin,
    That was it! Thank you so much!
    I will let NI UK support that you identified the issue and get them to close the CAR.
    cheers
    David
    Attachments:
    Turn off Monitor.vi ‏12 KB

  • Auto cleanup crashes LabVIEW (and VI isn't even that large)

    Hi,
    I'm trying to cleanup a VI, and whenever I hit auto cleanup LabVIEW crashes and when retsrated it doesn't even say it previously crashed. I narrowed down the problem location to a for loop. The wierd thing is that I went through all the wires and objects within the loop and did auto cleanup on them but it doesn't crash. So why when I do it on all combined does it crash?
    I wrote a comment in the loop that crashes to show which on it is.
    I'm on Windows 7 LabVIEW 2010.0f2 32bit
    I did see this posting http://digital.ni.com/public.nsf/allkb/599FB39777B​DB12486257514005B7293, but even when doing it manually as suggested it still crashes.
    Thanks,
    Matt
    Solved!
    Go to Solution.
    Attachments:
    Score Videos temp.vi ‏126 KB

    This crash corresponds to a known issue in LabVIEW (CAR #298911), which has been fixed in the forthcoming LabVIEW 2011 release. I have attached a copy of your cleaned up VI from 2011, saved for 2010. You might try to copy the block diagram into a new VI and see if that still crashes LabVIEW, but otherwise an upgrade to 2011 when it's available should clear up the problem. Hope that helps.
    John B.
    Embedded Networks R&D
    National Instruments
    Certified LabVIEW Developer
    Attachments:
    Score Videos temp-1.vi ‏104 KB

  • Labview database problem: Create a database table from user defined fields

    I am trying to create a new table in an access database opened by an ODBC connection from information entered a table stored in the database, but every time I try to create the table, the Labview Database connectivity toolkit VI for creating a table throws a cryptic error
    "Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][ODBC Microsoft Access Driver] Syntax error in field definition. in NI_Database_API.lvlib:Conn Execute.vi->NI_Database_API.lvlibB Tools Create Table.vi->DatabaseCreateHeaders.vi"
    I think this is becuase I am trying to re-create the database  column variable type, but I am not sure what I am doing wrong.  Everything seems to be fine as the data types go, and everything works as long as I use a constant to create the database columns.  I even tried putting all of the information into the format labview defined, changed that to a variant, and redefined it as the labview database column type. 
    I have attached a simplified VI and a picture of what I am trying to
    do, but I would appreciate any help I can get.  Hopefully I won't have
    pulled out all of my hair by the time some one replies!
    Solved!
    Go to Solution.
    Attachments:
    DatabaseUserDefinedTable.vi ‏14 KB
    UserDefinedColumns.JPG ‏48 KB

    Hi everyone. I am new to the database tool kit using labview. I am using labview 9.0f2 on Windows Xp. I am required to create a database (task is to create a table and to insert values into the table using Microsoft access 2007). I am trying to learn using the Create Database table.vi found with the software. I understand that need to create an access file and also had a mdl file which is name after it.(I had created them). Looking at the example given, I would like to add a few more variables, to be exact 6 more variables(therefore i would have 6 colum in my access file rite?). From the "connection information" the help information shows that it contain an 1D array of DB tools colum. ctl and also a cluster of 4 elements. the link to the access file, LabVIEW.udl shows that it restrict the colum in the access file.eg it has only stringcol,intcol,doublecol. I need to add more colum but cant add just like tt.
    qn1: How to i add insert more varibles into the database so that it will apprears in access.
    qn2: I cant drag and insert the "connection information" just to have more input. how do i do it?
    qn3: where can i edit the info so that i can add more cluster into the access? when i drag out the input turn greyish.

  • Sub vi used in main vi

    Download this .zip and extract all files to a folder, used LabVIEW v9.0f2.
    I want to use Light Show as a Sub VI to Furnace Cycle MAIN1 (Front Panel) - I need to use this Sub VI (sub of one light control) with many light on the Furnace Cycle MAIN1 front panel.  In the light show VI, I am using an enumerated control to simulate inputs from a future PLC and the boolean switch simulates power is applied to that PLC.  The light color is white when the PLC is not active or does not have an output to the light.  The light show VI is written in the form of a state machine.  I need to to have a stop boolean control to stop the Furnace Cycle MAIN1 program and all the sub vi's. Any help would be appreciated.  I am open for other code processes like arrays etc. to accomplish the same results.
    Attachments:
    Light Show Project.zip ‏69 KB

    The Light Show SUB VI has a while loop in it. This would cause a problem when trying to communicate with it from your main VI as it will always wait for the subVI to complete executing before moving on to any other code that you want to run after it. I would recommend removing the while loop from the subVI and just keeping the case structure and its contents in the subVI. This way, you can have the Light Show subVI inside a while loop in the main VI. This will allow you to place a 'Stop' control in the main VI, which can be wired into the subVI as well.
    I hope this helps you out. 
    Vivek Nath
    National Instruments
    Applications Engineer
    Machine Vision

  • Applicatio​n builder error creating

    After install Labview 9.0f2, no longer is possible to build application
    Solved!
    Go to Solution.

    Would you like us to continue guessing, or would you be capable of providing some details?
    Such as what the error is?
    What was the version of LabVIEW you were using?
    What toolkits you are using?
    Anything else you can think of?
    Remember, we don't have one of those nice troubleshooting scripts that call centers have.

  • Import string programmatically to reentrant VI

    I am working on a multi-language application that includes a reentrant VI. I have been successful at importing a strings file to non-reentrant VIs but seem to have issues importing strings to a reentrant VI. I basically call the reentrant VI dynamically in a loop (open VI ref, import strings file, run VI). The first iteration is error free, but after that it returns error code 1000.
    I know that the import strings function does not execute when the VI is running and that is why I am receiving this error, but my VI is reentrant and set to preallocate clone for each instance. Is this behavior expected when using the import strings function while calling a reentrant VI multiple times? If so, is there a workaround this issue?
    Thanks,
    Cristian
    (Using LabVIEW 9.0f2)
    Solved!
    Go to Solution.

    Ben wrote:
     "...I believe all re-entrant VI's share the FP...."
    If this is true, then I should be able to just import strings on the first iteration of my loop and the strings should change for all of them.
    I made a simple VI of this for testing and found that on the second iteration, the Run VI method returns error code 1000. The loop runs correctly on the first iteration because the reentrant VI was not in memory, but on the second iteration, it seems like when a new reference is made to the reentrant VI, it sees that it is already running in memory.
    From what I understand about reentrant VIs (set to preallocate clone for each instance), they should act very similar to VIT's. Someone correct me if I am wrong.

  • Problems using ActiveX controls

    Hello all,
    I bought a set of ActiveX controls provided with a installation routine.
    Using those controls within LabView after installing them were no
    problem, but for distribution purpose I have to install those ActiveX
    controls manually.
    So I tried to do it on a separate computer by registering the ActiveX
    controls with regsvr32 [regsvr32 ]. But the attempt to
    start a LabView program where these controls were embedded ended with
    the error message "error opening document" (ole_lv5container) and "error
    510 occurred while loading ActiveX control ..."
    I'm working with Windows NT 4.0 and LabView 5.0f2.
    Does anyone know, what I made wrong?
    Bye, Alexander
    Sent via Deja.com http://www.deja.com/
    Before you
    buy.

    Hello all,
    I bought a set of ActiveX controls provided with a installation routine.
    Using those controls within LabView after installing them were no
    problem, but for distribution purpose I have to install those ActiveX
    controls manually.
    So I tried to do it on a separate computer by registering the ActiveX
    controls with regsvr32 [regsvr32 ]. But the attempt to
    start a LabView program where these controls were embedded ended with
    the error message "error opening document" (ole_lv5container) and "error
    510 occurred while loading ActiveX control ..."
    I'm working with Windows NT 4.0 and LabView 5.0f2.
    Does anyone know, what I made wrong?
    Bye, Alexander
    Sent via Deja.com http://www.deja.com/
    Before you
    buy.

  • Looking for occurrence RefNum vi

    Hi all,
    I am looking for the occurrence-RefNum-vi in LabView 5.0f2.
    The only functions I found according to occurrences are
    advanced->synchronisation->occurrences->generate/w​ait on /set
    occurrence. So where's the occurrence-RefNum-symbol, which is mentioned
    in the Online-Reference.
    Thanks, Alexander Salim
    Sent via Deja.com http://www.deja.com/
    Before you buy.

    The "Occurrence RefNum" is not a function, it is a control(indicator)
    found in the front panel palette "Controls >> Path & RefNum >> ...".
    In article <861tpn$78d$[email protected]>,
    Alexander Salim wrote:
    > Hi all,
    >
    > I am looking for the occurrence-RefNum-vi in LabView 5.0f2.
    > The only functions I found according to occurrences are
    > advanced->synchronisation->occurrences->generate/w​ait on /set
    > occurrence. So where's the occurrence-RefNum-symbol, which is
    mentioned
    > in the Online-Reference.
    >
    > Thanks, Alexander Salim
    >
    > Sent via Deja.com http://www.deja.com/
    > Before you buy.
    >
    Sent via Deja.com http://www.deja.com/
    Before you buy.

  • Bug: Cubic Spline Fit error when some (x,y) weight(s)=0

    Hi,
    I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 287065
    I was trying to use Cubic Spline Fit.vi and control its
    behaviour using the "Weights" array input.
    The VI doesn't like Weight=0 in some cases.
    The error reported "Analysis:  The input must be non-zero."
    The VI will work if the number is a very small but
    non-zero number.
    Steps To Reproduce:
    I have attached a VI to demonstrate the issue.
    Run the program with Select=TRUE and new element = 1 The
    cubic fit will run OK without any error.
    Change new element = 0
    The cubic fit will run but this time the error is -20141
    Change new element = 0.0001 The cubic fit will run OK without any error.
    Change Select = FALSE
    This will then use the Example Weights array. This is a
    real example of input I am supplying to this VI.
    The cubic fit will run but this time the error is -20141
    Set Offset = 1E6 i.e a small number close to zero.
    The cubic fit will run OK without any error.
    cheers
    David
    LabVIEW 10.0f2, Windows 7 32-bit.
    Attachments:
    Cubic Spline Fit Zero Weight Issue.vi ‏74 KB

    Hi,
    I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 287065
    I was trying to use Cubic Spline Fit.vi and control its
    behaviour using the "Weights" array input.
    The VI doesn't like Weight=0 in some cases.
    The error reported "Analysis:  The input must be non-zero."
    The VI will work if the number is a very small but
    non-zero number.
    Steps To Reproduce:
    I have attached a VI to demonstrate the issue.
    Run the program with Select=TRUE and new element = 1 The
    cubic fit will run OK without any error.
    Change new element = 0
    The cubic fit will run but this time the error is -20141
    Change new element = 0.0001 The cubic fit will run OK without any error.
    Change Select = FALSE
    This will then use the Example Weights array. This is a
    real example of input I am supplying to this VI.
    The cubic fit will run but this time the error is -20141
    Set Offset = 1E6 i.e a small number close to zero.
    The cubic fit will run OK without any error.
    cheers
    David
    LabVIEW 10.0f2, Windows 7 32-bit.
    Attachments:
    Cubic Spline Fit Zero Weight Issue.vi ‏74 KB

  • Error 1 when building my application in Labview 2010 Version 10.0f2

    I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
    Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
    =========================
    NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
    Method Name: Linker:Write Info To File
    I have searched and can find no real sollutions to this problem.  I did the updates and still nothing.  Now I can't even build an app with Laview 8.6.  I reference several .NET items and refuse to rebuild each and every one of them.  My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
    Help if you can.

    Hello RBrown
    I am really sorry for this inconvenience!  This is a known issue.
    Can you please attempt the following for me:
    When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
    If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
    Here are some forum posts strictly for your information:
    I have found users that have had similar issues. I am trying to make this workaround work for you.
    http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
    This is a known issue that some customers have already commented on:
    http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
    I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
    Sincerely,
    Greg S.

  • LabVIEW Internet Toolkit 6.0f2.zip patch did not work

    I was installing the LabView 8.2 distrubution that came along as my August update package. Since I was loading this on a brand new machine, I went straight to 8.2. According to the information in the package, when I load in the Toolkit Software, I needed to add some patches. I located two patches, one for the Express VI Development Toolkit and one for the Internet Toolkit. The Express VI Development Toolkit patch worked exactly like its documentation said it would. The Internet Toolkit would not run correctly. It gave me this diagnostic: "The LABVIEW Internet Toolkit 6.0f2 patch was unable to update your files. Ensure you have administrator/root privileges ana that none of the files in <LabVIEW dir>\www\cgi-bin or <LabVIEW dir>\vi.llb\addons\internet are set to read-only. Then re-run the patch."
    I have adminsitrator privileges (I've been installing software for two days). I looked at the files in the two directories that they asked about, and there were none at read-only. Help!!
    Thanks!

    Dave,
    I've seen this problem before.  When you unzip the patch files, you must preserve the folder structure included in the ZIP file.  Specifically, it creates some subfolders (Windows, Mac, and Linux, I think) that reside next to the patch LLB.  The patching VI will be looking for specific files in those folders next to the LLB (depending on your operating system)...if you just have all the files from the ZIP next to each other, with no folder structure, the patch VI will error out.  This happened to me more than once, and it was always because I accidentally just dragged all the files out of the ZIP onto my Desktop instead of actually "unzipping" them into the proper folder structure...I believe the readme for the patch mentions this issue.
    Let me know if this suggestion works.  For future patches, I'll probably recommend we either include all patch files in a flat structure, or have some error checking code in the patch VI that checks next to the patch LLB if the expected location is not found.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Application crashes when calling DLL built with LabVIEW 2011

    Hello everybody,
    Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
    Thank you in advance.
    #Date: Fr, 16. Sep 2011 16:25:25
    #OSName: Microsoft Windows XP Service Pack 3
    #OSVers: 5.1
    #OSBuild: 2600
    #AppName: PasTA
    #Version: 11.0f2 32-bit
    #AppKind: AppLib
    #LabVIEW Base Address: 0x30000000
    16.09.2011 16:25:26.181
    Crash 0x0: Crash caught by NIER
    File Unknown(0) : Crash: Crash caught by NIER
    minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
    ExceptionCode: 0xC0000005
    N
    0x3072C804 - lvrt <unknown> + 0
    0x3072CBB8 - lvrt <unknown> + 0
    0x7C864191 - KERNEL32 <unknown> + 0
    0x7C83AB50 - KERNEL32 <unknown> + 0
    0x00000000 - PasTA <unknown> + 0
    Attachments:
    error.PNG ‏11 KB

    On that note, you should be able to create DLLs in 2010 and run them with 2011, correct??  In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

  • Reading objects from a binary file works but crashes LabVIEW on exit

    I've been hunting for the source of some crashes on LabVIEW exit and I was finally able to track it down to this. In my application I wrap measurements into objects that I stream into a binary file during the inspection. In another application I read the file again to browse and analyze the measurements. All this seems to work just fine except that the reading part causes LabVIEW to crash once I close the IDE. Built applications don't report any crashes but I am afraid if it might still cause some instability or unexpected behaviour.
    The snippet below represents the writing and reading scheme I use and with which I am able to reproduce the problem every time. I attached the project for testing it.
    Parts from the internal warning report:
    #OSName: Windows 8.1 Pro N
    #AppName: LabVIEW
    #Version: 13.0f2 32-bit
    DWarn 0xEFBFD9AB: Disposing OMUDClass definition [LinkIdentity "Class 1.lvclass" [ My Computer] even though 1014 inflated data instances still reference it. This will almost certainly cause a crash next time we operate on one of them.
    Possible path leak, unable to purge elements of base #0
     The full log is also attached.
    Notes:
    Remember: the reading works without any problems, the crash after LabVIEW exit is what I'm concerned about
    Seems to only happen with classes/objects—not the default LabVIEW Object, though
    Prepending array size or different byte orders make no difference
    The writing is time critical, the reading is not, in case you wish to suggest other options
    Has anyone else run into this? Should I be concerned for the built applications or can this be simply ruled as an IDE problem?
    Solved!
    Go to Solution.
    Attachments:
    test_project.zip ‏16 KB
    lvlog.txt ‏5 KB

    Right off, if you say you can read and write lv objects, try casting your object as a lv object before saving it. The lv object is the ultimate parent of all classes.
    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

Maybe you are looking for