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:
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.
As of Active Roles 7.3.1, the fix is 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.