Lookout 6 Hypertrends - Symlinks- Static URL problems

[erblock]

OK Avi,

Thanks for that.

Now how about status on this thread's direct issue with Hypertrends via Symbolic Links via the internet, or outside of the server's (symlink pointer address) subnet.  This issue is also quite critical.

Regards,

Ed

[.avi file]

Greetings!
       Yes, the direct issue with Hypertrends via Symbolic Links via the internet, or outside of the server's (symlink pointer address) subnet issue has also been resolved.
Thanks
Avi

[MarkB 89]

Has there been any update on the release of this fix. The problem I an having is with the sqlsevr.exe process is using 100% of the processor. If I stop the nicitdl5.exe then the sqlservr process goes to 0. I had this problem when i first upgraded to 6.0.1 but I let the processes run without Lookout running and in about 24 to 30 hours it stopped using the 99 to 100% and Lookout ran pretty much normal. This all started again when by mistake the computer was logged on to the network administrator, normally this computer is just logged on with the local administrator. This is a real problem.

[nickf]

I'm pleased to announce that the Lookout 6.0.2 update has been posted at:

ftp://ftp.ni.com/support/lookout/updates/6.0.2/

This is a free update to current users of Lookout 6.x.
After downloading the update, you must uninstall any existing copies of Lookout 6.0.x before installing Lookout 6.0.2

Regards,
Nick Folse
Lookout Product Support Engineer
National Instruments

[erblock]

Thank You!!!!

[erblock]

Quote:

----------------------------------------------------------:

Greetings!
       Yes, the direct issue with Hypertrends via Symbolic Links via the internet, or outside of the server's (symlink pointer address) subnet issue has also been resolved.
Thanks
Avi

______________________________________

Remote (web) clients outside of server process's subnet still do not populate hypertrends when using IP address symlinks!!  Has this issue been resolved yet??  It has been well over a year now since I identified this MAJOR issue.  Are there any workarounds available to get hypertrends to display in web clients that are on remote subnets (internet).

Pleeeease Update Status!

Thanks,

Ed

Message Edited by erblock on 11-14-2006 11:55 PM

[Ryan.S]

These are what I have tested.

On server side, create a pot and log its value.

On client side, create a hypertrend, add a trace of that pot.

The ip of server is 10.xxx.0.xxx, the one of client is 10.xxx.1.xxx. The gateway of them are different. They can ping each other.

First, I run the client process in Lookout Client software. I tried both ip and pcname in the URL, and both worked.

Then, I run the client machine as the web server. The result was the same. The hypertrend in IE read data fine, no matter ip or pcname were used.

So, I think this problem has been solved in Lookout 6.0.2.

[erblock]

Now take that client home with you and tell me it works from there as well.  I cannot get it to work across different Class A subnets. With your test equipment, those may be  virtual subnets, which is not the same as differents physical segments?  Please get some more info from the Lookout team.  I'm willing to test whatever is necessary.

Note: make sure your test client uses a symlink for the connection.  That is the form of the original bug report and acknowlegement.

This is the generic error form for all my Hypertrend traces:

Failed to open trace "\\nnn.nnn.nnn.nnn\stgis\table1.NT_7UH3". The trace may not exist, or it's not logging to a Citadel 5 database.  Note that all my client's Hypertrends link to a DataTable on the server process through a Symbolic Link.

Ed

Message Edited by erblock on 11-16-2006 07:21 AM

[Ryan.S]

I have tried the symbolic link and it worked fine.

What do you mean by "subnet"?

I'm sure if I take the client process back home, it won't work. I don't think we need to make it work. They cannot even ping each other. How can Lookout make them communicate?

[erblock]

Of course it needs to work....that is the whole point of a web client!  If you put the client processes on a web server, you should be able to access it from anywhere on the Internet given the proper permissions and firewall allowances of course.  I have a complete set of client screens working just wonderfully from anywhere in the world.  Unfortunately, all the Hypertrend displays are missing traces!

Anyone got Hypertrends working on a remote web client process?  Anyone?

I'm continuing to test this situation to verify the problem but I know your engineers initially acknowledged this issue, said it would take longer to fix that the IP symlink on local subnet issue.  But there never was a definitive update stating that the tougher fix was complete.

I find it had to believe that you NI folks wouldn't pat yourselves on the back and promulgate that fix because it is a huge deal (BUG...).