LabVIEW 2009: Installation of scripts VI after Servicepack 1 - no effect

Similar Questions

• LabVIEW 2009 installation, one of MS Office Excel VI is broken

  After installing Labview 2009, one of the MS Office Excel VI is broken. Tried several facilities. The same VI is broken and other screw works very well. What happens on 1 single laptop. the broken VI works fine on other laptops.

  Have you tried to search the forum? http://forums.NI.com/T5/LabVIEW/set-Excel-cell-color-and-border-broken-can-t-build-application/m-p/1...

  Open the Subvi, click the node to invoke that generate the error and select again the same method, it should get rid of the error (do not forget to save changes once the error disappeared.

  Ben64

• LabView Run - Time Engine 2009 installation failure

  Hello

  I have problem to install Labview Run - Time Engine 2009.

  This error occurs:

  Die Installation von NI VC2008MSMs x 86 ist auf Grund of the following Fehlers fehlgeschlagen.

  Auf den Windows-Installationsdienst konnte nicht rarely werden.

  Die kann occurrence, wenn Sie Windows im abgesicherten Modus implement oder der

  Windows-install extension installed ist nicht. Wenden Sie sich an den Support, um Hilfe zu receive.

  (The installation of the NC is VC2008MSMs x 86 has failed due to the following error.

  The Windows Installer Service could not be accessed. That may occur when you run

  Windows in safe mode or Windows Installer is not correctly installed.

  Contact your support team.)

  I tried to reinstall and reregistrate program windows installation, I tried to upgrade the installer from windows to version 4.5

  I installed Microsoft Visual C++ 2008 Redistributable-x 86.

  IM runing Windows XP Service Pack 3

  (Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427 - 1636_ Service Pack 3))

  I have no problem installing other programs, for example, can I install runtime labview 7.1.1.

  So my question is:

  How do to solve this problem, how can I make a Labview Run-Time Engine 2009 installation on this computer which gives me the error described at the beginning?

  Best regards

  Simon

  Now I have solved my problem.

  The solution was to raise and to build my code in Labview 2010.

  But the question of the installation contains yet to install LabView Run-Time Engine 2009.

  I don't think it's associated Windows Installer, because I can install everything on my computer in addition to LabView Run-Time Engine 2009.

  I can even install LabView Run - Time Engine 7.1.1 and LabView Run-Time Engine 2010.

  So, my solution was to jump using LabView 2009 and install LabView 2010.

  Best regards

  Simon

• My compiled program crashes after the first run (LabVIEW 2009)

  I have a compiled program created with LabVIEW 2009 which, in the first round, once the computer is restarted, works fine but after discontinuation of the program, it will not work properly.

  The program uses a compiled Launcher to dynamically activate a set of VI containing the expectation driven by State Machines (QDSM).  Begins subsequent program launcher module appears fine, and his progress bar shows that she starts each of the VI.  Once the Launcher is complete it removes memory launched Dynamics VI and caressed.  The spear that do not reach the main UI that VI is barely long enough for the observer to see (if there is one) then stops.  The program then went from memory I can say.  There is no process in memory or anything.

  Also, when I try to run the installed version of the exe file on a computer with installed 2009 development environment I get this behavior consistently successful launch once again.

  In both case, my program does raise all errors (that are connected), or runtime generates everything I can see.  Also, when I run my program in the development environment the program does that way.  He has no problem at all.

  I have used this style of architecture front of LV8.6 with all the problems.  Can anyone suggest some possible solutions or even a few debugging tips?  I've never had a problem that I could not duplicate in the development environment, so I'm not sure how to start to attack my question.

  Thanks for any help.

  Jason

  

  I solved the problem I think that (at least with regard to the tests on this point revealed).   After that I added the possibility to connect the past States to of the QDSM, I was able to determine that the program was 'plant' after that I dynamically closed the Panel front of the Launcher.  My program is designed to close the Panel before the pitcher, then pop up the façade of the main user interface.   My EXE is inspired to hold the Launcher with my other files QDSM kept outdoors in specific directories.  What seemed to be happening is that when Launcher closed its façade and before UI opening upward the runtime engine decide since it is y no Windows Open he was closing down.  It's my guess on what might happen any way.  I modified my code to change the Launcher window to hidden and delay for 1/2 second to give a chance to fully start running to the main user interface.  This will correct the problem, or at least worked around her.  If someone out there can explain me exactly what is happening that I sure would appreciate it.

  Thanks for all the help that those of you who responded.  Your advice has been very beneficial and certainly led me to a faster resolution.

  Jason

