blocks|key|1987699|text|这是一个非常常见的错误，原因有很多:从KB+811889开始|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1987700|1987701|什么版本的SQL+server?客户端和服务器上的|unordered-list-item|1987702|和Windows？|1987703|本地或网络SQL实例？|1987704|域或工作组？Provider?|1987705|Changing+password|1987706|Local+windows记录错误？|1987707|任何其他受影响的应用程序？|1987708|1987709|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/811889^0|J|9|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|18|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|19|8|@]|9|@]|C|$]]|$1|L|3|M|5|G|7|1A|8|@]|9|@]|C|$]]|$1|N|3|O|5|G|7|1B|8|@]|9|@]|C|$]]|$1|P|3|Q|5|G|7|1C|8|@]|9|@]|C|$]]|$1|R|3|S|5|G|7|1D|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

It's quite a common error with a variety of causes: start here with <a href="http://support.microsoft.com/kb/811889" rel="noreferrer">KB 811889</a>

<ul>
<li>What version of SQL Server?</li>
<li>And Windows on client and server?</li>
<li>Local or network SQL instance? </li>
<li>Domain or workgroup? Provider?</li>
<li>Changing password</li>
<li>Local windows log errors?</li>
<li>Any other apps affected?</li>
</ul>

blocks|key|1858880|text|听起来你的电脑已经有一段时间没有联系验证域控制器了。(我曾经在我的笔记本电脑上发生过几次这种情况。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1858881|如果您的密码过期，也可能发生这种情况。|1858882|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It sounds like your PC hasn't contacted an authenticating domain controller for a little while. (I used to have this happen on my laptop a few times.)

It can also happen if your password expires.

blocks|key|1859123|text|当Windows用户帐户过期并且他已经使用旧密码登录时，通常会出现此错误。只需要求用户重新启动计算机，并检查密码是否过期或他是否更改了密码。希望这能有所帮助！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859124|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This error usually comes when the Windows user account is expired and he is already logged in with old password.
Just ask the user to restart his machine and check if the password is expired or he has changed the password.
 Hope this helps!!!!!

blocks|key|556512|text|在更改运行MSSQLSERVER-Service的用户后，我也遇到了同样的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556513|为了解决SQL+Server中不正确的SPN问题，我使用了此工具|556514|http://www.microsoft.com/en-us/download/details.aspx?id=39046+-+Microsoft®Kerberos+Configuration+Manager+for+SQL+Server|offset|length|556515|在我的例子中，它工作得很好。|556516|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/en-us/download/details.aspx?id=39046^0|0|0|0|1P|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

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 

<a href="http://www.microsoft.com/en-us/download/details.aspx?id=39046" rel="noreferrer">http://www.microsoft.com/en-us/download/details.aspx?id=39046</a> - Microsoft® Kerberos Configuration Manager for SQL Server

In my case it worked pretty well.

blocks|key|556504|text|您应该做的第一件事是进入日志(Management\SQL+Server+Logs)并查看SQL+Server+successfully+registered+the+Service+Principal+Name+(SPN)。如果您看到某种类型的错误(The+SQL+Server+Network+Interface+library+could+not+register+the+Service+Principal+Name+(SPN)+for+the+SQL+Server+service)，那么您知道从哪里开始。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|556505|当我们更改SQL+Server运行时所使用的帐户时，我们看到了这种情况。将其重置为本地系统帐户解决了问题。微软也有一个关于手动配置SPN的guide。|556506|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/library/bb735885.aspx^0|F|Q|1K|1K|3I|3B|0|1X|5|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

First thing you should do is go into the logs (<code>Management\SQL Server Logs</code>) and see if SQL Server <code>successfully registered the Service Principal Name (SPN)</code>. If you see some sort of error (<code>The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service</code>) then you know where to start.

We saw this happen when we changed the account SQL Server was running under. Resetting it to Local System Account solved the problem. Microsoft also has a <a href="http://technet.microsoft.com/en-us/library/bb735885.aspx" rel="nofollow">guide</a> on manually configuring the SPN.

blocks|key|1987992|text|如果您在IIS上托管，请确保AppPool帐户的密码未更改。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1987993|如果有，请执行以下步骤：|1987994|1987995|转到IIS|unordered-list-item|1987996|单击application|1987997|Right+Pools|1987998|选择您的应用程序的AppPool单击您的IIS+AppPool|1987999|1988000|entityMap^0|B|I|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|Z|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|10|8|@]|D|@]|E|$]]|$1|N|3|O|5|K|7|11|8|@]|D|@]|E|$]]|$1|P|3|Q|5|K|7|12|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

