I tried to upgrade from the Novell IPX driver 5.5 to the Universal 3.0. The 2 installation steps for ARev 3.12 appeared to go well as did the Server install on a Netware 6.0 server. LH3Start started OK. I switched the protocol on the W2K workstation from preferred IPX to IP. When I started AREV there was a long pause (20 sec.) and then the error "FS231". I looked for other discussions in Works relating to this error but nothing seemed to address this type of configuration.

The REVPARAM is configured as follows:

ServerOnly=True

ServerName=FSERVER2

TcpIpPort =9998

ShareName =OI413

ShareName =ARev31

The lh3srvc.ini is as follows:

Initial configuration - See Manual for examples

Global

TcpIpPort=9998

NamedPipeName=None

AnonymousUsername=ServiceLogOn

Shares

AREV31=SYS:ARev

OI413=SYS:OpenInsight

#=

#=

David,

Can you ping the server with the server name? Or try using the IP address as the server name.

Jody

Could be a name resolution issue with the server. Where is your DNS being hosted? Is the server mentioned as a host. You could always enter an IP Address in the Revparam file.

I changed the Revparam file to look like this:

ServerOnly=True

ServerName=192.168.0.2

TcpIpPort =9998

ShareName =ARev31

I ran 'arev lanpack' and changed to the Universal driver.

I then ran Arev from the W2k workstation using IPX and Arev hung.

I renamed Revparam to xxx and Arev would run.

I switched the workstation to IP and renamed xxx back to Revparam

When I ran Arev, I got the startup banner screen and then it hung. At that time I got a critical error on the server which suspended some processes. I rebooted the server and set everything back to the IPX 5.5 driver.

Any ideas as to what to try next?

David,

You are no longer getting the FS231, but some other error, correct?

In the course of testing the UD I would:

- Rename the revparam to something else

- Stop the old Revelation NLM files, and rename/remove them. This includes the lhipxser.nlm and the lh.nlm

- confirm that your apps are using the UD driver

- confirm that your revparam and lhsrvc.ini are configured correctly

- modify your Novell Client32 to use IP as the preferred protocol

Then rename your revparam file back to revparam, and start the UD on the Novell Server with the "lh3start" command. Now see if you can get into Arev. If you cannot then:

- try starting Arev from a command line to see if you get a better error message

- try loading the UD files individually to see if there is an error there

- send me the errors and your lhsrvc.ini and revparam files

Hope it helps.

Another thought…

With the UD, there is only one revparam in most cases. With the NLM 5.5, there is one in every subdirectory with a .lk/.ov file. Be sure to rename them when moving to the UD…

I followed the steps that you outlined and was successful in getting ARev to run using the UD. However the W2K workstation that was using was very slow. It took a timed 45 seconds to load Arev. I installed the UD on OI 4.13 and got an error "Filing System installation failed. (Repos_BFS–FS) Open Engine cannot continue." I unloaded the UD and reloaded it. OI ran very slowly on this workstation but was OK on other workstations.

After doing some checking with Novell, I found an article that recommended using "Auto Detect" in the Link Speed of the Network card. I remember that someone on Works had suggested setting a fixed speed when I was having trouble installing 5.5 in OI. I reset the card's link speed to 'Auto Detect' and that fixed the problem

Now all is well. Thanks for the help.

View this thread on the Works forum...