Always On SQL Kerberos Authentication getting failed with Automation Suite installation.
Scenario: The installation of the Automation Suite is encountering failure during SQL-Prechecks when using Always ON SQL Authentication.
Symptoms:
When utilizing Always On SQL, the connection to SQL Servers is facilitated through the SQL Listener. If there is no Service Principal Name (SPN) registered for that SQL Listener, the error message is likely to appear.
Resolution:
First check registered SPN against that AD SQL Account which is using for SQL Kerberos Authentication, use below mentioned command to check SPN.
- As in above screenshot, can see there are 2 SPN registered against AD SQL Kerberos Account
- If customer using different port for SQL Server, then customized port should be registered instead of 1433
- If you did not find any registered SPN then check with customer that are they using different accounts for SQL Services and SQL Authentication
- If customer using different account for SQL Services and SQL Authentication, then check SPN against that account by which SQL Services have been configured
- Ask customer to register SPN via below mentioned command
- setspn -s MSSQLSvc/sqllistnr.kddomain.local kddomain\sql_svc
- setspn -s MSSQLSvc/sqllistnr.kddomain.local:1433 kddomain\sql_svc
- After this SPN error should be fixed
- Rerun validation script to verify it.