Lookout 4.5 crash

Dear All,
I am using lookout 4.5 in server-client architecture.
Now facing problem of (primary) server getting crash, while working in client processfiles. request you all to guide me to trace the error.
Where I can get the logs ?
with wrm regards.

The modbus cbx file has been altered to correct this issue.
1)Rename the old file to modbus.old
2)Insert the cbx into the Lookout folder
3)Delete the lookout.dat file
It will be recreated
4)Start Lookout and open your process.
Attachments:
modbus.cbx ‏145 KB

Similar Messages

How To Stop Lookout Web Client Crashing IE Web Browser

Hi,
I am using Web Client with Lookout. My problem is I can only load a panel within Internet Explorer once. If I reload the URL within the same session then Internet Explorer crashes.
Can anyone offer me advice to fix this problem please?
Software is as follows:
- Lookout V 6.0 (build 5)
- Browser: Internet Explorer 6.0.28
- Web Server: Tomcat 5.5.7
The steps I took are as follows:
1. Created Process
2. Set up File-> Web Server Options->Export Directory to:
c:\telemetrysms\webapps\root\user\fishfarmlive\
(where “c:\telemetrysms\webapps” is Tomcat webapps folder)
Set up server URL to:
http://HOSTNAME/user/fishfarmlive/
(where “HOSTNAME” is the server name)
3. Export Web Server Files
4. Start IE and open web page. My panel displays correctly (with live data), although the only alarm Lookout displays is “The remote position source is not writable”.
5. HOWEVER, when I reload the page in IE the browser will always go blank for several seconds and then crash (with no error message).
Furthermore…
As a test I created a simple test process with nothing but one panel containing a single line of static text. This simple project also crashes.
This computer also has Lookout 5.1 installed. And projects created in 5.1 only crash the browser very occasionally.
Any suggestions (about the crashes or the missing alarms) would be greatly appreciated?
Thanks.
Regards Brett Sheeran

Brett,
I have some info for you regarding the web client. I am including links to two documents that have information that will help you with your problem. The first document is good info about developing a web client application and the second has information directly pertaining to the IE crash that is occurring. It also has other troubleshooting information. I would also recommend checking the firewall on the computer. It windows security settings also have to be set to low in order for web client to communicate correctly.
Deploying a Lookout Application
Lookout Web Client Troubleshooting
Regards,
Danny G
Applications Engineer
National Instruments

Lookout 6.1 crashing when trying to compile .lks file

When trying to compile my .lks file in Lookout 6.1, Lookout crashes. From the event viewer I get the following information on the crash:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  10/16/2007
Time:  1:19:38 PM
User:  N/A
Computer: SCADA-PE-1
Description:
Faulting application cbl.exe, version 6.1.0.27, faulting module lkworks.dll, version 6.1.0.27, fault address 0x000e7377.
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 63 62 6c   ure cbl
0018: 2e 65 78 65 20 36 2e 31   .exe 6.1
0020: 2e 30 2e 32 37 20 69 6e   .0.27 in
0028: 20 6c 6b 77 6f 72 6b 73    lkworks
0030: 2e 64 6c 6c 20 36 2e 31   .dll 6.1
0038: 2e 30 2e 32 37 20 61 74   .0.27 at
0040: 20 6f 66 66 73 65 74 20    offset
0048: 30 30 30 65 37 33 37 37   000e7377
0050: 0d 0a                     ..
Any assistance on correcting this problem would be GREATLY appreciated, since I will lose a bunch of work I have completed working with the l4p file.
Computer Info: Windows XP SP2 OS, Dell Optiplex GX745, 2.66GHz, 2GB RAM, Dual Core Processor
Thanks!
Jason Phillips

Geoff,
Go into your Lookout folder and look for the file "cbl.err". Open that file in notepad or wordpad and you should see where your errors are that are preventing your file from compiling.
I got so used to Lookout generating the errors when a compile failed and displaying them immediately that I forgot about checking this file.
Good luck!
Jason Phillips

