Lookout 6.5 clients not connecting to server

[JPhillips]

Ryan,

On my primary server I created a new process, added a pot, and the result was the same error.

I then performed a repair which did not work, so I then did a complete uninstall/reinstall. After the reinstall, I opened Lookout at which point the default.l4p opened. I immediately opened Tag Monitor and was able to browse tags in the default process. I then opened my server process file, and when I went back to tag monitor I could not access tags in the server process or the default process file.

My next step was to recompile my server process file, and once I did that I was able to access tags in the Tag Monitor file. I was even able to open up the client file on my secondary server which is running 6.5. Unfortunately, after a short period of time, I lost my trends on the secondary, and then when I went to the primary and tried to browse tags in tag monitor, I got the same error I had previously sent you. Also, I saw the "CLOSE_WAIT" statements for my secondary when I ran "netstat -an" on the primary. Upon attempting to close Lookout on my primary, Lookout hung as it did before.

So, right now I have my server process file running, and I am able to browse tags. I just do not have any computers running 6.5 other than my server.

I will keep things this way until tomorrow morning to see if I can still browse tags, and if so, I will then try opening my client file on my secondary again to see if the problem resurfaces.

Hopefully, you guys can come closer to a solution with the info I have given you.

Thanks again.

[JPmsu]

Is there a solution to this issue yet?  I've just run into the same problem upgrading a pair of Lookout servers from 6.1 to 6.5.  The servers processes within Lookout 6.5 are able to access their data fine, but 6.5 clients cannot. 

I tried running TagMonitor on the 6.5 clients and get the "cannot enumerate items in this hierarchy" error.  6.1 clients I haven't upgraded yet have no problem and TagMonitor works without any issue on those. 

[Ryan.S]

This is the Logos problem. If you have firewall enabled on server or client computer, follow the KB to add process to exception, and open the necessary port.

http://digital.ni.com/public.nsf/websearch/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument

http://digital.ni.com/public.nsf/websearch/8AE45BBFA1D7025E862570F200642FD8?OpenDocument

[JPhillips]

JPmsu,

Did you uninstall 6.1 before you installed 6.5 on the computer running your server process?

[JPmsu]

I uninstalled 6.1, and then zorched the "Program Files\National Instruments" directory just to be sure, and then (because I had to do this on my servers or MAX kept dying) zorched the "All Users\Application Data\National Instruments" directory too prior to installing 6.5.

I'm not running Windows firewall on either the server or the clients, so that doesn't seem like the issue.  I can uninstall 6.5 client (with the appropriate zorching of NI directories above) and put 6.1 client back on the exact same PCs, and it talks to my 6.5 servers fine (TagMonitor works and everything).

[JPhillips]

When I first installed 6.5, I did not uninstall 6.2 first, and I thought that is why I am having this problem. However, the fact that you did a complete uninstall of your earlier version before installing 6.5 tells me that is not the cause of the problem.

Also, I have ICS service disabled on my servers, and all of my clients have the Windows firewall turned off automatically by our IT department. So, I agree that this is not a Windows firewall problem, and if it was, why did it not occur when 6.2 was running on my servers?

What type of computer is your server? I have a Dell Precision 690MT Workstation, 2.33 Ghz Quad Core Xeon Processor, 4GB RAM, running WinXP_SP3. The reason I ask is because I had a problem in the past when a new version was released similar to this problem, and it was due to the speed of the processor I had in my computer. They only discovered the problem when another person who was having the same problem actually sent his computer to tech support.

For now, I have just been running 6.5 on my server and 6.2 on my clients.

Hopefully, since someone else is now having a similar problem, tech support will dig deeper into this issue.

Ryan please help...

[JPmsu]

Our main server is a 2.2GHz Sempron box running XP SP3, a second one we run as a client-less clone of the primary for testing purposes is a 3GHz Pentium 4.  I never had an issue with CPU speed before, but I did discover when we upgraded hardware a few years back that Lookout 6.1 server would crash on anything with more than a single processor core.  This was one of our reasons for upgrading to 6.5, so I'm glad to hear your 6.5 runs on a quad-core box.

Our IT folks disable the Windows Firewall also.  I read through the links Ryan recently provided and the second looked promising at first, it discusses how Logos changed at one point from using UDP to using TCP connections.  But this change looks to have happened about Logos version 4.6, and my 6.1 clients claim to be using Logos version 4.9 while the 6.5 clients use 5.1, so if it was that Logos UDP/TCP change causing the problem my 6.1 clients shouldn't work either (and they work fine).

For the time being I'm sticking with 6.1 on the clients as well, though that's a stop-gap measure.  The folks who manage the control screens make changes every couple of weeks, and I have to hand-edit the *.lks files 6.5 makes before the 6.1 clients is able to compile them into a *.l4p to load.

[JPhillips]

Man, what a pain having to hand edit those files!

My thought is that since the "lkads" version changed from 6.2 to 6.5, and it is responsible for handling the communication line between the server and clients, something must have been changed in lkads from 6.2 to 6.5 that is causing this problem.

[Ryan.S]

When you had problem with 6.5 client, is there any other lookout software on the client computer besides the lookout 6.5 client software,?

Is the client computer in the same subnet as the server computer? Are they in the same domain? If not, are they in the same Windows workgroup?

As the TagMonitor has error, the problem is in Logos communication. The strategy of Logos communication doesn't change in lookout new release. If the logos with 6.1 works, the one from 6.5 should work. Perhaps we miss something in minor change of Logos.

When you tried the 6.5 client, how many 6.1 clients were connecting to the same server at the same time?

If you are okay to do some tests, please install 6.5 client upon the 6.1 client. Don't uninstall 6.1. The logos will be upgraded. And then try to use the 6.5 client to connect server. With both 6.1 and 6.5 installed, I want to know if either works.

[JPmsu]

No other NI software on the client PC I've been testing with.  Same subnet and domain as the server. 

TagMonitor works with just 6.1 installed.  When I install 6.5 over the top of it without an uninstall TagMonitor no longer functions and gives me the same "cannot enumerate the items in the hierarchy: Could not set current folder to:" error I got with just 6.5 installed.  Two other 6.1 clients were connected to our 4-client-license server when I tried 6.1 and it worked, the same two were connected when I tried 6.5 and it didn't.

Trying 6.1 client worked fine before I installed 6.5, then it stopped working.  6.5 client continues not to work.