|
|
|
To connect to FairCom DB, a client calls a FairCom DB API function such as InitCtree(), InitCtreeXtd(), InitISAM(), InitISAMXtd(), or CTDBLogon(). A connection attempt may fail for various reasons. Check the function return code to determine possible causes for the connection failure. The following table sections lists errors a FairCom DB API function may return in the event of a failed connection attempt and describes possible causes and troubleshooting steps for each:
|
|
|
Error description
Memory allocation error during logon.
Possible causes
An attempt to allocate memory during logon failed. The most common cause is a shortage of system memory.
Troubleshooting steps
Check system memory usage by FairCom DB and other processes on the system. Free system memory (for example by stopping unnecessary processes or shutting down and restarting FairCom DB) and attempt to logon again.
|
|
|
Error description
Maximum users exceeded.
Possible causes
FairCom DB enforces a limit on the number of concurrently connected clients. This error indicates that the maximum number of concurrent connections has been reached.
Troubleshooting steps
In some cases, it is expected that the maximum number of clients may be logged on. In this situation, try the operation again after clients have logged off. If reaching the connected user limit is unexpected, use the ctadmn utility to list the current client connections and to view their activity. Use ctadmn to determine if there are any inactive client connections that can be terminated. When the number of connected clients is below the connection limit, try to logon again. Note, the Server is designed to allow one instance of the user ID “ADMIN” to be able to connect to the Server even if the maximum number of supported connections has been reached.
Note: A client which belongs to the ADMIN group and which sets the USERPRF_ADMSPCL bit of the user profile can log onto to FairCom DB even if the server already has the maximum permitted number of clients logged on. This capability is useful in situations in which it is necessary to perform system administration even when the client limit has been reached. The ctadmn utility automatically uses this feature.
|
|
|
Error description:
Could not send request. A communication error occurred while sending a request to the server.
Possible causes and troubleshooting steps:
The section "Clients Lose Connection to Server" describes possible causes and troubleshooting steps for this error.
|
|
|
Error description:
Could not receive answer. A communication error occurred while receiving a response from the server.
Possible causes and troubleshooting steps:
The section "Clients Lose Connection to Server" describes possible causes and troubleshooting steps for this error.
|
|
|
Error description:
The server could not be located.
Possible causes:
Troubleshooting steps:
|
|
|
Error description:
Server is shutting down. The client connected to the server but the server closed the connection.
Possible causes and troubleshooting steps:
The section "Clients Lose Connection to Server" describes possible causes and troubleshooting steps for this error.
|
|
|
Error description:
Server has gone away. The client connected to the server but the server closed the connection.
Possible causes and troubleshooting steps:
The section "Clients Lose Connection to Server" describes possible causes and troubleshooting steps for this error.
|
|
|
Error description:
Invalid user ID.
Possible causes:
The specified user ID does not exist.
Troubleshooting steps:
|
|
|
Error description:
Invalid password.
Possible causes:
The specified password is invalid for the specified user ID. Note that passwords are case-sensitive.
Troubleshooting steps:
To resolve this error, logon using the correct password for the specified user ID or use the ctadmn utility to change the password to match the specified password.
|
|
|
Error description:
Server could not process user or account information. FairCom DB encountered an error when reading the account information for the specified user.
Possible causes:
This logon error points to possible problems with the user account data in the FAIRCOM.FCS superfile. Depending on the location of the problem, the c tree Server may log one of the following messages to CTSTATUS.FCS:
User ID file processing error
User/Group file processing error
Valid ID file processing error
Troubleshooting steps:
Use the ctadmn utility to list the properties for the specified user account. If necessary, change account properties or delete and re-create the account. If the error persists, using the ctscmp utility to compact FAIRCOM.FCS may help correct this type of error. Or, if a good backup copy of FAIRCOM.FCS exists, restoring this file from backup is an option.
|
|
|
Error description:
Guest logons disabled.
Possible causes:
The client attempted to logon as guest by specifying a NULL or empty user ID, but guest logons are disabled. The guest account is disabled unless GUEST_LOGON YES is specified in a server settings or configuration file (the guest account is also disabled by specifying GUEST_LOGON NO).
Troubleshooting steps:
To avoid this error, logon using a non-guest account or reconfigure FairCom DB to allow guest access.
|
|
|
Error description:
Client does not match server.
Possible causes:
Some FairCom DB instances only accept connections by specially-configured FairCom DB clients. When a standard FairCom DB client attempts to connect to such a server, the server rejects the connection attempt with FairCom DB error 530.
Troubleshooting steps:
To avoid this error, connect to the server using the appropriate specially-configured FairCom DB client.
|
|
|
Error description:
Logon interval error. FairCom DB can be configured to require a user to logon at least once within a defined time. This ability can be configured on a per-user account basis and on a system-wide basis if desired. If the user fails to logon at least once within the prescribed time period, FairCom DB disables the user account and subsequent logon attempts using that user ID fail with FairCom DB error 579.
Possible causes:
A required logon time period is in effect for the specified user account and the user did not logon at least once within the specified time period.
Troubleshooting steps:
An administrator can re-enable a user account that FairCom DB has deactivated due to exceeding the required logon interval by using the ctadmn utility.
|
|
|
Error description:
Exceeded failed logon limit. FairCom DB supports setting a limit on the number of consecutive logon failures due to specifying an invalid password. This limit can be set on a per-user and on a system-wide basis. If a user exceeds the specified number of consecutive logon failures, the server disables the user account and subsequent logon attempts using that user ID fail with FairCom DB error 584.
Possible causes:
A consecutive logon failure limit is in effect for the specified user account and the user has exceeded the limit.
Troubleshooting steps:
An administrator can re-enable a user account that FairCom DB has deactivated due to exceeding the failed logon limit by using the ctadmn utility.
|
|
|
Error description:
Logon date exception. FairCom DB supports setting starting and ending validity dates for user accounts. An attempt to logon using a user account before its starting validity date or after its ending validity date fails with c tree error 585.
Possible causes:
A validity period is in effect for the specified user account and the starting validity date has not yet arrived, or the ending validity date has already passed.
Troubleshooting steps:
An administrator can change the starting and ending validity dates for a user account using the ctadmn utility.
|
|
|
Error description:
Member of ADMIN group required.
Possible causes:
A client is attempting to connect to FairCom DB in an administrative mode (for example, logging on using ctadmn or logging on in order to shut down the server) but the specified user ID is not a member of the ADMIN group.
Troubleshooting steps:
Logon using a user ID that is a member of the ADMIN group, or use the ctadmn utility to add the specified user ID to the ADMIN group.
|
|
|
Error description:
Non-ADMIN user blocked from logon. FairCom DB can be put into an operational mode in which only users that are members of the ADMIN group are allowed to logon. When this mode is in effect, logon attempts by non-ADMIN users are rejected with FairCom DB error 593.
Possible causes:
The server administrator has enabled FairCom DB’s ADMIN group only logon mode using the FairCom DB SECURITY API function or using the STARTUP_BLOCK_LOGONS keyword in the server configuration file.
Troubleshooting steps:
To resume normal server operation, the server administrator can call the c tree Plus SECURITY API function with a mode of SEC_BLOCK_OFF.
|
|
|
Error description:
One-use temporary password failure. FairCom DB supports establishing a one-time password that another client can use (along with the user ID matching the caller that set the password) as long as the original caller is still logged on. Once the original caller logs off, the one-time password becomes invalid. Once the password is used by the subsequent client, the password is no longer available.
Possible causes:
Either no one-time password is in effect for the specified user ID, or the specified password is invalid.
Troubleshooting steps:
Confirm that the client that established the one-time password is already logged on, that a client has not yet connected using the one-time password, and that the specified password is correct.
