Feedback
Did this article resolve your question/issue?

   

Article

Error received when connecting a second time with the SQL Server JDBC driver and creating a new schema

Information

 
TitleError received when connecting a second time with the SQL Server JDBC driver and creating a new schema
URL NameError-received-when-connecting-a-second-time-with-the-SQL-Server-JDBC-driver-and-creating-a-new-schema
Article Number000152005
EnvironmentProduct: Connect for JDBC SQL Server driver
Version: 5.1
OS: java
Database: SQL server 2012
Application: all supported applications
Question/Problem Description
The below error is received when connecting a second time with the SQL Server JDBC driver and creating a new schema.
Steps to Reproduce
Clarifying Information
The two connections are taken from separated connection pools and NTLM authentication is used.

The following collation query is run in the first connection:

SELECT CONVERT (varchar, SERVERPROPERTY('collation'))

If this collation verification is removed, the second connection works. 
Error Message[DataDirect][SQLServer JDBC Driver]A username was not specified and the driver could not establish a connection using Kerberos (type 4) integrated security
Defect Number
Enhancement Number
Cause
Resolution
The error is not caused by the driver. Changing the application code solved this issue.
Workaround
Notes
Last Modified Date8/3/2016 7:06 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.