This is a generic error. It can be triggered due to many reason including an outdated password, clock drift, failure to register an SPN, or Active Directory access permission. In this article, we take a look at a few troubleshooting steps to help you resolve the cannot generate SSPI context error on the Windows server.
How can I fix the target principal name is incorrect – cannot generate SSPI context error?
1. Change SQL Service User
Try changing the SQL SERVICE user with the one that is Domain Admin. When you shut down the service, you need an account with privileges to create a new SPN (Service Principal Name). When a service starts without it, it will trigger the error. Changing the privileges of your system account can fix the error. However, it is always recommended for service accounts to give them the least privileges due to security reasons. Remove the SPN entries from AD Users and Computers
2. Check your password
The error cannot generate SSPI context can occur due to password issues. If you had recently changed your password, but haven’t logged out of your account, it can trigger the error. Try logging out and then signing in with the new password to fix the error. In other instances, the issue could be due to password expiration. Change the expired password and login with the new credentials to see if that resolves the error. 3. Change Active Directory permission
Try establishing a new connection and check if they cannot generate SSPI context error is resolved. Make sure you restart the SQL Services that are associated with the current account to apply the changes. Changing the Active Directory permission is a safe option than changing the SQL server user. However, before you proceed to change the permission, make sure the problem is triggered due to permission issues. Log in to the server where your SQL instance is running and then check the error logs to check if the error is triggered due to permission problems. The error in the log will look something like this: The error cannot generate SSPI context can occur due to permission as well as expired credentials issues. Changing the password and permission should help you fix the error and log back into your SQL server.
SPONSORED
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
