how to upgrade SCM when the database is using a non default port

  • 7016385
  • 02-Apr-2015
  • 02-Apr-2015

Environment

NetIQ Secure Configuration Manager 6.0

Situation

Cannot connect to database during upgrade when it is using a non default port

Resolution

The following is a workaround. It will be resolved permanently in the next release
The steps below are to use port 5833.  Substitute the actual port number for 5833.
1. Update SQL Server TCP/IP port to 5833 by using SQL Server Configuration Manager. Then restart SQL services.

2. Launch the Core Services Configuration Utility in advance mode by going to Program files/Netiq/Secure Configuration Manager/Core Services/bin and select config.bat and double click to execute.
Update the following advanced tab settings in the Core Services Configuration Utility.

    pool/core/url=jdbc:jtds:sqlserver://SQLServername:5833/database=VigilEnt;appName=Core Services;TDS=8.0
    database=vigilent
    pool/core/url/port=5833
    pool/core/url/properties=/disableStatementPooling=false/portNumber=5833

3. Restart the Netiq Core Services service.

4. Check the registry key 
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client \SuperSocketNetLib\Tcp\ DefaultPort (DWORD Value).
   Add the registry key if it is not present and set the value to 5833

5. Login to SCM to verify connectivity.
 
6. Upgrade to 6.0 (after upgrade pool/core/url gets replaced with old port(1433) where as other property values  reflect the changed values).

Cause

Login to SCM console fails by throwing the error unable to connect to database. This may be because the coreurl is getting appended with pool/core/url/properties

Status

Reported to Engineering

Feedback service temporarily unavailable. For content questions or problems, please contact Support.