• Switch Executive stops working after LabVIEW 2009 installed.

  I just installed LabVIEW 2009 and now Switch Executive 3.0 does not work.

  NISE open session vi returns 0 instead of the valid session ID. It does now with LabVIEW 8.6.1 too.

  Everything looks OK in MAX.

  Any suggestions?

  Hi Pirkola,

  I'll try to replicate that.  I understand it is a returned 0 for a session ID.  Is there an error returned as well?

  Thank you!

  Chad Erickson

  Switch Product Support Engineer

  NOR - USA

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• How to interface a simple way using LabVIEW 2009 simulink model and SIT?

  Hello

  I finally found a way to use a template simulink with LabVIEW and the Toolbox to SIT, but I'm not satisfied.

  If you have any suggestions, the link of resource that I missed, please do not hesitate to answer

  Note that I do not know much about simulink, so that is my question seems stupid, let me know what

  Software configuration

  OS: Windows (not an RT target)

  LabVIEW 2009

  SIT 2009

  question 1: interfacing the model DLL (mapping considerations) with a driver VI

  We have created a model of DLL by using the 'Workshop in real time' tab in simulink.

  In LabVIEW, launch us the tool 'SIT connection manager' and try to use the DLL with a driver VI by mapping the e/s model for screw/lights orders.

  The fact is that I fail to connect to my controls/indicators VI/o model because they do not appear in the mapping dialog box.

  The simulink single objects that I managed to map are "constant" and "test points" while I need to edit the template simulink itself (example below)

  

  Are in e/s model, not considered as part of the parameters of the model? (this could make sense because the mapping says in fact that it operates on "model parameters")

  Is it possible to link the IO model VI commands/lights?

  Note:

  -the "configure HW i/o mapping" dialog box allows me to map model e/s with e/s HW...

  -The examples also use these "constant" and "test points".

  2nd question: use of direct screw SIT

  I tried to use the DLL directly with the screws SIT (code example below)

  This kind of code works well on another project (target of 8.0/RT LV) but not on the current project (LV 2009/Windows)

  The second stage of the model never ends:

  -0-index of the loop works as expected (model doing its job).

  -index of the loop 1 starts normally, but execution is stuck in the 'SIT scheduler.vi.

  Then I have no choice that to kill LabVIEW ("Reset screws" windows appear if I try to stop/close them).

  

  Is there a reason that I do not see what explains this behavior?

  Thanks for reading.

  Any help appreciated.

  Kind regards

  Hello

  I spent some time analyzing the VI driver as you suggested.

  Here are my findings.

  Question 1: the SIT connection manager does not pass to the model SW controls/indicators. Only, it allows the user map HW AIs/AOs.

  The only solution I found (to have a SW - for example a shared variable - object that is mapped to an input/output model) is to customize the VI driver that is scripted by the SIT Connection Manager ("_Baserate Loop.vi" in the flat sequence structure named "read code")

  Question 2: after spending some time in the VI driver, it seems that the VI to call right is not 'SIT scheduler.vi' but 'If SIT take model no time' (which uses the other as a Subvi)

  

  My conclusions are correct? If I use the API in the wrong way, please let me know.

  Kind regards

