A.2 Anonymous User Creation

Login failed for user

Possible Cause: The password might be invalid or the user does not exist.
Action: Give the Admin User ID (or User ID with security equivalent to admin) and password.

Failed to map Name to ID. Trying to contact Master server. This could take several minutes.

Possible Cause: The server might be a read-only/non-replica server and the master server is down or the anonymous user object just created would not have been synchronized in the master server.
Action: Try again later.

Failed to allocate and initialize NDS buffers.

Possible Cause: Inadequate system memory.
Action: Free some system memory.

Failed to add Anonymous user object to NDS.

Possible Cause: The username should have security equivalent to admin to create an anonymous user object.
Action: Create an admin user (or user with security equivalent to admin) and password.

Failed to generate an ObjectKeyPair for the Anonymous object.

Possible Cause: The username should have security equivalent to admin to create an anonymous user object.
Action: Create an admin user (or user with security equivalent to admin) and password.

Failed to open a connection with the local server

Possible Cause: The NCP connection table might be full.
Action: Do the following:
  1. Load monitor.nlm.

  2. Clear the connections that are not required.

Failed to create Anonymous home directory

Possible Cause: Any of the following:
  • The username might not be security equivalent to admin to create an anonymous user object

  • The volume does not exist

  • There is a directory I/O error

  • There is a hardware failure

Failed to add rights to Anonymous user

Possible Cause: Any of the following:
  • The username might not be security equivalent to admin to create an anonymous user object

  • The volume does not exist

  • There is a directory I/O error

  • There is a hardware failure

Failed to initialize Anonymous user access

Possible Cause: Any of the following:
  • The user should be security equivalent to an admin user

  • The memory is insufficient

  • The local server might be a read-only/no-replica server and the master server is down or not reachable

  • The connection table might be full