If you get unexpected errors when attempting to enable or use Kerberos authentication, it is recommended that you enable additional diagnostic messages on the database server and client.
Specifying the -z option when you start the database server, or using CALL sa_server_option( 'DebuggingInformation', 'ON' )
if the server is already running includes additional diagnostic messages in the database server message log. The LogFile
connection parameter writes client diagnostic messages to the specified file. As an alternative to using the LogFile connection
parameter, you can execute the command dbping -z. The -z parameter displays diagnostic messages that should help identify
the cause of the connection problem.
Symptom | Common solutions |
---|---|
"Unable to load Kerberos GSS-API library" message |
|
"Unable to acquire Kerberos credentials for server name "server-name"" message |
|
"Kerberos login failed" client error |
|
If the client got an error attempting to connect using Kerberos authentication:
Symptom | Common solutions |
---|---|
"Kerberos logins are not supported" error and the LogFile includes the message "Failed to load the Kerberos GSS-API library" |
|
"Kerberos logins are not supported" error |
|
"Kerberos login failed" error |
|
"Login mode 'Kerberos' not permitted by login_mode setting" error |
|
"The login ID 'client-Kerberos-principal' has not been mapped to any database user ID" |
|
Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |