SSPI handshake failed with error code 0x8009030c

Question

SSPI handshake failed with error code 0x8009030c

Viewing 11 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply

NJ-DBA SSChampion Points: 13834 More actions · Answer 1

also, perhaps there is something running as a local account (ie MACHINENAME\USER) or NT AUTHORITY\SYSTEM that is trying to log in...

If you have the client machine, you should be able to do a netstat -o to determine what process is initiating a connection to your sql server.

shilpa_akula SSC Enthusiast Points: 104 More actions · Answer 2

Nothing running under local account and no issues with RDP

NJ-DBA SSChampion Points: 13834 More actions · Answer 3

You always see the same IP address in the error log, right?

If so, can you go to that machine and do a netstat -o... this will show you all connections from the client and the associated process id. You should be able to look through the results and find connections to your SQL Server from that client. You can then have a look at the task manager and sort by process id to see what process is connecting to your server.

Really curious to find out what this is.

ps. One Orange Chip Points: 29423 More actions · Answer 4

I've faced this issue in the past. For me, manually registering the SPN resolved the issue.

Here is the syntax for the same.. This has to be run by a domain administrator on AD.

setspn -A MSSQLSvc/myhost.redmond.microsoft.com:1433 accountname

Refer:- http://blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx

Pradeep Singh

Paul White SSC Guru Points: 150468 More actions · Answer 5

Paul White NZ (4/4/2010)
There are answers to most connectivity problems on the SQL Server Protocol Team's blog:
http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
...etc.

From earlier. 🙂

Not the same link exactly, but the same blog.

Might have saved some time by visiting it...?

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

ps. One Orange Chip Points: 29423 More actions · Answer 6

Paul White NZ (4/7/2010)

Paul White NZ (4/4/2010)
Might have saved some time by visiting it...?

I should have :w00t:

Pradeep Singh

Paul White SSC Guru Points: 150468 More actions · Answer 7

ps. (4/7/2010)
I should have :w00t:

LOL :hehe:

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

Perry Whittle SSC Guru Points: 234064 More actions · Answer 8

NJ-DBA (4/5/2010)
correction- i think it was “Read servicePrincipalName” and “Write servicePrincipalName”

Correct they are the permissions to assign in ADSIEDIT to the service account. You also need to trust the account for delegation in AD users and computers > account properties

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQLRNNR SSC Guru Points: 281344 More actions · Answer 9

Paul White NZ (4/7/2010)
Paul White NZ (4/4/2010)
There are answers to most connectivity problems on the SQL Server Protocol Team's blog:
http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
...etc.
From earlier. 🙂
Not the same link exactly, but the same blog.
Might have saved some time by visiting it...?

Possibly.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

chubbsm SSCommitted Points: 1770 More actions · Answer 10

We have this issue almost every month or so on various server. It has turned out to be a DC issue in each case. Withe several hundred instances and numerous DC's it has been a pain to resolve!

SQLRNNR SSC Guru Points: 281344 More actions · Answer 11

chubbsm (4/8/2010)
We have this issue almost every month or so on various server. It has turned out to be a DC issue in each case. Withe several hundred instances and numerous DC's it has been a pain to resolve!

I would say reduce the number of DCs, unless they are out there at remote offices that have poor connectivity (which would also be another cause for this issue).

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events