This section contains a list of error codes that can be generated by the Novell SecretStore service, along with a short description of the error.
-800 NSSO_E_OBJECT_NOT_FOUND |
Can't find the target object DN in NDS. (Resolve name failed). Possible cause: The server is unable to verify the user that is trying to read a SecretStore. The User object is not in NDS or is in a different partition or replica. Possible cause: The server that holds the read/write replica containing the User object is not up. |
-801 NSSO_E_NICI_FAILURE |
NICI operations have failed. |
-802 NSSO_E_INVALID_SECRET_ID |
Secret ID is not in the User SecretStore. |
-803 NSSO_E_SYSTEM_FAILURE |
Some internal operating system services are not available. |
-804 NSSO_E_ACCESS_DENIED |
Access to the target SecretStore has been denied. |
-805 NSSO_E_NDS_INTERNAL_FAILURE |
Some internal NDS services are not available. |
-806 NSSO_E_SECRET_UNINITIALIZED |
Secret has not been initialized with a write. |
-807 NSSO_E_BUFFER_LEN |
Size of the buffer is not in a nominal range between minimum and maximum. Possible cause: The programmer or vendor that wrote the connector for the application did not meet requirements. |
-808 NSSO_E_INCOMPATIBLE_VERSION |
Client and server component versions are not compatible. Possible cause: The version of Novell SecretStore that is running on the server is earlier than the version of SecretStore that is running on a client workstation. Possible action: Upgrade your server to the latest version of SecretStore. |
-809 NSSO_E_CORRUPTED_STORE |
SecretStore data on the server has been corrupted. Possible cause: A key has become corrupted and cannot decrypt data. If corruption occurs in the data, SecretStore repairs corrupted data. Whenever you add new secrets to SecretStore, the first read after a write automatically repairs and synchronizes SecretStore. If corruption occurs in the key, SecretStore discards the data and begins anew. |
-810 NSSO_E_SECRET_ID_EXISTS |
Secret ID already exists in the SecretStore. Possible cause: Using the Add option, you are trying to add a secret ID. The system informs you that the secret already exists. |
-811 NSSO_E_NDS_PWORD_CHANGED |
The network administrator has changed the user's NDS password. SecretStore is now locked. Possible action: If an application is locked, use SecretStore Manager or SecretStore Status to unlock SecretStore. |
-812 NSSO_E_INVALID_TARGET_OBJECT |
Target NDS User object not found. Possible cause: During a logon process, you passed the ResolveName process. However, the SecretStore service cannot find the target NDS User object to read a SecretStore in eDirectory. |
-813 NSSO_E_STORE_NOT_FOUND |
Target NDS User object does not have a SecretStore. Possible cause: The User object exists but does not have a SecretStore on it. This message usually comes while you are attempting to read (or enumerate) SecretStore. If you add or write to SecretStore, the SecretStore service automatically creates a secret. |
-814 NSSO_E_SERVICE_NOT_FOUND |
SecretStore is not on the network. Possible cause: The client pinged to find a server that is running the SecretStore service, but no SecretStore was found. Possible actions: - Install SecretStore on a server.
- Make sure that SSS.NLM is running on a SecretStore server.
|
-815 NSSO_E_SECRET_ID_TOO_LONG |
The length of the Secret ID buffer exceeds the limit. Possible cause: An application has attempted to pass in a secret ID that is longer than 256 characters. Possible action: Contact the vendor. |
-816 NSSO_E_ENUM_BUFF_TOO_SHORT |
The length of the enumeration buffer is too short. Possible cause: A programmer needs to make a call again to a larger buffer. NSSO returns what data it can in the buffer that was passed. Possible action: The maximum buffer size is 128KB. The maximum packet size is also 128KB. If you have more secrets IDs in SecretStore than 128KB, use wild cards to change the scope of your enumerations. Change the scope at the API level or in SecretStore utilities. |
-817 NSSO_E_NOT_AUTHENTICATED |
The user is not authenticated. Possible cause: A SecretStore server was found, but the SecretStore client was unable to open a connection. Possible action: Log in to eDirectory again. |
-818 NSSO_E_NOT_SUPPORTED |
Unsupported operations. Possible cause: A feature is published during beta but is not yet implemented. |
-819 NSSO_E_NDS_PWORD_INVALID |
The NDS password is not valid. Possible cause: You tried to unlock SecretStore, but you incorrectly entered a password. Possible action: Enter the correct password. |
-820 NSSO_E_NICI_OUTOF_SYNC |
Session keys of the client and server NICI are out of sync. Possible cause: A server went down and the connection was lost. When the server came up again and Client32 re-established a connection, the SecretStore client tried several times to get a session key from the SecretStore server and failed. SecretStore's session keys are not valid anymore. Possible action: Try to run the application again. |
-821 NSSO_E_SERVICE_NOT_SUPPORTED |
The requested service is not yet supported. Possible cause: The SecretStore client tried to call a plug-in (service) that SecretStore doesn't know about. Novell does not support the particular service. |
-822 NSSO_E_TOKEN_NOT_SUPPORTED |
The NDS authentication type is not supported. Possible cause: Although SecretStore recognizes the requesting service, SecretStore does not recognize the eDirectory authentication credential. The SecretStore plug-in might be a later version than the SecretStore version. |
-823 NSSO_E_UNICODE_OP_FAILURE |
A Unicode* text conversion operation failed. Possible cause: SecretStore tried to translate Unicode but was unable to. Possible action: Try again. |
-824 NSSO_E_TRANSPORT_FAILURE |
The server connection has been lost. Possible action: Wait for the server to reboot, or log in again. |
-825 NSSO_E_CRYPTO_OP_FAILURE |
A cryptographic operation has failed. Possible cause: When SecretStore tried to encrypt of decrypt data, the key or data was corrupted. Possible action: Try again. |
-826 NSSO_E_SERVER_CONN_FAILURE |
An attempt to open a connection to the server failed. Possible cause: The Transport plug-in SSNCP.NLM or SSLDP.NLM is not running on the server. Possible action: Ask the system administrator to load the Transport plug-in modules on the server. |
-827 NSSO_E_CONN_ACCESS_FAILURE |
Access to a server connection failed. Possible cause: A SecretStore client could not get exclusive hold of a connection table on the client. |
-829 NSSO_E_SECRET_BUFF_TOO_LONG |
The size of the secret buffer exceeds the limit. Possible action: Make the secrets smaller. |
-830 NSSO_E_SECRET_ID_TOO_SHORT |
The length of the secret ID should be greater than zero. Possible cause: The secret ID is zero. You have specified a null ID. Possible action: Contact the application vendor. |
-831 NSSO_E_CORRUPTED_PACKET_DATA |
Protocol data was corrupted on the wire. Possible cause: While sending data to the server or reading data from the server, SecretStore discovered that the data packets don't match. Possible action: Try again. |
-832 NSSO_E_EP_ACCESS_DENIED |
Enhanced protection password validation failed for the application. Access to the secret is denied. Possible cause: For reading this particular secret, you need to pass a particular application enhanced protection password. Possible action: Try again. Pass the enhanced protection password or enter a master password. Otherwise, contact the application vendor. |
-833 NSSO_E_SCHEMA_NOT_EXTENDED |
The NDS schema is not extended to support SecretStore on the target tree. Possible cause: SecretStore is not properly installed. SSS.NLM or SSS.DLM is running on a server, but the NDS schema has not been extended. Possible action: Reinstall SecretStore. |
-834 NSSO_E_ATTR_NOT_FOUND |
One of the optional service attributes is not instantiated. Possible cause: You are trying to open a set of configuration attributes, but a particular attribute is missing. Possible action: Configure the system. |
-835 NSSO_E_MIGRATION_NEEDED |
The server has been upgraded. The user's SecretStore should be updated. Possible cause: Internally, the SecretStore service has detected an older format in a user's SecretStore. The service reads the older format and then writes (migrates) the data by using the new format. |
-836 NSSO_E_MP_PWORD_INVALID |
The master password could not be verified to read or unlock the secrets. Possible cause: You entered an incorrect master password. Possible action: Correctly enter the master password. |
-837 NSSO_E_MP_PWORD_NOT_SET |
The master password has not been set on SecretStore. Possible cause: You are trying to read enhanced protected secrets or unlock SecretStore, but a master password is not set on SecretStore. Possible action: Set a new master password. |
-838 NSSO_E_MP_PWORD_NOT_ALLOWED |
The administrator has disabled the ability to use the master password. Possible cause: While configuring the SecretStore service, you checked the Disable Master Password Operations check box. |
-839 NSSO_E_WRONG_REPLICA_TYPE |
Not a writable replica of NDS. Possible cause: The replica is read-only. SecretStore is unable to write to or modify the replica. Several replicas might be running on the server, but the particular replica is read-only. Possible action: Go to a different replica. Set up SecretStore so that a user can always go to a writable replica. |
-840 NSSO_E_ATTR_VAL_NOT_FOUND |
The SecretStore service didn't find an attribute value (secret ID) that you are trying to read. |
-843 NSSO_E_CONFIG_NOT_SUPPORTED |
A user or a container has been assigned to use a particular configuration that is not available. Possible cause: Servers that support the configuration are all out of service for whatever reason. Possible actions: Make sure that the servers are functioning properly. Also make sure that the SecretStore service on those servers is loaded with the proper command line parameter. |
-888 NSSO_E_NOT_IMPLEMENTED |
This feature is not yet implemented. Possible cause: A feature is published during beta but is not yet implemented. |
-899 NSSO_E_BETA_EXPIRED |
The product beta life has expired. Purchase an officially released copy. |
