Hi Mariusz Lasota

Maybe the below article would help 

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0028483 

Best regards, 

Loredana 

Thank you Loredana, however I am looking for a solution that does not involve uninstalling the update and rolling back to the previous version. I would think updates are introduced to improve usability rather than to break it.

Hi Mariusz Lasota

they are , to be honest I am not really sure why and what triggered the error, might be the update or not, but let me try to reproduce this and to see if the same on my case . Can you please provide me with a bit more details regarding  the steps you followed prior to the message appearince? 

Hi Ana, there was just one step, I installed SDL Studio 2019 SR1 CU3 55768 on top of the previous version, which I believe was SR1 CU2 48878. Not sure if this is of any importance but I downloaded the package from SDL's FTP site, as I have multiple licences of SDL Studio PRO and I did not want to waste time downloading it on every machine. I always update my machine first and then test it for a week to make sure there are no issues. And there you have it, SDLXLIFF converter stopped working. Of course I did not update other machines as SDLXLIFF converter is important functionality allowing to delegate jobs to people who do not run SDL Studio. This happened before and I was aware for the "solution" you suggested, i.e. going back to the previous version by uninstalling everything and installing it again.

I found a temporary solution. To cut my investigation and long story short It appears that the latest update of SDL Studio 2019 SR1 CU3 55768 replaced the vital DLL file at the following path "C:\Program Files (x86)\SDL\SDL Trados Studio\Studio15\DocumentFormat.OpenXml.dll" and updated it to a newer version, which broke the SDLXLIFF converter.

I downloaded the proper version of the DLL file (2.7.2.0) from www.nuget.org/.../2.7.2 and replaced the file at the path I mentioned above. This fixed SDLxliff converter for me. I retained the original file with a modified extension in case I need to restore it.

Now it would be good if SDL developer team came up with a more elegant solution.

Hi Mariusz Lasota

Out of interest is there a reason you use this app instead of the built in functionality in Studio?  Export for Bilingual Review.

Functionality was introduced by the same developer in both cases.

Export for Bilingual Review within Studio lacks basic functionality, namely control over what is exported (exclusion filters) and what is updated. For me Export for Bilingual Review is quite unusable.