Logging data after a trigger with Lookout Direct

Hi,
I would like to log data with Lookout Direct after a trigger input (not periodically or continuously). I am using Lookout DIrect version 4.5.1 build 19 and a Direct Logic 250 PLC.
Does anyone have suggestions on how to do this? I would prefer that this data be logged into Excel. I have 24 sensors connected to the PLC and each time a sensor transitions from hi to low I would like to log the time of transition.
Currently I have individual spreadsheet storage objects for each sensor as well as individual latchgates to indicate when logging has been completed. In the PLC code there is a state machine for each individual sensor as well and one of the states waits for an acknowledgement from Lookout that data logging has been completed before moving on to the next state (I will have to dig a bit deeper to remember exactly why I needed to do that).
I am hoping there is a more traditional approach that is easier than what I am doing. One of the problems I have been facing is Lookout Direct crashing every few days and I suspect it is because the sensors are often sensed within milliseconds of each other and opening/closing so many files is causing problems. I worked through a list of possible reasons that Lookout may be crashing (provided by tech support) and I am nearly convinced I am just asking too much of the program...
Any help will be greatly appreciated
Thank you,
David

In case someone can help with this, here is a bit more information about my application and the PLC/Lookout code I have developed:
Actuators have two positions, nominal and folded. Prox sensors are used to monitor the position of actuators. 12 actuators can be monitored simultaneously. The time at which prox sensors are sensed high is recorded so that actuator speed and actuation success is logged.
The PLC code consists of 12 separate state machines, each with the following 8 states:
State 1
System reset or nominal timer reset
Wait for nominal prox release
State 2
Nominal prox released
Wait for folded prox sense
State 3
Folded prox sensed
Wait for folded ack from Lookout (acknowledges that timer value has been logged)
State 4
Folded ack from Lookout received
Wait for folded timer reset (this state is active for one scan only)
State 5
Fold-in timer reset
Wait for folded prox release
State 6
Folded prox released
Wait for nominal prox sense
State 7
Nominal prox sensed
Wait for nominal ack from Lookout (acknowledges that timer value has been logged)
State 8
Nominal ack received from Lookout
Wait for nominal timer reset (this state is active for one scan only)
Lookout acknowledges that timer values have been read and saved with LatchGates. Lookout uses a SpreadSheet Storage Object to save the PLC timers when the PLC enters states 3 or 7 (prox sensor triggered). The logged member of the SpreadSheet Storage Object is used to change the state of the LatchGates which, in turn, signal the PLC to proceed to the next state. When the folded file is saved, the nominal LatchGate is turned off and the folded LatchGate is turned on and vice-versa for the nominal file.
The LatchGate/SpreadSheet Storage combination is what I am hoping to improve upon. I believe Lookout is crashing when 12 SpreadSheet Storage Objects log to 12 different files during the same 1 second period of time.
If anyone has suggestions of a way to log this data in the PLC memory or a software package better suited for this application, please let me know! I believe this would be simple with LabVIEW, unfortunately obtaining the additional hardware and software that I would need hasn't been easy!

Lookout 6.1 Edit Mode Bug

I don't remember seeing this in older versions of Lookout, but in 6.1:
Edit mode allows you to open a second session of object editing. It used to be you had to close an open object edit (connections, data member configuration, etc) before opening another.
Well in 6.1, it will let you open a second one....and Lookout will always crash after you close them and save the process (sometimes it will crash before you try to save).
Ed

Ryan,
Windows XP SP2 32-bit, fully updated. Dell Precision 690 with single Xenon 5160 dual core @ 3.0GHz
I sent you an email with more details....
I have not restored to original release 6.1 only. I will progress the entire upgrade path scenario when I have time to reload the machine in question and I'll test each phase.
Ed
Message Edited by erblock on 03-31-2008 01:38 AM

Lookout 4.5 / Windows XP problems

