STATE ID : YH000 Cannot Generate SSPI context

vanton

Hi everyone, i need your help. I migrate a Navision SP1 SQL2000 to Sp3 SQL2005. The only problem i have is that i want to connect with windows authentication login and i get the following error ....."Cannot Generate SSPI context..... STATE ID : YH000". I have made a synchronization and i got no errors.

I also want to tell you that i can connect with windows authentication from the local machine, but NOT from a client.

PLEASE ANY HELP..........?????????????????

jth

Solution
- SQL Server services must be executed by a domain user account
- domain user account must have local administration rights on the sql server

Further hints:
- DNS should be up and running
- Time sync on DC, server and clients

vanton

I did it but I still cannot connect....... ](*,) ](*,) ](*,) ](*,) When you say Time DC Synch, you mean that restart the services? I allready have an account that is starting SQL Server service and thw account has administration rights in the Server. The DNS Services are started...What am i doing wrong??????

DenSter

I get 20 hits in google (Click Here). The most promising looking ones:
http://support.microsoft.com/kb/843248
https://www.microsoft.com/technet/prodt ... x?mfr=true
http://www.dbforums.com/showthread.php?t=977044
http://www.sqlnewsgroups.net/group/micr ... 22714.aspx

bramdedaele

I've had the same problem, when logging onto a SQL server from another computer with NAV, with windows authentication.

After a long search and after reading about many probable causes I stumbled upon the following link, which was not really the solution, but pushed me in the right direction.

http://support4.scriptlogic.com/kb/article.aspx?id=13534

The cause in this case had also something to do with the SQL SERVER SERVICE on the SQL server. This service logged on by a domain admin user of whom the password recently changed :-). And there was our solution... :roll: So after changing the password in the service to the correct one, it worked...

So that service comes into play (/gives us a hard time) when using windows logins on SQL Server.

Grtz,
Bram.