LabVIEW 2009 launches with errors

Hi Folks,
LabVIEW 2009 launches with errors now everytime I open it.  A window appears showing an error list with nothing in it, with a close and show dialog box (hangs with hour glass).  Neither option is possible since the window self closes in about two minutes.  It's a little frustrating since it adds to my loading time everytime I launch it.
Any suggestions other than unistall/install process?
Windows XP Professional 2002, SP3
Labview 2009, Mem Alloc 39125K, TCP Server inactive, Version 9.0 (32bit)
Regards,
-SS

Hi!
The exact sme thing happend to me. But for me it was on the LV2010 version. Just suddenly it started to launch everytime I opened LV. After a re-installation of LV it was gone. 
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway

Similar Messages

  • Mail quits on Launch with Error -2857

    Hi,
    didnt use Mail for some days and now I cant launch it anymore. Im on 10.5.5 and also have Entourage 2008 and Xcode installed.
    I repaired permissions tried starting with shift and moved my Preferences nothing helped.
    I get no Mail Crash-Report but in Console I see the following :
    14.10.08 11:19:23 [0x0-0x48a48a].com.apple.mail[18744] /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp[187 44] Launch failed with error code -2857 (cfragCFragRsrcErr) for application /Applications/Mail.app/Contents/MacOS/Mail
    14.10.08 11:19:23 com.apple.launchd[140] ([0x0-0x48a48a].com.apple.mail[18744]) Exited with exit code: 215
    Anyone knows whats happening here ?

    Hi webgonzo
    I am not sure what happened but my guess is the application has lost some needed data to run.
    As you have deleted the .plist thus scrubbing your settings, I would suggest you reinstall it from the 10.5 DVD under the Custom Install option.

  • 3 Creative Cloud packages all fail on Launch with Error 16

    Hi,
    I am using creative cloud packager to create applications to deploy using SCCM, which I have successfully deployed in the past.
    I created 3 new creative cloud packages this week, Edge Animate, After Affects and Premier Pro, for the 64bit platform.
    The machines their to be deployed to are Windows 7 SP1 64bit, two machines I tested to were absolutely fine, all other machines tested to have deployed, but on launch all three apps behave the same way. A prompt suggesting I uninstall and reinstall the product. contact Adobe support if the problem reoccurs. Error: 16  (These machines are a mixture of freshly built and established desktops)
    I have tried the steps to resolve similar issues for error 16 in this link http://helpx.adobe.com/x-productkb/policy-pricing/configuration-error-cs5.html
    But they did not resolve the problem, I have recreated the packages and tweaked some settings but this consistently occurs regardless of what I do.
    Any suggestions on what could be the issue or where to look for information to find the cause on the machines would be appreciated, there is not much regarding this scenario available from forums.

    Error 16 is usually related to a permissions issue.
    Try checking the logs, for more information: http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html
    Also, check the installation logs, for any relevant information: http://helpx.adobe.com/creative-cloud/packager/creating-packages.html#Adobe Creative Cloud Packager logs

  • ITunes launched with Error 13005

    Hi, I don't know if anyone has come across this problem before.  I have been using my iTunes library on an external drive so that I can use it between my Mac Pro and my MacBook Pro.  Both macs have Lion 10.7.3 and iTunes 10.5.3.
    Today my iTunes has been working until just now.  When I tried to relaunch it, I had the following error message:
         "The iTune application cannot be opened.  An unknown error occured (13005)."
    I did not install any new apps nor made any changes to the apps other than syncing it with my iPhone and iPad2.
    I tried to start iTune in safe mode and still had the same error message.  I even created a new user account and test it in there.  Still the same error.
    Anyone has any suggestion as to where I should look.  Thanks.

    I had the same problem on my Mac, and I searched throught the forums, tired the advice, but nothing worked. Then (just on a whim) I copied the contents of my iTunes folder to a tempory folder on my desktop, located here:
    [hard drive] > Users > [user name] > Music > iTunes
    Then I relaunced iTunes. It started, which was great, but without any media in my library (of course). Then I compared the old directory and the new directory to see the differences, and I found something simple: my iTunes Library.itl file didn't have the extension [itl] (it was simply called "iTunes Library"). So I recopied all my files back in, added the extension on to the file name, and iTunes worked.
    I'm not sure if this will work for you, but maybe it will solve your problem.

  • Quicktime fails to launch with Error 46 in Windows 7

    "Error 46: Could not load or find the QuickTime ActiveX control," in Windows 7 Ultimate 64bit. Tried uninstall - re-install as administrator without success. I have seen several postings indicating a permissions issue but install and run as administrator should avoid such issues. I also tried running in XP compatabilty mode with admin rights to no avail.  I have yet to see any real solution. I have my Pro license but can't apply it till the appl;ication runs. Any suggestions for a real solution?

    Hmmmm. So FairPlay, BonJour and iTunes didn't update, but QuickTime, AAS and AMDS did.
    This has me wondering about security software interference. If that's afoot, we may be able to get past it by a "download, restart, disable, install" strategy.
    First download and save a fresh copy of the iTunes64setup.exe (installer) file from Apple. (Don't run the install on line and don't start the install just yet.)
    http://support.apple.com/kb/DL925
    Now restart the PC. After the restart, do not open any applications. Disconnect from your network and/or the internet. Now disable all your security software (firewall, antivirus, antispyware).
    Just in case, this time we'll start the install by right-clicking the iTunes64Setup.exe and selecting "Run as administrator".
    Reenable all security software prior to reconnecting to the internet and/or your network.
    ... Any better luck with the install this time around?

  • Open IE link from Dynamics AX 2009 fails with error 04-00000A09

    Hello, 
    I have virtualized Microsoft Dynamics AX2009 with App-V 4.6.1.30091 and it has been working great for years. 
    On tuesday 18th february a user reports that he is no longer able to open the locally installed Internet Explorer from within the virtual environment. App-V gives the following errr: 04-00000A09 (explained here: http://support.microsoft.com/kb/930631).
    They are using Windows Server 2008 R2 servers and the OSD file paramtere local interaction is set to TRUE.
    I've also resequenced the application where I have clicked on the button to verify that IE opens from AX. 
    Process monitor doesn't give me anything useful in regards to missing regkeys or files. 
    Do you have any suggestions how I should proceed to troubleshoot this, why won't the locally installed application open from within the virtual environment. 
    Regards, Thomas. 

    The log file doesn't say much.
    It says the App-V client cannot open the URL requested by the button inside Dynamics AX that is clicked. 
    Then it gives the error message 461758B-0B211204-00000A09 like i said in my first post. 
    Here is the verbose output from sftlog
    [03/10/2014 08:57:38:287 INTF VRB] {tid=313C:usr=%USERNAME%}
    SWCreateApp(url=http://ELKO-EYE-WEB01/eyeshare1/default.asp?docid=D647120607, ...)
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    CreateApp(osd=http://%server%/eyeshare1/default.asp?docid=D647120607150507, icon=)
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    Parsing type from url http://%server%/eyeshare1/default.asp?docid=D647120607
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=CE8}
    Got app event ID 3 forapp uid 0x175c1630, parent pid = 0xfffff8a0, pid = 0x0, thread = 0x0
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    FindAppByName(name=http://%server%/eyeshare1/default.asp?docid=D647120607, ver=, owner=0xffffffff
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=CE8}
    FirstApp(ulFilter=0x0000200f)
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    FindAppInternal(..., match=http://%server%/eyeshare1/default.asp?docid=D647120607, owner=0xffffffff, ...)
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    No full matches for 'http://%server%/eyeshare1/default.asp?docid=D647120607', returning failure
    [03/10/2014 08:57:38:287 AMGR VRB] {tid=313C:usr=%USERNAME%}
    FindAppInternal(..., match=http://%server%/eyeshare1/default.asp?docid=D647120607, owner=0xffffffff, ...)
    [03/10/2014 08:57:38:303 AMGR VRB] {tid=313C:usr=%USERNAME%}
    No full matches for 'http://%server%/eyeshare1/default.asp?docid=D647120607', returning failure
    [03/10/2014 08:57:38:303 AMGR VRB] {tid=313C:usr=%USERNAME%}
    URL http://%server%/eyeshare1/default.asp?docid=D64712060715050729 is not a description, checking mime DB
    [03/10/2014 08:57:38:303 AMGR ERR] {tid=313C:usr=%USERNAME%}
    Application Virtualization Client kan ikke åpne http://%server%/eyeshare1/default.asp?docid=D647120607
    [03/10/2014 08:57:38:490 TRAY ERR] {tid=313C:usr=%USERNAME%}
    Application Virtualization Client kan ikke starte det ønskede programmet.
    Det angitte programmet finnes ikke. Kontroller navnet du har angitt, og prøv på nytt.
    Feilkode: 461758B-0B211204-00000A09

  • AE crash during launch with error message

    Faulting application name: AfterFX.exe, version: 13.0.2.3, time stamp: 0x53e06bec
    Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
    Exception code: 0x40000015
    Fault offset: 0x00000000000761c9
    Faulting process id: 0x3d4
    Faulting application start time: 0x01d0565e61dd4b74
    Faulting application path: C:\Program Files\Adobe\Adobe After Effects CC 2014\Support Files\AfterFX.exe
    Faulting module path: C:\Windows\system32\MSVCR100.dll
    Report Id: b9af4ebb-c251-11e4-b1d7-8086f24de3fa

    Start by imstalling the latest update. You are several bug-fix updates behind.
    http://adobe.ly/DVA_updates

  • Error in ni visa control out for usb in labview 2009

    Hi,
    I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface.
    the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL OUT.vi gives error "0xBFFF003E : Could not perform operation because of i o error.". while the control in.vi works fine in both the labview versions and any other PC that i tried.
    I have run the application in total of 4 PCs with same set of cards/interfaces. two of them having labview 8.6 are running fine and giving no error but other two with labview 2009 are giving error.
    and it doesn't stop here.... i searched in the vi and did some experiment and found that when i give Request value input to control out.vi as "0x36 "(as required by my PIC program) then it is giving error but when i give other value such as " 0x35 or 34 or 55"(used for other purpose) then it is not giving error.
    Can it be a PIC programming problem? (i dont think so as everything is fine in other PC with LV 8.6)
    I have already explored the ni forum for this error solution but could not find helpful.
    Can anyone solve my problem?

    I installed labview 8.6 in that machine and made a small program with only 3 vis (visa open session, visa close session and visa usb control out.vi) which is working in LV 8.6 platform.
    Sorry the above statement is not correct actually.
    When i run the program in LV 8.6 it giving that same error but this time it is not displayed as pop up window. so i could not judge that error was still there.

  • Labview 2009 x32 and x64 installation error on windows 7 x64

    When attempting to install the evaluation version of labview installed by clicking the try labview for free link on ni.com, I am experiencing an installation error.
    the full error is shown in the attachment below, and is as follows;
    The NI VC2005MSMs x64 installation has failed with the following error.
    Error 1935. An error occured during the installation of assembly 'policy.8.0.Microsoft.VC80.OpenMP, type="win32_policy",version="8.0.50727.762".publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'. Please refer to Help and Support for more information.
    processor is an INTEL core 2 duo
    running windows 7 x64
    The above error occurs with both 32 and 64 bit versions. I belive I have installed this version of labview on this computer before.
    Thanks
    David
    Solved!
    Go to Solution.
    Attachments:
    labview_error.jpg ‏48 KB

    Why Does My LabVIEW Installation Fail With Error 1935?
    Also see this discussion

  • Bug? LabVIEW 2009 Enum in Datalog Refnum Loses Data in LabVIEW 2010+

    Hi 
    Can I please get support from an AE?
    Attached is a LabVIEW 2009 VI with a Control of an Enum in a Datalog Refnum.
    Whereby the Enum's FP Object is represented as an image.
    In LabVIEW 2009 this works fine however, in any higher version (I have definitely tested with LabVIEW 2011, but have been told LabVIEW 2010 is the same) the image is blank.
    Is this a bug - is data being lost?
    Interestingly enough, if I remove the LabVIEW 2009 Enum from the Datalog Refnum then load in LabVIEW 2011 this image displays correctly.
    Is there anything I can do (setting? etc...) in LabVIEW 2009 that will correct this problem so it displays correctly in later versions?
    This issue originated in this LAVA thread.
    Cheers
    -JG
    Certified LabVIEW Architect * LabVIEW Champion
    Attachments:
    Datalog Refnum Enum_LV2009.vi ‏10 KB

    This was reported to R&D (# 311354) for further investigation. 
    As a possible workaround, if you move the enum control out of the datalog refnum before saving in LV 2009, when you open your VI in LV 2011 the image will still show up for the enum control. You can then move the enum control back into the datalog refnum and it should work fine. 
    Thanks for the feedback,
    Daniel H. 
    Customer Education Product Support Engineer
    National Instruments
    Certified LabVIEW Developer

  • DocumentRo​ot in niwebserve​r.conf (LabVIEW 2009)

    I'm using the LV2009 built-in web server and trying to pick my way through building a stand-alone application.  So far I have done fairly well, but I have some questions regarding directives in the web server configuration file.  There seems to be some conflicting information in the forum regarding the path directives, so I'd like to pin it down here.
    The two posts I found that seem to relate to this directly are:
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=434722#M434722
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=393057#M393057
    So, can the path used for DocumentRoot be relative?  And if so, relative to what?
    Ideally, I'd like to have this relative to the configuration file (this seems to be indicated in the first post above).  However, it may be that the path is relative to the web server engine itself (as inidicated in the second post).
    Thanks for any clarification!
    James
    Solved!
    Go to Solution.

    Hi James,
    I believe that your first link to the post by NathanK is correct. He says there that "In 2009 all relative paths in niwebserver.conf are relative to the location of the config file itself." So the path can be relative, and relative to the path of the webserver.conf file.
    I think that the difference in his two posts is because the post in your second link is talking about LabVIEW 8.6, while the post in your first link is about LabVIEW 2009, along with information about the differences between the two versions.
    Regards,
    Stephen S.
    National Instruments
    Applications Engineering

  • Error when trying to set up OPC I/O server with LabView 2009

    Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported.  I have tried to repair LabView, but with no luck. Any idea what it could be?

    The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

  • Why does labview 2009 32-bit closes up with no error message?

    Hello.
    I am developing an application using a PCI-6534 board, Windows XP SP3, and LabVIEW 2009 32-bits. In this application I am generating a 300 Hz signal using the P2.0 digital line. I am trying to make digital acquisition using the P0 port (8 bits), using N-sampling. The program that generates the 300 Hz clock, works with no problem. However, when I start running the program that performs the data acquisition, LabVIEW suddenly closes up with no error message. The LabVIEW windows just disappear from the screen.
    As for me it looks like a LabVIEW bug.
    In case anyone decided to help me, I could attach the programs so that you could check them.
    What can I do to solve this problem?
    Thank you.

    I had the same problem with one of our applications. I supplied gigabytes of process monitor and desktop execution toolkit logs, but nothing was resolved. I upgraded from WS2003 and LV2009sp1 to W7 64b and LV2010, per NI's recommendation but the problem persists.  I had the corresponding service ticket open for 3 months where NI said the application ran fine for them on W7 with 2010. (long story) 
    I understand your frustration, and I recommend getting your local application engineer involved as an advocate with application support.. If you pay for service, pound on them to provide it. My $0.02.

  • SourceGear Vault with LabVIEW 2009 gives error

    Hi,
    I try to evaluate SourceGear Vault for version control in LabVIEW 2009.
    At their website they say that Vault is compatible with Microsoft SCC interface, but as soon as I select  "SourceGear Vault Classic Client" as provider in LabVIEW I get the error "Error -2924 occurred at prefPage_Source Control.vi".
    Does anyone successfully use Vault with LabVIEW?
    Any ideas of things I might need to do to get i to work?

    The text of the error is "An error occurred while opening a source control project or accessing a file.
    The specified path is invalid." Some providers are expecting certain values in parameter calls based on assumptions on how they will be used by various IDEs (mainly Visual Studio). It is possible that valid information passed by LabVIEW to SourceGear's provider does not match what they expect. This would require testing on both LabVIEW's and SourceGear's side to determine what is going on. It would probably be a good idea to start with SourceGear's support to see if they can identify what is invalid.
    George M
    National Instruments

  • Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

    We have discovered an issue with the above listed software.  Specifically this pertains to Print Report.vi in the Report Gen palette.  Basically, we have discovered that with Office 2003 installed the VI will error out.  We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft).  With Office 2007 we don't have a problem.  We've tried building the examples into executables, and those work because they are printing HTML reports.
    Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly.  Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

    yeah, we had seen that, and been told about it by another user.  we tried, to no avail.  we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

Maybe you are looking for