If you are hosting on IIS, make sure the password for the AppPool account has not changed. 

If it has, then follow these steps:

<ul>
<li>Go to IIS</li>
<li>Click on Application Pools</li>
<li>Select the AppPool of your application</li>
<li>Right Click on your AppPool</li>
<li>Advanced settings</li>
<li>Identity</li>
<li>Update Password</li>
<li>Restart AppPool</li>
</ul>

blocks|key|579840|text|我使用SQL+Server配置管理器解决了Cannot+Generate+SSPI+Context错误。因为我的机器上有SQL+Server+native+client+10.0，所以到服务器的连接正在尝试使用命名管道(或共享内存？)。其他机器可以毫无问题地运行我的应用程序。当我查看配置管理器时，命名管道和共享内存都已启用(很好)。但是，在别名下，计算机的名称是强制TCP的。由于我不知道更改此设置会产生什么影响，因此我将程序中的连接字符串更改为使用。而不是。已修复。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|579841|entityMap^0|L|S|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I resolved my <code>Cannot Generate SSPI Context</code> 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 &lt;servername>.&lt;domainname> instead. Fixed.

blocks|key|579746|text|"Cannot+Generate+SSPI+Context“错误非常常见，可能有多种原因。只是任何底层Kerberos/NTLM错误的掩护错误。Gbn的知识库文章链接是一个很好的起点，通常可以解决问题。如果您仍然有问题，我建议您遵循Troubleshooting+Kerberos+Errors中的故障排除步骤。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|579747|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/downloads/details.aspx?FamilyID=7DFEB015-6043-47DB-8238-DC7AF89C93F1&displaylang=en^0|38|V|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The "Cannot Generate SSPI Context" error is very generic and can happen for a multitude of reasons. Is just a cover error for any underlying Kerberos/NTLM error. Gbn's KB article link is a very good starting point and usualy solves the issues. If you still have problems I recommend following the troubleshooting steps in <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=7DFEB015-6043-47DB-8238-DC7AF89C93F1&amp;displaylang=en" rel="nofollow noreferrer">Troubleshooting Kerberos Errors</a>.

blocks|key|579886|text|我也提出了这个问题，服务器管理员按照indu_teja在http://www.sqlservercentral.com/Forums/Topic546566-146-1.aspx中提出的解决方案解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|579887|indu_teja提出的解决方案是：|579888|如果你得到这个"SSPI+Context+|579889|“。我们面临的问题是：|blockquote|579890|579891|579892|SQL+|579893|我们将无法连接到SQL+Server+remotely.|unordered-list-item|579894|
|579895|However，我们将能够使用本地帐户连接到服务器。|579896|579897|原因:该问题可能是因为Active+directory中的SPN没有发生正确的同步。|579898|解决方案：|579899|579900|您需要重置SPN。使用synytax+"SET+SPN“。您可以在net中检查语法一次。|ordered-list-item|579901|将您的sql+server服务帐户从域帐户更改为本地帐户，回收sql，然后用域帐户重新设置，并回收sql+server。|579902|579903|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sqlservercentral.com/Forums/Topic546566-146-1.aspx^0|S|1P|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@$A|1G|B|1H|1|1I]]|C|$]]|$1|D|3|E|5|6|7|1J|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1K|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1L|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1O|8|@]|9|@]|C|$]]|$1|O|3|P|5|Q|7|1P|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|T|3|U|5|Q|7|1R|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1T|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1U|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]|$1|11|3|12|5|13|7|1W|8|@]|9|@]|C|$]]|$1|14|3|15|5|13|7|1X|8|@]|9|@]|C|$]]|$1|16|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|17|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]]|18|$19|$5|1A|1B|1C|C|$1D|1E]]]]