Hi my name is Roger and I am new to this forum, but have been using Lookout for SCADA since it came on floppy.
I was asked to replace an aging Win 98 era PC with a faster machine and ran into numerous glitches.
I am finding Lookout 4.5 unstable with Windows XP... Before starting this project, I asked around and everyone thought it would be ok, but no.
I loaded my Lookout Integrator V5.1 onto the new machine and all the problems seem to dissapear. Unless I am missing something, it looks like upgrade time for my client.
Anyone else?

Hi Allan
We are running 18 processes in a U.S. Buraeu of Reclamation supplied canal system...
First issue:
Process files load ok manually, but when auto loading them via the startup option, it chokes and crashes.
Second issue:
Lookout V4.5 crashes just sitting there running no processes, and has to be terminated with task mgr.
I tried re-installing, but the order of failures just changes with each new install.
There are no other apps running on this pc, just lookout.
Pretty much gave up on 4.5, and am looking into upgrading them to 6.0 and using that license to activate 5.1, which I have the install disk for. I am alittle nervous about 6.0 right now and will use 5.1 (hopefully) until 6.whatever addresses the issues I have read about here.
I don't have 4.5 on this machine now, so if I get an upgrade I guess it will be a moot point.
Thanks
Roger

Lookout Client V6.0.2 keeps crashing - lkwrks.dll problem

On several of my machines running the Lookout client version (6.0.2 with updates), Lookout consistently crashes. Below is the information from Event Viewer:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  4/3/2007
Time:  12:40:46 PM
User:  N/A
Computer: SCADA-SD
Description:
Faulting application lookout.exe, version 6.0.2.1, faulting module lkworks.dll, version 6.0.2.1, fault address 0x00021c5b.
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 30 2e 32 2e 31    6.0.2.1
0028: 20 69 6e 20 6c 6b 77 6f    in lkwo
0030: 72 6b 73 2e 64 6c 6c 20   rks.dll
0038: 36 2e 30 2e 32 2e 31 20   6.0.2.1
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 32 31 63   t 00021c
0050: 35 62 0d 0a                       5b..
Again, this is only happening on machines running the Client version.
All machines are Dells running Windows XP SP2 and have at least 1 GB of RAM.
Please respond A.S.A.P.
Thanks!
Jason Phillips

I am aware of the fact that you cannot copy the updated lkworks.dll file to the client version - if you do you will get an "evalutaion version" dialogue box everytime you open the client.
This problem is occuring with all of the updated files, except "lkworks.dll", copied to the Lookout 6.0 folder.
I found out late yesterday afternoon that this crash is occuring on machines running the client version and running my client process file. On machines running the client version but not running the client process file, the crash does not occur. For example, I have one machine running the client version and a logging process file which does not crash. Also, on machines running the server version and the client process file, the crash does not occur. So, it appears that the problem has to do with machines running the client version and the client process file. This process file is much bigger than the logging file I had previously mentioned, about 11Mb. Attached are my client and server files to assist you in diagnosing and correcting this problem.
Please respond A.S.A.P.
Thanks!
Jason Phillips

Lookout 6.5 critical crash - writes to random modbus addresses

Hello,
We are experiencing a rather critical problem with Lookout 6.5. The proces file contains approximately 148 Modbus/TCP connections, some overview panels, a properties panel which uses a symbolic link to retrieve properties from a certain modbus object.
Seemingly random, Lookout crashes during operation (with the Windows send/don't send window). When this happens, the second before the crash actually occurs Lookout starts writing seemingly random values to addresses to all the modbus devices. Some to addresses which are connected in Lookout, and to some that are not (even to addresses that actually don't exist on the device, which causes it to return an exception). The addresses do seem to be in an increasing sequence (i.e. it starts at 500, then starts writing further until about 850). Values I've seen are mostly 0, but also 256, 2308, 512, 2048, 3844.
I've attached a packet capture log which shows the write commands Lookout is sending.
Does anyone have any idea what could cause this crash or things I can check?
Attachments:
dump.txt ‏175 KB

