Cannot Generate SSPI context

Hello everyone,
Yesterday I changed the MSSQLServer Service logon account as well as the
SQLAgent logon account. Now when one of my DB's attempts to run a
particular job, she gets the following error:
Error #: -2147467259
Description: Cannot generate SSPI context
Source: Microsoft OLE DB Provider for SQL Server
SQL State: HY000
Native Error: 0
I mention the account changes as the job ran fine for several months before
this change. When I made the change of the account properties, I made them
thru the SQL Enterprise Manager. However, I also followed the article
relating to doing the change manually thru the services applet to cover all
of my bases afterwards and trying to ensure all properties on registry keys
and sql folders took. Those check out.
Thoughts?I managed to figure this one out ...
Looks like the SPN was still showing up in Ad under the old account for the
SQL Service logon. I proved this out by noting the KDC event error message
on my domain controller. At this point I simply ran
setspn.exe -d MSSQLsvc/hostname:1433 server
and
setspn.exe -a MSSQLsvc/hostname:1433 server
to delete and add back the correct SPN information. All appears to be
working normally now.
"Tekmazter" <Sigs48@.Hotmail.com> wrote in message
news:umRL9gw4GHA.932@.TK2MSFTNGP04.phx.gbl...
> Hello everyone,
> Yesterday I changed the MSSQLServer Service logon account as well as the
> SQLAgent logon account. Now when one of my DB's attempts to run a
> particular job, she gets the following error:
> Error #: -2147467259
> Description: Cannot generate SSPI context
> Source: Microsoft OLE DB Provider for SQL Server
> SQL State: HY000
> Native Error: 0
> I mention the account changes as the job ran fine for several months
> before this change. When I made the change of the account properties, I
> made them thru the SQL Enterprise Manager. However, I also followed the
> article relating to doing the change manually thru the services applet to
> cover all of my bases afterwards and trying to ensure all properties on
> registry keys and sql folders took. Those check out.
> Thoughts?
>