AREV points to database on a different server (AREV Specific)
At 05 JAN 2000 12:58:46PM cliff priddy wrote:
I have several netware 4.x servers running the arev nlm. In the process of upgrading the servers for y2k, I began with a spare server, used it to repace an existing non-compliant server, then upgraded that server, used it to replace the next one, and so on. Each time, I did not restore, but simply copied data from one server to the other, including the arev data and application, and reinstalled security. Now, when I run arev on a given server, it uses the nlm and the data on the server that originally had its name. I'm guessing that the arev licence is tied intrinsicly to the netware license at installation time. Is there a way to correct this without reinstalling arev? A hidden file that can be moved? A file which can be modified manually or through some arev utility? Can I reinstall a license only, without reinstalling all of arev?
on the
At 05 JAN 2000 01:10PM Stephen S. Revelation wrote:
Cliff,
I'm guessing that the arev licence is tied intrinsicly to the netware license at installation time.
To my knowledge this is not the case. Under normal ARev migration scenarios under Novell using our NLMs the following should be done as a general rule:
1) Copy the entire ARev directory structure over to the new Novell server with the same ARev root directory path as before (c:\revsoft\arev for example).
2) Install the Revelation NLMs to the new Novell NetWare server as was once done to the older NetWare server.
3) Remap workstation's network drive from old ARev copy to the new copy. Use the same path for simplicity (this way shortcuts, etc. will not have to be modified).
Now, if you were attaching data from other servers/directories outside of the ARev root this will have to be modified/copied to the new server as well.
-Stephen
At 05 JAN 2000 04:31PM cliff priddy wrote:
I reinstalled the original 1.12 client and nlm, then upgraded with the 1.5 client and nlm. No errors during the install or upgrade, but when I attempt to load the nlm I get a series of "Server-410-1586 Loader cannot find public symbol nnn" errors, nnn being LHInitialize, LHCreateFile, LHOpenFile, etc.. I kept extensive notes when I originally upgraded to the 1.5 client and nlm, and the process does not now go through the same series of screens, although the messages indicate it is installing and upgrading correctly. Both the install and upgrade have been simple in the past. Am I missing something now?
At 06 JAN 2000 11:27AM cliff priddy wrote:
Resolved the problem. Since I had moved only data, not system directories, the file LHSTART.NCF still had references to the original file server, ie. LOAD LHIPXSER /N=SERVER_NAME. I changed these to correctly indicate the file server on which the NLM was being loaded, and the problem appears to be resolved. HOWEVER … It still appears to me that there is an intrinsic link between the AREV NLM and the server on which it was installed, because when I load the NLM on any of these servers, I get a message on the primary server (the server which has the master copy of the NDS) indicating that the address for the server on which the NLM was originally loaded has changed. This is a Netware information message, and does not necessarily indicate an error. However, it does tell me that the AREV NLM has some link to the name and address of the file server on which it was originally installed.