DLL causes error when quiting LabVIEW 2009 on WIN7

Hello,
I have reduced the problem in my EXE application to the following attached code (see attachment). Somehow the DLL (To User32.dll) calls are creating a problem when quiting Labview 2009. The Application stays resident in the Windows taskbar and after a while an error appears about that there was a problem closing the application and that it can be reported to Microsoft if desired. Then a second error message appears before the application dissapears from the taskbar. If I remove the DLL:calls from the code then the problems dissapear.
Should I unload the DLL calls on a special manner before quiting LabVIEW?
Solved!
Go to Solution.
Attachments:
DLL-WIN7 problem.jpg ‏35 KB

Another potential problem not mentioned in that article is that you have included your user32.dll explicitedly in your built application. Doing that creates 200% for sure trouble as the kernel32.dll, user32.dll and others are always residently loaded into memory anyhow and mapped into the system memory section of any process. If you tell an application to load this DLL again by explicit name, you end up having two copies of it mapped in your process memory space and that will cause very weird problems.
To avoid this problem make sure the library name inside the Call Library Node only specifies the DLL name without any path information. Then close the dialog and save it. If you reopen the dialog it will show the full path but still save the name only until you make a modification in the path control at which time you can end up having a full path again.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

  • MSVCR90.DLL Error when start LabVIEW 2009

    Hi,
       My LabVIEW 2009 failed to start. It pops up a window says fault module MSVCR90.DLL. I have reinstalled LabVIEW but the problem is still there. Anybody has similar problem before?
       Thanks for help!
       Tom

    Hi,
    unfortunately I can't do anything in c:\windows\... because I'm not an adnministrator. I have to wait at least a week before he comes back and maybe do it for me. There are 2 Versions of Microsoft Visual C+ installed on this comuter: 2008 and 2010. When LabView crashes and I select "Debug" there are 2 possibilities: 2008 and 2010. The msvcr90.dll which is marked as "failure" in an error message referres to Microsoft RunTime Engine 2008 (according to its properties). 
    I had made another experiment: set "runTime Engine" as VI server by Test Stand. In this case VIs are marked as "erroneus" (with a red button on the module panel). I have to reload every VI (the red button stays, but the picture is loaded), then start execution and ingnore the message, that there are errors. The sequence works OK. When I close TestStand I get an error message "TestStand doesn't work any more-> SeqEdit APPCRASH". 
    I think it shows, that RunTime Engine (I select the option "Recognize the version automatically") loads VIs in another way than LabView Development Environment does.

  • Error 43 when accessing LabVIEW 2009 write/read file functions through the web server functionality

    Is there any way around to avoid Error 43, "Operation cancelled by user" when using Web server?
    I am using the example VI:s RemotePanelMethods-Server.vi and RemotePanelMethods-Client.vi to acces the MainGUI.vi from my workstation to a lab computer. * LabVIEW 2009 is installed in both machines.
    * MainGUI.vi is wired to the VI access list in the Server VI but it also contains a hierarchy below that isn't, is this a problem?
    * Several functions in MainGUI calls file read and write operations
    The problem ocurrs when file read/write operations with no preselected path are selected through the Client. The traditional popup window requesting the file to read or write is never seen in the Client, but only the Error 43.
    Thanks in advance

    See this

  • Error 1612 when uninstalling LabVIEW 2009

    Hello,
    I'm trying to uninstall LabVIEW 2009 from an Acer tablet running Windows 7.  Whenever I attempt to uninstall it though, I receive error 1612.  Also, I'm not doing any weird methods of uninstalling; I'm following what the NI website says to do!  When looking at previous topics that discussed this issue, none really seemed to come to a clear solution and I'm not sure yet if using a 3rd party program is the way to go.  Have any new solutions to this problem appeared?  I need to uninstall LabVIEW 2009 so I can install the 2014 version on it.  That way I can move a program that I wrote on my personal laptop to my lab's tablet.
    Any help is much appreciated!
    Amy 

    You don't need to uninstall 2009 to install 2014.  That said, it sounds like something is corrupt.  As counter-intuitive as it may sound, you might try installing 2009 from the command prompt using the command:  setup.exe /reinstall
    That will force the installer to overwrite registry entries and the such.  After that's complete, you should be able to uninstall.

  • User32.dll Causing Error on Application Exit

    I have an application built into an exe with LabVIEW 8.2. It uses 1 simple call to user32.dll to determine if caps lock is on. When I build the application, it copies user32.dll to the 'data' subdirectory of my application. Everything works fine, however when I exit the program it throws a Windows error, "... has encountered a problem and needs to close..."
    Now the fun part. If I remove user32.dll from this directory, everything works fine. I guess it just goes out and finds the original user32.dll in the system directory and there are no errors when I exit. Replacing the file in \data causes the error again.
    The simplest thing would be to remove the call in my program as it isn't absolutely necessary (it just shows a warning when entering a password if caps lock is on), but there seems to be something weird going on because it only throws the error when using the dll it copied.
    Is there any way to stop the application builder from copying dlls? I couldn't find anything.
    Is there a way to force LabVIEW to release and cleanup any dlls it is using? If I could do this when the user exits, maybe whatever is causing this won't get left behind.

    Marc A wrote:
    I have an application built into an exe with LabVIEW 8.2. It uses 1 simple call to user32.dll to determine if caps lock is on. When I build the application, it copies user32.dll to the 'data' subdirectory of my application. Everything works fine, however when I exit the program it throws a Windows error, "... has encountered a problem and needs to close..."
    Now the fun part. If I remove user32.dll from this directory, everything works fine. I guess it just goes out and finds the original user32.dll in the system directory and there are no errors when I exit. Replacing the file in \data causes the error again.
    The simplest thing would be to remove the call in my program as it isn't absolutely necessary (it just shows a warning when entering a password if caps lock is on), but there seems to be something weird going on because it only throws the error when using the dll it copied.
    Is there any way to stop the application builder from copying dlls? I couldn't find anything.
    Is there a way to force LabVIEW to release and cleanup any dlls it is using? If I could do this when the user exits, maybe whatever is causing this won't get left behind.
    You should not copy system DLLs to other systems. That is a recipy for troubles. Make sure to reference user32.dll form inside the Windows System directory in your Call Library Node. LabVIEW will then see this as system library and not include it in the build. Any Windows system will have user32.dll in the system directory so there is really absolutely no need to distribute that with your app, (and actually it is legally not even correct).
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Fatal Error when installing LabView 8.5

    I encounter a fatal error when I attempt to install LabView 8.5. The error that occurs has the following in its details:
    ".\UberInstaller.cpp(1871): IInstallerError 10014
    Fatal Error. A failure has occurred in NISystemInfo.
    CoLoadLibrary failed on C:\lv8.5\bin\NISysInf.dll"
    I am installing from a system that previously had LabView 8.2 installed, however everything was uninstalled before I began installing the new version.
    No hardware is connected in my computer.
    I copied the files from the DVD to my harddrive and am still failing to install it from there.
    The disc should be fine as my supervisor had used the same disc to install on his computer. ( our licence allows this )
    Any help would be appreciated.
    Attatched is a screenshot of the error.
    Attachments:
    error5.JPG ‏165 KB

    IInstallerError 10014 
    I searched for and found the same error in this forum that I am experiencing. I am trying to install the NI Switch Executive and the install fails every time. This is a fresh install and I am not running any antivirus s/w. It is a DVD copy of the Switch Executive s/w. Has there been any conclusive explanation as to what is happening with this? I have included a .jpg of the error. Thanks in advance for any help.
    Attachments:
    Error_Message.jpg ‏96 KB

  • Third-party keyboard caused error when shifting in iMessage

    I Just upgraded to iPhone 6 plus and immediately install the 8.0.2. When using iMessage, the third-party keyboard caused an error when shifting between keyboards as in the picture. The selection animation was shifted to the left beyond the screen. The problem was gone when I deleted the third-party keyboards (fleksy and riffsy gif). The error also did not occur in email app or Safari.

    Reset your phone - no data loss
    Restart or reset your iPhone, iPad, or iPod touch - Apple Support

  • Counter change to high when quitting LabVIEW

    Hi,
    I am using the GPCTR0_OUT output on my PCI-6052E board as a watchdog output. I need this output to be low while my application is running and high otherwise. However I have found that the output switches back to low as soon as I quit LabVIEW. How can I avoid this behavior?
    Thanks!

    You can apply pull-up resistors to the counter outputs to force their default state to be low or high (depending on your requirements). Take a look at the following KnowledgeBase article (Default State of Counter Output Lines on E Series Data Acquisition Devices). At the bottom, there is a link to another KB that describes how you can change the default power-up state of the DIO lines, and this also applies to the counters.
    http://digital.ni.com/public.nsf/websearch/0089956​33E33E47486256B5F00034436?OpenDocument
    David McClelland
    National Instruments

  • MS Visual C++ error when launching LabVIEW 8.6

    I'm using a PC (running Windows XP) which has LabVIEW 8.6, 2009, and 2010 installed on it.  When trying to launch 8.6, I receive this runtime error:
    If I click OK on this window before the Getting Started screen initializes, I close LabVIEW.  However, If I wait until after the Getting Started screen appears, the window above becomes inactive and unusable.  I haven't tried much programming or poking around, but as far as I can tell LabVIEW behaves normally (I can open and create projects and VIs).
    Has anyone run into this before?  Any insight would be great.
    Thanks,
    Adam Fern
    Adam Fern
    Systems Engineer, CLD
    Cyth Systems, Inc.
    Solved!
    Go to Solution.

    so this Runtime error doesn't stop or effect LabVIEW if you ignore it, and if you click ok it will close LV down. Are the other versions of LV working?
    National Instruments
    Applications Engineer

  • Merry Christmas!...   iTunes causes error when executed

    Hi!
    I have recieved a nice new iPod nano for crimbo. I already had a previous version of iTunes on my desktop as a friend was using it for their mini some time ago. I installed all the software which came with the new nano and for some reason when i plug the nano in it comes up with an error message saying iTunes caused an error and won't load. I have uninstalled via control panel/ reinstalled using the latest version of iTunes from apple and its the same error:
    "iTunes has encountered a problem and needs to close. We are sorry for the inconvenience." It then copies a list of technical stuff to appcompat.txt which goes for about 2 pages.
    I have installed iTunes on my laptop (which didn't have a previuous version of iTunes on it) and it is working fine. It's just a pain only having it working on that machine.
    Has anyone else had problems? I am guessing it might have something to do with the registry or something that cannot be removed via control panel.
    Happy Christmas to all and I hope Santa was good to you!
    P.S. I have no NIS firewall running. Only a router from which the laptop is running also.

    "iTunes has encountered a problem and needs to close. We are sorry for the inconvenience."
    the first thing i check for with one of those is a broken quicktime. does your quicktime currently launch, or does it give you an error message?
    if it gives you an error message, first try this technique (switch off any antivirus or antispyware prior to uninstalls or repair installs):
    iTunes 6 for Windows unexpectedly quits when opened
    keep us posted.
    love, b

  • Invalid Device Error when using Labview to comunicate with Jorway 73A

    I'm having a problem when trying to get Labview to communicate with the Jorway 73a CAMAC crate controller. Keep in mind while reading this that I'm still fairly new to both the CAMAC system and Labview. I've downloaded the drivers for the Jorway 73a off your site and run into a "Invalid device" error whenever I try to read or write from the CAMAC crate using the read or write VI's. Oddly, the initialize/clear/inhibit VI runs without error. When reading cmjwdll.c I can tell that this error occurs whenever "the device selected is not a JW 73A". Not sure why I'd be getting such an error, and only with the read/write VI's, not on the initialize/clear/inhibt one.
    Thank you for your time.

    Hi Caleb,
    You may want to contact [email protected] for this question. Looking at the driver (http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/398258c61da17663862568ab005fbcbc?OpenDocument) It states that these drivers use 32-bit dll's that only work on 95/NT and are provided by Jorway.
    Hope this helps out!
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • Memory Error when installing labview 6.1

    I had labview 6.0, 6.1 and RT installed on my PC (windows 2000). I tried to install application builder but I got Error that I have no labview installed, so I tired to uninstall RT, but I was abe to. Then I found out that I can't install or uninstall any of the Labview versions. So I went and deleted the whole NI directory, all the keys related to NI in the registry file, and Labview.ini. Now I'm trying to install labview 6.1, but I'm getting memory error and setup terminates. What can I do!
    Attachments:
    LB_Setup_Error.gif ‏36 KB

    First, I recommend contacting NI support at ni.com/ask and starting an incident report.
    Second, I recommend either restoring your registry from backup, or wiping your system and starting over. I know it doesn't sound like fun, and it isn't, but it is probably the only way now you can guarantee a good clean registry. Alternatively, go through the registry again and make sure all National Instruments and LabVIEW entries are deleted.
    In the future, and I make this recommendation to everyone, you should, as a safe practice, make a backup of your registry before you install anything, and also periodically. Archive these and label them with the list of programs installed, or with any new programs that have been installed.
    The Windows registry is obsolete,
    and complete hopeless when it comes to a stable system. There is no automated backup of the registry to my knowledge. The registry is the biggest source of problems with Windows, followed of course by DLLs (everyone has their own version, and noone's is alike, much less works right.) The registry can be backed up by using "Export" from the regedit program. Backups can be restored with the "Import" function in regedit of course.
    Good luck.

  • ITunes shows a CoreGraphics.dll inpage error when I try to open it.

    I have always use itunes and recently my itunes wont open anymore. It shows an "inpage error" every time when I try to open it. It never happen before and I just check my computer for viruses and its clean. I have already tried to uninstall itunes and donwload it again, didnt work. Help please, i cant even upload songs to my ipod now.

    b noir wrote:
    Is CoreGraphics.dll cited in the iTunes events?
    Also check for error events happening a few seconds prior to the iTunes events. Open those events. Do they all cite the same .ttf file? If so, what's the precise spelling of the .ttf (font) file?
    YES! There is a CoreGraphics.dll cited in the iTunes event. This is what exactly the window said
    "Faulting application iTunes.exe, version 9.0.3.15, faulting module CoreGraphics.dll, version 1.0.60.0, fault address 0x00266560."
    For the .ttf file, this is what it showed.
    "Windows cannot access the file C:\WINDOWS\Fonts\ARIALUNI.TTF for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program ARIALUNI.TTF because of this error.
    Program: ARIALUNI.TTF
    File: C:\WINDOWS\Fonts\ARIALUNI.TTF"
    I hope this will help. I still cant open iTunes.

  • Error when quitting After Effects

    Somtimes when I quit After Effects CS6 on my MacBook Pro (2.2 GHz i7 Processor, 6750M Radeon Graphics Card), I receive the following error message:
    After Effects Alert
    Last log message was: <140735189834080>
    <ae.blitpipe> <2> HardwareBlitpipe Disengaged
    Generating crash log, which may take a few minutes
    The error is only appearing on some occassions, not all, and I was wondering what it means.

    Still receiving the same error.
    1. After Effects CS6 with the update linked above.
    2. Yes, I installed them
    3. Mac OS Lion 10.7.4
    4. No problems with codecs.
    5. Full text:
    After Effects Alert
    Last log message was: <140735189834080>
    <ae.blitpipe> <2> HardwareBlitpipe Disengaged
    Generating crash log, which may take a few minutes
    6. It happens when I'm quitting the program.
    7. Optical Flares, Twitch, Looks, YY Ramp+, Sure Target, and some scripts. The only one of these usually present is Optical Flares.
    8.  2.2 GHz Intel Core i7 4 cores, 8 GB RAM, AMD Radeon HD 6750M
    9. No 3rd party I/O hardware.
    10. Yes, using OpenGL features (Ray-Traced 3D Rendering, etc.)
    11. It occurs when I quit the program.

  • Renaming a Project causes error when running locally

    The app uses an HTTPservice on a remote webserver. I have
    been running the same app locally for weeks. I occasionally publish
    up to the web server and all has been fine.
    I renamed the project (in the IDE) but now anytime I try to
    run the app locally I get:
    [RPC Fault faultString="Security error accessing url"
    faultCode="Channel.Security.Error" faultDetail="Destination:
    DefaultHTTP"]
    Still works fine when pushed to the web server.
    I have other apps that work fine locally and hit the same web
    server for HTTPservice.
    I tried renaming other projects and found that the same
    problem occured each time the project was renamed.
    Any suggestions?

    Found the cause of the problem, its FlashFireBug in Mozilla. When a swf is launched FlashFirebug tries to capture the swf, this messes up mobile apps running on the desktop.
    Found the answer in this post: http://forums.adobe.com/thread/852612

Maybe you are looking for