I have been fighting this one for days: my computer is currently joined to our corporate domain, but I am logged in as a local user. I've used "Manage network passwords" to add all of the relevant credentials for domain access. However, I still get the following error when logging in via Windows Authentication in SSMS:
Login failed for user ''. The user is not associated with a trusted SQL Server connection.
The error logs show that the SSPI handshake is failing - meaning that Windows is not passing along my valid domain credentials to SQL Server.
Finally, I found a workaround that deals with what I'm experiencing by making use of the runas command. It's hacky, and this is definitely due to Vista's "wonderful feature", but it gets the job done. Thanks to Jason Follas for the following tip:
http://www.jasonfollas.com/wiki/Default.aspx?Page=SQL%20Management%20Studio%20on%20Vista&AspxAutoDetectCookieSupport=1
For the record, we should not have to do this.
Subscribe to:
Post Comments (Atom)
1 comment:
Hi Dave,
I saw that the referred article was created in 2007. Has Microsoft come up with a decent fix already ? I also am experiencing this issue in excel pivottables and any application that uses integrated authentiction towards a database :(
Thanks!
Post a Comment