SQL Server 2005 Connection Error: Unable to Create SSPI Context

Provided by: Microsoft OLE DB Provider for SQL Server. Can anyone help me with this .. I tried to connect to LLBLgen

+3
source share
11 answers

In my case, I found that the account is locked. The reason was that I used to try to log into the system more than 3 times before on another machine. He did not recognize me - and finally, he blocked my account.

Re-opening the account made everything work fine.

w yang

+2

, , Windows. SQL- ( /) , Windows SQL- , .

-Edoode

+1

, , MSSQL. , , - , MSSQL .

+1

SQL Server Windows. , - , .

, - ? , : P

0

. SSPI Active Directory, . . !

0

Microsoft KB, (KB811889) URL-: http://support.microsoft.com/kb/811889.

Google , , .

, , . , , , , , , SSPI SQL Server (2k8), ( 250) "Can not Generate SSPI context". , - , Kerberos, .

0

, , - , AD ( ).

0

: , ? ?

: , , , . , . , :

, Sql- (, usr), , - .

, Local System bam . , . . , , , , - . . ... , , , , - , - .

, , , , Sql , . , . . . , , . , (, Sql Server 2008 ... 2005 ). ... , , .

Vista Vista ( Windows 7)... Googled "sspi vista" - ( , sspi vista, , , ... , , Google ), , , . .

0

Windows 2003 .

, , ; , , 1 .

Also, besides the time on their watch, check also the time zones.

0
source

Verify that Named Pipes is enabled in SQL Server Configuration Manager. It worked for me.

  1. Open SQL Server Configuration Manager.
  2. Expand SQL Server Network Configuration from the list on the left.
  3. Select "Protocols for [Your Instance Name]".
  4. Right-click on "Named Pipes" in the list on the right.
  5. Select "Enable"
  6. Restart the Instance service.
0
source

Source: https://habr.com/ru/post/1697977/


All Articles