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

Question

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

Answer 1

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