"yba02" <yba02@discussions.microsoft.com> wrote in message
news:EB4981FF-04E5-4394-9160-30199BF7E8CD@microsoft.com...
> 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
>
> "Geoff N. Hiten" wrote:
>
>> 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
>>
>>
>> "yba02" <yba02@discussions.microsoft.com> wrote in message
>> news:DF8AFECF-EDEA-4CC9-88DF-A7339E3E4921@microsoft.com...
>> > 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
>>
>>
>>

"yba02" wrote:

> 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
>
> "Geoff N. Hiten" wrote:
>
> > 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
> >
> >
> > "yba02" <yba02@discussions.microsoft.com> wrote in message
> > news:DF8AFECF-EDEA-4CC9-88DF-A7339E3E4921@microsoft.com...
> > > 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
> >
> >