I am getting the following error messages when syncing a TDS 5.5 project:

Item template with path ... already exists

enter image description here

Found duplicate id ... for item ... and ... in project. Please remove one of these items from your project before attempting to sync with Sitecore.

enter image description here

This error happens for many items, and there are definitely no duplicates—neither in the project file, nor on disk.

This might have begun after I updated TDS to a newer version.

How do I fix these errors?

  • Did you try the solutions from here: sitecore.stackexchange.com/questions/750/… ?
    – jammykam
    Oct 7 '16 at 9:14
  • Thank you for the link! That question looks similar, although the error message is a little bit different, and I think it's shown in the Output window, while for me the errors are shown as modal popups. The answers from that question do not work. Oct 7 '16 at 9:17
  • 1
    I'm sure I've seen that duplicate ID issue before but can't for the life of me remember exactly what the issue was. It could have been something to do with whitespace and newline handling in the GIT repo (but it's a hazy memory as we've switched to Unicorn over here now). Have you tried getting in touch with the TDS support guys? I always found them to be very helpful & responsive back in the day. Oct 7 '16 at 12:52
  • 1
    @OwenNiblock You're right, it could be related to GIT line endings. Maybe the TDS caching subsystem can't handle them properly. See the fix I posted as an answer. Oct 7 '16 at 12:59

There is a reliable fix.

  1. Go to Tools→Options→TDS Options and set Background Cache Loading to False.

enter image description here

  1. Restart Visual Studio.
  2. Set Background Cache Loading back to True.

Errors will stop after these steps—courtesy of Angel from TDS support.

The errors are caused by broken cache files. Changing the Background Cache Loading makes TDS rebuild the cache from scratch, hence fixing the issue.

  • 1
    Fantastic! This worked for me. What a lifesaver...
    – tjans
    Jun 6 '17 at 14:41
  • any other way to work on this error. Above mentioned approach didn't work for me.
    – Shaurya
    May 20 '19 at 15:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.