I also issued this problem, and the server admins solved it by following the same solution as indu_teja proposed in <a href="http://www.sqlservercentral.com/Forums/Topic546566-146-1.aspx" rel="nofollow noreferrer">http://www.sqlservercentral.com/Forums/Topic546566-146-1.aspx</a>
The solution proposed by indu_teja says :
<blockquote>
If you get this &quot;SSPI Context Error&quot;. The issues we face are:
<ol>
<li>We will not be able to connect to SQL Server remotely.</li>
<li>However we will be able to connect to server with local account.</li>
</ol>
CAUSE: The issue might be becasue of no proper sync happenign fro the
SPNs in Active directory.
RESOLUTION:
<ol>
<li>You need to reset SPN. Use the synytax &quot;SET SPN&quot;. You can check the syntax in net once.</li>
<li>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.</li>
</ol>
</blockquote>

blocks|key|1987874|text|我刚刚遇到了同样的问题，我所做的就是使用另一个用户id删除sql+server中的用户登录凭据，然后重新添加它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1987875|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just had the same problem and all I did was delete the user log in credentials in sql server using another user id and adding them back.

blocks|key|1988046|text|这是我的案例。我有一台托管SQL+Server的远程计算机。在我的本地机器上，我试图通过一些C#代码访问SQL实例，我得到了这个错误。我的计算机/域上用户帐户的密码已过期。我用以下代码修复了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988047|1988048|打开远程计算机，提示我更改密码|ordered-list-item|1988049|我在此提示符中更改了密码并登录到远程计算机|1988050|我锁定了我的本地计算机(使用windows+%2B+L键，这样我就不必完全注销)，这样我就可以返回登录页面|offset|length|style|CODE|1988051|H111我使用新密码重新登录到我的本地计算机|1988052|然后一切都运行得很好。|1988053|entityMap^0|0|0|0|0|E|7|O|1|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|X|8|@$J|Y|K|Z|L|M]|$J|10|K|11|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

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:

<ol>
<li>Opened the remote machine, which prompted me for a password change</li>
<li>I changed my password within this prompt and logged into the remote machine</li>
<li>I "locked" my local machine (using <code>windows</code> + <code>L</code> key so I didn't have to completely sign off) so that I could get back to the sign-on page</li>
<li>I signed back onto my local machine with the new password</li>
</ol>

Everything then worked fine.

blocks|key|556552|text|在我的例子中，它是一个缺失的SPN，必须运行这两个命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556553|556554|+setspn+-a+MSSQLSvc:服务器名服务器名setspn+-a+MSSQLSvc:服务器名:1433服务器名|blockquote|556555|556556|556557|换句话说，在我的例子中，我已经正确地输入了FQDN，而不仅仅是NETBIOS名称，在添加它们之后，它工作得很好。起初它没有，但在等待了2分钟后，它做到了。|556558|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|K|$]]

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

<blockquote>
 setspn -a MSSQLSvc:SERVERNAME SERVERNAME 
 setspn -a MSSQLSvc:SERVERNAME:1433 SERVERNAME
</blockquote>

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.

blocks|key|1988162|text|我有这个错误-它的发生是因为我的密码过期了，我必须更改它。我没有注意到这一点，因为在一些程序中，我仍然可以登录，一切都可以正常工作(包括windows)，但我无法登录到任何sql服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988163|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this error- it happened because my password expired and I had to change it. I didn't notice it, because in some programs I could still log in and everything would work normally (including windows), but I couldn't log to any sql servers.

