Error 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 Business Learn more about hiring developers or posting ads with cannot generate sspi context sql 2000 us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow cannot generate sspi context. (microsoft sql server error 0) Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Cannot cannot generate sspi context windows 7 create SSPI context up vote 20 down vote favorite 4 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 cannot generate sspi context after changing sql service account 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. sql sql-server security sspi
Cannot Generate Sspi Context Microsoft Sql Server 2008
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 –Prasanna Nov 28 '09 at 17:12 3 Fixing App pool user/password did it for me. –SAM I AM Jun 24 '15 at 13:36 add a comment| up vote 13 down vote 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
account to run the SQL service. I’m sure you do too! However, once you do the right thing and change the SQL Service
Cannot Generate Sspi Context Sql Server 2008 R2
account, you may start getting the following error message when attempting to connect the target principal name is incorrect. cannot generate sspi context to the sql server: “The target principal name is incorrect. Cannot generate SSPI context.” The explanation, as given cannot generate sspi context fix by Microsoft in this KB article If you run the SQL Server service under the LocalSystem account, the SPN is automatically registered and Kerberos authentication interacts successfully with the computer that http://stackoverflow.com/questions/1812541/cannot-create-sspi-context 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 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 https://cmatskas.com/fixing-error-cannot-generate-sspi-context-after-changing-sql-service-account/ 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 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
»sysadmincommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/sysadminuse the following search parameters to narrow your results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from "example.com"url:textsearch for "text" in urlselftext:textsearch for "text" https://www.reddit.com/r/sysadmin/comments/3eb9z8/help_understanding_the_target_principal_name_is/ in self post contentsself:yes (or self:no)include (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 post was submitted on 23 Jul 20153 points (100% upvoted)shortlink: remember mereset passwordloginSubmit cannot generate a new linkSubmit a new text postsysadminsubscribeunsubscribe151,530 readers960 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 cannot generate sspi 24 hours old will be unable to post to /r/sysadmin. For IT career related questions, please visit /r/ITCareerQuestions Please check out our Frequently Asked Questions, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read! Checkout the Wiki Users are encouraged to contribute to and grow our Wiki. So you want to be a sysadmin? RTFM Sysadmin Jobs Official Subreddit IRC Channel - #reddit-sysadmin on irc.freenode.net Posts of pictures are not permitted. If your post requires a picture put it in the text. /r/iiiiiiitttttttttttt (i7t12) for your rage comics, and "Read Only Friday" posts. /r/techsupportanimals for your memegenerator images Link Flair Filters Gilded Comments Traffic Stats a community for 7 yearsmess