• MathScript node: an error internal mathscript: 64-bit LabVIEW 2009

  Hi people.

  I have an installation now LabVIEW 2009 9.03f, Vision and Advanced Signal Processing Toolkit, all 64-bit versions on a new computer, so that I can convert a code from 32 to 64-bit.

  I tell myself that I will address the errors one by one and this is the first.  I have a VI with mathscript node and the VI, who instructed and ran very well in the 32-bit environment, is now broken and giving the error "mathscript node: a mathscript internal error."  My main concern - is mathscript unsupported in LabVIEW 64-bit right now?

  I enclose the VI.  Any ideas are appreciated.  I need to get this working.

  In addition, NEITHER is there a special forum of 64-bit we should publish in the future, or create to post on?

  Sincerely,

  Don

  2009 help

  LabVIEW MathScript is a language based on text that you can use to write scripts and functions. You can process the scripts using LabVIEW MathScript in the Window of LabVIEW MathScript or a MathScript node. When you create a LabVIEW MathScript, you use data types supported.

  The MathScript syntax is intuitive and logical syntax essentially based on the standard mathematical and computer programming terms, mandate of widespread and common use truncation or descriptive abbreviations and concatenations of standardized terms. The Window of LabVIEW MathScript and MathScript nodes are able to process files that you create using the MathScript current syntax and, for backward compatibility, files that you created using legacy MathScript syntaxes. The Window of LabVIEW MathScript and nodes MathScript can also process some of your files using other textual syntaxes, such as files that you created by using the MATLAB® software. Because the MathScript RT Module engine is used to treat the scripts in the Window of LabVIEW MathScript and MathScript node, and the MathScript RT Module engine can't stand any of the syntaxes, not all existing text scripts are supported.

  (64-bit LabVIEW) LabVIEW MathScript is not supported in LabVIEW (64-bit).

• Remove labview 2009 without using Add/Remove program

  Hi all

  I have problem with the removal of LabVIEW 2009.

  I deleted some folders in the C drive, folder OR.

  Now I can't start my LabVIEW 2009 and it does not appear in my Add/Remove Programs list.

  I tried to delete all the folders and files in the C drive under folder OR, but the pop out error message shows that I don't have the authority to do so.

  So, how can I remove it completely?

  I had intended to reinstall LabVIEW 2009 after that I have completely removed.

  Very much appreciate your help.

  That's why I say try to reinstall LabVIEW. He could just do a repair of your installation. Then, you can use Add/Remove programs to uninstall completely.

  But when you uninstall completely there will be folders OR remaining. These are things like user.lib.

  Have you tried to reinstall the runtime?

  One last thing. I don't know how you got your installation so messed up, but remember that if you build a Setup program you should not install on a system with the development environment. There are so many things that can go wrong.

• LabVIEW 2009 32 bit does not not on xp 64-bit

  Hi all

  I tried to upgrade to LabVIEW 2009 LabVIEW 8.6 on the XP machine 64-bit windows. After about a deletion of 2 hours of installation 8.6 and later of LV 2009 it turns out that the device drivers are not compatible with a 64-bit computer. At the launch of LabVIEW 2009 (32-bit), an error box is displayed indicating that it is corrupt or missing files and to fix this using the control panel etc. I tried this and still the same error occurs and LV refuses to start.

  All license files are correct and the components are enabled.

  Someone knows how to fix this? Or do I go back to 8.6 and cancel my subscription?

  Second, I use a firewire camera and was informed that neither IMAQ legacy are more supported and go to ni.com/ifo and enter legacy1394 to see how to download drivers for that etc. I find myself on a page that says no "authorized".

  Any help appreciated gratefully.

  Dear Leeser

  Since 2006, National Instruments has annually released a new version of LabVIEW each month of August in order to establish a more predictable release schedule. This allows users to better plan the new developments and improvements for future versions of LabVIEW. In addition, this year, NOR changed the name of the product to LabVIEW + year (for example, LabVIEW 2009) reflecting the year of the release and setting the stage for future annual editions of LabVIEW. Please see the following site for more information on this:

  http://www.NI.com/LabVIEW/product_lifecycle.htm

  What about Windows XP 64-bit it is not officially supported by hardware or software drivers. For a list of drivers who have been known to work, please see the link below:

  http://Joule.NI.com/nidu/CDs/fn/p/SN/N19: Windows.7809/lang/en

  Now with Windows Vista x 64 is a 32-bit compatibility of excellent "windows on windows" mode which allows our drivers work correctly. In regards to LabVIEW 2009, there is now a dedicated 64-bit version is recommended for use with 64-bit operating systems. Yet once Windows XP 64-bit is not officially supported.

  More details on the compatibility of Windows XP x 64 is located in the following article:

  http://digital.NI.com/public.nsf/allkb/C4EC0C87B6D70AA886256E61006568C8?OpenDocument

  I hope this helps to clarify some things.

  Kind regards

