July 28, 2003 at 10:10 am
I installed Ms SQL server 2000 standard edition on my Windows 2000 Active Directory Server.For the past 3 days, it has been running well. I managed to install the client version on 2 PCs and these PCs have been connecting perfectly to the database on the AD server. I changed the password for the Administrator account on the AD server. I'm now getting this error "Cannot generate SSPI context" each time I want to add an additional client to connect to the AD server SQL Db. I configured my SQL to recognise Windows Authentication. I have restarted the Active directory server and I cannot even view the databases, the SQL Server task that I had set to automatically start at Logon is nolonger starting the server. Trying to start the SQL server (on the AD server) gives me an error message like;
"A connection could not be established to <SERVER>
SQL Server does not exist or access is denied.
ConnectionOpen(Connect())..
Please verify that SQL Server is running and check your SQL server registration properties by righht clicking on the <SERVER> node and try again."
How can I enable SQL to see the new password because I think that all this has been caused by the password change that I did?
Please help me.
July 28, 2003 at 11:18 am
What type of client are you using? My user's get that error in Windows 98 if they didn't log on to the network. You know, they just hit ESC and bypass the log on.
All the best,
Dale
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 28, 2003 at 11:22 am
Something to check in your Services on the server:
Right click on MSSQLSERVER and also SQLSERVERAGENT and verify the Log On account and password.
All the best,
Dale
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 29, 2003 at 9:38 am
We just spent most of yesterday on this exact same problem. Try re-booting or stopping and re-starting all the services. That fixed our problem.
July 29, 2003 at 6:34 pm
I agree that it could be just a logon issue
with the SQL server
You can also register and update the current instance of SQL server in Active Directory, If it hasn't been updated since changing the details would this not cause issues with logging on and starting services ?
Just an idea
Let us know how you go with this issue 🙂
------------------------------
Life is far too important to be taken seriously
September 18, 2006 at 4:37 am
Don't know if this is going to be of any help, but I got this message after moving a SQL 2K server to a new domain of the same name (long story so I won't go into it because it is ir-relevant) but I had added the (SQL) service account as a SQL user on this particualr SQL server, and when trying to connect using Ent Man and Windows Authentication I got the above message all I needed to do was remove and re-add the Windows Account in SQL (suspect the SID information it contained was incorrect) and restart the service using the service account.
So to summize if you are getting the above error and your service account is listed as a sql login try removing and re-adding the login and then restarting the SQL service(s).
September 21, 2006 at 2:23 am
"I'm now getting this error "Cannot generate SSPI context" "
Try doing the work of adding users through the server console, not any kind of remote admin tool like RDP or EM from your client. If any part of the setup is still in an NT4 domain you can get this.
The basic problem is account delegation which can only be enabled in AD:
Use the Account is Trusted for Delegation option in Active Directory Users and Computers when you start SQL Server.
October 6, 2006 at 8:57 am
I experienced the same problem two months ago. It is a problem in registering the Service Principle Name (SPN). You need to have at least domain admin privilege to fix it. You can refer the following links to fix the problem.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply