We have gotten to the point that we believe it is the server O.S. that is causing my troubles. I am changing to another PC today with a standard O.S. Lookout 5.1 has a neat new object called a tracer. According to that my server app is still serving data to Logos, but at 2:57:31.6 this morning, my clients quit recieving data from Logos.
OK, I have changed to a desktop PC and everything seems to be running fine. A little sluggish since it's a lesser machine, but it WORKS. Still have not been able to determine if it's the server O.S. or the server machine or both. NI has said they may look into supporting the server machines in the future.
I am running regular XP Pro 2002 Service Pack 1 on the computers that are having a problem and on the previous ones running that had no problems. At this time, I have the old computer back in place as the master(server) and have had no problems in over 6 days.
I won't be able to get back to troubleshooting this until 10/27 so when and if I make some progress I will let you know.
Lookout clients do save state files, too. Are you opening process files on network? If so, when Lookout trying to save the state file (.l4t) in the same folder as the process file, there are chances that Lookout fails to open the remote file. You may copy the process files to the client machine to solve this.
The process files have been copied to the clients. I finally got fed up, unplugged my machine and shipped it to NI. I'll let you know the final outcome.
Preliminary testing has revealed some problems with LOGOs dealing with dual hard drives and processors that are 2GHz and up. Some of the original development can no longer keep up. A new version of LOGOs may be forthcoming.