September 30, 2024 at 7:12 pm
We are trying to update a sqlservice account from a user account to a domain account. The service runs fine under the user account but when we update it to a domain account we face the following error and the sqlservice does not start.
Error: 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.
October 1, 2024 at 4:08 am
hello ,
Use the setspn command to manually register the SPN. The command usually looks like this:
setspn -A MSSQLSvc/FQDN:port DOMAIN\service_account
October 1, 2024 at 7:04 am
If you are using the AD for a service account why not use a MSA?
Using Managed Service Accounts with SQL Server (mssqltips.com)
Using Group Managed Service Accounts with SQL Server (mssqltips.com)
October 1, 2024 at 10:58 am
Being unable to register the SPN does not prevent the SQL service from starting. I'd check in the SQL log for any other potential errors AND check the Windows Event Logs, especially the Security log.
A couple possibilities come to mind as the possible cause of SQL not starting with the domain account, though:
October 14, 2024 at 7:27 am
This was removed by the editor as SPAM
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply