When you open a file from a project published on GroupShare, you receive following error:

Failed to open 'filename.sdxliff'. [...]
SDLXLIFF validation error: Data at the root level is invalid. Line X, position Y.

Workaround A: Ask Previous User to Check in New Version of the File

This workaround has to be applied on the computer where the file was last checked in.
Ask the user who worked on the file before you to perform following steps:

1. If checked out, check in file
2. Check out file
3. Open file in editor
4. Save file (no changes necessary)
5. Check in file

This repairs the file on the server. Other users should now be able to open it again.
 

Workaround B: Repair SDLXLIFF File

This workaround can be applied by any user who encounters the error. Basic XML knowledge is recommended if you want to apply this workaround.

1. Activate the Files view
2. If the file is not checked out, check out (right-click > Check Out)
3. Right-click file and select Explore Containing Folder to find affected sdlxliff file in Windows Explorer
   
4. Make a backup copy of the affected sdlxliff file
5. Open the affected sdlxiff file in a text editor (e.g. Notepad or Notepad++)
6. Scroll to the end of the file
7. You will most likely find that the file contains
   • a closing tag </xliff>,
   • some content after this tag followed by a second closing tag </xliff> - or possibly only part of a closing </xliff> tag
8. Delete all content after the first closing tag </xliff>
   
9. Save your changes
10. Verify that you can now open the project file in Trados
11. Check in the file to propagate the fix to the project on the server.

Note: It is possible to apply the workaround without checking out and checking in the file (steps 2 and 11). However, in this case you will only repair the file on your computer - not the file on the server.

In rare cases, the bilingual sdlxliff file can be corrupted when deleting content from it. No data is lost - but Trados Studio is unable to open the file until you apply one of the workarounds found below.

SDL Development is aware if the issue and is working on a solution. We hope to deliver a fix in one of the next cumulative update for GroupShare 2017 (CU4).