05-18-2010 03:43 AM
How long does the report object wait after the batch file is executed? When lookout is maximized, a lot of resources will be loaded. I suggest to wait a bit longer.
05-19-2010 02:07 AM
Now it waits 75 seconds. Should we expand that period?
Ivan Krantic
UNO-LUX Processing
05-19-2010 03:45 AM
75 seconds is enough. Did you notice which module crashed? When it crashes, a window dialog will pop up and you can click "click here" to get the crash module name. Usually it is a DLL file. Was the crash dump enabled? If you have a crash dump of this crash, upload to our ftp.
This time doesn't look like the last database crash. It looks like the crash is related to the report object. If the database is corrupted, we can fix it by creating a new one and archive the good data. But if the crash happens in report object or lookout DLL files, we need to look into the crash dump or to reproduce the crash and debug it.
05-20-2010 02:43 AM
I just uploaded the dump file to your ftp. The file is "Dr Watson.zip".
Ivan Krantic
UNO-LUX Processing
05-20-2010 03:05 AM
05-20-2010 07:41 AM
Now I see, you are right. I must check that with the guy that sent me those log file.
Ivan Krantic
05-27-2010 01:09 AM
It looks like that Dr, Watson didn't created the dump file for the latest crush. Should it be enabled again each time it activates?
Ivan Krantic
UNO-LUX Processing
05-27-2010 02:23 AM
I don't think we need to enable it again. After we execute "drwtsn32 -i" for the first time, it is installed and enabled.
After each crash, the new information will be added to the log file, and the new dump file will replace the current one.
You can try to remove the log file and dump file.
06-14-2010 03:31 AM - edited 06-14-2010 03:37 AM
We had another crash two days before. I will upload the dump file to your ftp.
Can you please inspect the file and tell me what cause the crash this time.
File name is Dr. Watson.zip
Ivan Krantic
UNO-LUX Processing
06-14-2010 03:16 PM
In the log file, there is an error on 6/12/2010 @ 08:05:28.453. I guess this is the crash.
The problem is in C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\KMUC41LF.DLL. It is not a lookout file. It looks like the printer's driver. When lookout prints the panel, lookout.exe calls the driver(DLL file). The DLL file has an exception, and then lookout.exe crashes.
I'm sorry I don't know what we can do, because the problem is not in lookout.