Unable to get information from SQL Server.
Applies to: Microsoft SQL Server 2016 Standard Edition.
Problem Description.
We were installing a third-party security software for a company that
provides telecommunications services, when the installation failed we found
below content on the application setup log. As it can be appreciated the los has
some Java SQL exceptions.
[2018-11-09 14:50:02,192] FATAL - com.quintron.vx.core.om.PersistenceException:
org.hibernate.exception.GenericJDBCException: Cannot open connection
com.quintron.vx.core.om.PersistenceException:
org.hibernate.exception.GenericJDBCException: Cannot open connection
at com.quintron.vx.core.omimpl.hibernate.HB_VXModel.init(HB_VXModel.java:327)
at com.quintron.vx.core.omimpl.hibernate.HB_VXModel.init(HB_VXModel.java:304)
at com.quintron.vx.core.omimpl.hibernate.HB_VXModel.init(HB_VXModel.java:224)
at
com.quintron.vx.core.omimpl.hibernate.HB_VXModelConnector.a(HB_VXModelConnector.java:11)
at
com.quintron.vx.core.omimpl.hibernate.HB_VXModelConnector.connect(HB_VXModelConnector.java:49)
at
com.quintron.vx.core.omimpl.hibernate.HB_VXModelConnector.connect(HB_VXModelConnector.java:24)
at
com.quintron.vx.core.omimpl.hibernate.HB_VXModelConnector.connect(HB_VXModelConnector.java:64)
at
com.quintron.vx.core.omimpl.hibernate.HB_VXModelConnector.connectWithLicenseInit(HB_VXModelConnector.java:15)
at
com.quintron.vx.appserver.VX_AppServerWrapper.start(VX_AppServerWrapper.java:68)
at org.tanukisoftware.wrapper.WrapperManager$10.run(WrapperManager.java:3963)
Caused by: org.hibernate.exception.GenericJDBCException: Cannot open connection
at
org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
at
org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at
org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426)
at
org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at
org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:50)
at com.sun.proxy.$Proxy0.getMetaData(Unknown Source)
at com.quintron.vx.core.omimpl.hibernate.HB_VXModelSession.<init>(HB_VXModelSession.java:790)
at com.quintron.vx.core.omimpl.hibernate.HB_VXModel.init(HB_VXModel.java:218)
... 9 more
Caused by: java.sql.SQLException: Unable to get information from SQL Server:
YourServerName.
at net.sourceforge.jtds.jdbc.MSSqlServerInfo.<init>(MSSqlServerInfo.java:91)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:263)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:178)
at
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:120)
at
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:143)
at
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:132)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPoolManager.initializeAutomaticTestTable(C3P0PooledConnectionPoolManager.java:772)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPoolManager.createPooledConnectionPool(C3P0PooledConnectionPoolManager.java:696)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPoolManager.getPool(C3P0PooledConnectionPoolManager.java:257)
at
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPoolManager.getPool(C3P0PooledConnectionPoolManager.java:271)
at
com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
at
org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:56)
at
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
... 14 more
[2018-11-09 14:50:02,192] INFO - FAILED
Workaround/Solution.
The steps we followed to troubleshoot this issue were the following:
- Open SQL Server Configuration Manager and make sure the SQL Server
service related with that instance is started. Make use of
this documentation
- When working with a named instance, make sure the SQL Server Browser
service is enabled and is started. Make use of
this documentation.
- Make sure TCP/IP and Named Pipes protocols are enabled. Restart SQL
Server service once you enable a protocol. Make of use
this documentation.
- Test connection to the SQL Server instance using SQL Server Management
Studio or Azure Data Studio. Make use of
this documentation.
- Verify the license file of the third-party application is not expired.
Contact the vendor of the application if the license has expired.