#Gss initiate failed dbvisualizer install
#Gss initiate failed dbvisualizer driver
#Gss initiate failed dbvisualizer code

This may require using a CallableStatement to execute the query, and adding calls to registerOutputParameter and getXXX.

#Gss initiate failed dbvisualizer code

See “Installing Stored Procedures” in Chapter 3 of the jConnect for JDBC Installation Guide.Īn output parameter was received and ignored.ĭescription: The query you executed returned an output parameter but the application result-processing code did not fetch it so it was ignored.Īction: If your application needs the output parameter data, you must rewrite the application so it can get it. Error encountered while attempting to retrieve metadata information: _ĭescription: The server may not have the necessary stored procedures for returning metadata information.Īction: Be sure that stored procedures for providing metadata are installed on the server.

#Gss initiate failed dbvisualizer install

Please install the required tables as mentioned in the jConnect documentation. Metadata accessor information was not found on this database. See Chapter 3, “Security” for more information. Please check your Kerberos environment and configuration.Īction: Check your Kerberos environment, and make sure that you authenticated properly to the KDC. Most likely, this was because of a Generic Security Services (GSS) exception. The server rejected your Kerberos login attempt. However, if you wish to avoid this warning, you should set the HOSTNAME to a string less than or equal to 30 bytes in length. Hostname property truncated, maximum length is 30.ĭescription: You provided a string greater than 30 characters for the HOSTNAME connection property, or the host machine on which the jConnect application is running has a name longer than 30 bytes in length.Īction: No action is necessary, since this is just a warning to indicate that jConnect is truncating the name to 30 bytes. Therefore, jConnect is using the hostname of _ as the service principal nameĪction: Make sure to explicitly specify a service principal name using the connection property. The client did not specify a SERVICE_PRINCIPAL_NAME Connection property. Sybase high-availability failover is not supported by this type of database server.ĭescription: The database to which jConnect attempted a connection does not support high availability failover.Īction: Connect only to database servers that support high availability failover. Please reconfigure your database, or do not request a high-availability session.ĭescription: The server to which jConnect attempted an HA-enabled connection did not allow the connection.Īction: Reconfigure the server to support high availability failover or do not set REQUEST_HA_SESSION to 'true.' The server denied your request to use the high-availability feature. In this case, you can safely ignore this warning. However, you may want your application to take advantage of the precedence of connection properties defined in the property list over those defined in the URL. In this case, the property value in the connection property list takes precedence.Īction: Be sure your application defines the connection property only once. The connection property may also be defined both in the connection properties list, and in the URL.

#Gss initiate failed dbvisualizer driver

It may be defined twice in the driver connection properties list with different capitalization, for example “password” and “PASSWORD.” Connection property names are not case-sensitive therefore, jConnect does not distinguish between property names with the same name but different capitalization. Also, if connecting to SQL Anywhere, use the SERVICENAME connection property to specify the database.ĭuplicate connection property _ ignored.ĭescription: A connection property is defined twice.

Error message:_.ĭescription: jConnect cannot connect to the database specified in the connection URL.Īction: Be sure the database name in the URL is correct. All pending statements on this transaction (if any) are committed.Īttempt to set database at login failed. Message = _.ĭescription: An internal assertion in the jConnect driver has failed.Īction: Use the devclasses debug classes to determine the reason for this message and report the problem to Sybase Technical Support.ĪutoCommit option has changed to true.

SEVERE WARNING: An assertion has failed, please use devclasses todetermine the source of this serious bug. The following table lists the SQL exception and warning messages that you may encounter when using jConnect.