Lookout 5.1 quits serving data to clients

[JPhillips]

That is great to hear!! Finally, some progress. And since my new computers have dual hard drives and 3.06GHz processors those problems with Logos make sense.

Thanks for the update, Carl!

[LDS@MGAS]

I wish this was a closed topic, but I´m having this problems too. It´s been a long time since the last post and I´d like to know if someone could finally come up with the solution. My server has 2 hard drives (lookout 6.0.2 with updates, installed on drive E:\SCADA\Lookout 6.0, 😧 is CDROM), an x86 Family 6 Model 10 Stepping 1 701MHz processor and 1 GB of RAM. Windows 2000 with SP4. HP Netserver 10/100TX PCI LAN Adapter.
This issue happens usually once in a week, but this week it happened three times. No change was made to the server.
The server processes are running on E:\SCADA\PRODUCCION\CAMPO and the database is on E:\SCADA\LOOKOUT6.0\DATABASE

All clients connect to the server through symbolic links. There are about 12 clients. They show the same behaviour described in previous posts. First no data is refreshed, then the red X´s appear. In this red X situation, when I enter on edit mode on the development machine, I can access through the symbolic link to the server for some time, and then, all of a sudden, it´s gone.

Please give me some advice, This problem is driving me crazy.

[LDS@MGAS]

Forgot to mention the OS is Windows 2000 "Server" with SP4.

[LDS@MGAS]

Also forgot to mention that all clients have (at least) P4 2.8 GHz with 1GB RAM and Windows 2000 Professional or WinXP.

[Ryan.S]

When you have this problem, try the tagmonitor.exe on client machine. It is in  \National Instruments\Shared\TagMonitor\.

If you cannot read data or access the item on remote server either, it is the logos communication problem. Since all your clients fail at the same time, I guess the problem in on the server machine. The logos communication is maybe blocked on the server machine.

Here is a KB about the logos and networking. Pay attention to the UDP port that logos needs, make sure that the logos is not blocked by firewall or something.

http://zone.ni.com/devzone/cda/tut/p/id/3681

[LDS@MGAS]

Thanks for your answer. I will try the tagmonitor the next time this problem appears. I´ll also check with the people in charge of the firewalls to see if the ports are forwarded and open as they should. Will be updating when I have new information.

[LDS@MGAS]

It happened again today. Red crosses in my client app. I used the tagmonitor and was able to see the objects on the server and to access them; so it seems that it´s not a Logos problem... The weird thing is that the red crosses appeared just after I closed LookOut (which gave me a runtime error) and reopened it, on the development PC. Any ideas?

Thanks.

[Ryan.S]

The development pc is a different pc from the lookout server and client, right? Do you get the runtime error every time you close Lookout?

If the red X always happen after a crash on your development computer, the crash may corrupt something.

How did you recover the client? Did you just reopen the Lookout client, or you need to also reopen the lookout server?

[LDS@MGAS]

It is a different pc from the server, but it may be considered as a client one, although I don´t open the client app unless I need to modify something. This runtime error doesn´t always happen, and I really don´t know if the red X appear always after this error, but I will check it.
The client only recover when I restart Lookout on the server machine.
I should mention that I have another app running on a pc to monitor communications. This app has a symbolic link to another process on the server. When the red X problem happened last time, I checked this monitor app, and it worked alright. This makes me think that it isn´t a comm problem with the server, but a problem with the client or the server process.
The client process has about 10 symb links all of them pointing at the server. One to the main process and the others to some smaller processes. It´s size is about 11 Mb.
The main server process has about 10 symb links; 2 to communicate with 2 other servers (both with Lookout 5.1 and a small app with some modbus objects; clients don´t connect to these 2 servers). I´ve never had a communication problem with these servers.  The other symb links are to gather data from the smaller processes (all of them running on the main server machine).
Can you think of an idea on how to troubleshoot this system?

[Ryan.S]

I don't have much idea of troubleshooting this problem.

You can upload your server and client process file to ftp://ftp.ni.com/incoming. Hope we can reproduce the problem here.

Except the two 5.1 modbus servers, your both problem server and client are running in Lookout 6.1, right?