Anna Hughes 

The AI answer may not be helpful, and this might be improved with the addition of more relevant information.  For example:

• what version of Trados Studio?  The full version number.
• what filetype were you working with?
• did you create the project yourself or was it the result of opening a package, or an sdlxliff someone sent you?
• what's the full error message and not just a headline screenshot?

Some of these things would be provided if you gave us the underlying error message, or stack.  To get this consider what's in your image:

I numbered the links at the bottom so I can explain what they are for:

1. this will search the community for similar errors based on the full error details and not just the headline
2. this will search the knowledgebase for similar errors based on the full error details and not just the headline
3. this will allow you to save the full error stack as an xml file to your computer.  Then you can add this file to your post and we will have a lot more to go on.
4. this will let you read the full error stack without saving it.  Sometimes useful as the message can sometimes make it very clear where the problem lies... other times it needs a developer to interpret!

So, can you try some of these to see if it helps, and if not please provide the full error stack and any other details that you consider helpful when you think about it a bit more.

Anna Hughes 

The AI answer may not be helpful, and this might be improved with the addition of more relevant information.  For example:

• what version of Trados Studio?  The full version number.
• what filetype were you working with?
• did you create the project yourself or was it the result of opening a package, or an sdlxliff someone sent you?
• what's the full error message and not just a headline screenshot?

Some of these things would be provided if you gave us the underlying error message, or stack.  To get this consider what's in your image:

I numbered the links at the bottom so I can explain what they are for:

1. this will search the community for similar errors based on the full error details and not just the headline
2. this will search the knowledgebase for similar errors based on the full error details and not just the headline
3. this will allow you to save the full error stack as an xml file to your computer.  Then you can add this file to your post and we will have a lot more to go on.
4. this will let you read the full error stack without saving it.  Sometimes useful as the message can sometimes make it very clear where the problem lies... other times it needs a developer to interpret!

So, can you try some of these to see if it helps, and if not please provide the full error stack and any other details that you consider helpful when you think about it a bit more.

Thanks very much for your help Paul. In fact that's exactly what I did in the end. I knew it was a tag error and looking in the full error stack it gave me the number of the tag so I went through manually and found it. Is there any way of searching for a tag at all rather than going through manually?
I use Studio 2022 and the document was an xlf file provided by my client. Thanks again,

Anna

 Anna Hughes 

Anna Hughes said:

Is there any way of searching for a tag at all rather than going through manually?

Ensure the Tag verification check box is ticked in your Project Settings:

Then press F8 and when the Verify is done, check the list of errors/warnings. If there is a tag error, the report will state the segment; double-clicking will take you directly to the offending segment.

Thank you. I'll try that next time. The only problem is that all the tag problems come up with that (including tags removed on purpose etc.) and it's still really hard to find the problem for the Spanning Code. The error stack gave me the actual name of the tag that was causing the problem and I was wondering if there's a way to search for a particular tag. If not your solution will cut it right down at least so thanks a lot!