Error 10 occurred at New VI Library.vi when building .exe

This is driving me crazy!  What is causing this.  The program worked fine in 8.5.1 and before.  The only thing that has changed is that I had to create directories for each class in the Microsoft Report Generation Toolkit which was a huge pain itself.  See Building an EXE in LabVIEW 8.6 using the Report Generation Toolkit application note for more information.  Anyway, any suggestions would be much appreciated.

After a lot more testing I think I have identified the problem.  Our executable uses the Microsoft Report Generation toolkit.  Due to how LabVIEW 8.6 has implemented the toolkit, it creates directories for each class of the toolkit to prevent name collisions.  Maybe LabVIEW should start using namespaces.  Anyway, we did not want the code to be visible to out customers.  We wanted it to be in a single executable.  So I found a knowledge base article that addresses the issue.  It's called "Managing the Resulting Files from a Build Containing LabVIEW Classes" and it's document id is 4OKDCDES.  Anyway this article says to add .llb destinations into the build so that instead of 5 directories with exposed VIs, you get 5 .llb.  This worked ok with no build issues, but then the article said to rename the .llb to .dll so the extra directories would appear to look like dlls.  The first time you build this it works, but if you build it again, it fails and you get error code 10.  You can then build it again and it will work.  So the problem has to do with renaming the extra .llb to .dll. 

