Ryan,
Unfortunately, a few hours after my last post my issue returned. However, unlike before the Lookout services are not crashing - in fact, my problem is similar to the same problem I had approximately 7 years ago >> http://forums.ni.com/t5/Lookout/Lookout-5-1-quits-serving-data-to-clients/td-p/102593
I did not want to post on the forum until I could pinpoint exactly what happens and make sure the same thing is happening over and over again. I already reinstalled Lookout 6.5 on my server, reactivated Lookout 6.5 on my server, recompiled my server file, and wiped out my database on my server. Windows firewall is disabled on my server and my clients. I can telnet to port 2343 before and after the problem occurs from the server to the client and vice versa.
Here is exactly what is happening: (this can happen 15 minutes or up to 45 hrs. after my computer running my server process has been rebooted)
1.) Lose Trends on clients (nicitdl.exe still shows running in task manager and resource monitor), but Lookout is still updating between client and server and I still can access server from client running development through symbolic link and network in object explorer. And, the client file running on the same computer as the server file behaves normally. At this point, I can reopen Lookout server file after stopping nictdl5 and everything works fine again.
2.) After some time without trends, I am unable to access server from client running development through symbolic link and network in object explorer. No red X's appear on the client machine that was running when trends were lost. However, if I open client process on a machine that wasn't running when the problem occurred I will see red x's everywhere. Also, on the server file I can still see clients listed in the Client Connection Monitor. And, the client file running on the same computer as the server file behaves normally. At this point, I can reopen Lookout server file after stopping nicitdl5.exe and everything works fine again.
3.) After some time without trends and being unable to access server from client running development through symbolic link and network in object explorer, my client connection monitor list goes blank. I then get red x's on all my clients. And, the client file running on the same computer as the server file makes lookout hang if I try to access any screen. At this point, if I reopen Lookout server file without stopping lkads.exe, Lookout will momentarily hang at splash screen then show "loading file" screen, and then "process registration failed" box will pop up. I have to close Lookout, stop lkads.exe and nicitdl5.exe, then reopen Lookout and everything works fine until the problem occurs again.
Through this entire process I do not see any evidence of the lkads or nicitdl5 service crashing in event viewer on the server computer or clients, I can telnet into port 2343 as I mentioned before, and the computer running my server process is still receiving data from the plcs in the field.
I have uploaded my server process and one of my client process files to the ftp site in the incoming folder under JPSCADA_jphillips folder. There is also cbx file you will need to open the process files.
The computer I am running my server process file on is a Dell Precision T3500 CMT, 32-bit Intel Xeon Six Core Processor,X5650,2.67GHz, 4Mb RAM.
Please see if you can duplicate this problem as soon as possible. If you need me to ship you my computer as was done in the past to solve the problem, please let me know.
Thank you for a quick response.
Jason Phillips
