ePolicy Orchestrator installation or upgrade fails when using either of the SQL options AlwaysOn or SQL mirroring

Technical Articles ID: KB86152
Last Modified: 2023-07-19 07:14:16 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.x

Supported Microsoft SQL Servers

For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator.

Problem

An ePO upgrade or a fresh installation fails on servers that use either of the following SQL options:

AlwaysOn
SQL mirroring

The following error displays after you enter the details for the SQL Server:

The SQL Server TCP port does not match the selected database server. Correct the problem and try again

The EPO-CommonSetup.Log file records the following:

20151027103137 Passed function validSQLCollation
20151027103137 Server = [Server_Name1] Instance = [Instance_name1]
20151027103137 Retrieved the SQL Server with Instance Name as: [Server_Name2\Instance_name1]
20151027103137 NetBIOS server name is Server_Name1
20151027103137 Server names DO NOT MATCH so block the install.
<Server_Name> from SQL Server : [Server_Name1\Instance_name1]
<Server_Name> from installer : [Server_Name2\Instance_name1]
20151027103137 Failed in validSQLInstance with error code

The EPO-Install-MSI.LOG file records the following:

MSI (c) (28:CC) [10:31:36:375]: Invoking remote custom action. DLL: C:\Users\SVCEPO\AppData\Local\Temp\MSI90E2.tmp, Entrypoint: f34
Action ended 10:32:23: Prod_UI_ValidateDBServerInfo. Return value 1.
MSI (c) (28:20) [10:32:23:364]: PROPERTY CHANGE: Adding DontShowPortErrors property. Its value is '1'.
MSI (c) (28:20) [10:32:23:364]: PROPERTY CHANGE: Deleting DontShowPortErrors property. Its current value is '1'.
MSI (c) (28:20) [10:32:30:868]: PROPERTY CHANGE: Modifying MFSDATABASESERVERNAME property. Its current value is 'Server_Name2'. Its new value: 'Instance_name1'.
MSI (c) (28:20) [10:32:30:961]: Doing action: ConvertDBInfoDialogToUnicodeEscaped
Action 10:32:30: ConvertDBInfoDialogToUnicodeEscaped.
Action start 10:32:30: ConvertDBInfoDialogToUnicodeEscaped.
MSI (c) (28:80) [10:32:30:961]: Invoking remote custom action. DLL: C:\Users\SVCEPO\AppData\Local\Temp\MSI661C.tmp, Entrypoint: ConvertDBInfoDialogToUnicodeEscaped
Action ended 10:32:30: ConvertDBInfoDialogToUnicodeEscaped. Return value 1.
MSI (c) (28:20) [10:32:30:977]: Doing action: Prod_UI_ValidateDBServerInfo
Action 10:32:30: Prod_UI_ValidateDBServerInfo.
Action start 10:32:30: Prod_UI_ValidateDBServerInfo.
MSI (c) (28:80) [10:32:30:977]: Invoking remote custom action. DLL: C:\Users\SVCEPO\AppData\Local\Temp\MSI662C.tmp, Entrypoint: f34
Action ended 10:32:32: Prod_UI_ValidateDBServerInfo. Return value 1.
MSI (c) (28:20) [10:32:32:677]: PROPERTY CHANGE: Adding DontShowPortErrors property. Its value is '1'.
MSI (c) (28:20) [10:32:32:677]: PROPERTY CHANGE: Deleting DontShowPortErrors property. Its current value is '1'.
MSI (c) (28:20) [10:32:37:295]: PROPERTY CHANGE: Modifying MFSDATABASESERVERNAME property. Its current value is 'Server_Name1'. Its new value: 'Instance_name1'.
MSI (c) (28:20) [10:32:37:357]: Doing action: ConvertDBInfoDialogToUnicodeEscaped

The core-install.log, core-patch.log, or core-upgrade.log, depending on the installation scenario, might include the following message or a similar message:

BUILD FAILED

E:\Program Files\McAfee\ePolicy Orchestrator\Installer\core\build.xml:1116: java.sql.SQLException: The operation cannot be performed on database 'Name of database' because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

Cause

Sometimes, when you use the AlwaysOn or SQL mirroring SQL options, it causes the ePO installation or upgrade to fail to identify the correct SQL instance in use.

Solution

You must disable the SQL options before you install or upgrade. You can safely re-enable these options after the installation or upgrade successfully completes.

To learn more about these options, see the following articles:

Workaround

The upgrade might work successfully when using the IGNOREVALIDATIONERRORS switch during the upgrade. But, it's still needed to disable the SQL mirror during the upgrade:

Leave the availability group in place.
Disable SQL mirroring for the ePO database.
Leave <ePO installation directory>\Server\conf\orion\db.properties to be directed to the availability group or virtual name.
Run the ePO upgrade with the IGNOREVALIDATIONERRORS=1 switch using the following command:

"<ePO_installation_directory>\setup.exe" IGNOREVALIDATIONERRORS=1
Enable SQL mirroring for the ePO database. This action allows SQL to handle the replication of any changes made to the database during the upgrade.

If this action doesn't work, you might need to disable the SQL availability group as well. Point ePO to the physical SQL Server name, as explained in the "Solution" field above.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

ePolicy Orchestrator installation or upgrade fails when using either of the SQL options AlwaysOn or SQL mirroring

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

ePolicy Orchestrator installation or upgrade fails when using either of the SQL options AlwaysOn or SQL mirroring

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title