Labview.exe error is generating

It is giving me labview.exe has generated error message, when I am trying to generate, data log file with time stamp, to find last run of my program. I have attached the vi here.
Message Edited by Support on 04-13-2006 10:46 AM
Attachments:
get_last_run.vi ‏69 KB

I'm assuming that the VI you posted is running as a subVI in your main and that you are getting the path somewhere else. If that's the case, then you should know that the path to a folder is different when you build a executable. For example, if you use something like Current VI's Path, in the development environment, it might be something like c:\folder\example.vi. In an executable, the path would be c:\folder\application.exe\example.vi. You need to do an extra strip path in an executable. You can use the Application property called Application.Type to determine whether or not you are working with an exe or development system to decide whether or not to do an extra strip path. There have been numerous postings on this exact same topic and if you need example code, you can search the forum.
p.s. It's not a good idea to post your phone number and email address in a public forum unless you enjoy spam and unsolicited phone calls. It's also a bit unreasonable to expect the users of this forum (most of whom do not work for NI) to respond directly to you.
Message Edited by Dennis Knutson on 04-13-2006 09:22 AM

Similar Messages

  • RWRBE60.exe error when generating a report to a file format

    Hi people,
    I'm employed as a consultant by a major Petrochemical facility in South Africa.
    My problem is as follows:
    Our product dispatching system contains a number of reports which need to be generated to a file format (either PDF, RTF or Text).
    Whenever one of the users attempts to do the above in the Reports Previewer
    (by clicking on "File" -> "Generate to File" -> "Text"); the following error is displayed:
    "RWRBE60.exe - Application Error. The instruction at 0x00281036 referenced memory at 0x00000000. The memory could not be read."
    This error only occurs when they attempt to run a report through the Application itself.
    I've recompiled and executed the same report(s) using Reports Builder 6, and it generates the file(s) with no problems whatsoever!
    Only when running said reports through the Production application, does this error appear.
    Your feedback will be highly appreciated!
    Thanks!

    This certainly looks like a bug, but you should probably check and make sure that you're on the latest patch set (or at least patch set 10 - Reports 6.0.8.19) before contacting support and pursuing further.
    Hope this helps,
    Danny

  • Opening Excel2000 Labview.exe generated errors

    I am trying to generate an Excel speadsheet to report test results with LabVIEW 6 and Excel 2000 on a Windows 2000 machine. The LV 6 Excel library distributed by NI has an "excel open.vi" which causes LabVIEW to crash. The error message is "Labview.exe has generated errors and will be closed by Windows. Error log is being created." Is this because of WIN2K or Excel 2K? What do I need to do to use Excel?
    Attachments:
    excel_toolkit_lv6i.zip ‏929 KB

    I have the same configuration as you do in my computer with everything working fine, except for one thing, I have the update of LabVIEW 6.0.2, so I will recommend you three things in order to fix this issue:
    1. Get the update for LabVIEW (www.ni.com >> Software Downloads >> Drivers and Updates >> Current Software Versions >> LabVIEW >> Select the update for your system, please follow all the instructions for installation. Reboot the computer after installation and try the example again.
    2. Try the examples that I'm sending to you as attachment and also try the example for writing data to Excel which is located in the Help >> Examples... >> Communications >> ActiveX >> Write Table to Excel
    3. Try reinstalling Excel or re-assigning the automation refn
    um.
    If you still found issues concerning this VI you may want to try to contact us directly and have a copy of the VI that is failing in order to test, you may find the information to reach us at www.ni.com/ask
    Good luck!
    Nestor Sanchez
    Applications Engineer
    National Instruments
    Nestor
    National Instruments
    Attachments:
    WriteXL2000.zip ‏76 KB
    R_W_from_Excel2000_51.vi ‏129 KB

  • Error in LabView.exe after each start

    I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
    1) Reinstalling
    2) updating video card driver and ActiveX
    3) installing on a different drive
    none of these help.
    Any help you may have would be appreciated.
    Attachments:
    LabVIEWlog.txt ‏1 KB

    Hello,
    The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
    There are two types of log files. There are those created by LabVIEW and those created by Windows.
    The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
    NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
    hidden files and folders.
    If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
    If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
    If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
    ther dlls with the VIs that cause LabVIEW to crash?
    Zvezdana S.
    National Instruments

  • Runtime Error: abnormal shutdown of c:\program files\...\labview.exe

    Okay.  I've just upgraded to labview 8.0 last week and have been using it without error until the program hung when I opened it one day.  To remedy the situation and after waiting a while, I "ctrl+alt+del"ed it and forcebly closed the application.  From then on, the main lab view program will not function.  I get a runtime error saying that the program (c:\program files\...\labview.exe) was shutdown adnormally and to consult with the software manufacturer. Other NI applications function without error (ie: Measurement and Automation Explorer, Previous versions of labview, etc).
    I tried to reinstall the upgrade to no avail.  Leason learned:  ctrl+alt+del is evil.  If you have any ideas, I would greatly appreciate any input and I will relay the results.  Thanks in advance. 

    Hi Wiztrek,
    This does indeed sound like an odd error/situation. We'll do our best to get it sorted out for you though! A few questions for you:
    1. What kind of computer is this? Laptop, server, desktop, etc?
    2. What OS? Service Pack (if applicable)?
    3. When does it happen? You mentioned the splash screen -- is that as far as it gets?
    Something you could try (and this is a shot in the dark) is to rename or delete the LabVIEW.ini file (it's in the same directory as LabVIEW.exe). If that doesn't work, I think a reinstall is best to try to fix it. Remove LabVIEW 8.0 from your computer via Add/Remove Programs. Then completely delete the "LabVIEW 8.0" folder from "Program Files/National Instruments" on your harddrive.  
    When you run the installer again (after rebooting of course), make note of any errors you receive (if any). Try following the steps outlined in this KnowledgeBase -- we might get something useful out of the install log:
    How Do I Generate an Error Log File for a Software Installation?
    I hope this helps shed some light on the issue - let us know what you find out!
    Charlie S.
    Visit ni.com/gettingstarted for step-by-step help in setting up your system

  • Program Error : Labview.ex​e has generated errors,,et​c? Any Ideas

    I keep getting this error popup titled Program Error.  The message reads, "LabView.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." 
    This appears to happen randomly including while a program is running, while LabView is sitting idle and even after I've closed Labview. I am running 8.0 on Windows 2000. Any ideas?

    Hello Paul,
    There is actually a great online Knowledgebase that explains where you can find error logs, and I have linked it for you here. If you don't get a prompt from LabVIEW after the crash to "investigate the error" (which simply guides you through the process of submitting your error log), then you can submit your error log directly by going here and choosing "Email NI". Be sure to include a detailed description about how to reproduce the crash or what circumstances increase the frequency of crashes like this.
    Kind Regards,
    E. Sulzer
    Applications Engineer
    National Instruments

  • IPod generates a svchost.exe error and blocks the computer

    Ok, I got an iPod Nano 2GB Silver today and when I plug it in the USB port, a svchost.exe error pops up. The only thing I can do is to press OK, but when I do that, another and another and another... same error pops up. I have to reset the computer in order for the computer to start functioning normally.
    I will try to translate what the Event Viewer says about the error (and this is what the error pop-up also states):
    Opening application: svchost.exe - Program error : Instructions on »0x00000000« reffered to the memory on »0x00000000«. The memory couldn't be written.
    The thing is though, it's working fine on some other laptop, but I don't understand why this is happening on my desktop?! And some of the older mp3 players (not iPods) are working just fine.
    Please, help me!

    I have a similar problem which began a couple weeks ago. Same svchost.exe closure, only I couldn't figure out what was causing the problem. Did the format C: and clean XP install, then gradually reinstalled software. When I got around to installing iTunes again, and about 24 hours goes by, I get the same message again. Both the popup and event viewer tell me that the iPod
    Service caused the failure. Windows would only suggest that the problem was caused by Windows Update.
    Before the fault bucket was generated, there was an Application Information message that states:
    The description for Event ID ( 0 ) in Source ( iPod Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Service started.
    So now I am unable to keep my iPod updated, charged, used. Is this what I paid a premium price for?

  • I have Labview 5.0 and I can't run a program it gives me a runrime error C++ relating to the Labview exe file. Do you know where to start to fix this?

    I've had this version for quite a long time and haven't had any problems with it. When I start Labview normally it seems to work fine I can look at individual Vi's and such but when I go to start a Vi program or even the tutorial it gives me a "Runtime error message C++ 
    C:\Program File\National Instruments\LabView\LabView.exe  abnmormal program termination." I'm not sure if it is a computer problem DAQ card (PCI 6023E) problem or a software glich. If you have any ideas of where to start tracking this down please let me know ASAP. It is a work stoppage situation.
    Thanks for your consideration
    Maurice Massey
    UES,Inc

    Have you tried doing a repair or reinstalling?

  • Labview.exe - Application Error

    While running VI in Labview 7.1, I receive the following error:
    Labview.exe - Application error
    The instruction at "0x05791a4b" referenced memory at "0x00000034".  The memory could not be "written".
    Has anyone seen this error?  Does anyone have an idea of the cause?
    For reference, this is a new computer, XP Pro, 4G ram.  I did not get the error on the previous computer running the same code, but the old computer had other issues that required it be replaced.

    This looks like an error popup from windows.  Those hex values are going to be different depending on where the problem is in memory, and that could be different every time.  It might have created a Dr Watson's error report, but that usually isn't enough to determine the cause.
    I agree with John's direction -- is it reproducible?  Is it only one VI?
    Do you ever get another type of error message from LabVIEW?  If fatal, it will appear when the error occurs.  If a warning, it will appear at LabVIEW's next start-up.  Please refer to:
    KB 2PBCSFDW: Where Are LabVIEW Error Log Files Saved?
    Trey B
    Applications Engineering
    National Instruments
    Message Edited by Trey B on 10-24-2007 09:55 AM

  • Occasional error message saying "Labview.exe has stopped working"

    Hi,
    I am using Labview 8.0 on a Windows Vista operating system to communicate with lab instruments through GPIB. Occasionally, when one of my programs finishes running, an error message appears saying "Labview.exe has stopped working". The error window gives me the option to close the program or debug. After clicking debug, Windows cannot find the source of the error and the all labview applications get closed. Any ideas? Thanks.

    The code that I have been having an issue with is attached. The main program is called "Frequency Sweep Real Time2". The other two attachments are subVI's used within the main program. I am a young programmer and I have never had any official training with Labview so sorry if my Labview programming is unconventional or just plain bad. Thanks to whoever looks this over.
    -Ryan
    Attachments:
    Frequency Sweep Real Time2.vi ‏443 KB
    Read multiple values.vi ‏26 KB
    Save_data2.vi ‏22 KB

  • Application Builder Error "Browse to LabVIEW.exe"

    LabVIEW gurus...
    I am currently building a standalone app from my project.  When I run the application (which builds successfully), LabVIEW prompts me to browse to the LabVIEW.exe file.  However, I want this app to run on a computer that will not have LabVIEW installed, and so browsing to this file isn't an option.
    I know that the reason for this problem is that I'm using 2 call library functions named StrLen and MoveBlock within the LabVIEW.exe library (to access data from a pointer to a pointer).
    LabVIEW.exe shows up as one of the dependencies in my project, but I can't figure out how to add it to my build specifications.  I tried to build an installer and include the LabVIEW runtime environment, but this doesn't seem to work either.
    Any suggestions would be greatly appreciated!
    I'm using LabVIEW 8.6.
    Thanks,
    Jason
    Solved!
    Go to Solution.

    In the dll call simply type LabVIEW without any path. This should work (I used it on 7.1)to automagicallylink it.
    The functions are also located in the lvrt.dll which is the main part of the runtime engine.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • Labview load error code 21

    I have a VI which includes subvi for vision utilities like IMAQ winddraw, wind close etc. I build the exe file for the main VI. What extra files should I include in the exe generation? since when I build the exe file normally and it generates the error labview load error code 21. what other extra files should I inculde?

    This should answer the question I think:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/f695b089e3b1cd3286256a4000702136?OpenDocument
    MTO

  • How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

    I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
    have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

    Jay del Rosario wrote:
    >
    > How do I troubleshoot installation/distribution of a LabVIEW .exe
    > which processes data using Matlab when it works on some computers but
    > not others?
    Poke around zone.ni.com and
    http://digital.natinst.com/public.nsf/$$Search/ .
    Good luck, Mark

  • Error in generating HTML output using Central Output Pro Server 5.5

    I am getting the following error while generating HTML output using the Output Pro Server. A new printer was created with the Physical Device as "HTML Template Generation - [html]" and added to the Job.<br /><br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [400](1801) The printer name is invalid.<br /><br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [3015]Error, unable to open printer.<br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [3008]Error, unable to get info about device 'PAYMENTADVICEHTM.html' attached to port '<nil>'.<br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [400](183) Cannot create a file when that file already exists.<br /><br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [2]Error opening output device/file 'PAYMENTADVICEHTM.html'.<br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [400](6) The handle is invalid.<br /><br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [3018]Error ending page on printer.<br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfmerge: [210]Nothing was printed.<br />2004/05/07 20:09:53 D:\Program Files\Adobe\Central\Bin\jfserver.exe: [314]Agent exit message: [3018]Error ending page on printer.

    If I were to guess, I'd guess that your filename is invalid. How about removing all special characters (spaces, brackets, etc.) from the device name. Also, make sure your form was compiled for HTML.
    I haven't actually used the HTML driver, but these are general things you should do if you have trouble with any Central driver.
    Regards,
    Rob McDougall
    Indigo Pacific

  • Error in generating COM DLL via DCOM Object Builder

    Hi,
    Iam creating a COM DLL for a BAPI and I always get the error when generating the DLL. I have Visual C++ 6.0 installed in the same PC.  Pls help.  Thanks.
    C:\vb>CALL "C:\Program Files\Microsoft Visual Studio\VC98\bin\vcvars32.bat"
    Setting environment for using Microsoft Visual C++ tools.
    Microsoft (R) Program Maintenance Utility   Version 6.00.8168.0
    Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
         midl.exe /Oicf /h "Flights.h" /iid "Flights_i.c" "Flights.idl"
    Microsoft (R) MIDL Compiler Version 5.01.0164 
    Copyright (c) Microsoft Corp 1991-1997. All rights reserved.
    Processing .\Flights.idl
    Flights.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\oaidl.idl
    oaidl.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\objidl.idl
    objidl.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\unknwn.idl
    unknwn.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\wtypes.idl
    wtypes.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\ocidl.idl
    ocidl.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\oleidl.idl
    oleidl.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\servprov.idl
    servprov.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\urlmon.idl
    urlmon.idl
    Processing C:\PROGRA1\MICROS4\VC98\INCLUDE\msxml.idl
    msxml.idl
    Processing C:\Program Files\SAPpc\SAPGUI\rfcsdk\include\sapconn.idl
    sapconn.idl
         rc.exe /l 0x407 /fo "Flights.res" /d "NDEBUG" "Flights.rc"
         cl.exe /nologo /GX /MD /W3 /O1 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D "_ATL_DLL" /FD /c /Fp"Flights.pch" /Yc"FlightsAfx.h" FlightsAfx.cpp
    FlightsAfx.cpp
    bapiret2.h(116) : error C2059: syntax error : 'constant'
    bapiret2.h(117) : error C2146: syntax error : missing ';' before identifier 'rfc_padd_4_1bperC'
    bapiret2.h(117) : error C2059: syntax error : 'constant'
    bapiret2.h(119) : error C2146: syntax error : missing ';' NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
    Stop.
    Regards,
    Kelvin
    [email protected]

    Hi,
    For those who might encounter a similar problem, I manage to solve the problem by installing the DCOM Connector from the same SAP GUI CD (ver 6.2).   I had the impression to download the DCOM Connector from sap.com but they have the 4.6D version which causes a problem if you are using a higher version of SAP Gui.  The rule of thumb is to install the RFC SDK and DCOM Connector from the the same SAP GUI CD.
    Just note that DCOM Connector is reaching End-of-life.
    Cheers,
    Kelvin

Maybe you are looking for