Holly James 

Holly James said:

I've followed all the advice I can find in the forums, contacted Trados support

Can you elaborate on what this means?  What have you tried exactly?

Also, do you have a ticket number from Support so we can check what the result of their investigation was?

Hi Paul,

Thank you for your reply.

The issue I'm experiencing happened after my computer crashed while Trados was open. Here is part of the message I receive when I try to open the project:

Error processing command line arguments: An error occured whilst trying to determine the file version.

USAGE: SDLTradosStudio.exe [/help|/?] /arg1 val1 /arg2 val2

And if I try to open the sdlxliff file, the message is as follows:

SDL XLIFF validation error: Name cannot begin with the '.' character, hexadecimal value 0x00. Line 3828, position 176080.

These are the steps I have already followed:

https://gateway.sdl.com/apex/communityknowledge?articleName=000001414

Studio cannot open a sdlxliff file


As for the support, I used the chat function that appears on the Trados website and after being referred to the above was told to refer to the community for advice. I don't think I was assigned a ticket number so perhaps I need to raise the issue elsewhere?

Very much appreciate any advice you can give. 

Holly James 

Thank you.  The problem may be related to content in the sdlxliff itself.  Can you drop the sdlxliff into a browser and share what you see?  This post is sort of what I mean:  RE: "sdl xliff validation error" when reopening the file on trados 2017 

Holly James said:

As for the support, I used the chat function that appears on the Trados website and after being referred to the above was told to refer to the community for advice. I don't think I was assigned a ticket number so perhaps I need to raise the issue elsewhere?

ok - the chat function on Trados s not technical support.  They are there to help answer questions and guide users in the right direction but will not able to help with anything that gets technical and will rightly send you here, or to technical support if you have a support contract.

Hi Paul,

I've pasted the file into my browser and from what I can tell, the result that comes up is more or less what I would see if I opened the file in Notepad or similar. The text is millions of characters long but here's a section as an example:

Would it be possible to send the file over to see if you can make any sense of it?

Thanks for your help so far.

Holly James 

ok - please send me the file: pfilkin at sdl dotcom 

Hi Paul,

I just wanted to check whether you received the email I sent? 

Best,

Holly

Hi Paul,

I just wanted to check whether you received the email I sent? 

Best,

Holly

Holly James 

Apologies for the late reply... I did receive your files and just checked them now.  If you open the sdlxliff with a text editor you'll see this towards the end:

Note that the text stops and is replaced with nonsense.  This is because the sdlxliff is corrupt.  You will not be able to work with this file and will have to recreate your project.

Hopefully you have backed up your work to a TM at least?

One thing you may be able to do is recreate the SDLXLIFF from a source file and then replace the content at the start with the content that is still there in the corrupt file.  The good thing is that the embedded source is all there so you might be able to recover the parts that are not corrupt at least.  If you're not sure how to do this if you can at least create the project again and then send me a new sdlxliff untranslated, then I'll take a look for you and see what we can recover.

I also think you should look at how you're working.  So do you use One Drive for your projects for example... that could be a cause of this; do you use some other network drive for projects; do you have some intrusive security software running on files that are open in Studio perhaps?  Things like that which could cause a synchronisation issue that corrupted the file.  It is quite unusual to see something like this so I'd look for external influences that may have caused it.