Lookout Client not updating Hypertrend

[WaterWorks]

I have read several posts on this problem but I have not seen any fixs or patches.

I am running Lookout 6.02.    Using lookout client I have built several screens and have used Hypertrend to trend several different items.

As long as client is run on the local machine, the data in HyperTrend will fill in quickly and will ALWAYS be there.

When we remote into the server with the client, rarely does HyperTrend work, and even then gives us very little data.

Sometimes only two to three days worth of data will show up. 

From what I have seen on the posts this has been an issue for quite awhile.

There must be a fix out there by now! 

[Ryan.S]

We have done a lot of tests on this problem. We are able to reproduce that the hypertrend will stop updating after the trendwidth changes. It happens sometimes, but not always, and the missing data will come back after 2~3 minutes. This is not expected. Do you see the data missing always after you change the trendwidth?

If the Hypertrend rarely works, it's not the same issue. Have you installed the updates for Lookout 6.0.2? The attachment is the hyper.cbx in the updates. If you use web client, copy it to the Lookout folder, and then export to web server. If you use Lookout client software, just copy it to the lookout client folder and replace the old one. It fixes a performance problem in Hypertrend.

Then, I'd like you to have a look at the firewall if there are any on server or client computers. Follow these two KBs to configure the firewall.

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

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

[T@TPCG]

This was a citadel problem in 6.0.2. It wasn't solved for me until I upgraded to Lookout 6.1 which updated citadel. See this post for a temporary workaround.

http://forums.ni.com/ni/board/message?board.id=170&message.id=166255#M166255

[WaterWorks]

Thanks for the reply Ryan.

All updates for 6.0.2 are current.

I updated the hyper.cbx as noted in your post.

This did not seem to correct the problem.

We do not have any of the client laptop firewalls turned on.  If I turn the server firewall on, I can't connect to the client laptops.(Seperate issue that I will deal with in another post.) 

I turned the firewalls for the client laptops on and added the following exceptions to the the firewall exceptions list.

C:\Windows\system32\lkads.exe

C:\Windows\system32\lktsrv.exe

C:\Windows\system32\nicitdl.exe

C:\Windows\system32\nicitdl5.exe

C:\Program Files\National Instruments\Lookout x.x\lookout.exe

I can now connect and get the Hypertrend to work.

The first couple of times the trending was slow but by turning the

trend off, the trend would slowly load.  It is now a lot faster and

probably is restricted, now by the modem speed.

Thanks for your help.

WaterWorks

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

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

hyper1.zip (89 kb)

Message Edited by WaterWorks on 06-25-2008 06:23 PM

[Ryan.S]

That's great.

The hypertrend needs to load all data in the period of the trendwidth at the begining. All these data need to be copied from server to client's local cache, that's why it may be slow at first especially when the network is not good. Then, the hypertrend just read the latest data and append to the trend, so it can be faster.