Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Lookout 4.0 w/Fieldpoint

11 views
Skip to first unread message

Todd Buchholz

unread,
Nov 2, 1999, 3:00:00 AM11/2/99
to

Installed Fieldpoint 1.7 after Lookout 4.0 and restarted PC. Lookout no longer
ran due to missing "lkhist.dll" file. Reinstalling Lookout solved problem.
Anyone else seen this yet?

Anita Anderson

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to

Todd,

I tried to replicate your problem on a newly reformatted NT machine. My
lkhist.dll was on my machine, both before & after. Lookout ran fine so I'm
not sure why your machine experienced the problem. There are a few other
things you should be aware of.

Fieldpoint Explorer 1.7 is an older version of the software, designed prior
to Lookout 4.0. It will run with Lookout 4.0, but there are a few reasons
for why you should install the current version (2.0) when using Lookout 4.0.
When you install version 1.7, it will actually overwrite the fpoint.cbx
in the Lookout 4.0 directory with an older version. The main reason to upgrade
your FieldPoint software is that there is a crash associated with using the
old fpoint.cbx with Lookout 4.0. Also, the older version of the FieldPoint
software does not support the FP-1600 network module. I'm guessing that
you aren't using this network module, but if you decide to use it in the
future, you would need to upgrade anyway.

The most recent version (2.0) is available in a zip file from our ftp site
at
ftp://ftp.ni.com/support/fieldpoint/Server/

After you install that software, you can go to the site below and download
a couple of fixes available for Lookout 4.0. Among them is a newer version
of fpoint.cbx which fixes the crash problem.

ftp://ftp.ni.com/support/lookout/Lookout4fixes/

Anita Anderson
National Instruments

Ronald Morrison

unread,
Nov 16, 1999, 3:00:00 AM11/16/99
to

I saw the same error using LO 4.0 with FP 2.0 on a WIN98 machine. LO 4.0
had been running and I received the FP1600 module with the Updated 2.0 software.
Loaded the FP 2.0 software and LO 4.0 no longer ran.
It was looking for the lksock.dll file. I have not tried to re-install yet
but i assume that will correct the error. The question I have is, when I
re-install LO 4.0 will it overwrite the files installed by FP2.0 software
for proper operation with FP stuff??

Aaron Gelfand

unread,
Nov 22, 1999, 3:00:00 AM11/22/99
to

>>I saw the same error using LO 4.0 with FP 2.0 on a WIN98 machine. LO 4.0>had
been running and I received the FP1600 module with the Updated 2.0 software.>
Loaded the FP 2.0 software and LO 4.0 no longer ran.>It was looking for the
lksock.dll file. I have not tried to re-install yet>but i assume that will
correct the error. The question I have is, when I>re-install LO 4.0 will
it overwrite the files installed by FP2.0 software>for proper operation with
FP stuff??

The problem is that FieldPoint is trying to update some of the Lookout services
that it also uses. However, it does not always suceed in stopping them to
properly update the file. Try the following reinstall of FieldPoint (not
Lookout) to properly update the services:

Take a look at this article from the NI knowledgebase:
FieldPoint Explorer 2.0 Fails to Install LKSock.dll for Lookout
Services. When the computer is rebooted, it generates an error
saying that it can not find the lksock.dll (NT also generates
an error log saying that the Lookout Citadel Service, Lookout
Time Service and Lookout Classified Ads are unable to start).

This will primarily occur if you are using a pre-release build
of FieldPoint Explorer 2.0 (Builds 65-78). However, it has also been seen
when installing FieldPoint on machines that had pre-release and release versions
of Lookout 4. The cause of the problem is that the installer will be unable
to stop the Lookout Services that are running in the background, which lock
several dll's preventing the updated version from being installed.


On Windows 95/98:
WARNING: Be careful when editing the registry. Make a backup first!

1) Run Regedit
2) Goto HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
and delete the following 3 keys:
"LKADS"="lkads.exe -win95"
"LKCITDL"="lkcitdl.exe -win95"
"LKTSRV"="lktsrv.exe -win95"
3) Re-boot the machine
4) Reinstall FieldPoint Explorer 2.0

On Windows NT:
1) Go to Control Panel==>Services
2) Disable the following 3 Services:
Lookout Citadel Server
Lookout Classified Ads
Lookout Time Synchronization
3) Re-boot the Machine
4) Reinstall FieldPoint Explorer 2.0

support

unread,
Jan 12, 2000, 3:00:00 AM1/12/00
to
Anita,

I followed your instructions and downloaded the updates from the FTP
site.
One of that was "lksock.dll".
However if you use this version the following error message is generated
when starting the Citadel services.

"The LKSOCK.DLL file is linked to missing export
LKDYNAM.DLL:ThreadStartup"

Does this mean that the updated "LKDYNAM.DLL" is missing from the FTP
site.

David Crofts
Acquisition Systems Ltd

Anita Anderson

unread,
Jan 13, 2000, 3:00:00 AM1/13/00
to

David,

You're very right. At the time that I made that post, it was valid information.
In the mean-time, the version of lksock.dll on the ftp site has changed,
and it references parts of the new lkdynam.dll (not on the ftp site).

We will be releasing a maintenence update to Lookout at the end of this month
that will resolve all of these inconsistencies.

Obviously, with file versions on the ftp site changing frequently in this
interim time period, I do not want to give directions on how to "fix" this
until the maintenence release (lest my advice once again become invalid before
someone else reads it).

For anyone else who experiences similar problems, please go to our Ask an
Engineer site at http://www.ni.com/ask
and provide the details as David did. You will receive a reply from one
of our Applications Engineers who will help you get a consistent combination
of files.

I apologize for the inconvience during this interim time before the maintenence
release. David, I will send the current instructions to you after posting
this message.

Anita Anderson

0 new messages