LookOut server client connection problem

[Ryan.S]

It looks like the problem happens after you rename your computer. Could you try to use the ip address instead of the computer name "EBWP4" in the symbolic link in the client process?

[Tulong]

I did that also, but it didn't work.  I will try that one more time and let you know.  Thanks.

[Tulong]

OK I did try to use the IP address instead, but the result remained the same.

[Tulong]

Update:

I formated the hard drive today and reinstalled the O.S. from the scratch on EBWP4 (which I did few times before too and still had problem with LookOut back then).  After getting all Windows updates done, I installed LookOut (N.I. must be tired of me keep reactivating LookOut licenses).  Launched client process on the server while having the server process running on EBWP5 and it worked just fine.  However, I still saw other client computers connected to EBWP4 thru the Client Connection Monitor.  I was expecting that none of our clients would show up in there since I didn't have the server process running on this server.  I haven't try the switch over yet because it was very late.  I will try it out tomorrow morning to see if it works (cross my fingers).

[Ryan.S]

I know why you still see the client connection on EBWP4 when they actually are connecting EBWP5. I didn't realize the client should have this connection all the time. Actually you have the monitor object in client process. The monitor object keeps reading data from the primary server EBWP4, no matter if the data is online or not. So even if you don't run the server process on EBWP4, the clients are still connecting to it to monitor the status. So the "problem" connection in connection monitor is not an issue.

After you run the server process on EBWP4, please try to run the client process on EBWP5 and see if it works.

[Tulong]

I tested out this morning.  All of my clients got correct information and everything was fine at the time.  However after only two to three minutes, all of my client screens got locked up (you could see LookOut was froze at that time).  Closed LookOut on client machines and reopened it, nothing worked.  All client didn't get any update, even the one that ran on EBWP4.  I then rebooted EBWP4 and opened server process again, but the problem remained.  I had to put EBWP5 back online after that.

[Ryan.S]

Could you give me your both server and client processes? You can upload to ftp://ftp.ni.com/incoming

I want to make sure that the problem is not in the process. And I will also try to setup the redundancy system here.

[Tulong]

OK I uploaded the file to the FTP server.  The file name is EBWP.zip.  This zip file contains four process files:  ebbpsvr.l4p which is the server file that we are talking about; ebclient.l4p is the client process; ebfpsvr.l4p is a server process that is running on a different server at a different site.  Clients are pulling data from both sites; and last one is the standby loader process ebwtpbpstandbyloader.l4p.

[Tulong]

Any news Ryan?

[Ryan.S]

I tested your program on my computers and did see something wrong. It looks like I have reproduced your problem here. We are still working on it.

The problem is probably in lookout and the specific lookout process. I don't think it's related to the hardware or the OS environment.