blocks|key|1988197|text|也许您已经在连接字符串中使用了Integrated+Security+=+SSPI。SSPI用于使用Windows的可信连接，为了在windows身份验证中正常工作，您的系统和数据库服务器应该位于相同的域中并且使用相同的Authentication.hence服务器地址，或者应该位于受信任域中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988198|如果您的系统和数据库服务器在同一个域中，请检查系统网络连接中的IPV4属性的DNS服务器地址，并提供数据库服务器正在使用的DNS服务器。|1988199|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|1856767|text|在vb.net中，如果您使用的是链接服务器，请检查连接字符串。集成的%25+Security=true；并非在所有OleDb提供程序中都有效，它在与SQL提供程序一起使用时会引发异常。因此，基本集成的Security=SSPI是首选，因为它可以同时与SQLClient和OleDB+provide一起使用。如果仍然命中错误，请完全删除语法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1856768|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In vb.net, if you are using a linked server than check your connection string. Integrated Security=true; doesn't work in all SQL providers, it throws an exception when used with the OleDb provider. So basically Integrated Security=SSPI; is preferred since works with both SQLClient &amp; OleDB provide. If you still hit with error, remove the syntax completely.

blocks|key|579786|text|我可以通过重置域(服务器计算机，它是域服务器，但除了域管理之外与SQL+server无关)来解决这个问题，然后重置客户端计算机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|579787|感谢大家对我们的支持！|579788|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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!

blocks|key|556494|text|有一个非常奇怪的实例；所有具有包含SQL服务器的windows计算机名称的连接字符串的web产品都工作正常，但是具有附加了内部域的FQDN的产品给出了SSPI错误。例如，COMPUTERNAME+vs+COMPUTERNAME.DOMAIN+(ping始终按预期工作)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556495|只有在使用新的SQL服务器，并且主机文件将计算机名和计算机名都指向连接字符串的FQDN时，才会出现问题。|556496|这种情况下的解决方案是将所有连接字符串仅设置为计算机名，删除域引用。|556497|SQL+:+2008R2+SQL2012|556498|IIS+:+2008R2|556499|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

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

blocks|key|556658|text|在将服务用户从Domain1\ServiceUser更改为Domain2\ServiceUser的实例中，我们遇到了此问题。SPN仍在Domain1\ServiceUser下注册，从未在Domain2\ServiceUser下注册。我们在Domain2\ServiceUser下注册了SPN，但问题仍然存在。然后，我们删除了Domain1\ServiceUser下的SPN，该问题已得到解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556659|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|556691|text|如果您运行的代码不是在您的计算机上编写的，而是在您的同事使用的计算机上运行的，请检查web.config。也许你同事的名字叫userPrincipalName，在某个地方应该是空白的。当我们在VS中创建对项目的服务引用时，这会自动发生。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556692|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In case you are running a code not written in your computer, that runs in a computer used by your work peer, but not in yours, check the web.config.
Maybe there is your colleague's name as userPrincipalName at some place that should be in blank. That happens automatically when we create a service reference to the project in VS.

blocks|key|556702|text|我可以通过运行以下命令来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556703|在管理模式下运行CMD|556704|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+%7C+findstr+/i+[your+hostname+here+in+the+new+opened+cmd+window]|code-block|syntax|javascript|556705|根据指定的条件重试这些命令，然后重新启动电脑。|556706|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I am able to solve it by running the following commands.
Run CMD in admin mode
<pre><code>klist.exe -li 0x3e7 =&gt; 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]
</code></pre>
Try again these commands depending upon the condition specified, and then restart your PC.

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 &amp; 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.

Cannot create SSPI context

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在开发一个.NET应用程序，试图在其中构建数据库脚本。在构建项目时，我收到错误消息“无法创建SSPI上下文。”此错误显示在输出窗口中(在VS2008屏幕内)，构建过程失败。请在这方面提供帮助。SQL Server被配置为在Windows身份验证上工作&作为网络服务运行(这两件事对于我的项目来说是必须的)。请在这方面提供帮助。这个错误似乎是不一致的。在过去，通过重新启动机器，更改系统时间以匹配域

问无法创建SSPI上下文
EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法创建SSPI上下文EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法创建SSPI上下文
EN