Probability score: 0.6  

Question improvement suggestion: Please provide the exact version of Trados Studio you are using, as well as any recent changes made to your system or software that might be relevant to the issue.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It sounds like you're encountering a common issue when working with Translation Memories (TMs) in Trados Studio after a re-installation. The error message 'An item with the same key has already been added' typically indicates that there may be duplicate entries in your TMs or plugins. Here are some steps you can take to resolve this issue:  

**Step 1:** Check for Duplicate Plugins  

1. Close Trados Studio.  

2. Open the SDL Plugin Management tool.  

3. Look for any duplicate plugins installed.  

4. Uninstall one of the duplicate instances.  

5. Reopen Trados Studio and check if the error persists.  

**Step 2:** Recreate the Project  

1. Go to the Projects view and create a New Local Project.  

2. Use the same source file as in the original project.  

3. Add the translation memory used in the original project during the Translation Resources step.  

4. Click Finish to create the project.  

5. During the batch task pre-translate step, the saved segments in the TM will be used to translate the original source file.  

**Step 3:** Check TM for Corruption  

If the issue persists, it may be worth checking if your TM is corrupted. You can use the SDL TM repair add-in to fix it.  

**Step 4:** Restart Trados Studio  

Sometimes, simply restarting the application can resolve temporary issues. Save your work, close Trados Studio, and then reopen it.  

If these steps do not resolve the issue, please provide the exact version of Trados Studio you are using and any recent changes made to your system or software. This information will help in diagnosing the problem more effectively.  

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

These steps haven't worked. 

Chris Barella 

You have to provide more helpful information.  Your title suggests you have a problem with generating XLIFFs... does this mean target files from a source XLIFF or are you referring to SDLXLIFFs in some way?

Your main post refers to Translation Memories?

What exactly is your problem?  What are you trying to do?

When does that error appear?

What are your source filetypes?

Can we see the full error message (click on the small disk symbol in the error message, save the file to your desktop, then attach to your reply)?

What version of Trados Studio are you using... although the full error details will tell us that!

I am trying to create a project using Word source files in Studio 2019. I am trying to use TMs I have but I get the error message I detailed earlier. i.e. an item with the same key has already been added. I get the message at the end of the process - stage 9 preparation. 

There's no save function on the error message, so I can't share it. I have just successfully created another project using different TMs so it seems to specific to these TMs. 

Chris Barella 

Can you share a screenshot of the error message so we can see where it's being surfaced?

Sure, here you go. 

Chris Barella 

Can you click on "messages reported" to activate that line and then "Results"?

Sure, here you go. 

Chris Barella 

ok - and now what do you see when you click on the "Reports" and "Files" tabs?

Chris Barella 

ok - and now what do you see when you click on the "Reports" and "Files" tabs?

I'm having trouble uploading the images of the Reports and files tabs

Chris Barella 

ok - my bad.  I think the place you need to look is scroll right here:

Sorry for the small images but you are only giving me very small screenshots.  Have you tried simply copy/pasting the images in?  I never upload them!

So, scroll across to the right and there may be a link to the error file.  That's what I'm looking for as it should give us a lot more information to help identify where your problem is coming from.