LabVIEW 2013 Patch f2 update problem

I have installed LV 2013 (13.0.1f1) Patch f1 (32-bit). I tried to install NI LabVIEW 2013 f2 Update but I got error message: "NI LabVIEW 2013 must be installed before you can install this update."
So, why it doesn't recognize installed app?
BR,
Jick

There is a difference between
LabVIEW 2013 f2-Patch and
LabVIEW 2013 SP1 f2-Patch
Choose the right one.

Similar Messages

  • 11.1.0.1.6 Patch Set Update problem

    Hi guys!
    I have problem with 11.1.0.1.6 Patch Set Update for Oracle Management Service.
    After i have installed OMS on my RHEL 5.2 server together with agent (Repository is on remote host) i have decided to install recommended patches as well.
    I have followed PSU install procedure, so i have first run
    [oracle@gc ~]$ opatch lsinventory
    Oracle Interim Patch Installer version 11.1.0.9.6
    Copyright (c) 2012, Oracle Corporation. All rights reserved.
    Oracle Home : /opt/oracle/Middleware/oms11g
    Central Inventory : /home/oracle/oraInventory
    from : /opt/oracle/Middleware/oms11g/oraInst.loc
    OPatch version : 11.1.0.9.6
    OUI version : 11.1.0.8.0
    Log file location : /opt/oracle/Middleware/oms11g/cfgtoollogs/opatch/opatch2012-04-12_10-24-52AM_1.log
    OPatch detects the Middleware Home as "/opt/oracle/Middleware"
    Lsinventory Output file location : /opt/oracle/Middleware/oms11g/cfgtoollogs/opatch/lsinv/lsinventory2012-04-12_10-24-52AM.txt
    Installed Top-level Products (1):
    Oracle Enterprise Manager Grid Console 11.1.0.1.0
    There are 1 products installed in this Oracle Home.
    Interim patches (3) :
    Patch 13248190 : applied on Wed Apr 11 11:41:33 CEST 2012
    Unique Patch ID: 14355092
    Created on 12 Jan 2012, 03:49:58 hrs PST8PDT
    Bugs fixed:
    10122270, 9930146, 9836815, 8638231, 9963717, 9543582, 9276193, 9911851
    9506062, 10361050, 10218699, 12657533, 10372559, 12908384, 10246310
    10418856, 10313110, 9500255, 10100210, 9462098, 12799578, 9747671
    10279457, 10400454, 9562462, 9570911, 11727299, 10638043, 9937784
    7340407, 9575427, 10204587, 10177562, 9935898, 12833678, 11809598
    9446422, 12545526, 9586285, 9548105, 10201753, 10353911, 9308029
    9534200, 12669853, 9184007, 9684768, 9686658, 9341486, 10122223, 11683765
    9241402, 9838084, 9849222, 9903280, 9888852, 9478844, 9558026, 9604064
    11728549, 9342290, 10410743, 10020408, 9151748, 9953045, 9221090
    9559264, 10264990, 10036568, 10065631, 9804442, 9576468, 10372513
    10108019, 9928480, 9535382, 11726378, 10114291, 10278756, 9892455
    9476313, 11900474, 9876632, 9386076, 12552334, 11076661, 9803798
    10408402, 10043790, 10307099, 9965939, 9646681, 9390531, 9662869, 10333908
    9544428, 9489355, 10190000, 9706552, 11890440, 8859562, 11808680, 12758241
    8234692, 9723689, 9734399, 9504581, 9558551, 9874327, 9313608, 12423703
    12360281, 12693879, 11901582, 12654105, 12536173, 10307544, 13248190
    9537948, 8930257, 10118817, 11696545, 9919614, 10404792, 12734089
    10636783, 9541036, 9821890, 12738517, 10270073, 10257014, 10223586
    10213026, 9952713, 9491872, 9507363, 10015330, 9726686, 10042225
    Patch 9367763 : applied on Tue Apr 10 14:03:38 CEST 2012
    Unique Patch ID: 12252189
    Created on 1 Mar 2010, 22:30:36 hrs PST8PDT
    Bugs fixed:
    9367763
    Patch 9207217 : applied on Tue Apr 10 14:03:30 CEST 2012
    Unique Patch ID: 12151251
    Created on 27 Jan 2010, 15:49:36 hrs US/Pacific
    Bugs fixed:
    9207217
    OPatch succeeded.
    [oracle@gc ~]$ echo $PATH
    :/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/X11R6/bin:/usr/kerberos/bin:/opt/oracle/agent11g/bin:/opt/oracle/oms11g/bin:/opt/oracle/Middleware/oms11g/bin:/opt/oracle/Middleware/oracle_common/OPatch
    [oracle@gc ~]$ echo $ORACLE_HOME
    /opt/oracle/Middleware/oms11g
    after this checks i have stopped oms server and successfully executed opatch apply command.
    Then next step is to connect to rcuJDBCEngine as SYSMAN and run the apply.sql script as follows (in my case):
    [oracle@gc 13248190]$ pwd
    /opt/InstallGrid/Oracle11g/11106_patch_32bit/13248190
    [oracle@gc 13248190]$ /opt/oracle/Middleware/oms11g/bin/rcuJDBCEngine [email protected]:1521:gcoemrep JDBC_SCRIPT apply.sql $PWD $ORACLE_HOME
    Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String index out of range: 0
    at java.lang.String.charAt(String.java:686)
    at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:386)
    at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:634)
    at oracle.net.ns.NSProtocol.connect(NSProtocol.java:208)
    at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:966)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:292)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:203)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:154)
    at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:259)
    at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:142)
    at oracle.sysman.assistants.common.dbutil.jdbc.ConnectionHelper.getConnection(ConnectionHelper.java:61)
    at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.getConnection(JDBCEngine.java:889)
    at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.connect(JDBCEngine.java:417)
    at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.main(JDBCEngine.java:1982)
    maybe my variables are not good?
    Any suggestions?
    Edited by: rootsman on Apr 12, 2012 1:36 AM

    Hi Rootsman,
    There are 2 possible causes for this issue.
    1. Because an incorrect syntax was used to apply the SQL part of the patch. If the password for the user is not added in the command line, the rcuJDBCEngine will fail. The rcuJDBCEngine will not prompt for the password (like sqlplus does), if it is not provided on the command line.
    - Incorrect syntax
    +$ORACLE_HOME/bin/rcuJDBCEngine sys@<host>:<port>:<SID> JDBC_SCRIPT post_install_script.sql $PWD $ORACLE_HOME+
    - Correct syntax
    +$ORACLE_HOME/bin/rcuJDBCEngine sys/<password for sys>@<host>:<port>:<SID> JDBC_SCRIPT post_install_script.sql $PWD $ORACLE_HOME+
    2. This problem may also occur if the password has been supplied on the command line but includes some special characters.
    The solution is to stick to the syntax described in the README.txt which states to enter the sys password on the command line:
    +$ORACLE_HOME/bin/rcuJDBCEngine sys/<password for sys>@<host>:<port>:<SID> JDBC_SCRIPT post_install_script.sql $PWD $ORACLE_HOME+
    If there are any special characters in the password, enclose the password in single-quotes ' '. For example:
    +$ORACLE_HOME/bin/rcuJDBCEngine sys/'<password>'@<host>:<port>:<sid> JDBC_SCRIPT post_install_script.sql $PWD $ORACLE_HOME+
    Hope your problem gets resolved.
    Thanks,
    Cris

  • Labview 2013 error 1304

    Hi
    I have the latest  version of Labview 2012 on my computer. It has been running well now for over 6 months. I now wish to update that with Labview 2013
    First question do you have to remove Labview 2012 and two modules first before you install Labview 2013?
    Problem 1.  Within a few minutes into the installation process l obtain error 1304. When reviewing the file location reported in the error popup, the file states its a Labview 2013 template. I do not how that occurred but l have installed the last critical updates for Labview 2013 including the NI 488 driver updates for Labview 2012
    Problem 2. If you ignore error a second error box pops up with no code.
    A month ago l contacted our local NI support but they could not help. I have been away for a month and now l was hoping to have the bug fixed. But it still occurs. I could not find anyone who has had this error in the search for errors. The closest was error 1303
    So at the moment l cannot install Labview 2013.
    Has anyone had this problem. The word file illustrates the pop up messages.
    Regards
    Wetland
    Attachments:
    Labview 2013 installation error.docx ‏60 KB

    Hi
    Thank you for your response. I am downloading Labview 2013 onto my own home computer using the supplied DVD.  I have full administrative privileges.
    When l get Labview working at home l then download it at work. I cannot afford to have Labview not operating at work.
    Last night l received a critical update for Labview 2013 patch f2. The update program seems to think l now have Labview 2013 installed. If l get no solutions to the problem l will install the patch just to see if that will fix the problem.
    At the moment it seems that no one else is having the same problem since you are the first to respond. Thank you for your information
    Regards
    Wetland

  • Labview 2013 report generation toolkit word 2010 insert table problem

    Hi,
    I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
    I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
    It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
    I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
    Can anyone help/shed some light on this? 
    Thanks in advance,
    Dan.

    Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
    Attachments:
    Word_Insert_Table.vi ‏30 KB

  • Looking for a site that shows problems with windows patches or updates.

    Looking for a site that shows problems with windows patches or updates...so I know what not to install.
    Plenty of sites list and summarize individual patches, I want one that consolidates problems and complaints so I can better assess the risk. Currently I'm waiting to install patches several days and doing google searches. That works, but I'd rather find a place
    that does it with expertise.
    Which forums would be best to look for such problems.
    Thanks in and advance for suggestions

    Hi,
    I agreed with Cyber and Rick.
    Windows update helps to keep your PC safer—and your software current—by fetching the latest security and feature updates from Microsoft via the Internet.
    Although there might be some problems when installing it, Windows update is not the one to blame.
    For troubleshooting Windows updates, if needed:
    Fix Microsoft Windows Update Issues
    http://support2.microsoft.com/gp/windows-update-issues
    Best regards
    Michael Shao
    TechNet Community Support

  • FPGA FlexRIO SCTL LabVIEW 2013 Compilation Problems

    Hi,
    I have an FPGA FlexRIO (7962R) VI that interfaces to a 6585 LVDS board that consists of a SCTL running at 200MHz and using a Xilinx Coregen FIFO.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    The Xilinx FIFO is probably irrelevant as I have tried cloning the VI and removing the FIFO and still get the same problem.
    Any ideas, things to try or solutions? 
    Thanks,
    Dave
    David Clark
    CLA | CTA
    CLA Design Ltd
    Hampshire, England

    Have you tried optimising the Xilinx compiler for Timing?
    You can't modify the Xilinx compile options of a FlexRIO target.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    What compile error are you getting? Does not reliably mean that sometimes it does compile correctly? Can you upload a simple example of a piece of code that works in 2012 but not 2013?
    National Instruments
    FlexRIO Product Support Engineer

  • LLB file problem (Labview 2013)

    I have made labview project that builds a LLB file.
    It contains my "test VIs"(auto-populating dir) and all Dependencies(user.lib, vi.lib....)
    Building the LLB file goes fine.
    But when i try to run the "test VIs" in the LLB file using an .Exe that uses "open VI reference -> invoke node "Run VI" i get a broken arrow and error 2002200....
    Opening the "test VIs" in the LLB with Labview, the path for some of the sub VIs do not point to the LLB.  It still points to the original VI (in user.lib, vi.lib....) causing the "test VI" to not be executable . ("test VIs" where all sub VIs points to LLB woks)
    what am i doing wrong/how do i fix this?
    /J

    After some investigation.
    Using Projec Explorer building a "Source Distribution" LLB Then calling my "test VIs" in the LLB file using an .Exe that uses
    "open VI reference -> invoke node "Run VI" i get a broken arrow and  message  "VI has an error of type 2002200. The full development version of LabVIEW is required to fix problem"
    The functions are in "Programming->File I/O-> Configuration file VIs" menu
    (Directory C:\Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\Utility\config.llb\)
    Below VIs generates the error
    Get Key Names.vi
    write key.vi
    Remove Key.vi
    Remove section.vi
    Read key.vi (boolean)
    Read key.vi (Double)
    Read key.vi (I32)
    Read key.vi (path)
    But these works in llb
    Open config data.vi
    Get section names.vi
    Read Key.vi (string)
    Close config data.vi
    I cant find any reason why some works and some dont.
    is there someone how knows how to fix this?
    /J

  • I have a iphone 5, purchased dec 2013. Had no problems with downloads and syncing until yesterday. I updated to the latest 7.1.1 and now my purchased ringtones have bern deleted from ....Try providing more room for peoples questions ...

    I have a iphone 5, purchased dec 2013. Had no problems with downloads and syncing until yesterday. I updated to the latest 7.1.1 and now my purchased ringtones have bern deleted from my library and my phone, Where are they ????
    I have gone to download again and told i can purchase them again
    But there is no option to download all ready purchased items..
    Can you provide an explanation and solution .

    Are you using the same Apple id as used to originally purchase them
    and are you using iTunes on a PC/Mac

  • Report Generation Toolkit failure with Win 7 and Labview 2013

    I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files.  If I try to run the New Report.vi with report type Excel selected I get  error -2146777998.  Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error.  Selecting Standard Report or HTML also run without errors.
    I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
    Solved!
    Go to Solution.

    I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report  by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt.  The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
    Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

  • Office 2013 patches not installing

    I am trying to install some updates for office 2013 through Windows update and I keep on getting the error message 80070663 when installing these (8 so far). Other windows patches
    install fine.  I am running Windows 7 Pro in a Domain environment and am a domain admin running these with full admin privileges.
    I have tried just about every fix suggested in every other post 
    - Rebuilding the Windows Update environment
    - Running Sfc (no errors)
    - Running the relevant Fixit's (no issues or repairs found)
    - Running Chkdsk Scan (no errors)
    - Downloading the patches and trying to run them manually (They error out with a applicability test error)
    - Running Antimalware and similar scans (nothing)
    - Running a repair on Office 2013 (errors out with a 5 error towards the end of the repair - faulting module msvcrt.dll fault offset 35e1
    - Downloading and reinstalling the C++ library re-distributables (i.e. msvcrt.dll)
    Not this is only on the Office patches and not any other patches which suggests an office problem rather than a Windows update issue.
    Anyone got any thoughts - There was a suggestion that this might be caused by missing update packages...

    Hi,
    Apologize for the late reply.
    Regarding Office issue, have you tried Repair Office programs from control panel?
    Follow this guide:
    Repair Office programs
    Change recommended update and diagnostic settings
    Further, since this is more related with Office, it is recommended to ask inthe office forum for a better assistance:
    Microsoft Office IT Pro
    http://social.technet.microsoft.com/Forums/office/en-US/home?category=officeitpro
    Best regards
    Michael Shao
    TechNet Community Support

  • Slow LabView 2013

    Hi
    I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
    For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
    If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
    I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
    If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
    If I run for example, excel 2013 it does not seems slow.
    Do you have any suggestions ?
    Regards
    Solved!
    Go to Solution.

    EDGAR_PLATRONICS wrote:
    Hi Yamaeda:
    I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
    A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
    Actually it worked correctly in labview 8.5 but i converted to LV 2013.
    I will research about transparent borders overlapping.
    Hi Altenbach:
    17% is overall. 3 cores are high % than others.
    The problem is at edit mode and also when I run program.
    Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
    When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
    By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
    I am using 2 monitors in my PC. One to display LV panel and one for LV code.
    I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • Bug in LabVIEW 2013 RTETT Download

    I've called this in to NI, but am posting it here in case you've downloaded LabVIEW 2013 before they fix the problem.
    Downloading the toolkits from ni.com/trylabview usually is a three-step process.  First, you download a "downloader", a small program (154 KB) that manages the download of the Installer.  When you run the Downloader, it downloads the Installer, usually as an executable ZIP file.  The final step is to run the Installer, which first unzips itself into a folder (by default, C:\National Instruments Downloads), then executes the unzipped Setup.exe contained therein.
    There is a (usually) consistent naming convention to these various files.  For example, the files for LabVIEW Real Time are 2013RealTime-Eng_Downloader, 2013RealTime-Eng (the Installer), and LabVIEW RT (the name of the folder that the Installer "unzips" into).  I've downloaded 8 modules, and (with the exception below) they all follow a similar pattern.
    The "bug" is in the Real Time Execution Trace Toolkit (RTETT).  The Downloader is 2013RTETT_downloader, and it brings in 2013RTETT as the Installer.  However, the Installer is set to unzip into LabVIEW RT, the same folder that is used for LabVIEW Real Time.  The "fix" is to change the name of the UnZip folder to LabVIEW Real Time Trace Execution Toolkit (this name is analogous to the LabVIEW Desktop Execution Trace Toolkit name for 2013DETT).  Alternatively, you can run one installer, rename the folder, run the other, and adjust the folder names to your liking.
    Bob Schor

    I am using Windows 7 (x64), fully patched.  As I understand it, the purpose of the Installers is two-fold -- to extract themselves to individual folders (by default in C:\National Instruments Downloads) and then to run their respective Setup executable to actually install themselves.
    I have not (yet) installed RTETT, but I have installed LabVIEW RealTime.  However, in the interest of time-efficiency, I first did downloads of all of the elements I wanted to install (which included both RealTime and RTETT), ran the Installer, but only the "extractor", then planned to run the actual installations from the folders in the Downloads folder.  That's when I discovered that the folder labelled LabVIEW RT did not contain LabVIEW Real Time, but LabVIEW Real Time Execution Trace Toolkit.  Thinking I'd forgotten to extract Real-Time, I tried extracting it again, and discovered that it and RTETT "shared" the same folder in NI Downloads.  I fixed the problem for myself by manually relabelling the folders so one was LabVIEW RT (for LabVIEW Real Time) and one was LabVIEW Real Time Execution Trace Toolkit.  With these distinctive names, I'm much less likely to install "the wrong thing".
    I consider this a "bug", as NI clearly (and logically) intended for the different Toolkits to be downloaded into their own folders.  I mentioned it here in case others faced a similar confusion of "Where did my download folder go?".  Note that if you only download Real Time or only download RTETT, the "reuse" of the folder name won't matter to you.
    BS

  • Running Datasocket in labview 2013 open labview runtime engine 7.0

    Hello All,
    I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
    but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
    When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
    This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
    This is actually annoying and i doubt how things will work when i make an executable. 
    Need help. 
    Is this due to datasocket version installed... how to resolve this.
     

    Hi phil,
    That is interesting that you were unable to find the offending key that the installation is having trouble with.  Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys.  Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers.  You may want to try one of those to see if you can find the key and give it the proper permission.
    As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine.  One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there.  If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want.  Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer.  As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much.  Please try some of these suggestions out and let me know how they work out for you. Thanks!
    Regards
    Noah R
    Applications Engineering
    National Instruments

  • LabVIEW 2013 SP1 Compile Worker Fails

    Hello,
    after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
    The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
    When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
    At the Moment I hav not Idea what to do. Perhaps someone can help.
    What does I have to do to convert my system back to the Version 2013?
    Attachments:
    FehlermeldungCompileWorker.jpg ‏41 KB
    ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

    dfschunk,
    Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
    In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
    Go to Control Panel >> Programs and Features and select National Instruments Software. 
    This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
    Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
    After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
    Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
    Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

  • LabVIEW 2013 locks up while loading new VI

    When attempting to load an existing VI while a project is open and the new VI caues conflicts LabVIEW shows a warning window.  If LabVIEW has a loading window open when the conflicts message appears then LabVIEW becomes unresponsive on all of its windows except for the help window.  The buttons appear to function but nothing happens.  I can move the Loading ... window around but none of the others.  I left it for 30 minutes yesterday (different VI that I was trying to load) but no joy.  I had to kill LabVIEW and lost my work.  Same situation today.  These were both examples I downloaded from this forum.
    How can I avoid this problem in the future?
    Thank you.
    See attached image
    Windows 7 64-bit
    LabVIEW 2013, updated to current
    Attachments:
    LabVIEW Hang.jpg ‏83 KB

    The problem has reoccurred 3 times this morning (see attached image for the 3rd lockup).  All with local files.  I have a LabVIEW project open, when I open a VI outside of the project (using windows explorer) I sometimes get the mxLvGetFilePathBatch.vi loading message and then LabVIEW freezes.  mxLvGetFilePathBatch loading message is the last apparent LV action every time before the lockup  This happens when the loading window opens while another LabVIEW related popup is showing.  See attached image where I was trying to examine a vi that is in my user.lib while LabVIEW was open.  In this case the VI is referenced by the project (strict static vi reference) but that is not always the case.  The first two lockups this morning were with nonproject VIs that use some of the same user.lib VIs as the project.  My user.lib is at the default location in the LabVIEW program directory.
    The attached txt file is in html format, it is a table listing my installed packages.  An export from JKI package manager, massaged with excel for readability.
    I would appreciate any ideas on how to proceed with debugging this problem.
    Attachments:
    7-15-14_3rd_hang.jpg ‏50 KB
    InstalledPackages.html.txt ‏10 KB

Maybe you are looking for

  • How do I move Photoshop Elements from one computer to another?

    I would just like to clarify first of all that I don't have a disc, and I didn't download it - it came with my computer when I bought it. I've got the serial code and everything, but I can't find a way to download the Photoshop Elements trial so I ca

  • Unexpected value matrix(1,0,0,1,NaN,NaN) parsing transform attribute Anychart

    We are running Oracle Apex 4.2 and whenever a user creates a new session,  the chart on the home page shows the No Data Found Message. However, when you refresh or submit the page, the correct data and rendering appears. On the initial page load, the

  • HT201077 I need to stop photos from syncing to the ipod touch how

    How can I find the  menu where you can choose what sync's to the ipod touch?  I cannot find it with the "new" set up.  I need to stop the photos from my computer from moving to the ipod touch.

  • Field grouping in BP

    Dear Gurus, I am new to IS media, While creating BP, in Sales and Distribution tab, the Sales area data fields are in display mode. I tried changing through field group settings from Cross applications, i was not able to identify the exact way. Is th

  • /SDF/HANA_BW_SIZING

    Hi, We are performing the sizing required to migrate our BW system to HANA and in this regard when we executed the report /sdf/hana_bw_sizing it displayed : 1. ABAP size Row store 2. ABAP size Column store What does the word ' ABAP' in the above mean