Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to connect to server - Cannot generate SSPI context

Status
Not open for further replies.

varajan

Technical User
Oct 5, 2001
42
0
0
IN
While trying to connect to the SQL error, the following message appears:

Under the SQL Query Analyser message box, the following message appears:

Unable to connect to server XXXXXXX:

Server: Msg 1311, Level 16, State 1
[Microsoft][ODBC SQL Server driver] Cannot generate SSPI context

Can somebody please help with the above issue ?

In addition, tries installing the MSDE component again. Issue remains.
 
Couple of questions:

-What version of SQL are you using?
-What version of Windows is SQL installed on?
-What version of Windows is your local PC on?

--James
 
Have you changed the password of the account the SQL Server runs under recently? This error is often caused by the SQL Server running under a domain or local account that the password has been changed and the SQL Server has not been restarted under the new password.

Denny

--Anything is possible. All it takes is a little research. (Me)

[noevil]
(My very old site)
 
James,

Answer to your queries are a follows:

-What version of SQL are you using?
SQL Server 2000

-What version of Windows is SQL installed on?
Windows 2000 Advanced Server Edition

-What version of Windows is your local PC on?
The application is being done on the console itself.
Windows 2000 Advanced Server Edition

____________________________________________________________

Denny,

Answer to your queries are a follows:


Have you changed the password of the account the SQL Server runs under recently?
Local account password has been changed.

This error is often caused by the SQL Server running under a domain or local account that the password has been changed and the SQL Server has not been restarted under the new password.

SQL Server was re-started after the password change.


 
I'd recommend restarting the service again. It may not have taken correctly.

You might also want to reset the password in the services control pannel. It may be logging it in with the wrong password and cashed credintials for some reason.

Denny

--Anything is possible. All it takes is a little research. (Me)

[noevil]
(My very old site)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top