Odbc Error 0 Cannot Generate Sspi Context Sqlstate Hy000
Contents |
360 games PC games cannot generate sspi context sql server 2008 r2 Windows games Windows phone games Entertainment All Entertainment sqlstate hy000 cannot generate sspi context Movies & TV Music Business & Education Business Students & educators the target principal name is incorrect cannot generate sspi context Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Cannot Generate Sspi Context Odbc
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All cannot generate sspi context fix Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Administering » the target principal name is incorrect. cannot generate sspi context. (.net sqlclient data provider) ODBC SQLState HY000 Cannot generate SSPI... ODBC SQLState HY000 Cannot generate SSPI context
Sqlexception (0x80131904): The Target Principal Name Is Incorrect. Cannot Generate Sspi Context.
Rate Topic Display Mode Topic Options Author Message El bartoEl barto Posted Wednesday, February 11, 2009 5:40 AM SSC Journeyman
The Target Principal Name Is Incorrect Cannot Generate Sspi Context C#
Group: General Forum Members Last Login: Wednesday, November 9, 2011 4:45 AM Points: 84, Visits: 425 Hello everyone, When running scheduled jobs from SQLAgent all jobs fail with the error message.[Microsoft SQL-DMO (ODBC https://support.microsoft.com/en-us/kb/843248 SQLState: HY000)] Error 0: [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI contextThere server has been rebooted, and I have confirmed connectivity to the box from various machines. The error still occurs when a) A new job is created b) When the user running the job is changed. Any advice?. Many thanks, Kindest Regards,Nick Post #654688 Khwaja ArshaduddinKhwaja Arshaduddin Posted Wednesday, February 11, 2009 6:17 AM SSC Journeyman Group: http://www.sqlservercentral.com/Forums/Topic654688-146-1.aspx General Forum Members Last Login: Wednesday, December 8, 2010 3:57 AM Points: 75, Visits: 100 This will help you.http://www.sqlservercentral.com/Forums/Topic10251-106-1.aspx Post #654712 « Prev Topic | Next Topic » Permissions You cannot post new topics. You cannot post topic replies. You cannot post new polls. You cannot post replies to polls. You cannot edit your own topics. You cannot delete your own topics. You cannot edit other topics. You cannot delete other topics. You cannot edit your own posts. You cannot edit other posts. You cannot delete your own posts. You cannot delete other posts. You cannot post events. You cannot edit your own events. You cannot edit other events. You cannot delete your own events. You cannot delete other events. You cannot send private messages. You cannot send emails. You may read topics. You cannot rate topics. You cannot vote within polls. You cannot upload attachments. You may download attachments. You cannot post HTML code. You cannot edit HTML code. You cannot post IFCode. You cannot post JavaScript. You cannot post EmotIcons. You cannot post or upload images. Copyright © 2002-2016 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.
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 http://stackoverflow.com/questions/177678/sql-server-2005-connection-error-cannot-generate-sspi-context Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SQL server 2005 Connection Error: Cannot generate SSPI context up vote 3 down vote favorite 1 cannot generate Provide Used: Microsoft OLE DB Provider for SQL Server. Can anyone help me with this.. I was trying to connect with LLBLgen sql-server share|improve this question asked Oct 7 '08 at 8:55 jazzrai 4,592204880 add a comment| 10 Answers 10 active oldest votes up vote 2 down vote accepted This MSDN blog page has some useful on this... http://blogs.msdn.com/sql%5Fprotocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx share|improve this answer answered Dec 9 '09 at 15:17 vince 362 add cannot generate sspi a comment| up vote 2 down vote In my case, I found the account was locked. Reason was I previously, on another machine more than 3 times tried to login. It did not recognise me - and tthen finally it locked my account. Reopening account made all work fine. 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 problem with using Windows Authentication. Please try switching to a SQL server login (username/password), or make sure your current Windows login has access to the SQL server and database you're trying to connect to. -Edoode share|improve this answer answered Oct 7 '08 at 14:46 edosoft 9,6872064103 add a comment| up vote 1 down vote I fixed this by mapping a drive to the server running MSSQL. This seemed to generate some kind of trust that allows MSSQL to connect without this error even after a reboot. share|improve this answer answered Dec 11 '09 at 10:20 voidstate 6,16712342 add a comment| up vote 0 down vote I used to get this error sometimes when connecting to my local SQL Server with Windows Authentication. I never fixed it unfortunately - it went away whe