Renaming the server can also have an effect on SQL Server.Ģ. This can cause many different problems with logins, especially domain groups and users if they aren't the same in the new domain. You said you named the server, everything was setup and working, then you renamed it, disconnected from one domain and connected to another. I'm presently installing server 2008 sp2. I want to begin with i'm a IT systems admin, not a sql admin or anything related to sql. ***Xiao Min Tan***Microsoft Online Community*** If there are any more questions, please let me know. Reference: How to: Change the Service Startup Account for SQL Server (SQL Server Configuration Manager) To work around it, you could select a domain account for SQL Server service account and add it to the domain administrators group and the groups for the SQL server service which comes under the Local Users and Groups. If SQL Server is not running under one of these accounts, the SPN is not registered at startup and the domain administrator must register the SPN manually. To register the SPN, the Database Engine must be running under a built-in account, such as Local System or NETWORK SERVICE, or an account that has permission to register an SPN, such as a domain administrator account. What’s your SQL Server service account? Based on the error message, it seems you use Kerberos authentication with SQL Server. Administrator should deregister this SPN manually to avoid client authentication errors.
08:49:20.02 Server The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. This is an informational message only no user action is required. 08:49:19.88 spid7s SQL Trace was stopped due to server shutdown. You may need to clear the Windows Events log if it is full.
08:49:19.78 spid13s The current event was not reported to the Windows Events log.
08:49:19.78 spid13s Service Broker manager has shut down. 08:49:18.57 Server SQL Server is terminating because of a system shutdown.
0 kommentar(er)
