Logon SSPI handshake failed with error code 0x8009030c

Question

Logon SSPI handshake failed with error code 0x8009030c

zhayatali

SSC-Addicted

Points: 438
More actions
May 26, 2010 at 12:31 pm

#147239

Hi,
We have two node clustered Sql server 2005 EE x64 on windows 2003 R2 EE on domain. we have default instance which is having sharepoint 2007 databases.
We are getting the below error on On node 1 instance
2009-02-16 15:20:30.12 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 10.10.10.10]
2009-02-16 15:20:30.12 Logon Error: 18452, Severity: 14, State: 1.
2009-02-16 15:20:30.12 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 10.10.10.10]
any help in this regard i need to know is it problem related to sql server or shared points we are using mixed authentication in SQL 2005.
we get error not frequently it comes in month or 2 monthes of gap.
Regards

Viewing 15 posts - 1 through 14 (of 14 total)

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

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

Does this happen after people have changed their passwords?

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

zhayatali SSC-Addicted Points: 438 More actions · Answer 2

No during password changing I did not get any error it's comes in 2 or 3 monthes last time I got that error in feb 2010 we are using shared point 2007.is there any problem in active directory as on SQL server we have enabled both authentcation modes SQL and windows in our cluster environment

regards

SQLRNNR SSC Guru Points: 281334 More actions · Answer 3

If it is an intermittent issue and sparsely occurs (doesn't happen for everybody when it does happen), then it could be a communications error with AD that is quickly resolved by AD and the SQL Server. If it is persistent and happens to everybody then a problem has occurred in AD where your server is not properly recognized. In that scenario, readding the sql server to AD has resolved the issue for me in the past.

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

zhayatali SSC-Addicted Points: 438 More actions · Answer 4

Thanks for the detail reply!

i need to tell you this error occurred for a mint (1:00PM to 1:01) after that it automatically resolved.As i explain more we have 30 databases in SQL cluster instance this problem comes with only shared point database not other like blackboard,help desk

i want to know , is this problem related to SQL or Shared point ?

SQLRNNR SSC Guru Points: 281334 More actions · Answer 5

Both - I have seen it most frequently in SQL. But that is what i deal with predominantly.

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

zhayatali SSC-Addicted Points: 438 More actions · Answer 6

My problem has been resolved thanks for great help

Saravanakumar R Mr or Mrs. 500 Points: 506 More actions · Answer 7

i'm facing the same issue...can you tell me how to resolve the issue

SkyBVI SSCoach Points: 15128 More actions · Answer 8

I dont have any idea about clustered scenario but

I had the same problem a lot many times on my prod sql server.

We had changed the passwords of hte sql agent services and so we were getting messages.

we resolved it by reentering the credentials in the sql server.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

Saravanakumar R Mr or Mrs. 500 Points: 506 More actions · Answer 9

where you reentering the password? In services.msc or in Log reader agent or in publication authentication ?

Saravanakumar R Mr or Mrs. 500 Points: 506 More actions · Answer 10

and why we are getting these error message on particular time around 1 AM (Night) every day ?

do you have any clue on these ?

can you pls describe step by step.. i don't have the clustered environment. so I faced, the same problem which you have..

Thanks for your reply..

SkyBVI SSCoach Points: 15128 More actions · Answer 11

@ saravan

I went into sql server management studio-->security-->credentials

Then reenter your passwords..

check and see if it works.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

SkyBVI SSCoach Points: 15128 More actions · Answer 12

@ saravan

It may be some application or job which runs at night 1 am is using the credentials for autentication.

It checks and cant get authenticated and so you get the message.

Regards,

Sushant

Regards
Sushant Kumar
MCTS,MCP

SQLBuddy123 One Orange Chip Points: 28294 More actions · Answer 13

This login may occur due to the Incorrect Connection string specified when connecting to the SQL Server or due to the inability to resolve the login.

Thank You,

Best Regards,

SQLBuddy

bobnysoftz Old Hand Points: 324 More actions · Answer 14

Probably try get some hotfixes for your sql server 2005 and install them. Your authentication methods are ok to me, j