03-21-2010 10:42 PM
Solved! Go to Solution.
03-23-2010 01:03 AM
What if you start the primary server process now? If it has problem, try to restart it just as what you did on secondary server. Let's see if it behaves the same way. From your description, it seems that the server doesn't work properly until you restart it.
If you use ip address in the symbolic link or monitor object, make sure the server computer uses the same ip address.
03-23-2010 09:05 AM
Ryan,
I did try that several times, but the problem remained. I even format the hard drive (this is a brand new workstation) and reinstall XP. Reinstall LookOut (at least three times) and still the problem. Another note that I should have mentioned before that I renamed the old LookOut servers; uninstall LookOut development/run time; and reinstall LookOut free client on those machine so that I can use them to replace our very old Client machines. The weird thing is the server process is working fine on the new secondary server, but not on the primary.
03-23-2010 04:13 PM
03-23-2010 09:19 PM
Yes, you can try to ghost the secondary server so that you will have an indentical one. At least the softwares will be exactly the same.
When you run the server process on primary server, try to run the client process on the same computer. Let's make sure that the server process and client process are good. If it works, try to run the client process on secondary server computer and see if it works.
03-24-2010 02:32 AM
03-24-2010 01:19 PM
03-24-2010 01:57 PM
03-25-2010 03:11 AM
Where do you see the "EBWP5" in Measurement&Automation? Is it still EBWP5 now?
The computer name in Lookout system menu is for the database. It doesn't affect the live data.
If the Lookout on primary server is development/runtime license, please take a look at the object explorere and check its computer name. I want to make sure the computer name is correct in Lookout, not like the one in MAX. I guess the problem is related to the computer name/ip address.
As you said the client connection monitor mistakenly displays all the client sites, are these lookout clients disconnected? Or they are connecting the secondary server? By design, once the client computer doesn't read the server data any more, the computer name/ip address will disappear in monitor immediately, just like what you saw on secondary server. If it shows some clients, it means those clients are connecting the server. So I wonder the actual status of those client processes.
I believe you use the symbolic link to connect the server process. If 20% items cannot read data, are they all from one or two specific link?
03-25-2010 01:35 PM
Ryan,
EBWP5 is the secondary, EBWP4 is the primary. I ghosted EBWP5 and put the image on EBWP4. Without trying to rename the machine after ghosting, my EBWP4 (after ghosted is EBWP5) was working perfectly. That eliminate any hardware related problems. I changed the machine name back to EBWP4. I saw "EBWP5" in Measurement&Automation. LookOut Object Explorer was still showing EBWP5, and of course nothing worked. However, I still saw bunches of clients connected to this guy EBWP4 even though I didn't have server process running. I went ahead and deleted a link in ODBC in order to be able to recreate the database with EBWP4 name. Launch LookOut then server process, some of my screens that weren't updated before were working but not all. A bunch of screens were working before, now stopped. The only client that got all correct data was the one that run on EBWP4. Data on clients come from two symbolic links: One is from this primary/secondary servers depended on which one is running the server process. The other is from another LookOut server running different server process at another site. The problem seems to happen with only server process running on EBWP4.