Similar Messages

  • Error: "not enough memory to complete this operation" when building EXE + LLB in LabVIEW 2009

    Just upgraded to LabVIEW 2009 last week and can't build anymore.
    I am building and EXE with support files in LLB.
    PC Specs:
    -P4 3GHz
      -4GB RAM
    -Windows XP PRO SP2 
    - Windows is already enabled to use up to 3GB of virtual memory for applications. 
    - Performed a mass compile on all vi's.
    Not sure what else to try and will appreciate any suggestions.
    Thanks,
    Tavi. 

    This issue as well as a few others have been fixed in the LabVIEW 2009 f2 patch that was released today.  For more information, check out the following Knowledgebase for the list of resolved issues as well as download instructions.
    David_L | Certified LabVIEW Architect
    LabVIEW Tools Network | LabVIEW Tools Network Developer Center

  • When I try to open my iTunes an error message appears saying "New iTunes Library". What should I do?

    When I try to open my iTunes an error message appears saying "New iTunes Library". What should I do?

    Hi!
    Thanks for contacting us today! I understand you are having issues with updating, and using the device.
    I believe that we are aware of the update issue however, it is ultimately the carrier/ manufacturer to provide updates. Please contact the respective company for assistance.
    As for device using, and things not working. Please provide us with more details. (Note: the bug may have already been fixed, but is available in a later update).
    Thanks!

  • Error 7 occurred at Open VI Reference with Application Builder

    Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
    "Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

    Dear Sir;
    There are two things that are good to try:
    First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
    Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
    .llb file to compile.
    Regards

  • Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Build.lvclass:Bui

    During software build to make exe file, I got the following error message:
    Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    Method Name: Build:Application
    The vi was working fine before the build. It just access some text files and creates some excel files. No hardware is involved. See if anybody know how to solve this problem. Thanks.

    I am using LabVIEW 2014 and have been getting this error randomly, but fairly consistently on a recent build. I searched all over and could not find a solution that worked. However, just through trial and error I discovered that the problem is related to SSE2 Optimization in the Advanced properties window. I can consistently cause this error by enabling this feature and consistently compile successfully when it is disabled. Try turning this feature off and see if it solves the problem.
    ...UPDATE: After closing and re-opening LabVIEW this error came back, and did not seem to be affected by the SSE2 option. Not that it isn't related, but perhaps not the silver bullet I thought it was.
    I also got the error to go away sometimes when I compiled the EXE while the main program VI was open, whereas it gave the error most of the time when no VIs were open...again, nothing seems to consistently solve the problem...there is definitely some kind of bug in the appllication builder, and it seems like there are a lot of people that have been struggling with this for a long time (as far back as LV 8)...hopefully NI eventually finds this bug and squashes it!..although, I doubt that anybody at NI is even looking for it...

  • Getting "Error 10 occurred" when building exe

    I am getting the following error when trying to build an executable: "Error 10 occurred at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\Daq\lvdaq.dll"
    Listed under possible reasons were:
    LabVIEW: Duplicate path.
    NI-488: New I/O attempted with old I/O in progress.
    I made some changes and added a .vi to my program, but get no errors if I run the program from the top level .vi.
    Any ideas?

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • Error 7 occurred when building Exe in LabVIEW2010 SP1

    Hi All,
    I wanted to build an Exe for my Application. When I created an Exe and give Generate Preview, I got the following warning.
    Further, I tried to delete most of the code and give generate preview
    I didnt get any warning but I dont know, What is that empty file under data folder? Please explain if any one know the reason
    Then I build the Exe, the following error is popped up.
    Error copying files.
    Source: D:\Test Exe\SC\SubVIs\
    Destination: D:\Test Exe\Exe\data\
    source does not exist
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 7 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488: Nonexistent GPIB interface."
    Herewith I have attached the LabVIEW code (LV 2010 SP1) which I extracted from my Project.
    I browsed our ni forum and the answers posted couldnt sort my problem.
    Thanks for your reply in advance
    Thanks,
    Charu Praba
    Attachments:
    Test Exe.zip ‏9 KB

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • "An error (1502) occurred during the action Open." when opening original .VSD files, but NOT copies!?

    We have a weird situation we're trying to troubleshoot for quite a while: We have multiple .vsd files stored on our network in DFS shares.. We have multiple users who cannot open the files, when they try by navigating to the file and double-clicking it,
    they get "An error (1502) occurred during the action Open. File not found"
    However, if they copy and paste the file to the same exact network folder, THAT file they can open with no problem!
    The problem is very bizarre. I've checked obvious things such as file/folder permissions, versions of Visio installed, things in common between people who can and can't open the files.. I even did some testing today with some strange results...
    Windows 7 x64 machine with Visio 2010 Pro installed (x86):
    1. Opened file by double-clicking it in explorer, "Got the 1502 error"
    2. Tried it again, this time I just get "File not found"
    3. Opened Vizio, did a File --> Open --> navigated to the file and opened it that way... 1502 error.
    4. Copy/pasted the file into the same folder where it's stored, then double-clicked the copy and it opens fine.
    5. Closed the copy, tried to open the original, still get file not found / error 1502.
    The file does exist, it IS there.. sometimes the user just copies it to their local desktop (well, it's not really local, it's redirected) and it opens fine there.. other users email themselves a copy of the file and then open it that way.. it works for
    some, not for others.. and there's no discernible pattern yet to identify who this is affecting. Anyone have any ideas?
    -Keith
    -Keith Elkin

    Hi,
    Based on the error message, the issue may be caused by the Visio file is occupied by some other program in DFS.
    >>4. Copy/pasted the file into the same folder where it's stored, then double-clicked the copy and it opens fine.<< If you did this step, the Visio file would rename in the same folder, like file1.vsd. Thus, it opened well.
    Thus, I recommend you check the file's status in computer management in DFS server, see the below image:
    If the affected Visio files were occupied, please try to clean them(right click>close the file) to test.
    Hope it's helpful.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Sorry,
    This didn't help, the files are not open, locked open, and the issue still persists. Any other suggestions?
    -Keith
    -Keith Elkin

  • Error 1003 when building exe

    Hi all,
    I saw a couple of thread of other people here having the same "1003 error" when trying to build an exe with LV 7.1.1
    The exact text error is :
    Error
    1003 occurred at Open VI Reference in Dist Copy Non-VI
    Files.vi->Dist Build LLB Image.vi->Dist Build App
    Image.vi->Build Application.viPossible reason(s):LabVIEW: The VI is not executable.
    This is all the more surprising because this error will only happen on my computer !!!
    I borrowed a collegue's computer and the build went OK...
    After further investigations I noticed only one difference between my collegue's computer and mine : mine has VIPM installed.
    Could VIPM possibly be the source of this issue ??
    PS : recompling the code (ctrl+shift+run) on my CPU didn't make any change.
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

    Hi TiTou,
          You've probably solved this by now, but if not...
    A few months ago I was trying to distribute two EXEs - both of which made dynamic calls - and this error (among others) was giving me "fits".  I think it can happen if the caller has loaded a VI (.ctl or .vi) that also appears in the callee hierarchy - and the version loaded by the caller is incompatable with the callee's diagram(s.)  When the callee runs, it has to use same-named VIs already in memory.  If you see different behaviour on two different machines, are there two different versions of the caller?
    No matter what the problem really is (was,)  the attached VI will try to open all the broken VIs in a hierarchy - which can be a huge help in narrowing the problem.  Oh yeah, with the (broken) FP open, click on the broken-arrow to see an error-list that can (but-usually-doesn't) display helpful diagnostic info!  Compile this into your EXE (caller) so it runs if there's a problem running the callee.
    Cheers.
    Message Edited by tbd on 01-15-2007 10:58 PM
    Message Edited by tbd on 01-15-2007 11:00 PM
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    Util.VI.OpenBroken.vi ‏62 KB

  • Error while creating a new action in Oracle Process Builder 10gR3.

    Hi,
    After creating a process in Oracle Process Builder 10gR3 when I am creating a
    new action then the following exception is occuring :
    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an
    object.
    at Stellent.IBPM.Actions.ActionsToolbox.Load()
    at Stellent.IBPM.Actions.SelectActionForm.ActionModuleSelectForm_Load(Object
    sender, EventArgs e)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmShowWindow(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
    wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1891 (QFEN-1.050727-1800)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ActionLoader
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/ActionLoader/1.0.0.0__3fc10cde1afe6713/Acti\
    onLoader.dll
    BomInterop
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase: file:///D:/Program%20Files/Stellent/IBPM/BomInterop.DLL
    Stellent.IBPM.Builder
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Stellent.IBPM.Builder/1.0.0.0__3fc10cde1afe\
    6713/Stellent.IBPM.Builder.dll
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy\
    stem.Drawing.dll
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Stellent.IBPM.Actions
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Stellent.IBPM.Actions/1.0.0.0__3fc10cde1afe\
    6713/Stellent.IBPM.Actions.dll
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1891 (QFEN-1.050727-1800)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e\
    089/System.Windows.Forms.dll
    Infragistics2.Win.UltraWinTabControl.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.UltraWinTabControl.v6.2/6\
    .2.20062.34__7dd5c3163f2cd0cb/Infragistics2.Win.UltraWinTabControl.v6.2.dll
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50\
    a3a/System.Configuration.dll
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System\
    .Xml.dll
    Infragistics2.Win.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.v6.2/6.2.20062.34__7dd5c3\
    163f2cd0cb/Infragistics2.Win.v6.2.dll
    Infragistics2.Shared.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Shared.v6.2/6.2.20062.34__7dd\
    5c3163f2cd0cb/Infragistics2.Shared.v6.2.dll
    Infragistics2.Win.Misc.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.Misc.v6.2/6.2.20062.34__7\
    dd5c3163f2cd0cb/Infragistics2.Win.Misc.v6.2.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Hi Deena,
    This error:
    "[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
    javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
    is known issue
    Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
    You need to apply that patch.
    I hope this helps,
    Thiago Leoncio.

  • Call library node in builded exe - path problem

    Hi!
    I have builded an EXE with the App. Builder. In my application I use the Call Library Node, and call functions from a DLL.
    I give the path of the dll with the "Current VI path", than strip the path, and add the DLL-s name. So in the CallLibNode I check the "specify path on diagram" option.
    It works when I run my application on a PC that has the LV 8.5 installed.
    But when I install my app on a PC that does not have it, just my setup installs the Runtime Engine onto it, it does not work, and I get errors.
    Which is the proper way to give the DLL-s path, if I want my app run on any PC that does not have LV installed?
    Thanks:
    Waszil

    Does the executable run correctly on the development machine? If not I would imagine it is a problem with how you are referencing the dll.
    Have you installed all necessary support libraries you may be using throughout the program on the target machine? Are you able to confirm that the error messages are referencing to the dll not being found?
    It sounds like you are referencing the dll correctly. When compiled, the dll is put into the 'data' directory within the root directory, so make sure that is there on the target pc
    Message Edited by yenknip on 08-04-2008 10:42 AM
    - Cheers, Ed

  • Error when building exe

    Building an application with database connectivity toolset v 1.0.1.
    aplication builder crashes and gives error resource.cpp

    Usually when you get this kind of error it includes a line number. This can be helpful to find other reports of this error. Also we need to know what version Of labVIEW and your OS. Can you build any application at all?

  • Error new iTunes library

    Just downloaded latest update....now get error message saying: "New iTunes Library." when I try to open iTunes.

    Yes, I got this error too (New iTunes Library) when I was rolling back to Version 10, I found that you have to 'repair' iTunes under the windows control panel (Programs)  to get it to work properly, or at least that was my experience.  Here is a copy of a post I made earlier on how to fix this issue.
    <snip...> however If you have the same experience I had you are likely to get an "New Library Error" msgbox with just an OK button on it.  You press ok and nothing happens.  Not promising- but there is a fix.
    Next step is to go to the control panel - programs (where you would if you wanted to manually uninstall a program) and find the entry for iTunes.  Right mouse click on it and choose Repair.
    Now Windows will go off an do it's thing - this took about 3 minutes for me.
    Now you can open iTunes.  You wil notice that all your music and lists are now gone, but don't panic.  Close iTunes.
    Go to the iTunes folder on your c drive and find > iTunes > Previous iTunes Libraries > ......
    find the file "iTunes Library YYYY-MM-DD.itl" that has the latest date BEFORE you update to iTunes 11 if you are reinstalling v10, I would think you should use a later version if you have this issue with V11.  Don't use a version 11 dated library for Version 10, or visa versa or it won't work, copy this file into your iTunes folder (so up one folder level) and rename it "iTunes Library.itl" (replacing the existing file - I usually rename it iTunes Library_OLD.itl)
    Now restart iTunes and all your music and lists should be restored.
    That is what worked for me.  As always - approach with care.  Your milage may vary.

  • TS3219 Error message "New iTunes Library"

    I can't access my iTunes on my computer. I get an error message that says "New iTunes Library".  What do I need to do?

    Hi Shayla22,
    Welcome to the Support Communities!
    Have you recently tried to update your iTunes software on your PC?
    The links below will provide troubleshooting steps for you:
    iTunes: How to install the latest version
    http://support.apple.com/kb/ht5654
    iTunes for Windows Vista or Windows 7: Troubleshooting unexpected quits, freezes, or launch issues
    http://support.apple.com/kb/TS1717?viewlocale=en_US
    No content shows up in iTunes after updating
    http://support.apple.com/kb/TS1967
    iTunes: How to open an alternate iTunes Library file or create a new one
    http://support.apple.com/kb/HT1589
    Hope this helps ....
    - Judy

  • Error 8 occurred at Invoke Node in AB_EXE.lvc​lass:Build​.vi- AB_En​gine_Build​.vi- AB_Bu​ild_Invoke​.vi- AB_Bu​ild_Invoke​.vi.ProxyC​aller

    Hi there,
    Hope someone can help me.  I recently upgraded to LV 8.5 and am having a problem building a .exe which has a subvi in it that opens in a new dialog window.  When I try to build this I get the following error:
    Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Bu​ild_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    Method Name: Build:Application
    I have built the .exe with the same subVi but without opening it in a dialog window and it works fine., so the problem seems to be linked to the inclusion of the dialog window.
    Any advice greatly appreciated
    Regards
    Tadhg

    UPDATe:  I can get the .exe to build but now I get an error when I run teh .exe which is shown in the picture attached.
    Attachments:
    error screen1.JPG ‏122 KB

Maybe you are looking for