"Attempt to Log in Too Many Users Message"
(The following is from a posting on the AREV discussion board by Revelation
There have been some inquiries regarding users receiving an 'Attempt to login
too many users' message in Advanced Revelation. This message is a valid message
and should appear when the number of users who are attempting to log into Arev
exceeds the number of user licenses applied to Arev via the Lanpacks. In this
case users must purchase additional Lanpacks to increase the user count.
Lanpacks cannot not be duplicated and can only be applied to one Arev serial
number. (And one Arev serial number can exist only on one CPU).
We have identified a handful of situations where an 'Attempt to login too many
users' message appears when the number of users who are logging into Arev is
less than the number of user licenses. Here is a list of situations and remedies
for these cases.
Situation A: Old version of Novell Client32
You should make sure you have a recent version of Client32 loaded. We know that
the Client 32 dated 1/29/96 (in the release notes) caused this error. We have
also confirmed that the Client 32s dated 8/22/96 and 7/16/97 do not cause the
Situation B: CD ROM Tower or Proxy Server
Certain brands of CD-ROM towers or other types of pseudo-file server platforms
broadcast on the LAN as
a regular file server. This will cause Arev user locks to fail, generating the
error message. You can fix this by:
a) Enable access to the CD-ROM/Proxy Server only after they have logged
into AREV. If you have attached the
CD ROM/Proxy Server you will first have to delete the mapped drive before
entering Arev. This is done with the
command MAP DEL X: (where X: is the drive in question). You can add this line to
a batch file which then launches
Arev. Then within Arev you can restores the connection by issuing the command:
"suspend map x:=\\Server1\sys"
(Where \\Server1\sys is the name of the resource you are attaching.
b) Replace the CD-ROM server with one that reports back as a volume on an
existing server, not as a separate
Situation C: Attaching Multiple Servers with differing Novell User counts
For example in this situation you have two Novell Servers one with Unlimited
Novell users and the second with a five user Novell license. All your Arev
information and users are on the Unlimited Novell license, if you attach to the
five user system, Novell will report a user lock failure on the login of the
sixth user. This failure is interpreted by Arev as 'attempt to login too many
users'. To remedy this,
Attach the second server only after they have logged into AREV. If you
have attached the second server you will
first have to delete the mapped drive before entering Arev. This is done with
the command MAP DEL X: (where X: is
the drive in question). You can add this line to a batch file which then
launches Arev. Then within Arev you can
restores the connection by issuing the command: "suspend map
x:=\\Server1\sys" (Where \\Server1\sys is the
name of the resource you are attaching.
Situation D: You have multiple Arev's with the same serial number on the same
Every copy of Advanced Revelation must have a unique serial number; failure to
comply is a violation of the Revelation
Licensing Agreement. In this case a new license must immediately be purchased.
Furthermore, a Lanpack is also
uniquely serialized, and cannot be duplicated or applied more than once. If a
Lanpack has been applied to a license, that
license cannot be distributed to more than one server. If you need to deploy the
application on multiple servers, additional licenses
and Lanpacks must be purchased.