One of our SQL servers was generating these errors for «some» Windows logins but not all.
Error: 17806, Severity: 20, State: 2.
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.1]
Want to learn SQL from a master (or even better a pair of masters?) Have a free evening? Live within a reasonable drive of Houston? You wont want to miss this presentation. Over the years I've had the opportunity to listen to hundreds of different SQL speakers and 2 people who would make my short list of «don't miss presenters» happen to be presenting at a HASSUG meeting this month.
If your not in Houston, I'd recommend using the LiveMeeting link!!
The following Info is from the http://houston.sqlpass.org site
When creating a new application, after going through the entire business analysis & requirements gathering process, normally you wind up with a datamodel that includes many tables and relationships. By this time, depending on the size of the datamodel/system there has been considerable amounts of time invested on all sides. We need a way of preserving this investment of time while still allowing developers to do their thing!
Most shops have policies in place for what level of access developers can have in each environment. In many places I've seen, developers are allowed DBO access in development, and some lesser access in the higher environments (read only usually).
After you've deployed the datamodel to the physical database in a development environment, before you grant the developer group dbo access consider all of the time/effort that has been spent making the datamodel what it is. In order to allow the developers to do their jobs but not allow them to modify the actual table/schema layout you can grant a combinations of privileges.
Ran into this a while back, and we finally found a root cause so, I thought Id put it out here in hopes that it saves at least 1 person the amount of head bashing I had with it
Windows 2003 Enterprise R2 SP2 w/32GB RAM
SQL Server 2005 standard ed SP3 64bit active/passive cluster
In Houston? Hungry for lunch? Want to learn SQL Server from an expert? Head over to the Microsoft office and learn the top SQL mistakes and how to avoid them from Kevin Kline
Not in Houston? or hungry? there's always the live meeting option!
Here are the details from the HASSUG Site:
Delicious
Digg
Facebook
Furl
Google Bookmarks
Live Favorites
Magnolia
Reddit
Slashdot
Stumbleupon
Technorati Favorites
Twitter
Yahoo! Buzz
5 comments
No trackbacks
RSS 2.0
Bloglines
MyYahoo
Netvibes
Newsgator
Rojo