• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 1949 views
  • Users 0 members are here
Options
Related

"Index was out of range" error still not fixed

Philippe Riondel

According to the KB and my own experience, there is more than 5 years people are complaining about the "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index" error, and after multiple new versions and SR's, the errors still happens.

The error as such is already an issue, but what adds insult to injury is that one becomes unable to insert segments from memory in the subsequent segments until Studio is restarted. It is the 5th time I restart Studio this afternoon!

I work on a series of DOCX documents, and I own Studio 2021 SR1 (SR2 causes issues with Groupshare at this point, so I wait for that issue to be fixed).

I think resolving that long time issue should be a priority for SDL team. At least preventing the error to interfere with the ability to insert segments from memory after the issue happens.



Regards
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Philippe Riondel

    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 Slight smile
  • 0 in reply to Alison Field

    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
  • 0 in reply to 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 Heart eyes.

    Meilleures amitiés,

    Ali Slight smile