• LabView 2009 Service Pack 1 does this cause a problem with the MAthScripts for lo

  All,

  I just installed Service Pack 1 for Labview 2009.  All of my code that loops in my MathScripts now lets my MathScripts does not compile.  Have a clue what I do?

  Thank you

  Rich

  Windows XP (32-bit)

  LabView 2009 uninstalled, reinstalled after you have removed all files related to 2009.  SP1 installed, then applied for LabView and MathScript.

• does not by default the tab control in LabVIEW 2009

  I have a tab control in my LabVIEW program. I put the default value of the three page tab control. In older versions of LabVIEW, when the program opens, it opens with the display of page three. Prefect! But now in LabVIEW 2009, it opens to 1 page view. I tried to adjust the default time and again, but it is enough to open with the display of page three. Looks like it's broken in LabVIEW 2009. (I know that I can get around that, but apparently botched when the program opens on page 1 and jerks on on page three.) And change the order of pages would break the code. I don't do that.)

  To make the solution more smooth, you can uncheck see the façade when called property of vi and show it programatically after that you put on page 3.

  Felix

• Is the tool provided with the works of Labview 2009 with LabVIEW2010

  Hello

  I use currently LABVIEW 2010 want to know about toolkit provided with the dvd of LabVIEW 2009

  is compatible with the labVIEW 2010

  Thank you

  Check out this link.

  http://www.NI.com/support/LabVIEW/lvtool.htm

  If the required toolbox does not "(ou supérieur) ' after the requirement for 2009, or specifies LV2010 it is not compatible."

• LabView 2009 Web server crash

  Hi all!

  Here's a simple VI containing any control, functions or library in LabView 2009 f3.

  

  Web server settings are default. After the tools-> operation of another PC Web publishing tool we are connecting to this Panel (IE6 for example) and put a finger to the F5 not lifting.

  Web page with the VI is very refreshing.

  There are 3 results.

  1. in DevEnv: LabView die.

  2. in DevEnv: need to restart LabView for charging Web server and restore connection.

  3. in App.exe: die

  4. in App.exe: LabView interpreter loose some time-cycles in the cases where they exist, but connection stored.

  5. in App.exe: but lost connection application work.

  Is this normal? Are there settings in Web server to avoid this situation.

  
  

• LabVIEW 2009 SP1 crashes when moving large selection with the arrow key

  If I select a lot (10 or 15) diagram components and try to move some distance with the arrow button, I'm often a program crash.  Because a reduced number of components seems to hang after a longer distance traveled, it looks like some sort of buffer overflow error.  I don't see this problem when you use the mouse to move selections.

  I checked to make sure I have the latest version of the video driver for my NVIDIA Quatro FX570.  I also tried to work with no hardware acceleration and no handset, written.  What happens on Windows XP SP3 with all current updates.

  It became so bad that I have to do a save as every fifteen minutes to avoid losing data.

  Why not use my mouse for all movements?  Because it is not as specific and not so easy to limit to only one dimension of the movement.   My hand is not as stable as it once was.

  I'm hoping someone will have a suggestion that will clear up this problem.

  As I have indicated, I had the same problem with 8.5 and just DID a new install of Labview 2009.

  Since it is possible that my three monitors configuration, which of course requires more memory video, may be at the origin of the problem, I am satisfied with workaround by dragging the objects closer to their final destination and then using the arrow keys.

  Three monitors are ideal for the front, block and help/Internet/probe damaged.  When I got to work in the field with a single monitor, I felt severely handicapped.

  You can consider the issue closed.

  Thank you for trying to reproduce the failure.