ENG0805 Error on WIN98 SE workstation running OpenInsight (OpenInsight Specific)
At 13 FEB 2002 01:34:45PM John Taylor wrote:
We are running an OpenInsight product on Novell 4.1 server with Win98 SE on workstations. The product has been working fine for past three years. We changed harddrive on this particular workstation and attempted to install the client portion of NetProduct Novell version 1.5. We get the ENG0805 error "unable to locate LH.DLL." All the other workstations have the same hardware and parameters are the same. We have some stations using Novell client and others using Microsoft Netware client. Why this error on a reinstall when the same machine ran software before?
At 13 FEB 2002 03:39PM Kevin Revelation Technologies wrote:
John,
The Revelation NLM client install is a misnomer. It only needs to be installed on one workstation on the network because it installs a driver that all the connecting workstations use. You should be able to map to the application that the other workstations map to, and you will have the same driver as they do.
Did you do the OI client install on the new workstation/drive? If you do not have it, the client driver is available for download on the website. Don't know if that is the problem, but it won't hurt to try.
Kevin
At 13 FEB 2002 06:52PM John Taylor wrote:
Kevin:
Thanks for the response. Yes, we ran the OpenInsight client install first and then got the ENG0805 error when we attempted to open oinsight.exe. I'm running Novell client 3.0.1 on my workstation and have no problems. The workstation in question had to uninstall Novell client since it caused problems with the Goldmine software that was recently installed. That workstation is using Microsoft Netware client. We have a laptop that connects with Microsoft Netware client and it can open oinsight. I read a postreferring to the ENG0805 error on Win 2000. Is this an issue with Win 98 and/or with the Microsoft Netware client?
At 14 FEB 2002 01:06PM John Taylor wrote:
Kevin:
I have the problem solved! I used the suggestion by Tim Marler and copied the NWCALLS.DLL and NWIPXSPX.DLL into the windows\system directory of the particular workstation. Now the application was fine. Thanks Tim and Kevin.