A.1 SecretStore Return Codes
-800 NSSS E OBJECT NOT FOUND
Source:
Novell® SecretStore®
Explanation:
Can’t find the target object DN in NDS® or Novell eDirectory™. (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.
Source:
Novell SecretStore
Explanation:
NICI operations have failed.
-802 NSSS E INVALID SECRET ID
Source:
Novell SecretStore
Explanation:
The secret ID is not in the User SecretStore.
-803 NSSS E SYSTEM FAILURE
Source:
Novell SecretStore
Explanation:
Some internal operating system services are not available.
-804 NSSS E ACCESS DENIED
Source:
Novell SecretStore
Explanation:
Access to the target SecretStore has been denied.
-805 NSSS E NDS INTERNAL FAILURE
Source:
Novell SecretStore
Explanation:
Some internal eDirectory or NDS services are not available.
-806 NSSS E SECRET UNINITIALIZED
Source:
Novell SecretStore
Explanation:
A secret has not been initialized with a write.
Source:
Novell SecretStore
Explanation:
The size of the buffer is not in a nominal range between minimum and maximum.
Possible Cause:
The programmer or vendor who wrote the connector for the application did not meet requirements.
-808 NSSS E INCOMPATIBLE VERSION
Source:
Novell SecretStore
Explanation:
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.
Action:
Upgrade your server to the latest version of SecretStore.
-809 NSSS E CORRUPTED STORE
Explanation:
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 NSSS E SECRET ID EXISTS
Source:
Novell SecretStore
Explanation:
The secret ID already exists in the SecretStore.
Possible Cause:
You are trying to add a secret ID using the Add option. The system informs you that the secret already exists.
-811 NSSS E NDS PWORD CHANGED
Source:
Novell SecretStore
Explanation:
The network administrator has changed the user's eDirectory or NDS password. SecretStore is now locked.
-812 NSSS E INVALID TARGET OBJECT
Source:
Novell SecretStore
Explanation:
The target eDirectory or NDS User object is not found.
Possible Cause:
During a logon process, you passed the ResolveName process. However, the SecretStore service cannot find the target eDirectory or NDS User object to read a SecretStore in eDirectory.
-813 NSSS E STORE NOT FOUND
Source:
Novell SecretStore
Explanation:
The target eDirectory or 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 NSSS E SERVICE NOT FOUND
Source:
Novell SecretStore
Explanation:
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.
Action:
Install SecretStore on a server.
Action:
Make sure that sss.nlm is running on a SecretStore server.
-815 NSSS E SECRET ID TOO LONG
Source:
Novell SecretStore
Explanation:
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.
Action:
Contact the vendor of the application.
-816 NSSS E ENUM BUFF TOO SHORT
Source:
Novell SecretStore
Explanation:
The length of the enumeration buffer is too short.
Possible Cause:
A programmer needs to make a call again to a larger buffer. NSSS returns what data it can in the buffer that was passed.
Action:
The maximum buffer size is 128 KB. The maximum packet size is also 128 KB. If you have more secrets IDs in SecretStore than 128 KB, use wild cards to change the scope of your enumerations. Change the scope at the API level or in SecretStore utilities.
-817 NSSS E NOT AUTHENTICATED
Source:
Novell SecretStore
Explanation:
The user is not authenticated.
Possible Cause:
A SecretStore server was found, but the SecretStore client was unable to open a connection.
Action:
Log in to eDirectory again.
-818 NSSS E NOT SUPPORTED
Source:
Novell SecretStore
Explanation:
Unsupported operations.
Possible Cause:
A feature was published during beta but is not yet implemented.
-819 NSSS E NDS PWORD INVALID
Source:
Novell SecretStore
Explanation:
The eDirectory or NDS password is not valid.
Possible Cause:
You tried to unlock SecretStore, but you incorrectly entered a password.
Action:
Enter the correct password.
-820 NSSS E NICI OUTOF SYNC
Source:
Novell SecretStore
Explanation:
The 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 Novell 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.
Action:
Try to run the application again.
-821 NSSS E SERVICE NOT SUPPORTED
Source:
Novell SecretStore
Explanation:
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 that particular service.
-822 NSSS E TOKEN NOT SUPPORTED
Source:
Novell SecretStore
Explanation:
The eDirectory or 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 NSSS E UNICODE OP FAILURE
Source:
Novell SecretStore
Explanation:
A Unicode* text conversion operation failed.
Possible Cause:
SecretStore tried to translate Unicode but was unable to.
Action:
Try again.
-824 NSSS E TRANSPORT FAILURE
Source:
Novell SecretStore
Explanation:
The server connection has been lost.
Action:
Wait for the server to reboot, or log in again.
-825 NSSS E CRYPTO OP FAILURE
Source:
Novell SecretStore
Explanation:
A cryptographic operation failed.
Possible Cause:
When SecretStore tried to encrypt or decrypt data, the key or data was corrupted.
Action:
Try again.
-826 NSSS E SERVER CONN FAILURE
Source:
Novell SecretStore
Explanation:
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.
Action:
Ask the system administrator to load the Transport plug-in modules on the server.
-827 NSSS E CONN ACCESS FAILURE
Source:
Novell SecretStore
Explanation:
Access to a server connection failed.
Possible Cause:
A SecretStore client could not get exclusive hold of a connection table on the client.
-828 NSSS E ENUM BUFF TOO LONG
Source:
Novell SecretStore
Explanation:
The size of the enumeration buffer exceeds the 128-KB limit.
-829 NSSS E SECRET BUFF TOO LONG
Source:
Novell SecretStore
Explanation:
The size of the Secret buffer exceeds the limit.
Action:
Make the secrets smaller.
-830 NSSS E SECRET ID TOO SHORT
Source:
Novell SecretStore
Explanation:
The length of the secret ID should be greater than zero.
Possible Cause:
The secret ID is zero. You have specified a null ID.
Action:
Contact the application vendor.
-831 NSSS E CORRUPTED PACKET DATA
Source:
Novell SecretStore
Explanation:
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.
Action:
Try again.
-832 NSSS E EP ACCESS DENIED
Source:
Novell SecretStore
Explanation:
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.
Action:
Try again. Pass the enhanced protection password or enter a master password. Otherwise, contact the application vendor.
-833 NSSS E SCHEMA NOT EXTENDED
Source:
Novell SecretStore
Explanation:
The eDirectory or 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 eDirectory or NDS schema has not been extended.
Action:
Reinstall SecretStore.
-834 NSSS E ATTR NOT FOUND
Source:
Novell SecretStore
Explanation:
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.
Action:
Configure the system.
-835 NSSS E MIGRATION NEEDED
Source:
Novell SecretStore
Explanation:
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 NSSS E MP PWORD INVALID
Source:
Novell SecretStore
Explanation:
The master password could not be verified to read or unlock the secrets.
Possible Cause:
You entered an incorrect master password.
Action:
Correctly enter the master password.
-837 NSSS E MP PWORD NOT SET
Source:
Novell SecretStore
Explanation:
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.
Action:
Set a new master password.
-838 NSSS E MP PWORD NOT ALLOWED
Source:
Novell SecretStore
Explanation:
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 NSSS E WRONG REPLICA TYPE
Source:
Novell SecretStore
Explanation:
Not a writable replica of eDirectory or 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.
Action:
Go to a different replica. Set up SecretStore so that a user can always go to a writable replica.
-840 NSSS E ATTR VAL NOT FOUND
Source:
Novell SecretStore
Explanation:
The SecretStore service didn't find an attribute value (secret ID) that you are trying to read.
-841 NSSS E INVALID PARAM
Source:
Novell SecretStore
Explanation:
An API parameter is not initialized. A null or out-of-range parameter was passed to a client NDK API.
Action:
Don't pass null parameters to the APIs.
-842 NSSS E NEED SECURE CHANNEL
Source:
Novell SecretStore
Explanation:
An LDAP request to SecretStore is trying to make a clear-text connection, which is not allowed. The connection to SecretStore needs to be over SSL.
Action:
Use an SSL connection.
-843 NSSS E CONFIG NOT SUPPORTED
Source:
Novell SecretStore
Explanation:
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.
Action:
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.
-844 NSSS E STORE NOT LOCKED
Source:
Novell SecretStore
Explanation:
An attempt to unlock SecretStore failed because the store isn't locked.
-845 NSSS E TIME OUT OF SYNC
Source:
Novell SecretStore
Explanation:
The servers holding read/write replicas of the user’s SecretStore are out of sync with the time source on the network.
-846 NSSS E VERSION MISMATCH
Source:
Novell SecretStore
Explanation:
Versions of the client files don't match. For Windows, the files are nsss.dll, nssldp.dll, and nssncp.dll. For NetWare®, the files are corresponding .nlm files. For UNIX, the files are corresponding .lib files.
Action:
Install the latest client files.
-847 NSSS E SECRET BUFF TOO SHORT
Source:
Novell SecretStore
Explanation:
The buffer supplied for the secret is too short.
Action:
Use the proper buffer sizes out of nssscl.h to allocate for API use.
-848 NSSS E SH SECRET FAILURE
Source:
Novell SecretStore
Explanation:
Shared-secret processing and operations failed on the client.
Action:
Make sure that the shared secrets are in the correct format.
-849 NSSS E PARSER FAILURE
Source:
Novell SecretStore
Explanation:
Shared-secret parser operations failed on the client.
Action:
Make sure that the shared secrets are in the correct format.
-850 NSSS E UTF8 OP FAILURE
Source:
Novell SecretStore
Explanation:
Utf8 string operations failed on the client. This is an internal LDAP failure.
Action:
Check LDAP NDK components (.dll, .nlm, or .lib files).
-851 NSSS E CTX LESS CN NOT UNIQUE
Source:
Novell SecretStore
Explanation:
More than one DN contains the user’s Common Name in eDirectory. The contextless name for an LDAP bind does not resolve to a unique DN.
Action:
Specify the DN instead of the Common Name.
-852 NSSS E UNSUPPORTED BIND CRED
Source:
Novell SecretStore
Explanation:
The login credential required for the advanced bind operation is not supported by this version.
Action:
Refer to the list of supported protocols in the documentation.
-853 NSSS E CERTIFICATE NOT FOUND
Source:
Novell SecretStore
Explanation:
The LDAP Root certificate required for bind operations is not found.
Action:
Verify the accuracy of the user’s LDAP DN, password, or servers IP address.
-888 NSSS E NOT IMPLEMENTED
Source:
Novell SecretStore
Explanation:
This feature is not yet implemented.
Possible Cause:
A feature was published during beta but is not yet implemented.
Source:
Novell SecretStore
Explanation:
The product's beta life has expired.
Action:
Purchase an officially released copy.