I got a number of error message while working in the latest Trads Studio 2022 revision and those errors, while not crashing my work, are puzzling me as I was not trying to save any bilingual.
Note than the second message related to the bilingual file popped up over the first one a minute later while I was looking for documentation
New update on that issue—well, in fact, nothing new per se (the “0x%1” issue keeps popping up for more and more people in my organization), but here's what I noticed for now:
The error can happen in any of the circumstances below:
When creating a translation project, or a revision project package;
When confirming a segment;
When updating the preview;
When generating the target file;
When opening a project.
I couldn't say why it happens, but the messages seem to imply that it occurs because the file becomes temporarily unavailable, so that, usually, when the error occurs, you can retry the very next moment and it works. Or it still doesn't work several times in a row, and then it works without a problem.
I'm suprised than Paul has not yet followed up on that (I guess he's off for now), but here's the latest I could find about that from RWS: https://gateway.sdl.com/apex/communityknowledge?articleName=000019760
Unfortunately, in my organization, individual users don't have administrative rights to perform a checkdisk (chkdsk /r), but for anyone able to do it, that would be my first suggestion.
I'm suprised than Paul has not yet followed up on that (I guess he's off for now), but here's the latest I could find about that from RWS: https://gateway.sdl.com/apex/communityknowledge?articleName=000019760
I'm afraid this is the only update we have. The dev team are still monitoring and it seems to affect some other applications as well. So far we're not sure this is something we can actually fix so the KB may be the only way to resolve this which means users in some companies will have to raise a ticket and ask their IT to perform the fix for them.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Ok, thank you Paul for the update. It's always much appreciated, even when there is no clear solution.
Please let us know if the dev team ever finds some kind of workaround, or actual solution.
Please let us know if the dev team ever finds some kind of workaround
You mean other than the one you already have? To be sure we will!
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
I have an unfortunate update today about the “0x%1” issue and the potential solution: my computer finally had a chkdsk /r done this morning, and just a few minutes after it was done and my computer was restarted, I once again got the following message when confirming a segment:
So, the chkdsk is definitely not the solution.
I know the issue is not specific to Trados Studio, but do you know if RWS is in communication with Microsoft regarding that error (which, as I mentioned before, seems to be due to the 22H2 update)?
I guess it's our only hope, Obiwan! 
Thank you and have a nice day!
P.S. I really don't get how to make the “Get Sentiment” function happy... but again, thanks for your help, even though we're not out of the woods yet.
I've also tried chkdsk to no avail, unfortunately.
Even more worryingly, I have a further development to report: "The case of the disappearing sdlxliff".
This has actually happened twice since this set of problems began, but it's so strange that the first time I assumed it was me who had done something stupid.
One day (after doing the chkdsk) I had repeated 0x%1 and 0x%2 error messages when trying to save my file, which were always resolved eventually after trying several times.
The next morning, I went into my project and tried to open my file to continue translating, only to be faced with this:
When I went into the project file to have a look, the sdlxliff had indeed completely disappeared.
I had no choice but to recreate the project, which fortunately I was able to populate from my TM. Since then I've been very careful to back up my project files in a separate location before closing Trados, but it's a pain to do, and I don't really need the extra stress!
I've been a big fan and advocate of Trados for years, but this issue and the time it's taking to find a solution have me feeling like we're back to the bad old days...
I've also tried chkdsk to no avail, unfortunately.
Even more worryingly, I have a further development to report: "The case of the disappearing sdlxliff".
This has actually happened twice since this set of problems began, but it's so strange that the first time I assumed it was me who had done something stupid.
One day (after doing the chkdsk) I had repeated 0x%1 and 0x%2 error messages when trying to save my file, which were always resolved eventually after trying several times.
The next morning, I went into my project and tried to open my file to continue translating, only to be faced with this:
When I went into the project file to have a look, the sdlxliff had indeed completely disappeared.
I had no choice but to recreate the project, which fortunately I was able to populate from my TM. Since then I've been very careful to back up my project files in a separate location before closing Trados, but it's a pain to do, and I don't really need the extra stress!
I've been a big fan and advocate of Trados for years, but this issue and the time it's taking to find a solution have me feeling like we're back to the bad old days...
I can confirm this, Caroline. chkdsk did nothing and I have lost several sdlxliff files and even an entire project, not to mention the time I spent to try and come up with a fix. I use the Professional version, by the way.
Translate
