Kbase 12148: Resolving Error 1334 on VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Resolving Error 1334 on VMS
This entry describes a strategy to troubleshoot and resolve PROGRESS
error 1334: Rejecting login -- too many users for this server.
This entry is written specificly for VMS, but you can use it to
implement a strategy on other platforms.
Follow these steps to determine if the cause of this error is that
MAXCLIENTS is set too low.
1) Verify that the following startup options are set correctly for
the configuration you are using:
MAXCLIENTS (-Ma) - The maximum number of remote users per remote
client server.
MINCLIENTS (-Mi) - The number of remote users on a remote client
server before the broker starts another server.
MAXSERVERS (-Mn) - The maximum number of remote client servers that
can be started by the broker process.
MAXPROTOCOL (-Mp)- The number of remote client servers that can be
started to serve remote users for any one protocol.
PLEASE NOTE: The -Mp startup option must equal
the value of the MAXSERVERS and MUST BE USED, or PROGRESS
may generate an error. For example, if MAXSERVERS is set
to 40 and MAXPROTOCOL is set to 20, then only 20 servers
may be spawned and PROGRESS may generate an error.
2) Use the following formula to verify that the system resources are
adequate for PROGRESS:
CLIENT MEMORY -
{ NUMBER_OF_USERS * (STACK + EDIT_BUFFER + LOCAL_BUFFER_SIZE) }
+
{ NUMBER_OF_USERS * 512K (user data space) } = total client memory
SERVER MEMORY -
{ number of databases * 3 MB (server data space and general startup
options) + BUFFERS } = total server memory
3) Verify that the following NETWORK resources are adequate:
MAXLINKS - Each client requires one link, each remote client server
requires one link. Use SHOW KNOWN LINKS to display
MAXLINKS inNCP.
MAXIMUM DETACHED processes - use AUTHORIZE to verify.
MAXIMUM DECLARED OBJECTS - the number of DECNET objects allowed.
Use NCP to verify. Each remote client server and
broker require one object.
4) If you verify steps 1-3, then the error MAY be a known PROGRESS
bug in Version 6.2L for VMS - up to 6.2L15. In this bug, the
broker uses the MAXCLIENTS value instead of NUMBER_OF_USERS, and
it only allows a limited number of users into the database.
To workaround this bug, set MAXCLIENTS artificially high. For
example, set it to 100 users instead of 5.
5) If the steps 1-4 do not resolve the problem, then gather as much
information as you can and try to duplicate the problem against the
DEMO database.
The following documentation contains information regarding this issue:
PROGRESS System Administration II - Startup Options
VMS Documentation - NCP, AUTHORIZE
Progress Software Technical Support Note # 12148