Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

17SASL-GSSAPI
This section discusses the error messages logged by the SASL-GSSAPI authentication mechanism.
• Section 17.1, “Log File Locations,” on page 93
• Section 17.2, “Error Messages,” on page 93
17.1 Log File Locations
The error messages are logged as follows:
• Linux and UNIX: ndsd.log
• NetWare: logger screen
• Windows: c:\temp\saslgss.log
17.2 Error Messages
SASL-GSSAPI: Reading Object user_FDN FAILED eDirectory error code
Cause: This error is generated in eDirectory. The user_FDN does not exist.
17
novdocx (en) 6 April 2007
SASL-GSSAPI: Reading principal names for user_FDN failed eDirectory error code
Cause: This error is generated in eDirectory. The Kerberos principal names not attached to the user
object (userdn).
SASL-GSSAPI: Reading Object Realm_FDN FAILED eDirectory error code
Cause: This error is generated in eDirectory. The realm object does not exist.
SASL-GSSAPI: Not enough memory
Cause: Not enough memory to perform the specific operation.
SASL-GSSAPI: Invalid Input Token
Cause: Token from client is defective or invalid
SASL-GSSAPI: NMAS error NMAS error code
Cause: This error is generated in NMAS and is an internal error.
SASL-GSS: Invalid LDAP service principal name LDAP_service_principal_name
Cause: The LDAP service principal name is invalid.
SASL-GSS: Reading LDAP service principal key from eDirectory failed
Cause: The LDAP service principal object is not created.
SASL-GSSAPI
93