Philippe Riondel

Frustrating I know... but this error message is typical of many.  One error message in the title but hundreds of ways in which it could be caused.  The best thing you can do when you get problems like this is to provide details of the full error message, and a copy of your log files so that we can investigate it and find out where the issue is coming from.

Paul.

Thank you Paul,
I will provide you with the details next time it happens, which may not be long...

Also, It happens with the same repetitive segment through the dozens of files of my project...

Salut Philippe,

This isn't just an SDL error. If you Google it, you'll find it happens in thousands of contexts in many different software environments. I've seen it cited as C# (a high level, statically typed, multi-paradigm programming language developed by Microsoft) so maybe it's a Windows error or a Microsoft programming-triggered scenario. I don't know anything about things at that level, except that it has very many potential triggers and cannot be resolved as if it were one 'long time issue'.

Il suffit d'expliquer la situation précise qui déclenche l'erreur, ici sur la Communauté, pour que quelqu'un qui a déjà rencontré cette erreur, ou même qui la comprend, réagisse pour te secourir !

All the best,

Ali

Thank you for your reply Alison.
I understand it's certainly due to the underlying C# platform, but there is also something that is due to Studio, since, like I just wrote it, it happens repetitively in the same TUs. Also, there could be a workaround or error management in Studio coding that prevents the error to corrupt other functions, like the Translation Results insertion.

Regards

Philippe Riondel

Hi again Philippe,

I have been using Studio and its Trados predecessor for over 20 years and this error (among others) has not come up once for me unless it was due to the client's original source content or some external influence (e.g. a Windows update) triggering the issue. In this and any other cases that I could not troubleshoot myself (being a beta tester, I've enjoyed 'playing' at troubleshooting many 'unintentional' issues), I would not automatically blame any SDL element specifically but instead I'd normally, from experience, expect the issue to be generated by the source format software's programming or an error in the original source document or indeed an end client error.

I don't expect SDL Trados Studio to be able to automatically cope with ANY input from ANY software combination on ANY platform because I know from experience that it's impossible to achieve this perfect state of being... despite SDL's ongoing attempts to create a product that can cope with all possible outcomes.

This being said, I would nonetheless expect my voluntary and/or SDL-employed colleagues on the SDL Community to take an interest in helping me with this or any other problems I encounter with the software. This is because we're a huge, worldwide team who work together to make the software work better for us, because we want to .

Meilleures amitiés,

Ali

Philippe Riondel

Hi again Philippe,

I have been using Studio and its Trados predecessor for over 20 years and this error (among others) has not come up once for me unless it was due to the client's original source content or some external influence (e.g. a Windows update) triggering the issue. In this and any other cases that I could not troubleshoot myself (being a beta tester, I've enjoyed 'playing' at troubleshooting many 'unintentional' issues), I would not automatically blame any SDL element specifically but instead I'd normally, from experience, expect the issue to be generated by the source format software's programming or an error in the original source document or indeed an end client error.

I don't expect SDL Trados Studio to be able to automatically cope with ANY input from ANY software combination on ANY platform because I know from experience that it's impossible to achieve this perfect state of being... despite SDL's ongoing attempts to create a product that can cope with all possible outcomes.

This being said, I would nonetheless expect my voluntary and/or SDL-employed colleagues on the SDL Community to take an interest in helping me with this or any other problems I encounter with the software. This is because we're a huge, worldwide team who work together to make the software work better for us, because we want to .

Meilleures amitiés,

Ali