Summary of Steps Taken and Issue Encountered

Primary Server Setup (Build 7000)

1. Installed ADSelfService Plus on the primary server.

2. Launched the application for the first time to allow changeDB.bat to run.

   • This step required a local PostgreSQL instance to exist, which it did.

3. Successfully executed changeDB.bat to switch the product to use MS SQL.

4. Installed the ADSelfService service.

5. In SQL Server, assigned the Windows service account db_owner permissions on the ADSelfService database.

6. Updated the ADSelfService service to run under this Windows authentication account instead of Local System.

Secondary Server Setup (Build 7000)

1. Installed ADSelfService Plus on the secondary server.

2. Attempted to configure High Availability (HA) from the primary server.

3. Received the message: “Sorry, secondary service must be running.”

4. Attempted to start the ADSelfService service on the secondary server, but the service fails to start.

5. Based on behavior, it appears the service account is attempting to connect to a local database on the secondary server (which does not exist), causing the service startup to fail.

Current Problem

The ADSelfService service on the secondary server will not start, preventing HA configuration. The likely cause is that the service account is trying to authenticate against a local database instead of the shared SQL database used by the primary server.

Request

Looking for guidance on:

• Correct steps to configure the secondary server for HA when using MS SQL instead of local PostgreSQL.

• How to ensure the service account on the secondary server connects to the shared SQL database rather than expecting a local database.

• Any additional configuration required before HA can be enabled.