{{tag>category:"Network Product" author:"Dimitri Mandelis" author:"Kevin Ruane Revelation" author:"Kevin Ruane"}}
[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]
==== Getting Error installing Client piece of Universal Driver (Network Product) ====
=== At 13 FEB 2004 12:58:23PM Dimitri Mandelis wrote: ===
When I attempt to install the Universal Driver 3.0 client side
upgrade I get a warning that pops up at the end of the installation
that says "OpenInsight was unable to upgrade internal system files"
The 3.0 Driver is on OI because I can see it in there with NETDRV but
OI will not start up even if I Switch it back to all networks drivers.
I've tried the client install on a network drive and on a local drive.
any ideas,
thanks in advance
Dimitri
----
=== At 13 FEB 2004 01:12PM Kevin Ruane Revelation wrote: ===
Dimitri,
What version of OI is this?
I see this message occasionally - the internal files that do not get upgraded are the swapping of the active driver in NETDRV. Changing them manually should do the trick. Since OI is not starting after you change the driver, it makes me think there is a Driver/Server version mismatch going on.
What Service/NLM is on the server, and do you have the revparams in place?
Kevin
----
=== At 13 FEB 2004 02:32PM Dimitri Mandelis wrote: ===
Kevin,
I've copied OI32 4.1.2 to a new server and changed the drivers to
All networks ( tested startup ) and then did the 3.0 Uni upgrade.
I've copied OI32 4.1.2 to a new server and changed the drivers to
All networks ( tested startup ) upgraded to 7.0 (tested startup) and then did the 3.0 Uni upgrade.
I get the error message everytime
Thanks,
Dimitri
----
=== At 13 FEB 2004 04:40PM Kevin Ruane wrote: ===
Dimitri,
Was unable to reproduce here in the last few minutes...What version of the UD does it say in NetDrv? The most current version is 3.0.0.2. How about the date of your 7.0 download?
In General, when the UD Client installs, it drops in three .dlls:
LH3.dll
LH3CLNT.dll
RCL.dll
If you switch to an All Networks Driver, Then erase these .dlls, all things will be like they were prior to installing the UD Client.
Clean enough. But do not do it yet.
Depending on what version of 7.0 you have (the latest, as of this posting), it will already have the UD 3.0.0.2 client installed. Then there is no need to reinstall the UD client in 7.0.
The fact that you keep getting an error message about "unable to upgrade system files" is what is unnerving. Do you get any FS errors as well?
Do you want to delete the three .dll's out of your copy of 4.1.3 and have me send you new ones that you can drop in?
Kevin
----
=== At 13 FEB 2004 06:59PM Dimitri Mandelis wrote: ===
Well some progress was made - the 3.0 client installed and when
I check out the driver it is using the 3.0.0.2 version. Now I'm getting a FS231 error file 1 error. I've gone thru the revparam
file (many times) and it looks correct. If I switch to the all
networks driver and remove the revparam OI starts up ok. The NLM loads fine.
I read someone else had an similar error until he did put the hostname in his DNS server. We dont a have a DNS server here . Do
I need one now to run the 3.0 driver?
any ideas,
thanks Dimitri
----
=== At 17 FEB 2004 04:00PM Kevin Ruane wrote: ===
Dimitri,
Good, we're making progress. The following is an excerpt of a White Paper in progress dealing with the FS231:
-Confirm that the Universal Driver is loaded as the client
-Confirm that the lh3srvc.nlm is running (load using the LH3START on the Netware Console)
-Confirm that the lh3srvc.ini file and the revparam file are properly set (look at the examples in the UniDriver documentation). Matching case is critical between the file contents and the files themselves
-Confirm that the REVPARAM file does not have an extension (use a dos editor to confirm - Windows can lie about this)
-Confirm that you can ping the IP address of the Netware Server from a workstation
-Confirm that you can ping the Server by Name - if not:
Check the host file and confirm the server is listed or
Change the servername in the revparam file to the IP address of the Server
-Put an lh3srvc.log file in the same directory where the lh3srvc.nlm resides, and stop and restart the .NLM (LH3STOP and LH3START)
-You can also try a lh3.log file where the application resides
These should clear up the FS231 error.
Kevin
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=DA2AC2ABD3DB0CAA85256E390062BAB3|View this thread on the Works forum...]]