Lookout 6.2 - nicitdl5.exe keeps crashing

[JPhillips]

About 2 weeks ago nicitdl5.exe started crashing on my server. I have this service set to restart after 1 minute if it crashes so this was not a problem when it first started happening because my hypertrend data was still visible. Now, over the past few days my trend data is hardly ever visible because nicitdl5.exe keeps crashing shortly after it is restarted, and when it does not crash right away I still do not have any trend data.

I have done a Lookout repair install, deatched and deleted my database and started a new one, but the problem still exists.

I am running Lookout 6.2 on a  Dell Precision PWS 690, 2.33 GHz Xeon Processor, 3GB Ram, Win XP OS

Below is the error data from Windows that I was hoping someone could analyze to see what is causing the problem:

Faulting application nicitdl5.exe, version 5.6.0.49153, faulting module nicitdl5.exe, version 5.6.0.49153, fault address 0x0001ef16.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

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 6e 69 63   ure  nic
0018: 69 74 64 6c 35 2e 65 78   itdl5.ex
0020: 65 20 35 2e 36 2e 30 2e   e 5.6.0.
0028: 34 39 31 35 33 20 69 6e   49153 in
0030: 20 6e 69 63 69 74 64 6c    nicitdl
0038: 35 2e 65 78 65 20 35 2e   5.exe 5.
0040: 36 2e 30 2e 34 39 31 35   6.0.4915
0048: 33 20 61 74 20 6f 66 66   3 at off
0050: 73 65 74 20 30 30 30 31   set 0001
0058: 65 66 31 36               ef16   

[JPhillips]

One more piece of information - when I bring up my client process on the server computer, the trends come up instantaneously and run fine.

[Ryan.S]

Do you mean that a new database still has the crash repeatedly?

Could you upload the database to the ftp site? You may need to detach it from MAX first, and then copy the files.

We want to test if the problem is in the database.

The nicitdl5.exe is used for transfering data between server and client. So if it crashes, the client cannot get the trend.

In MAX, you can also detach any other unused database. It is possible that the problem is in other database, and the one being used is good.

[JPhillips · Accepted solution]

Ryan,

The problem was in the old database - before I created the new database, I archived the old database but did not detach it.

Once I detached the old database, the problem disappeared.

Thanks!