Bill Herde
asked on
kerberos error message
One of my SQL servers pops a Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOW N error every 15 minutes. Text of the error is
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 0:0:1.0000 1/22/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOW N
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XXXX.LOC
Server Name: MSSQLSvc/annie.XXXX.loc:14 33
Target Name: MSSQLSvc/annie.XXXX.loc:14 33@XXXX.LO C
Error Text:
File: 9
Line: e2d
Error Data is in record data.
Annie is another SQL server which this server sends log shipping to, and the errors occur at the interval of the LSbackups.
The quick link takes me to a MSFT page telling me how to reset stored passwords. Completed this on both servers involved with no improvement.
Went a step further and ran setspn.exe to verify no duplicate records.
I have rebooted Annie with no improvement, but do not want to reboot the production server unless it is sure to fix it. Nothing I read indicates it should be necessary.
Anybody more familiar with this?
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 0:0:1.0000 1/22/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOW
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XXXX.LOC
Server Name: MSSQLSvc/annie.XXXX.loc:14
Target Name: MSSQLSvc/annie.XXXX.loc:14
Error Text:
File: 9
Line: e2d
Error Data is in record data.
Annie is another SQL server which this server sends log shipping to, and the errors occur at the interval of the LSbackups.
The quick link takes me to a MSFT page telling me how to reset stored passwords. Completed this on both servers involved with no improvement.
Went a step further and ran setspn.exe to verify no duplicate records.
I have rebooted Annie with no improvement, but do not want to reboot the production server unless it is sure to fix it. Nothing I read indicates it should be necessary.
Anybody more familiar with this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The -R switch was the answer. Since the SPN was there, and was correct, It was just a matter of the first SQL server forgot about it. The -r switch says it means Reset, but a more accurate description shows when you run it. It RE-REGISTERS the SPN. So running 'setspn -R Annie' re-registered the SPNs set for Annie and the error went away.
Thanks for the pointers guys!
Thanks for the pointers guys!
ASKER
I used setspn -X to check for duplicate SPNs.
'setspn -L administrator' shows two registered SPN for Annie for the system administrator. The target names matche the servername in the error.
I note there is a -R option which says
To reset the default SPN registrations for the host names for an account
•Type the following at a command prompt:
setspn -R AccountName
Does anybody know what they mean by reset? I do not want to clear all SPNs for the administrator account.