|3.2 and Later||How-to||
What are remedial steps when an error message window pops up during creation of a Scalearc Kerberized Cluster - as below:
During a kerberized Cluster Creation we get above error when a Setup Cluster is done after the Cluster is fetched properly. To get around this issue you need to be sure of the SPNs which
need to be registered on the Domain controller to which Scalearc will join. As you can see from the screenshot below we have checked for available SPNs for the MSSQL service account
with the command:
c:\> Setspn -L "phil\administrator"
From output of above command we get related spn details for the SQL servers configured in Scalearc. But when you check such output it is seen that a VIP hostname is not yet registered in
the Domain controller with a proper SPN which is necessary for a kerberos handshake from Scalearc to Domain controller. Hence you need to specify the SPN over here and ensure that the
pre-requisite for such Cluster creation is met. The command to add SPN for a VIP hostnname of Scalerac in the Windows domain controller will be like:
C:\Users\Administrator>setspn -A MSSQLSvc/scale-vip2.PHIL.edu:1433 PHIL\sc10
Checking domain DC=phil,DC=edu
Registering ServicePrincipalNames for CN=SC10,CN=Computers,DC=phil,DC=edu
Pl. Note: General format of the command above is:
Setspn -A MSSQLSvc/<VIP_Hostname>.<domainname>:<port><domain\ScaleArc hostname$> (we have accordingly replaced values in command above).
The collective output of above remedial steps is as below:
In this way when all SPNs are properly registered and additional pre-requisites met properly then the Kerberos Cluster will be created successfully as seen below: