ZCM 10.1 Upgrade Error due to database connection errors for external MS SQL 2005 DB.

  • Document ID:7001346
  • Creation Date:12-Sep-2008
  • Modified Date:27-Apr-2012
    • Micro Focus Products:
      ZENworks Configuration Management

Environment

Novell ZENworks 10 Configuration Management with Support Pack 1 - 10.1 Installation - Server
Microsoft SQL 2005

Situation

Error: One or more serious errors occurred during the schema update.

Errors occur in the %ZENworks_Home%/logs/ZENworks_Install* folder

Troubleshooting:
 The currently installed version of ZCM (e.g. 10.0.3) is able to access the database without any issues.  An SQL client from the ZENworks Primary Server is able to make connections to the database fine.

A clip of the ZENworks Installation Log displayed in debug mode is shown below:

DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.Socket.connect(Socket.java:519)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.lang.reflect.Method.invoke(Method.java:585)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.SharedSocket.createSocketForJDBC3(SharedSocket.java:289)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:250)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:297)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: ... 7 more
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: Exception in thread "main" java.lang.NullPointerException
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at com.novell.zenworks.configure.actions.db.DatabaseUpgradeConfigureAction.configure(DatabaseUpgradeConfigureAction.java:166)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at com.novell.zenworks.configure.actions.db.DatabaseUpgradeConfigureAction.main(DatabaseUpgradeConfigureAction.java:570)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at com.novell.zenworks.configure.actions.db.DatabaseUpgradeConfigureAction.configure(DatabaseUpgradeConfigureAction.java:96)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at com.novell.zenworks.configure.actions.db.DatabaseUpgradeConfigureAction.main(DatabaseUpgradeConfigureAction.java:570)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: Caused by: java.net.ConnectException: Connection refused: connect
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.PlainSocketImpl.socketConnect(Native Method)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: SEVERE: Error while upgrading the Database
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: java.sql.SQLException: Network error IOException: Connection refused: connect
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:372)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:178)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.sql.DriverManager.getConnection(DriverManager.java:525)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at java.sql.DriverManager.getConnection(DriverManager.java:140)
DEBUG31/08/2008 22:42:44D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: at com.novell.zenworks.configure.util.DatabaseUpgradeUtils.getConnection(DatabaseUpgradeUtils.java:117)
DEBUG31/08/2008 22:42:43D:\ZCM\Novell\ZENworks\share\java/bin/java:: OUT: FINER: DatabaseUpgradeConfigureAction: getConnection



Resolution

By default, MS SQL 2005 uses Dynamic ports which causes the connection problem when the port is dynamically changed to something other than referenced in the ZDM.XML configuration file.

Below are some steps to check for the default Dynamic Port configuration, and to disable it.

(1) Check if TCP/IP is enabled in the SQL Server 2005 Configuration Manager(right click on server). Search for protocols and check if TCP/IP is enabled.  By default it is disabled. In that case make it enabled.

(2) "TCP Port: 1433 "  This should be there if it is static port... and it should not be blank. Port 1433 is the default, it can be modified to an alternate port number.  See example below:

IPALL: Active: Yes
TCP Dynamic ports: 1053
TCP Port: 1433
 

Additional Information



More information about disabling dynamic ports for SQL 2005 can be found here.

http://www.mssqltips.com/tip.asp?tip=1412