Installation with named MSSQL instance

Attempting to install 24.1 using a database server with a named instance. Repeatedly getting error of "Error: Failed to validate database parameters".

I have double and triple checked the parameters. Does the install allow for using a named instance?

Database is: DBServerName\NamedInstance

Port is 57253

Connection string looks like this: jdbc:sqlserver://DBServerName\NamedInstance:57253

  • 0

    Reviewing the logs and checking the password, below is the log entries.

    Executing: DatabaseServerCustomPanel
    Is validation 'DB_SUPPORTED_VALIDATION_ENABLED' enabled: true
    Validation name: 'SupportedDBEngineValidation'
    Validation status: FAIL
    Message type: ERROR
    User message: 'Failed to validate database parameters.'
    Log message: 'Error validation DB parameters
    EXCEPTION:
    com.hp.alm.platform.db.CTdDriverManager.getConnection(CTdDriverManager.java:63)
    com.mercury.optane.core.qccheckhelpers.DbAccessUsingConnection.openConnection(DbAccessUsingConnection.java:124)
    com.mercury.optane.core.qccheckhelpers.DbAccessUsingConnection.<init>(DbAccessUsingConnection.java:51)
    com.mercury.optane.core.qccheckhelpers.CTdCheckDBHelper.useConnection(CTdCheckDBHelper.java:517)
    com.mercury.optane.core.qccheckhelpers.CTdCheckDBHelper.getDbHelper(CTdCheckDBHelper.java:96)
    com.hp.alm.installAnywhere.utils.InstallationDbUtilFactory.getDbCheckHelper(InstallationDbUtilFactory.java:42)
    com.hp.alm.installAnywhere.validations.InstallationValidations.db.SupportedDBEngineValidation.execute(SupportedDBEngineValidation.java:37)
    com.hp.alm.installAnywhere.validations.InstallationValidations.AbsInstallationValidation.validate(AbsInstallationValidation.java:34)
    com.hp.alm.installAnywhere.validations.InstallationValidations.AbsValidationsExecutor.executeValidation(AbsValidationsExecutor.java:49)
    com.hp.alm.installAnywhere.validations.InstallationValidations.AbsValidationsExecutor.executeValidations(AbsValidationsExecutor.java:33)
    com.hp.alm.installAnywhere.panels.gui.customPanels.DatabaseServerCustomPanel.executePanelValidations(DatabaseServerCustomPanel.java:426)
    com.hp.alm.installAnywhere.panels.gui.customPanels.AbsInstallerCustomCodeValidatablePanel.checkOkToContinue(AbsInstallerCustomCodeValidatablePanel.java:23)
    com.hp.alm.installAnywhere.panels.gui.customPanels.AbsInstallerCustomCodePanel.okToContinue(AbsInstallerCustomCodePanel.java:59)
    com.zerog.ia.installer.AAMgr.clickNextButton(Unknown Source)
    com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'td_db_admin'. ClientConnectionId:15552759-ee8a-4d9d-bce4-b584c3deaebb
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:265)
    at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:305)
    at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:138)
    at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:42)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:6490)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:5068)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.accessLogonCommand.doExecute(SQLServerConnection.java:5002)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7685)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:4048)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:3487)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:3077)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2919)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1787)
    at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1229)
    at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:682)
    at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:191)
    at com.hp.alm.platform.db.CTdDriverManager.getConnection(CTdDriverManager.java:57)
    at com.mercury.optane.core.qccheckhelpers.DbAccessUsingConnection.openConnection(DbAccessUsingConnection.java:124)
    at com.mercury.optane.core.qccheckhelpers.DbAccessUsingConnection.<init>(DbAccessUsingConnection.java:51)
    at com.mercury.optane.core.qccheckhelpers.CTdCheckDBHelper.useConnection(CTdCheckDBHelper.java:517)
    at com.mercury.optane.core.qccheckhelpers.CTdCheckDBHelper.getDbHelper(CTdCheckDBHelper.java:96)
    at com.hp.alm.installAnywhere.utils.InstallationDbUtilFactory.getDbCheckHelper(InstallationDbUtilFactory.java:42)
    at com.hp.alm.installAnywhere.validations.InstallationValidations.db.SupportedDBEngineValidation.execute(SupportedDBEngineValidation.java:37)
    at com.hp.alm.installAnywhere.validations.InstallationValidations.AbsInstallationValidation.validate(AbsInstallationValidation.java:34)
    at com.hp.alm.installAnywhere.validations.InstallationValidations.AbsValidationsExecutor.executeValidation(AbsValidationsExecutor.java:49)
    at com.hp.alm.installAnywhere.validations.InstallationValidations.AbsValidationsExecutor.executeValidations(AbsValidationsExecutor.java:33)
    at com.hp.alm.installAnywhere.panels.gui.customPanels.DatabaseServerCustomPanel.executePanelValidations(DatabaseServerCustomPanel.java:426)
    at com.hp.alm.installAnywhere.panels.gui.customPanels.AbsInstallerCustomCodeValidatablePanel.checkOkToContinue(AbsInstallerCustomCodeValidatablePanel.java:23)
    at com.hp.alm.installAnywhere.panels.gui.customPanels.AbsInstallerCustomCodePanel.okToContinue(AbsInstallerCustomCodePanel.java:59)
    at com.zerog.ia.installer.AAMgr.clickNextButton(Unknown Source)
    at com.zerog.ia.installer.AAMgr.actionPerformed(Unknown Source)
    at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1972)
    at java.desktop/javax.swing.AbstractButton4.run(EventQueue.java:720)
    at java.desktop/java.awt.EventQueueJavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
    at java.base/java.security.ProtectionDomain5.run(EventQueue.java:747)
    at java.desktop/java.awt.EventQueueJavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
    at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:744)
    at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
    at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
    '

  • Suggested Answer

    0   in reply to 

    Hello Barry,

    ALM supports MS SQL named instances.

    Issue might be related to permissions of the td_db_admin user you created or something else.

    Have you tried using 'sa' or any other admin user to discard?

    Is the SQL Server configured to enforce a secured connection? 

    If so, additional parameters and steps are needed for ALM to properly connect.

    Check page 123 of the installation guide for more details:

    To configure a secure database connection for a new ALM installation

    Hope this helps!


    Claudio Urena

    OpenText ALM & ALM Octane Support

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.