I am having problems with some clients in that they do not reconnect trace data automatically when a server goes off and back on line. The client Lookout application needs to be restarted for traces to come back. I'm still looking into this, however I have seen the behavior inconsistently with both 6.2 (more consistently) and 6.5 clients. This problem also existed rarely before upgrade to 6.5 server with 6.2 server/client.
I am notified occasionally by some client users that they have no trends after I have restarted the server, and I have to stop and restart the nicitdl5 and lkads services as well as closing and reopening lookout on the client machine. I suspect it happens more but I assume my client users are rebooting their computers without notifying me which corrects the problem. And this does not happen on all of my clients after server restarts - random occurrences.
I am seeing the same problems, I have installed v6.5 on my servers and as I am going around to my clients, I install the software on the client machine and Lookout freezes up on both redundant servers, and I have to restart both servers.
I created the Logos folder and that corrected my client and server software not responding issues. Now I cannon see the alarms from the server on the client. I went into Alarms/Select Process clicked on network to expand it, but the hour glass just comes up and nothing happens. I tried registering the server computer and it says computer already registered. I also opened Tag Monitor, tryed connecting to the network computers and it cannot connect either. I am using a Laptop Compaq 1.40ghz running xp sp3.
