Return to Jive Software

Skip navigation
Up to Discussions in Jive Forums
1,919 Views 3 Replies Last post: Oct 28, 2009 3:53 AM by brad.heller RSS
geissler Novice
geissler
8 posts since
Feb 6, 2002
Currently Being Moderated

Sep 7, 2009 3:28 AM

Connection to MS SQL Server 2008 with integrated Security failing

Hi.

I have Jive Forum Version 2.6.4. working with MS SQL Server 2005 DB. Sun Java 1.6.15, Tomcat 6.0.18

The Database Connection here is configured with User and Password.

The Database Driver is mssql2005jdbc1.1.jar. All works fine!

 

No I want to change my Database to MS SQL Server 2008. With Integrated Security = true.

I Use the new Driver from Microsoft: sqljdbc4.jar.

and sqljdbc_auth.dll placed in my windows\system32 Folder.

In jive_config.xml I have the following configuration:

<database>

<defaultProvider>

<driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver>

<serverURL>jdbc:sqlserver://DEKLI1S7021;instanceName=SQL7021;integratedSecurity=true;DatabaseName=Jive</serverURL>

<username> </username>

<password> </password>

<minConnections>3</minConnections>

<maxConnections>10</maxConnections>

<connectionTimeout>0.5</connectionTimeout>

</defaultProvider>

</database>

 

When I connect to the Jive Webapp I get a null Pointer Exception

and in DefaultConnectionProvider.log i have:

Starting ConnectionPool:
dbDriver = com.microsoft.sqlserver.jdbc.SQLServerDriver
dbServer = jdbc:sqlserver://DEKLI1S7021;instanceName=SQL7021;integratedSecurity=true;DatabaseName=Jive
dbLogin = 
log file = D:\\daten\\www\\wikanet\\jive264\\WEB-INF\\jivehome\logs\DefaultConnectionProvider.log
minconnections = 3
maxconnections = 10
Total refresh interval = 0.5 days
-----------------------------------------
--->Attempt (1 of 5) failed to create new connections set at startup:
    com.microsoft.sqlserver.jdbc.SQLServerException: Dieser Treiber ist nicht für integrierte Authentifizierung konfiguriert.

                                                             (in English: This driver is not configured for integrated authentication.)
    Will try again in 10 seconds...

 

I have another webapplication, which works correct with sqljdbc4.jar,

com.microsoft.sqlserver.jdbc.SQLServerDriver,

and jdbc:sqlserver://DEKLI1S7021;instanceName=SQL7021;integratedSecurity=true;DatabaseName=Jive

 

Any Ideas what I did wrong?

 

Thanks a lot

 

Martin

Tags: database, problem, configuration
Expert
brad.heller
3,517 posts since
Jun 18, 2009
Currently Being Moderated
Oct 16, 2009 12:40 AM in response to: Martin
Re: Connection to MS SQL Server 2008 with integrated Security failing

While Forums 2.6.4 is not supported, this looks like it's more a driver issue than anything else. What OS are you running on? Do the 2005 drivers support Integrated Security? If so, I would try using the 2005 drivers as the 2008 network layer is compatible with 2005.

 

Let me know how that works out.

 

- Brad

geissler Novice
geissler
8 posts since
Feb 6, 2002
Currently Being Moderated
Oct 19, 2009 12:35 AM in response to: brad.heller
Re: Connection to MS SQL Server 2008 with integrated Security failing

Hello,

thanks a lot for the answer.

 

Today I tried it and it worked.

Tomcat started as a service with the corresponding Domain\Username with the right to logon as a service.

This Username configured as DB_Owner in the SQL 2008 Database.

 

I have tried mssql2005jdbc1.1.jar and sqljdbc4.jar. Both working!

With this Configuration:

<driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver>
<serverURL>jdbc:sqlserver://DEKLI1S7020;DatabaseName=DE03059_WIKAnet_Jive;integratedSecurity=true;</serverURL>
<username />
<password />

 

Maybe my Computer or I needed a break :-)

 

Regards

 

Martin

Expert
brad.heller
3,517 posts since
Jun 18, 2009
Currently Being Moderated
Oct 28, 2009 3:53 AM in response to: Martin
Re: Connection to MS SQL Server 2008 with integrated Security failing

Thanks for sharing this solution. Integrated security with non-MS technologies (i.e. the Java stack) seems a bit spooky to me, but it's good to know that it works!

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.