TimeService problems with Lookout 6.02

[erblock]

On a machine that had lots of Lookout 5.1 and Lookout 6 and Labview 7 with several components installed.  Uninstalled ALL NI software through contol panel.  Then performed clean install of Lookout 6.02.

Now Lookout will not start because it can't find the time service (although all Lookout services are listed as running in "Services" and task manager also lists lktsrv.exe as running.)

So far, I've only had this problem on one of two machines attempted, but the machine that had no problems did not have all the Labview and components previously installed.

Is there a registry cleaner for NI Products?

[erblock]

Performed manual registry clean of anything NI after uninstalling Lookout 6.02.

Still same problem after re-install!

HELP NI LOOKOUT TEAM!

[Doug M]

erblock,
Please see this Knowledge Base entry on how to manually remove and install the Lookout Services.  If this does not work, we do have a utility that exposes all National Instruments installer files and removes them -- if you would like to try this you will need to create a Service Request so we can email it to you.

[erblock]

Thanks Doug....but nothing works, even clean OS reinstall.

However, I found the bug!

***You cannot start Lookout 6.02 in a remote desktop session (mstsc.exe)***

That is it....I was doing everything remotely through mstsc and that remote connection somehow screws up finding the time service!

Could you please consider fixing this...It was not a problem in previous versions (to the best of my knowlege).

Cheers,

Ed

Message Edited by erblock on 11-29-2005 09:20 AM

Message Edited by erblock on 11-29-2005 09:20 AM

[Doug M]

Ed,
I am able to start Lookout 6.0.2 just fine using Remote Desktop using Win XP SP2, so there may be something about your system configuration that is causing this, especially if it is just occuring on one computer.

There is an older thread similar to this issue if you are running Lookout as an NT service.

Message Edited by Doug M on 11-29-2005 02:03 PM

[erblock]

Message Edited by erblock on 11-29-2005 07:25 PM

[erblock]

Hi Doug,

I neglected to tell you it was on Windows 2003 Server, Standard Edition SP1+ (to november updates).  I realize you don't officially support server OS's, however, I have been using them for many years with little problem. 

An chance you folks can at least look to confirm and maybe resolve this issue?  Afterall, Lookout is an industrialized product that should be able to run on more robust and reliable Operating Systems.

Thanks,

Ed

["lookout 6.0"]

I'm having the same problem too after I upgraded to Lookout 6.0.2 from Lookout 6.0.  I did a complete uninstall of Lookout 6.0, including removing all Lookout & National Instruments references in the registry files.  When I try to connect using Remote Desktop Web Connection, I get the timeservice problem, however, I can load lookout when I'm logon directly to the server (not using Remote Desktop).  I have Windows 2000 Server OS.

P.S. I didn't have the timeserver problem when connecting via Remote Desktop prior to upgrading.

[Doug M]

Thanks for contacting National Instruments!

Unfortunately, National Instruments does not currently support Windows Server OSes -- see the following KnowledgeBase:

As such, we cannot guarantee backwards or forwards compatibility of Lookout on Windows Server products, even when one version of Lookout seems to work fine on Windows Server, since Windows Server is not a platform we test on.  Our departments look very closely at customer feedback and I would urge you to leave feedback on features you would like to see in future versions of National Instruments products.  You can leave feedback on our website by going to this page:

["lookout 6.0"]

I found a solution that works for my timeserver problem via remote desktop, see my previous post (reply #8).  During the remote desktop session, I double clicked on the timeserver file located at c:\winnt\system32\lktsrv then Lookout would load successfully.