Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / June 2005

Tip: Looking for answers? Try searching our database.

SSPI error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
yba02 - 22 Jun 2005 15:31 GMT
Hi,
SQL 2K EE is running on a 2-node cluster.  All was fine.
Suddenly, node 2 owned the cluster group and now SQL is running on node 2.  
The reason is the problem:
One node 1, SQL service is not starting and the MMC SQL snap-in returns
"Cannot generate SSPI context" error when trying to connect to the registered
SQL server.
I searched for help and reached the stage where I downloded and ran the
SETSPN utility.
However, I am unable to translate the output so to determine which SPN is
failing.  For sure, restart is of no use in this case.  I also tried to reset
the default SPNs with -r switch but "Could not find account
domainname\servername".
Help Please.
Thanks
Yba
Geoff N. Hiten - 22 Jun 2005 16:33 GMT
Node1 is having trouble finding or communicating with a domain controller.
As such, it cannot authenticate the SQL service account credentials.  Check
for name resolution and communication to your domain controller(s).  Also,
check for major time synch errors.

Geoff N. Hiten
Microsoft SQL Server MVP

> Hi,
> SQL 2K EE is running on a 2-node cluster.  All was fine.
[quoted text clipped - 14 lines]
> Thanks
> Yba
yba02 - 23 Jun 2005 12:28 GMT
Hi,
I forgot to clarify that the SQL server is the DC. I know this is against
recommendations and alteration plans are undergoing but the need is immediate.
What are possible remedies.
Thanks
Yba

> Node1 is having trouble finding or communicating with a domain controller.
> As such, it cannot authenticate the SQL service account credentials.  Check
[quoted text clipped - 22 lines]
> > Thanks
> > Yba
Geoff N. Hiten - 23 Jun 2005 13:56 GMT
Is one or both nodes DC?  AD or NT 4 domain?

GNH

> Hi,
> I forgot to clarify that the SQL server is the DC. I know this is against
[quoted text clipped - 35 lines]
>> > Thanks
>> > Yba
yba02 - 25 Jun 2005 10:03 GMT
Both nodes are DC, AD 2K3 EE.
Thanks.

> Hi,
> I forgot to clarify that the SQL server is the DC. I know this is against
[quoted text clipped - 29 lines]
> > > Thanks
> > > Yba
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.