Error 0 Cannot Generate Sspi Context
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company cannot generate sspi context sql server 2008 r2 Business Learn more about hiring developers or posting ads with us Stack Overflow Questions
The Target Principal Name Is Incorrect. Cannot Generate Sspi Context
Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million cannot generate sspi context fix programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Cannot create SSPI context up vote 20 down vote favorite 4 I am working on a .NET application where I am
Cannot Generate Sspi Context Vpn
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 cannot generate sspi context (microsoft sql server) 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. sql sql-server security sspi share|improve this question edited Nov 9 '15 at 14:01 Brian Webster 17.3k37115199 asked Nov 28 '09 at 13:41 Prasanna 3102312 1 I got this error after I had changed my default DNS server addresses under my Network Adapter's IPv4 Properties. When I changed my DNS server back to default, it went away. –James McCormack Jul 19 '13 at 10:02 add a comment| 14 Answers 14 active oldest votes up vote 13 down vote accepted It's quite a common error with a variety of causes: start here with KB 811889 What version of SQL Server? And Windows on client and server? Local or network SQL instance? Domain or workgroup? Provider? Changing password Local windows log errors? Any other apps affected? share|improve this answer answered Nov 28 '09 at 13:48 gbn 267k40374480 Thank you for your immediate response! 1. SQL Server 2008 2. Windows Xp 3. Network instance 4. Domain 5. not changed password for a while 6. Logs only show this error 7. I could nt able to log in from my applicaation, thats it. I can able to log in directly in SQL –P
account to run the SQL service. I’m sure you do too! However, once you do the right thing and change the SQL Service account, you may start getting the following error message when attempting to connect
Cannot Generate Sspi Context 2012
to the sql server: “The target principal name is incorrect. Cannot generate SSPI context.” The
Cannot Generate Sspi Context Sql Server 2008 Windows Authentication
explanation, as given by Microsoft in this KB article If you run the SQL Server service under the LocalSystem account, the SPN cannot generate sspi context ssms is automatically registered and Kerberos authentication interacts successfully with the computer that is running SQL Server. However, if you run the SQL Server service under a domain account or under a local account, the attempt to create http://stackoverflow.com/questions/1812541/cannot-create-sspi-context the SPN will fail in most cases because the domain account and the local account do not have the right to set their own SPNs. When the SPN creation is not successful, this means that no SPN is set up for the computer that is running SQL Server. If you test by using a domain administrator account as the SQL Server service account, the SPN is successfully created because the domain administrator-level credentials that https://cmatskas.com/fixing-error-cannot-generate-sspi-context-after-changing-sql-service-account/ you must have to create an SPN are present. There are 3 ways to fix the problem: Revert to using the Network Service or Local System account (NOT RECOMMENDED) Assign the domain account to the Domain Admins group (NOT IDEAL – due to the elevated permissions) Fix the problem by giving the domain account just the appropriate permissions in Active Directory. Permissions required are ServicePrincipalName: Read ServicePrincipalName: Write We will use the 3rd option to fix the error. First, it is good practice to verify that the problem is actually due to permission issues. Log in to the server where you SQL Instance is running. Go to the error logs and look for the last time that the SQL service was restarted. You should find an error message similar to this: Date 10/17/2013 9:29:50 AM Log SQL Server (Archive #1 - 10/17/2013 10:53:00 AM) Source Server Message The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/servername.domainname.net:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. This is g
»sysadmincommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/sysadminuse the following search parameters to narrow your https://www.reddit.com/r/sysadmin/comments/3eb9z8/help_understanding_the_target_principal_name_is/ results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from "example.com"url:textsearch for https://www.experts-exchange.com/questions/28417538/The-target-principal-name-is-incorrect-Cannot-generate-SSPI-context-Microsoft-SQL-Server-Error-0.html "text" in urlselftext:textsearch for "text" in self post contentsself:yes (or self:no)include cannot generate (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dogsee the search faq for details.advanced search: by author, subreddit...this cannot generate sspi post was submitted on 23 Jul 20153 points (100% upvoted)shortlink: remember mereset passwordloginSubmit a new linkSubmit a new text postsysadminsubscribeunsubscribe151,482 readers388 users here nowA reddit dedicated to the profession of Computer System Administration This is a professional subreddit so please lets keep the discourse polite. In an effort to reduce spam, accounts less than 24 hours old will be unable to post to /r/sysadmin. For IT career related questions,
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0) Want to Advertise Here? Solved The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0) Posted on 2014-04-22 MS SQL Server MS Legacy OS Active Directory 1 Verified Solution 5 Comments 19,287 Views Last Modified: 2014-04-24 Hi, I have added a new PC to the domain where the SQL server resides, However, when I try to login to the sql server using windows authentication I get the following error: Cannot connect to a2\a. ------------------------------ ADDITIONAL INFORMATION: The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0) Now, 1. I am able to connect from the same pc using SQL AUTH without any problems. 2. I have other PC's I added to the domain and I was able to login to the SQL server using windows auth without an issue. 3. on this PC I am unable to login using windows auth with ANY domain user, even with users that I confirm working from other PC's on the domain. 4. I tested ping , dns and such its all good. How to proceed? Thanks. 0 Question by:kelso109 Facebook Twitter LinkedIn Google LVL 28 Best Solution bybecraig 1.. Verify you do not have a duplicate SPN (This more seems like your issue) Very detailed info on resolving spn issues: http://social.technet.microsoft.com/wiki/contents/articles/717.service-principal-names-spns-setspn-syntax-setspn-exe.aspx Go