Also uploaded a second dump file as Randomwritecrash2.zip - I'll keep uploading dump files in sequence.
Crash data from this dump:
(1328.bd4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01cbcd1a ebx=00f70000 ecx=3e720012 edx=3e720013 esi=00f70838 edi=00000009
eip=7c902a9d esp=0013f4f4 ebp=00f70838 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
ntdll!tan+0xcf:
7c902a9d 8b18 mov ebx,dword ptr [eax] ds:0023:01cbcd1a=????????
0:000> kb
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0013f4f8 7c91020e 00000009 00f70838 00f70000 ntdll!tan+0xcf
0013f510 7c9101db 0013f744 7c90e920 7c910228 ntdll!RtlAllocateHeap+0x14a
0013f528 7c91019b 00f70838 00000013 0000003f ntdll!RtlAllocateHeap+0x117
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\MSVCR71.dll -
0013f754 7c3416b3 00f70000 00000000 0000003f ntdll!RtlAllocateHeap+0xd7
0013f794 7c3416db 0000003f 7c3416f8 0000003f MSVCR71!_crtLCMapStringA+0x305
00000000 00000000 00000000 00000000 00000000 MSVCR71!_crtLCMapStringA+0x32d

Lookout 6.2, Citadel Crash

Ok, beating a dead horse... I think we are definitely getting to the end of our NI lifespan
Background
System installed with Lookout 6.1 in 2008, ran well for about 1.5 years. Random crashes, database corruption, etc. Initially believed to have been the machine (Software RAID 5 sucks). New machine built in Oct. 2010; no RAID, Intel Core2 machine, XP SP3. Upgraded to Lookout 6.2. Could not import the 6.1 database, performance slowed to a crawl, believed to be from a corrupt database. Created a new database.
Today
Machine is experiencing system failures on Citadel and Lookout. We have nothing but AlarmDialer 4 (custom notification software), RealVNC Enterprise, Lookout 6.2, HP Printer and standard system related tools (TrueImage, AVG, Adobe Reader (Latest version, for manuals)) installed on this machine. All updates installed.
Latest Windows Mini-dumps: http://support.forshock.com/files/MRCWD/Minidump.zip
Latest (related) error messages:
Event Type: Error
Event Source: SQLBrowser
Event Category: None
Event ID: 1
Date: 12/21/2010
Time: 5:27:46 PM
User: N/A
Computer: SCADA
Description:
The SQL configuration for SQL is inaccessible or invalid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4d 00 53 00 53 00 51 00 M.S.S.Q.
0008: 4c 00 53 00 65 00 72 00 L.S.e.r.
0010: 76 00 65 00 72 00 5c 00 v.e.r.\.
0018: 43 00 75 00 72 00 72 00 C.u.r.r.
0020: 65 00 6e 00 74 00 56 00 e.n.t.V.
0028: 65 00 72 00 73 00 69 00 e.r.s.i.
0030: 6f 00 6e 00 00 00 o.n...
Event Type: ErrorEvent Source: SQLBrowserEvent Category: NoneEvent ID: 1Date: 12/21/2010Time: 5:27:46 PMUser: N/AComputer: SCADADescription:The SQL configuration for SQL is inaccessible or invalid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 4d 00 53 00 53 00 51 00 M.S.S.Q.0008: 4c 00 53 00 65 00 72 00 L.S.e.r.0010: 76 00 65 00 72 00 5c 00 v.e.r.\.0018: 43 00 75 00 72 00 72 00 C.u.r.r.0020: 65 00 6e 00 74 00 56 00 e.n.t.V.0028: 65 00 72 00 73 00 69 00 e.r.s.i.0030: 6f 00 6e 00 00 00 o.n...
Event Type: Information
Event Source: MSSQL$CITADEL
Event Category: (2)
Event ID: 26037
Date: 12/21/2010
Time: 10:01:26 AM
User: N/A
Computer: SCADA
Description:
The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b5 65 00 00 0a 00 00 00 µe......
0008: 0e 00 00 00 53 00 43 00 ....S.C.
0010: 41 00 44 00 41 00 5c 00 A.D.A.\.
0018: 43 00 49 00 54 00 41 00 C.I.T.A.
0020: 44 00 45 00 4c 00 00 00 D.E.L...
0028: 00 00 00 00 ....
We get lots of these entries:
Event Type: Information
Event Source: MSSQL$CITADEL
Event Category: (2)
Event ID: 17401
Date: 12/21/2010
Time: 1:44:58 PM
User: N/A
Computer: SCADA
Description:
Server resumed execution after being idle 10079 seconds: user activity awakened the server. This is an informational message only. No user action is required.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: f9 43 00 00 0a 00 00 00 ùC......
0008: 0e 00 00 00 53 00 43 00 ....S.C.
0010: 41 00 44 00 41 00 5c 00 A.D.A.\.
0018: 43 00 49 00 54 00 41 00 C.I.T.A.
0020: 44 00 45 00 4c 00 00 00 D.E.L...
0028: 00 00 00 00 ....
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 12/22/2010
Time: 7:29:18 AM
User: N/A
Computer: SCADA
Description:
Faulting application lookout.exe, version 6.2.0.49153, faulting module nicitmid.dll, version 5.6.0.49153, fault address 0x00069ffb.
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 32 2e 30 2e 34 6.2.0.4
0028: 39 31 35 33 20 69 6e 20 9153 in
0030: 6e 69 63 69 74 6d 69 64 nicitmid
0038: 2e 64 6c 6c 20 35 2e 36 .dll 5.6
0040: 2e 30 2e 34 39 31 35 33 .0.49153
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 36 39 et 00069
0058: 66 66 62 0d 0a ffb..
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/21/2010
Time: 5:28:15 PM
User: N/A
Computer: SCADA
Description:
Error code 00000024, parameter1 001902fe, parameter2 b9cebbbc, parameter3 b9ceb8b8, parameter4 b965a667.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 32 0000002
0020: 34 20 20 50 61 72 61 6d 4 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 31 39 30 32 66 65 2c 20 1902fe,
0038: 62 39 63 65 62 62 62 63 b9cebbbc
0040: 2c 20 62 39 63 65 62 38 , b9ceb8
0048: 62 38 2c 20 62 39 36 35 b8, b965
0050: 61 36 36 37 a667
Forshock - Consult.Develop.Solve.

Year later. We have a system with approximately 8.05GB in citadel. System shutdown, restart. Database is now taking over 1 hour to "rebuild" and is not complete. Secondary has 7.99GB, same issue.
Processes will not function, system is sluggish, basically useless.
Long live Citadel...
Forshock - Consult.Develop.Solve.

Lookout crashes when i 'Edit Data Member Configuration'

SLC-500 Driver, Ethernet, SLC5/05 - only this one out of ten - im thinking something is corrupted. Any way to fix it? Or am i gona spend hours changing all the dependancies to a new driver?

There is probably something wrong in this object datamembers. Try to open the .lks file to recompile it and edit it. If it doesn't crashes, the problem is in the process file(.l4p). But if not, the source file(.lks) has the problem. If you are familiar with the lookout source file, open is by text editor and try to find it out, or post it here.
Ryan Shi
National Instruments

C++ runtime library crashing in Windows 7 and Lookout 6.5

Hello, I’m running Lookout 6.5 on a Windows 7 machine. After I load Lookout and try to go to some of my panels I get a “Microsoft Visual C++ Runtime Library” Runtime Error. It says “This program as requested the Runtime to terminate it in an unusual way. “ What can be causing this?
Thanks you.
SCADA Programmer at the Coachella Valley Water District.

Hi Windows7grl88,
Please type: "chkdsk /r /f" At the Command Prompt.
This kind of error can be caused by Software problem, please try to Place the computer in a clean boot state, which will start Windows by using a minimal set of drivers and startup programs, and follow the steps in this article to
perform a cleanboot:
How to perform a clean boot to troubleshoot a problem in Windows Vista, Windows 7, or Windows 8
http://support.microsoft.com/kb/929135
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Why does reopening Lookout 5.1 build 8 once a day stop radio polling crashes?

Polling 9 sites by radio has resulted in almost daily stoppage of Lookout process. At that time nothing is polled and the process stops taking in new information. To fix the problem the process must be reopened. While trying a fix, it was noted that if we reopened the process once a day before stoppages, that there would be no stoppage. Is this an issue only with Lookout 5.1?

I guess the fix you said is the one on the NI website.
Do you mean you were told by the fix that "if we reopened the process once a day before stoppages, that there would be no stoppage"?
We first need to locate where the problem is. So, which driver object do you use in your process?
Do you log the data to Citadel database?
Ryan Shi
National Instruments

LookoutDirect crashes when trying to open older .lks file

I am providing a new WinXP Pro SP3 PC with LookoutDirect v4.5.1 (build19) to upgrade/replace and older lookout system at a water treatment plant.
Being my first Lookout system I worked through the tutorials and everything worked great.
I then tried to open the .l4p file that I had copied from the existing system.
Lookout gave a message stating "The file C:\....l4p was created by an older version of Lookout. Please recompile it by opening the source file....lks"
I then try to open the existing .lks file and Lookout crashes. I get the standard Windows "Send Error Report" screen. The details say that the crashed Application is cbl.exe.
Details:
Finally I get a message that says "Cannot open specified file!"
Is there any way to repair the file? It may be possible that the existing system was NI Lookout and not LookoutDirect. Does anyone know if there is a restore path for the project?
Is it possible that I didn't correctly back up the existing project?
Thanks!
Nick

That can complicate things
I only have back to Lookout 5.1 in my library. However, a few examples on NI are for Lookout 4.0:
http://zone.ni.com/devzone/cda/epd/p/id/3811
http://zone.ni.com/devzone/cda/epd/p/id/4225
http://zone.ni.com/devzone/cda/epd/p/id/3978
http://zone.ni.com/devzone/cda/epd/p/id/4212
Forshock - Consult.Develop.Solve.

Lookout

We are running Lookout 6.1. After starting the program we get a message "Lookout Executable has encountered a problem and needs to close". It then asks to send an error report to Microsoft. When I hit "Don't send" the program closes. It has been doing this intermittently. We will start the program 2, 3, or 4 times and eventually it will continue to run. If it gets past 10 minutes or so, it will stay running. This morning we also had a couple of graphics disappear, a message came up saying the file was not there. I rebooted the computer, when lookout started up, (eventually), we were missing the data on the hypertrends, that has not happened before. Has anyone ever run across a similar problem(s). Can I reload the program without losing the processes we have built and data. Thanks for you help.

When you click more details on the error report, it will say the module that crashed.
What module?
We have experienced this with older CBX drivers that were made for Lookout 4.5/5.x on 6.0 and higher.
Forshock - Consult.Develop.Solve.

Java VM Error - Crashes while reading mjpeg

While reading a mjpeg I once and a while get the following exception which crashes the VM:
Please note this only happens after I reconnect to the mjpeg source and does not happen often.
# An unexpected error has been detected by Java Runtime Environment:
# Internal Error (0xc0000029), pid=5560, tid=936
# Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode windows-x86)
# Problematic frame:
# C [ntdll.dll+0x501cc]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x15ccf800): JavaThread "Thread-15" [_thread_in_native, id=936, stack(0x20200000,0x20250000)]
siginfo: ExceptionCode=0xc0000029
Registers:
EAX=0x2024f1f4, EBX=0x2024fa64, ECX=0x2024f24c, EDX=0x0ab04c90
ESP=0x2024f198, EBP=0x2024f520, ESI=0x2024f1a4, EDI=0x00000001
EIP=0x7c9501cc, EFLAGS=0x00000246
Top of Stack: (sp=0x2024f198)
0x2024f198: 0ab04d14 00000000 200ffde4 c0000027
0x2024f1a8: 00000002 00000000 7c342526 00000000
0x2024f1b8: 15ccf800 0ab04868 0aaf15c0 0aaf160c
0x2024f1c8: 0aaf19b4 2024f368 7c9101db 0ab04868
0x2024f1d8: 0b0b2a00 00000001 00010a94 00000000
0x2024f1e8: 157dfa64 0aaf1610 6d9daa61 c0000029
0x2024f1f8: 00000001 2024f1a4 7c9501cc 00000000
0x2024f208: 00000000 15ccf800 0aaf15f4 0aaf15f0
Instructions: (pc=0x7c9501cc)
0x7c9501bc: bd d8 fc ff ff 89 b5 dc fc ff ff e8 5c e3 fb ff
0x7c9501cc: e9 ab aa fd ff 48 48 74 2e 83 a5 e4 fc ff ff 00
Stack: [0x20200000,0x20250000], sp=0x2024f198, free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ntdll.dll+0x501cc]
C [msvcr71.dll+0x2526]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.sun.imageio.plugins.jpeg.JPEGImageReader.readImageHeader(JZZ)Z+0
j com.sun.imageio.plugins.jpeg.JPEGImageReader.readNativeHeader(Z)Z+12
j com.sun.imageio.plugins.jpeg.JPEGImageReader.checkTablesOnly()V+92
j com.sun.imageio.plugins.jpeg.JPEGImageReader.gotoImage(I)V+41
j com.sun.imageio.plugins.jpeg.JPEGImageReader.readHeader(IZ)V+2
j com.sun.imageio.plugins.jpeg.JPEGImageReader.readInternal(ILjavax/imageio/ImageReadParam;Z)Ljava/awt/image/Raster;+3
j com.sun.imageio.plugins.jpeg.JPEGImageReader.read(ILjavax/imageio/ImageReadParam;)Ljava/awt/image/BufferedImage;+4
j javax.imageio.ImageReader.read(I)Ljava/awt/image/BufferedImage;+3
..... and this traces back to my code where I call:
// imageDecoder is a ImageReader
        public void readJPG() { // read the embedded jpeg image
            if (!connected) {
                return;
            if (iis == null) {
                try {
                    iis = ImageIO.createImageInputStream(dis);
                } catch (Exception e) {
                    e.printStackTrace();
                    return;
            imageDecoder.setInput(iis, true);
            try {
                boolean jpegFound = false;
                boolean contentTypeFound = false;
                String line;
                do {
                    line = iis.readLine();
                    if (line.indexOf("Content-") > -1) {
                        contentTypeFound = true;
                    } else if ((contentTypeFound) && (line.length() == 0)) {
                        jpegFound = true;
                } while (!jpegFound);
// ****** This is where the call stack traces back to and its crashing here.
                image = imageDecoder.read(0);
            } catch (Exception e) {
                disconnect();
        }Edited by: avalanche333 on Jul 6, 2009 8:54 AM

unfortunately, this is a native crash, meaning the crash happens in a native library, not in java code. This makes it hard to nearly impossible to help you track the problem. The best you can do now is the following:
- search for your bug in the java bugs database
http://bugs.sun.com/
- if you cannot find it, gather as much information as you can and create a new bug report. Things to lookout for are your system specs, the JVM used, conditions under which the exception seems to occur (for example, does it always happen for the same source, or for different ones?). Be sure to post the crash output.
Of course that will not fix your immediate needs, so in the mean time you might want to try running on a different system to see if that changes anything.

Lookout 4.5 crash

Similar Messages

Maybe you are looking for