Since I didn't know what effect changing this would have, I changed the connection string in my program to use . instead. Rebooted the server3. Post navigation ← Happy Birthday SQL DBA Diaries! I thought it was an issue where our hosts changed a password on their original identity account, but I also have two set for backup use (which I've switched over to navigate to this website

Log in to the server where you SQL Instance is running. SQL Server is configured to work on Windows authentication & running as network service (these two things are must for my project). Gallup)? share|improve this answer edited Sep 22 at 21:10 Max Vernon 27.2k1160118 answered Sep 22 at 20:13 Bob Sullentrup 211 very helpful.

Reply ↓ Pingback: IT-Blog | Microsoft SQL Failed to generate SSPI Context Leave a Reply Cancel reply Search my blog My blogsData Science Recent posts No transaction is active message when 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 permalinkembedsavegive gold[–]retrovertigoIT Manager[S] 0 points1 point2 points 1 year ago(0 children)Yeah, credentials are fine.

You should now be able to connect even when SQL Server is restarted as the SPN is only created once. Looking for answers, I found this: SQL Server 2008 connectivity issue : cannot generate SSPI context But it doesn't help me, because they're working fine until yesterday. Issue for me was my AD account was locked out between login to machine and login to SSMS. –Brent Jun 3 '14 at 15:27 Bam, this is what was Sqlexception (0x80131904): The Target Principal Name Is Incorrect. Cannot Generate Sspi Context. If you see some sort of error (The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service) then you know where to

Here is the error message with which it was failing. Cannot Generate Sspi Context Fix I changed one method signature and broke 25,000 other classes. and one (or both) of them worked! You saved my time.. –Charan Sep 27 at 2:41 add a comment| up vote 2 down vote The "Cannot Generate SSPI Context" error is very generic and can happen for a

I'm trying to figure out the root cause for this and maybe someone here can point me in the right direction, but I'm also trying to understand what exactly is going The Target Principal Name Is Incorrect. Cannot Generate Sspi Context. Sharepoint 2013 Hope it helps someone. You cannot delete your own posts. we are changing the privileges of our system account.

Permissions required are ServicePrincipalName: Read ServicePrincipalName: Write We will use the 3rd option to fix the error.

As I mentioned earlier, from the error message it was clear that the issue was a result of errors with the SPN.

Cannot Generate Sspi Context Fix

What is Service Principal Name (SPN)? Why does Friedberg say that the role of the determinant is less central than in former times? The Target Principal Name Is Incorrect. Cannot Generate Sspi Context (microsoft Sql Server) You cannot upload attachments. The Target Principal Name Is Incorrect. Cannot Generate Sspi Context. (.net Sqlclient Data Provider) Click OK two times.

You cannot send emails. useful reference Once this was confirmed, the old SPN entry was deleted by using the -D switch in setspn.exe and the correct SPN was created by using the following command. You cannot post replies to polls. At least now we have verified that the problem is related to the SPN and we are ready to apply the fix. Odbc Sql Server Driver Cannot Generate Sspi Context

Solutions? Use the synytax "SET SPN". We tried switching to Local Service Account but that did not fix the issue. my review here But i was able to connect with SQL Server authentication."Cannot Generate SSPI Context"Thanks, Post #1265396 Roy ErnestRoy Ernest Posted Monday, March 12, 2012 1:57 PM SSCrazy Group: General Forum Members Last

The interesting thing I noticed at least the first time it happened, was recycling the app pool made the service completely unavailable, until I changed the identity. The Target Principal Name Is Incorrect Cannot Generate Sspi Context C# Go to the error logs and look for the last time that the SQL service was restarted. You cannot edit other events.