Using SQL Express 2005 for Openfire

Hi all,

I am having a heck of a time getting openfire to connect to Db. I have tried every combination of database URL that I can and have read about.

Database URL: jdbc:jtds:sqlserver://;appName=jive;instance=sqlexpress

I have used every combination of ip, port, and host name I can think of. I am installing openfire on the same machine that the Db is on. My machine name is chatterbox. I have made sure that TCP/IP, VIA, and Named Pipes are all enabled on the SQL Config. I am using sql auth. and just using sa to access my Db name openfire. I have already ran the query against the Db to put the tables an such in place. Following is the latest error I am getting after attempting to connect. Any help wold be greatly appreciate, as I am at the point of pulling out hair…and I do not do bald very well…LOL.

Thanks in advance for your help.

2012.02.08 15:44:18 org.jivesoftware.util.log.util.CommonsLogFactory - Prototype

java.sql.SQLException: Unable to get information from SQL Server: chatterbox.

at net.sourceforge.jtds.jdbc.MSSqlServerInfo.(

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.(

at net.sourceforge.jtds.jdbc.ConnectionJDBC3.(

at net.sourceforge.jtds.jdbc.Driver.connect(

at java.sql.DriverManager.getConnection(Unknown Source)

at java.sql.DriverManager.getConnection(Unknown Source)

at org.logicalcobwebs.proxool.DefaultConnectionBuilder.buildConnection(DefaultConn

at org.logicalcobwebs.proxool.Prototyper.buildConnection(

at org.logicalcobwebs.proxool.Prototyper.sweep(


I finally found the answer. So, if anybody is interested, here is what I found.

Why do I get a java.sql.SQLException: "Unable to get information from SQL Server" when trying to connect to an SQL Server instance?

The exception you are getting is usually caused by a timeout. When connecting to named instances jTDS needs to connect via UDP to port 1434 to get information about available SQL Server instances. While doing this it times out, throwing the exception you see (which means that jTDS was not able to get information about the running instances).

Connection timeouts occur when there is no server listening on the port (BTW, are you sure your SQL Server is configured to use TCP/IP and that you actually use named instances?).

On SQL Server 2005 the SQL Browser service must be running on the server host as the instance name lookup port UDP 1434 is hosted by this service on SQL Server 2005 rather than the SQL Server itself. The default install does not configure the SQL Browser service to start automatically so you must do it manually.