Home > Cannot Generate > Microsoft Odbc Cannot Generate Sspi Context

Microsoft Odbc Cannot Generate Sspi Context


Browse other questions tagged sql-server or ask your own question. Many thanks, Kindest Regards,Nick Post #654688 Khwaja ArshaduddinKhwaja Arshaduddin Posted Wednesday, February 11, 2009 6:17 AM SSC Journeyman Group: General Forum Members Last Login: Wednesday, December 8, 2010 3:57 AM Points: Formula 1 rebus River Crossing Puzzle more hot questions question feed lang-sql about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. have a peek here

You cannot edit your own posts. The content on this site reflects my own personal opinion and does not represent the views of any other individual or organization. Can Trump undo the UN climate change agreement? You can verify that the SPN has been registered successfully upon the restart by going to the SQL Server logs. https://support.microsoft.com/en-us/kb/811889

Cannot Generate Sspi Context Sql Server 2008 R2

The error which was being received was as follows. This is very simple to check and fix. You cannot post topic replies. Terms of Use.

still no idea why yet. I think a reboot used to fix it - have you tried that? Why is this C++ code faster than my hand-written assembly for testing the Collatz conjecture? Cannot Generate Sspi Context Microsoft Sql Server 2012 Privacy Policy.

br Jan share|improve this answer answered Jan 26 '11 at 10:13 JanAndersne 212 add a comment| up vote 1 down vote The error you get is almost always caused by a Cannot Generate Sspi Context Sql Server 2014 more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed You cannot post events. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password?

A month goes by and a power strip fries causing the server to have an unexpected shutdown. System.data.sqlclient.sqlexception: Cannot Generate Sspi Context. You cannot send private messages. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? share|improve this answer answered Jan 7 '09 at 21:19 JohnFx 28.6k1480138 add a comment| up vote 0 down vote I get the problem when I have the time set differently on

Cannot Generate Sspi Context Sql Server 2014

{{offlineMessage}} Store Store home Devices Microsoft Surface PCs & tablets Xbox Virtual reality Accessories Windows phone Software Office Windows Additional software Apps All apps Windows apps Windows phone apps Games Xbox Naming Information cannot be located because: The ... Cannot Generate Sspi Context Sql Server 2008 R2 Go to the error logs and look for the last time that the SQL service was restarted. Cannot Generate Sspi Context Odbc A colleague was trying to use SQL Management Studio to connect to a specific database server.

Help Desk » Inventory » Monitor » Community » Menu Skip to main content (Press Enter). http://usableflash.com/cannot-generate/odbc-cannot-generate-sspi-context.php I was trying to connect with LLBLgen sql-server share|improve this question asked Oct 7 '08 at 8:55 jazzrai 4,627214880 add a comment| 10 Answers 10 active oldest votes up vote 2 Polyglot Anagrams Robbers' Thread Where to take phone interview while at work Technological gradient within a solar system? First, it is good practice to verify that the problem is actually due to permission issues. Cannot Generate Sspi Context Fix

So other than the time on their watches, check the time zones as well. share|improve this answer answered Jul 20 '09 at 19:33 Lance Roberts 14.6k2384118 add a comment| up vote 0 down vote Short Answer: Have you recently change the user the service is This seemed to generate some kind of trust that allows MSSQL to connect without this error even after a reboot. Check This Out in case you need to Google it was well) that and ran across an article that pretty explained our scenario after we had a meeting we all remember these pieces and

About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up The Target Principal Name Is Incorrect. Cannot Generate Sspi Context. (.net Sqlclient Data Provider) Later that morning it crapped out again... What is Name Resolution Policy Table (NRPT) Licensing Windows Server 2012 or Windows 8 with KM...

Happy coding… P.S.

On the client (Windows 8.1 Pro) i get the following in event viewerthese point to Kerberos, but i know nothing about Kerberos lol A Kerberos error message was received:on logon sessionClient Or... Our admin guy doesn't like Vista and likes to blame everything on Vista (refuses to let us test Windows 7)... Sqlexception (0x80131904): The Target Principal Name Is Incorrect. Cannot Generate Sspi Context. This is an informational message.

We don't reboot. Connection failed: SQL State:'S1000' SQL Server Error 0 [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context After investigation this was caused by an incorrect time set on the SQL server. Eventually we ran across a set of actions that could cause this: If you change the user that the Sql Server runs as (e.g. http://usableflash.com/cannot-generate/microsoft-odbc-sql-server-driver-cannot-generate-sspi-context-hy000.php You should now see an entry similar to this: Date                    10/17/2013 10:53:58 AM Log                       SQL Server (Current - 10/17/2013 10:54:00 AM) Source                Server Message The SQL Server Network Interface library successfully

Connections to SQL Server should now succeed! After disabling this option he was able to connect without any problems. I am using Domain credentials to connect and up until early this morning they worked fine (for the last 2yrs)If I use the SA account to connect with ODBC it works Toggle navigation BlogsCommunitiesDiscussionsSite ContentLibraries on this day between these dates Not a valid date Not a valid date Posted by HomeJoin TodayChapters Find a ChapterMy Chapter CommunityMy Chapter RegistrationsMembership Levels &

All Rights Reserved. share|improve this answer answered Dec 11 '09 at 10:20 voidstate 6,20812442 add a comment| up vote 0 down vote I used to get this error sometimes when connecting to my local All was good in our world. Long Answer: I know this is old, but I want to post my experience that I just had.

Yet another month later we find out problem because we rarely connect to this particular database (Interestingly, Sql Server 2008 worked fine... We had spent hours Googling and found nothing that worked. share|improve this answer answered Sep 3 '09 at 13:59 Nazadus 692921 add a comment| up vote 0 down vote In my case, the time synchronization issue in the Windows 2003 domain Ultimately what was causing my problem was not mentioned in any KB or article I found on the net, but through trial and error I discovered that when the account used

Can anyone help me with this..