Lookout Error

We are seeing the following error on one of our machines.  Has anyone else seen this and found a fix??
Thanks!
Lookout Exe has encountered a problem and needs to close.
Error Signature
AppName:lookout.exe AppVer:4.0.1.61
ModVer:5.1.2600.2180 ModName:ntdll.dll OffSet: 0002ae22
When I click on the view file the following information was displayed.
Exception Information
Code: 0xc0000005 Flags: 0x00000000
Record: 0x0000000000000000
Address: 0x000000007c92ae22
C:\Docume~1\m5tenkip\locals~1\Temp\33df_appcompat.txt

LO Version  4.0.1 B16
Windows XP
Just for reference...
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512

Similar Messages

  • Lookout errors

    Dear sir,
     i am using labview 7.0 with DSC module to access the analog tags from my devices.  I have intialised all the tags in .LPD file and after that i am reading all the tags using read tags function.  For communication i am using modbus RTU protocol. If i disconnect my device from  communication i am  getting alarm message as no communication response from modbus secondary in Industrial automation Opc server window. But now i want to display this error message on the front pannel of my vi. So how can i implement thsi? please suggest me for that
    ragards
    falgandha mohire

    In LabVIEW 8.x, there is a DSC control, called Alarm & Event Display. Just put it on the front panel, it will show all the alarms.
    But I'm not sure if it's different in DSC 7.
    Ryan Shi
    National Instruments

  • Email: SMTP error 535 5.7.3 Authentication Unsuccessful

    I get the following Lookout error when using the Mailer object to send emails:
     Email authentication is failed. SMTP error 535 5.7.3 Authentication Unsuccessful
    It works just fine from my office location and other locations, but when I run the same program at my customer's location I get the above error.
    I had the IT tech at AT&T open up port 25 on my customers internet account. Before she opened up the port, all I would get
    is the error: Timeout during connection to SMTP server.
    We use our company's SMTP server in the Mailer object, The SMTP requires authentication

    Hi Marelise,
    For now, I have enabled these accounts, but in such cases, it is recommended to reach out to chat support or submit a ticket to get faster resolution.
    Do let me know if you have any question.

  • Lookout 6.6 - Logon Error: Security file does not exist

    I'm trying to run Lookout 6.6 evaluation. It loads fine, I get a message saying that it's running evaluation version. I press OK to clear that box and a logon window opens. It's filled in with the default settings, Administator, local doman, no password. I click Log On and it gives me the error which is in the subject line, security file does not exist.
    I've read on here that the lookout.sec file doesn't exist in the System32 folder. In this case, I've found it and it's there.
    I've trying different user names, I took the .sec file and copied it in various locations: windows folder, and the programs root folder - obviously there was no effect. I tried editing the lookout.ini file to remove the log on information to see if that clears it up (even deleted the file to see if that work), but to no avail. I also tried re-installing the program, but there is no uninstall button - windows program removal tool cannot even remove, modify, or repair the program. I ran the install a couple of times as well.
    Does anyone know what I can do?
    Here's what I'm running:
    (I bought this computer today)
    Windows 7 x64-bit Home Premium
    4gb ram
    500gb hard drive
    It's very minimal, since all the computer is meant to do is run this program and replace the computer Lookout 5.0 was running on (mobo got fried).
    - Please - let me know if you have any suggestions.
    Solved!
    Go to Solution.

    Hi Mike! Thanks for replying!
    I've just tried it in admin mode and it hasn't worked. I've also tried using compatability mode, but to no avail.
    I downloaded the lookout 6.2 version to try and it gives me the same error as well.
    Another thing to note, I tried uninstalling it (either lookout 6.6 or 6.2 doesn't matter), but all options it gives (modify, repair, and uninstall) are all greyed out.
    Any thoughts/ideas?

  • How can I install and run lookout 6.1 on windows server 2008 64-bit without errors?

    How can I install and run lookout 6.1 on windows server 2008 64-bit without any errors?
    I was unable to start the lookout applcation after I install the lookout 6.1 on windows server 2008 64-bit.
    (error code: 0xC0000142). Please help!
    Thanks

    This will pobably do http://joule.ni.com/nidu/cds/view/p/id/1051/lang/en but the major issue is that you should concentrate and read the instructions carefully. My two cents.
    Dieet
    Afvallen

  • OPC server error with Lookout 5.1 that was working with Lookout 4.5

    I was running a file on Lookout 4.5 with Field Point explorer 3.0 with field point objects. I recently upgraded the Lookout to 5.1 and Field Point Explorer was uninstalled. Now when I try to open my old Lookout file, I cannot control through the field point objects and I am getting the following error: OPC/OLE error. OPC server not registered properly (63). Invalid class string 800401F3.

    Hello,
    Thanks for contacting National Instruments. There are three known reasons that you may get this error.
    1. IAK file not setup or it has been moved or is missing.
    This error is easy to reproduce. In order for the OPC FieldPoint Server to work, it has to launch the FieldPointOPC2.exe which has looks at a registry key for FieldPoint Explorer. In this registry key is the path to the last saved or loaded IAK file. If this file has moved or has been deleted, then you will get this error. This also happens to customers that have upgraded their FP Explorer and haven't opened up their IAK file and saved it.
    2. OPCproxy is not registered. Which means the opcproxy.dll or opccomn_ps.dll are not registered or are version 1.0 (can be registered by running "regsvr32 opcprox
    y.dll" and "regsvr32 opccomn_ps.dll". The opcproxy.dll and the opccomn_ps.dll are located in the system32 folder in the WINNT directory.
    3.OPCserver is not registered (can be accomplished by running the .exe with a /regserver switch) . The Fieldpoint OPC server is located in the following path: [drive letter]:\Program Files\National Instruments\FieldPoint. From a DOS prompt you can manually register the EXE by going to that directory and typing FieldPointOPC2.exe /RegServer. In a dos prompt the command line looks like this (also see attached picture):
    c:\cd c:\Program Files\National Instruments\FieldPoint
    c:\Program Files\National Instruments\FieldPoint\FieldPointOPC2.exe /RegServer
    Hope this works. If it doesn't, then I suggest that you uninstall all NI software and try to do a fresh install. This will properly ensure that all the services and servers are registered.
    A Saha
    Applications Engineer
    National Instruments
    Anu Saha
    Academic Product Marketing Engineer
    National Instruments

  • Lookout Direct error: "Logos executable has encountered a problem and needed to close."

    I'm using Lookout Direct 4.5.1 (build 19) and see the following error after logging in to Windows XP Home:
    Logos executable encountered a problem and needed to close.
    I created a new process, added a hypertrend object, saved, rebooted, and the error did not occur after the first reboot but started again after subsequent reboots.
    I spoke with Automation Direct tech support and they recommended typing the following two commands at a command prompt:
    lktsrv -remove
    lktsrv -install -manual
    I tried this, rebooted and the error persisted.  Any ideas on what else to do here?
    Yesterday I had been working on finishing up a project using Lookout Direct and this error started occuring.  I reformatted the computer, reinstalled Lookout Direct and had no problems.  Today the error started again.  The only other software I had installed on this PC was Automation Direct's DirectSoft 5. 
    The guy I spoke with at Automation Direct said there was once a form or post on NI's site detailing a method to fix this problem but since recent website changes he is no longer able to find it.  Is anyone here familiar with that?
    Best regards,
    Dave
    Message Edited by davey31415 on 04-05-2010 02:15 PM
    Message Edited by davey31415 on 04-05-2010 02:16 PM

    I saw the Logos executable error twice more and also ran into a "waiting on time service error" when opening Lookout Direct, the latter of which prevented Lookout Direct from opening at all.
    In both cases removing and reinstalling the services fixed the problem (reboot afterwards).  If anyone is dealing with either of these errors I'd suggest typing the following into a command prompt (start -> run -> cmd):
    lktsrv -remove
    lktsrv -install -manual
    lkcitdl -remove
    lkcitd -install -manual
    You should see a dialog box which requires you to click OK and states that removal was successful after the two -remove commands.

  • Lookout 5.1 Application Error

    Hi
      I have a Lookout 5.1 application running under Windows XP Pro that has been running for over a year and all of the sudden we are getting Lookout application errors in GDI32.dll. We have not changed anything in the system and it is not connected to a network so it cannot update itself. The error happens at 11:59PM which is when it is setup to print the alarm logs and a screenshot of the main process screen. It will keep getting this error nightly unless the computer is rebooted and then it seems to go 2 to 3 weeks before we get the error again. I have scanned the drive for any issues and everything checks ok. I have run memory test and they come back ok also. I have also run a virus scan even though there is no network connection in case someone inserted a disk that may have been infected and it also came back ok. Any ideas would be greatly appreciated as this application runs a citys fresh water system and having it crash causes alot of issues. I have attached a PDF file with the error.
    Thank You
    Rob Miller
    Attachments:
    Error.pdf ‏26 KB

    The GDI32.dll is a windows component for graphics.
    I guess the crash happend when lookout tried to call GDI32.dll to get the panel screen.
    I'm not sure what's wrong. An idea is to update the Logos. You can get the Logos 4.5.1 from http://joule.ni.com/nidu/cds/view/p/id/501/lang/en
    Ryan Shi
    National Instruments

  • Lookout project file loading error

    Hi folks,
    I've got this problem.
    I migrate a project to Lookout 6.1 to Lookout 6.5 opening the .lks file an generating the .l4p file.
    I made lots of modification using the symbolic link objects with the dynamical option to point to communication objects data members (OPC client objects) and to internal object (Data table ojects data members).
    Usually, after lots of modification, I reopen a project using .lks file to recompile it.
    Now rises the problem.
    If I load the  lks file, lookout compile the source file without errors, but when it load the process file it goes in error after a little while and the usual error windows appears. In the event viewer I find this information:
    Event Type:    Error
    Event Source:    Application Error
    Event Category:    None
    Event ID:    1000
    Date:        27/05/2011
    Time:        15.25.40
    User:        N/A
    Computer:    VM-TEST-AB
    Description:
    Faulting application lookout.exe, version 6.5.0.49153, faulting module unknown, version 0.0.0.0, fault address 0x00005f6f.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 6c 6f 6f   ure  loo
    0018: 6b 6f 75 74 2e 65 78 65   kout.exe
    0020: 20 36 2e 35 2e 30 2e 34    6.5.0.4
    0028: 39 31 35 33 20 69 6e 20   9153 in 
    0030: 75 6e 6b 6e 6f 77 6e 20   unknown 
    0038: 30 2e 30 2e 30 2e 30 20   0.0.0.0 
    0040: 61 74 20 6f 66 66 73 65   at offse
    0048: 74 20 30 30 30 30 35 66   t 00005f
    0050: 36 66 0d 0a               6f..   
    If I load the process file .l4p, the project are correctly loaded and run.
    I try to compile manually the source project using cbl. After, when I load the .l4p file, the error rises.
    I check the symbolic links and It seems they are correct. I defined data members to point to obviate to point to a non existing object. In this way, the symbolic links always point to existing objects.
    Any ideas?
    Thanks to all
    Mario Fanelli
    Solved!
    Go to Solution.

    Now I rename all the data member names too long into one short. It's a long work. In the projects made under lookout 6.1 I had no problems with recompile and load using the data members names too long. Could be possible that a dynamic symbolic link causes a crash during the loading after the compiling phase? How the dynamic symbolic links are generated when a project starts? I have found a strange mode of operation about the dynamic symbolic links (an example is attached). When you define a symbolic link, you can generate an expression dragging the symbolic link on a panel (in the example is the expression in the high left side of the panel). When you reload the project, go into edit mode operation and try to drag a new expression with the symbolic link, you can't define it. It seems a dongle symbolic link. Only if you rewrite the expression inside the symbolic link, you can drag the new expression. Anyway, the symbolic link works correctly.
    Mario Fanelli
    Attachments:
    ex.zip ‏5 KB

  • FieldPoint Explorer genera errores de Lookout Services

    Realicé un programa ejecutable con LabVIEW 6.1 y FieldPoint 3.0, cuando se enciende el computador en el cual esta instalado dicho programa se presentan dos dialog box con el siguiente mensaje:
    Lookout Services:
    Lookout Citadel Server was not loaded
    y
    Lookout Services:
    Lookout Time Synchronization was not loaded
    Yo no estoy utilizando Lookout, solamente LabVIEW, FieldPoint Explorer y un driver de una tarjeta serial PCI-485. Estoy utilizando la instalación de FieldPoint explorer básica y Si desinstalo el FieldPoint Explorer del computador ya no aparecen estos cuadros de diálogo de error.

    Hola,
    Tengo algunas sugerencias. Puedes intentar reinstalar los servicios de Lookout (un componente del Fieldpoint Explorer) siguiendo las direcciones en este Knowledgebase:
    http://digital.ni.com/public.nsf/websearch/90F854DBAE26BE6C86256A010050A06B?OpenDocument
    Otra opcion es actualizar Fieldpoint desde 3.0 a 4.1. Si haces esto, tienes que construir otra vez tu ejecutable con la nueva version de Fieldpoint. Puedes descargar el driver aqui:
    http://digital.ni.com/softlib.nsf/websearch/7CF3FDE2EC1C043D86256EBC006FC786?opendocument&node=132060_US
    Avisame si todavia tienes problemas.
    Saludos,
    Erin

  • Lookout compiler activex controls error

    Lookout v6.5 Unlimited Client, whem Lookout Compiles the file I keep getting errors saying; Class not found: ActiveXControl.  I am using cwbuttons, and the errors are with all of the cw buttons.  Any ideas on how to correct the errors?
    MWarner

    In Windows\system32 folder, check if the cwui.ocx file is installed. This is for the ActiveX control. If you cannot find it, try to repair lookout.
    If it's there, follow this KB to manually register it.
    http://support.microsoft.com/kb/146219
    What's your OS?
    Ryan Shi
    National Instruments

  • Lookout 5: Error 1921 Service LkTimeSync during installation

    Working under W2000 workstation with virus scanner Ontrack: I have disabled all items (but not uninstalled it). I get "Service LkTimeSync could not be stopped. Verify privileges..." while in administrator mode. Everything else loads correctly.
    Any idea of what the problem is?

    Hello Steven,
    I now have 2 problems: one with my development machine (portable Acer) and one with the target (floor shop: W2000, standard PC).
    1) Acer under W2000: I renamed the Lookout 3.8 dir "OLD Lookout" and tried to install Lookout 5 (with Ontrack disabled) then got that 1921 error. I have a number of startup programs among which: Acrobat, HotkeyApp (to grab windows), Notebook manager, Net-It Launcher (Nat Inst), LoadQM, QuickTime Task, Fix-It Av (Ontrack). I don't have too many services but Interbase Guardian and ZipToA (? Zip drive) are also running. I will try to stop most of the services and install again.
    2) Shop PC: I also renamed Lookout 3.8 as OLD Lookout and installed Lookout 5. It did install correctly even with the Norton antivirus enabled. But th
    e Lookout 3.8 would no longer execute.
    So, I uninstalled Lookout 5 (but a number of files and registers are not removed by the MS uninstall... as always) and tried to re-install 3.8: nothing would work. I removed Norton, tried install 3.8 again but failed again to execute. I mean "nothing happens when double-clicking on the icon). The following message shows at the end of install: "Element 'program' to which this shortcut refers has been modified or has been replaced and it no longer functions correctly"... In fact, the Lookout icon dosn't show up on the module.
    I would like to have the shop machine re-execute 3.8 until I'm done with the newer 5 version: fortunately I have a few days to settle the problem.
    Thank you for your help
    Gabriel

  • The latest Lookout fix patch causes an error.

    I applied the latest fix patch for Lookout 4.5.1 dated 3/8/2002. It now causes this error when I attempt to open my program: "Cbl has caused an error in ALLBRAD.CBX. Cbl will now close." If I restore the original ALLBRAB.CBX the problem does not occur. Any ideas?

    We just currently put up the fixed ALLBRAD.CBX - check it out!
    www.ni.com/support > Drivers and Updates > Search Drivers and Updates > type 'Lookout 5' and you should get the link for 'Lookout 5.0 for Windows -- Fixes'
    Hope this helps
    Roland
    PS: You should be able to use the driver CBX version 5.0 in Lookout 4.5.1. Or you might consider to upgrade to Lookout 5.0. www.ni.com/lookout.

  • How to intercept the buffer full citadel error in lookout 6.1

    I've lots of data to log in the citadel database. Some of these are logged using the logger object drived on a specified event. Anyway, there are other data that are logged continuosly.
    Sometimes the "citadel buffer full" event occours.
    How can I do for intercept this error, if there is something than I can do?
    Thanks
    Bye

    It might compile perfectly well, but the message suggests that you didn't deploy it properly. The class loader can't find it.
    That .class file should appear with its package directory structure under the WEB-INF/classes directory or in a JAR in your WEB-INF/lib directory in some WAR file. Does it?

  • Lookout 5.1 - errors with recoursive text expression : test process

    For all the lookout developers
    I've developed an example with one recoursive text expression that doesn't work correctly.
    The lookout verion is the 5.1.
    Normally I use this expressions when I develop HMI applications and the example represent the 1% of this expressions.
    Thank to all, and enjoy youselves.
    Bye
    Mario Fanelli
    Attachments:
    test_exp.zip ‏10 KB

    Hi,
    The value on "Recursive text expression" will never be different of a saved and not modified value, unless you make a modification in your process file and save the modifications.
    Best Regards
    Andre Oliveira

Maybe you are looking for