This error occurs when 2 or more accounts have registered the same service principal name (SPN).
For example, I had a duplicate entry for host/cit10.xxxxdom1
1. From the domain controller, open a command prompt and then type the following string:
ldifde -f domain.txt -d dc=domain,dc=com
2. Open the text file in Notepad and then search for the SPN that is reported in the event log.
ie. host/cit10.xxxxdom1
3. Note the user accounts under which the SPN is located and the organizational unit the accounts reside in and determine which one is incorrect. In my example, one computer had both a correct spn (host/compna0003.xxxxdom1) and a duplicate spn (host/cit10.xxxxdom1) right below it that another PC also (correctly) had. I noted the where the offender was located in the AD hierarchy.
Then once the above has been located use the Windows Support Tools utility ADsiedit
Using ADSIEdit
1. Add ADSIEdit to the MMC and bind to the domain using the Domain well known naming context.
2. Navigate to each user account you previously documented as having a duplicate SPN registration and right click the account and select properties.
3. Scroll through the list of attributes until you see ServicePrincipalName, double click ServicePrincipalName and remove the duplicate SPN registration and click on OK and exit ADSIEdit.
Digg This | Save to del.icio.us
Comments
You can follow this conversation by subscribing to the comment feed for this post.
Leave a Comment