Recently had an issue where an engineer had decided to change an existing SQL Server from using dynamic ports to a static port.
The server was a named instance.
servername\instancename
Having made the change using SQL Server Management Studio (SSMS) on the actual server he did not notice that access to the server instance via SSMS remotely had stopped working.
Trying to connect remotely to the server resulted in a
“The target principal name is incorrect. Cannot generate SSPI context. “
error dialog appearing.
after a bit of investigation it was clear this was a problem with the Service Principal Name (SPN) that had been created. There are a number of troubleshooting articles about this issue and I list them in the references below.
One of the solutions is to remove and recreate the SPN. This involves using the setSPN.exe, however you need to know structure the URLs. However whilst looking at this I cam across this
Kerberos Configuration Manager for SQL server
This tool actual checks your SPNs and will generate a script to fix it, or you can just click fix and it will run the script.
In the end this is all I used to fix my issue
References
No comments:
Post a Comment