Неверное имя целевого субъекта невозможно создать контекст sspi microsoft sql server ошибка 0

I am working on a .NET application where I am trying to build the database scripts. While building the project, I am getting an error «Cannot create SSPI context.». This error is shown in the output window (inside VS2008 screen) and the building process failed. Please help on this. SQL Server is configured to work on Windows authentication & running as network service (these two things are must for my project).

Please help on this. This error is not seems to be consistent. It was fixed in the past by restarting the machine, changing the system time to match the domain time and some suggestions in the net. Please help on this.

answered Sep 13, 2016 at 10:17

I had the same issue after changing the user which was running the MSSQLSERVER-Service

To solve incorrect SPNs with SQL Server I used this tool

http://www.microsoft.com/en-us/download/details.aspx?id=39046 — Microsoft® Kerberos Configuration Manager for SQL Server

In my case it worked pretty well.

answered Dec 24, 2014 at 22:24

I resolved my Cannot Generate SSPI Context error by using the SQL Server Configuration Manager. Since I have SQL Server native client 10.0 on my machine, the connection to the server is trying to use named pipes (or shared memory?). Other machines could run my app with no problem. When I looked at the configuration manager, named pipes and shared memory were both enabled (good). However, under alias, the name of the computer was there with TCP forced. Since I didn’t know what effect changing this would have, I changed the connection string in my program to use <servername>.<domainname> instead. Fixed.

answered Nov 28, 2009 at 17:34

I also issued this problem, and the server admins solved it by following the same solution as indu_teja proposed in http://www.sqlservercentral.com/Forums/Topic546566-146-1.aspx

The solution proposed by indu_teja says :

If you get this «SSPI Context Error». The issues we face are:

1. We will not be able to connect to SQL Server remotely.
2. However we will be able to connect to server with local account.

CAUSE: The issue might be becasue of no proper sync happenign fro the
SPNs in Active directory.

RESOLUTION:

1. You need to reset SPN. Use the synytax «SET SPN». You can check the syntax in net once.
2. Change your sql server service account from domain account to Local account, recycle sql, and then reset again with your domain account and recycle sql server.

answered Oct 14, 2013 at 11:19

Here is my case. I had a remote machine that hosted SQL Server. From my local machine, I was trying to access the SQL instance via some C# code and I was getting this error. My password for the user account on my machine/domain had expired. I fixed it with the following:

1. Opened the remote machine, which prompted me for a password change
2. I changed my password within this prompt and logged into the remote machine
3. I «locked» my local machine (using windows + L key so I didn’t have to completely sign off) so that I could get back to the sign-on page
4. I signed back onto my local machine with the new password

Everything then worked fine.

answered Aug 10, 2016 at 19:53

In my case it was a missing SPN, had to run these two commands:

setspn -a MSSQLSvc:SERVERNAME SERVERNAME
setspn -a MSSQLSvc:SERVERNAME:1433 SERVERNAME

In other words in my case I had the FQDN in there already correctly but not just the NETBIOS name, after adding these it worked fine. Well initially it didn’t but after waiting 2 minutes it did.

answered Aug 31, 2016 at 13:21

answered May 8, 2017 at 7:39

Perhaps you have used Integrated Security = SSPI in connection string. SSPI is used for Trusted connections using Windows Authentication.hence, to work properly in windows authentication, either your system and database server should be in same domain and using same DNS server address, or should be in trusted domain.

if your system and database server is in same domain, Check DNS server address of IPV4 properties in your system’s network connection and provide same DNS server being used by database server.

answered Jun 29, 2018 at 13:13

answered Apr 4, 2019 at 14:49

I can able to get this resolved by resetting the domain (server machine, which is the domain server, but not related to SQL Server except domain managing) followed by the client machines.

Thank you all for your immediate support!

answered Nov 29, 2009 at 9:26

Had a really weird instance of this; All the web products that had connection strings containing the windows computer name of the SQL server worked fine, but the products that had a FQDN with the internal domain attached gave an SSPI error.
i.e.
COMPUTERNAME
vs
COMPUTERNAME.DOMAIN
(ping always worked as expected)

This ONLY gave problems when a new SQL server was being used and hosts files pointed both the computer name and the computername as a FQDN for the connection strings.

Solution in this case was to set all the connection strings to the computer name only, removing the domain references.

SQL : 2008R2 SQL2012

IIS : 2008R2

answered Jan 21, 2014 at 11:12

We had this issue on instances in which we changed the service user from Domain1ServiceUser to Domain2ServiceUser. The SPNs remained registered under Domain1ServiceUser, and never registered under Domain2ServiceUser. We registered the SPNs under Domain2ServiceUser, but the issue persisted. We then removed the SPNs under Domain1ServiceUser, and the issue was resolved.

answered Jul 10, 2019 at 12:11

I am able to solve it by running the following commands.

Run CMD in admin mode

klist.exe -li 0x3e7 => if you see no output or error then continue and from last command try these commands once again.
klist.exe -li 0x3e7 purge
gpupdate /force
gpresult /r /scope computer
klist purge
runas /user:[your domain here][your user name here] cmd.exe
klist.exe sessions | findstr /i [your hostname here in the new opened cmd window]

Try again these commands depending upon the condition specified, and then restart your PC.

answered Feb 9, 2022 at 13:26