Target principal name is incorrect: replication error

I am having problems with replication on a new Windows server 2012 R2.  This server replaced an existing server so during the installation I named the server differently to avoid duplicate names.  When I took down the old server and brought up the new server, I changed the server name.  Now I am getting replication error "The target principal name is incorrect.

Also,  I checked the service principal names with setspn -l servername and there were multiple entries with the old server name.  I tried to remove them with setspn -d servicename servername and it said that they were successfully unregistered, but when I did a setspn - l servername again they were still there.  What can I do to remove these entries and repair replication?

Thanks
Donna HSr. Manager of ITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Donna HSr. Manager of ITAuthor Commented:
This is a domain controller at a small remote site and only has Active Directory, DNS and DHCP roles.  It does not have the FSMO roles.  Can I demote this server, restart and then DCPROMO and re-add the DNS and DHCP roles to repair replication?
kevinhsiehCommented:
You don't need to remove the DNS and DHCP roles. Just demote as a DC, make sure there is no lingering metadata in AD, and then promote it to a DC again.

Clean Up Server Metadata
https://technet.microsoft.com/en-us/library/Cc816907(v=WS.10).aspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Donna HSr. Manager of ITAuthor Commented:
Demoting the DC, cleaning up the metadata and then promoting it to a DC again worked.  I also removed the DNS role as well as a precaution.  There were some entries related to the old server name that I wanted to clean up.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.