February 10, 2014 at 8:33 am
We have a 4 node windows 2012 cluster. Already 4 SQL server 2012 instances exists and is working fine with out issues.
However, when we try to install a new additional SQL 2012 instance, the installation is proceeding till the last phase and getting failed with the below reason. Can somebody please help me here?
SQL installation errors:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------
The following error has occurred:
The cluster resource 'SQL Server(yyy)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name(XXXX) ' online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
February 10, 2014 at 8:45 am
EVent log errors:
The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
February 10, 2014 at 8:45 am
SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
February 10, 2014 at 9:03 am
We had something similar, this KB fixed our SPN problems:
February 10, 2014 at 9:05 am
You can also manually update the SPN's, this would be issued from the command prompt with an Admin account:
setspn -A MSSQLSvc/myhost.redmond.microsoft.com:1433 accountname
setspn -A MSSQLSvc/myhost.redmond.microsoft.com accountname
setspn -A MSSQLSvc/myhost.redmond.microsoft.com:instancename accountname
February 10, 2014 at 2:23 pm
We find that Kerberos works much better (faster and less network traffic to the DC) than NTLM for SQL authentication.
So, for any new SQL Build we always grant these AD rights to the SQL service account:
- Read servicePrincipalName
- Write servicePrincipalName
If you then restart SQL, you should see successful SPN registration, which means that Kerberos will be used.
February 11, 2014 at 11:31 am
Rynga, did you fix your problem?
February 12, 2014 at 4:47 am
The network resource issue and the Kerberos issue are probably not related, and in any case the thing that is killing your cluster install is the network issue.
After your cluster install fails, have you looked using the Cluster Admin GUI to see if the network resource has been created. If it has, have you tried to bring this online manually? What error did you get?
Common problems that prevent a network resource coming online are:
a) The IP address requested is already in use
b) The network configuration within the cluster prevents the IP address you requested from being used
I think you need to troubleshoot the network resource problem in preference to troubleshooting the Kerberos problem. You may need to fix them both, but fixing one is unlikely to fix the other.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply