Unable to join second Active Roles service to an existing database when using a custom SQL port or Always On Availability Groups (248237)

When Active Roles is configured to use a database hosted on a SQL instance which is using a custom port or Always On Availability Groups, it is possible to successfully configure Active Roles to use this SQL instance by specifying the port number in the SQL server connection string like so:

sqlServer\instanceName,1234

However, attempting to configure a second Active Roles service to use the same configuration database using the Active Roles Configuration Center will fail. The SQL server settings for the Management History database will have the port stripped out, and the connectivity check will timeout and fail. When using a SQL Always On Availability Group, the Management History database does not use the listener and instead is hard-coded to use a particular SQL instance.

WORKAROUND 

Run  the Active Roles Management Shell to configure the administration service.

STATUS

As of Active Roles 7.3.1, this issue is resolved as a registry-enabled fix as per the Active Roles 7.3.1 release notes:

7.3.1 Registry Fix:

NOTE: Active Roles service account must have the View Server State permission in the SQL server.

1. After installation, open the Registry Editor by navigating to Start->Run and typing regedit on the machine where Active Roles Service is installed
2. Navigate to the registry key HKEY_LOCAL_ MACHINE\SOFTWARE\One Identity\Active Roles\ Configuration\ Service
3. Right click and select New DWORD (32-bit) Value
4. Enter the registry key name as IsCustomSQLPortUsed
5. Double click on the registry key name IsCustomSQLPortUsed and in the Value Data field, set the registry key value to 1 and click OK
6. Setting this value to 0 or deleting the key disables the fix
7. Re-start the Active Roles Administration Service