October 14, 2016 at 4:16 pm
I got this error from an Access frontend application connecting to the SQL 2014 via ODBC linked tables.
[Microsoft][ODBC SQL Server Driver]Cannot generated SSPI context
I am puzzled on what triggered the error. The user was using the Access application without an issue. Suddenly this error appeared and the connection to the sql server was lost. The user had to restart the workstation a couple times to get back the connection.
October 14, 2016 at 4:28 pm
Hi,
Probably , there might be issues with your SPN.
Check SPN on the service account. See if they are any duplicates.
Thanks
KAKA
October 15, 2016 at 9:35 pm
The service account was "Local System", which I think can register its SPN automatically. I do not know how to check its SPN. So I changed the service account to the domain administrator, which I checked and made sure only one SPN is specified in the Active Directory. I restarted the SQL service service and tested a couple workstations, which showed no connection error. Now I will have to wait to see whether this error will resurface on Monday.
November 16, 2016 at 1:39 am
The issue kept happening. The user was using the front-end Access without any issue, and then suddenly this error message appeared. The user had to restart the workstation to get back the connection. It is rather random and I saw no pattern.
Maybe I did not understand this "SPN on the service account" correctly.
In the Active Directory, the Properties of the Server shows many SPNs (it is the domain server/file server too) and one of them is "MSSQLSvr/ServerName.DomainName.com". When I tried adding this SPN "MSSQLSvr/ServerName.DomainName.com" to the domain administrator (also the server local admin) account (via Properties), I got the error message - “The operation failed because SPN value provided for addition/modification is not unique forest-wide”. Should I remove this SPN from the server?
Seaport
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply