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
I haven't come across this one before. Can you save the full error stack and share it? Click on the small disk and then attach it to the thread:
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
I've encountered the same problem for the first time today, after I confirmed a segment. And then again and again, each time I confirmed a segment. And on these occasions, I could not refresh the preview.
Closing and reopening Trados Studio solved the issue... but I expect it to reoccur at another random moment, since it has also happened to many of my colleagues (at the Government of Canada) in the last few days, apparently at random moments, and for various apparently unrelated tasks.
PROBABLE CAUSE:
I have been using Windows 11 AND Trados Studio 2022 without problem for a couple of weeks, and now the problem occurred right after my computer automatically installed Windows update 22H2. I guess that must be the source of the problem.
P.S. I use a French interface, so the message I got is this:
P.P.S. Here is a screenshot of the error stack, from one of the ten instances of a similar problem I just encountered (I changed my computer and network data for security reasons):
And then the error window that appears when I try to refresh the file preview:
With the following error stack:
Paul,
Some update on the issue on my side.
I have been nagged more and more frequently, when saving a file or adding a new term within Studio. One time, I got a full hangout and had to kill Studio.
Any local projects, not one in particular.
I just closed Studio because I could not add a new term and started again and I could add the new term.
Hopefully a solution will be found.
Paul,
Some update on the issue on my side.
I have been nagged more and more frequently, when saving a file or adding a new term within Studio. One time, I got a full hangout and had to kill Studio.
Any local projects, not one in particular.
I just closed Studio because I could not add a new term and started again and I could add the new term.
Hopefully a solution will be found.
Hi all,
I'm having this issue too, with Studio 2021 Freelance and Windows 11.
It started after a Windows update this morning, and Multiterm isn't working properly either. I can't add terms, and term recognition mostly isn't working.
Fortunately, I can still save my work and I haven't had any crashes so far.
Paul I hope you can find a solution soon!
Could you go in your Windows Update history to see what was the number of that specific update? In my case, the problem started right after installation of update 22H2.
Louis LaBonté It's 22H2 as well.
There are two updates but they both have that code:
2022-11 Mise à jour cumulative pour Windows 11 Version 22H2 pour les systèmes x64 (KB5019980)
2022-11 Mise à jour cumulative pour .NET Framework 3.5 pour et 4.8.1 pour Windows 11, version 22H2 pour les systèmes x64 (KB5020622)
Are there any news regarding this issue? More and more Studio users are having this bug in our organization and it´s becoming worrisome and very frustrating. As indicated before, it would seem that the problem start after the forced install of the Windows update in their work computers.
The only suggested solution that has been offered by RWS is to try a checkdisk (chkdsk) on the computer, but we have not been able to try it yet due to an admin rights issue.
We have all kinds of issue variations:
Inability to create projects (have to try many times until it works)
Inability to generate the target (have to try many times until it works)
Getting an %2 error message when trying to save as target or generate a preview. It's very inconsistent. So to save your text as a Word file, you might have to hit "Save target as" multiple times until you don't get an error message.
Could somebody investigate or escalate the issue?
Thanks.
Additional update – I got this new one today, at the first step of project creation: 
However, in that case, I had no option to display more technical information or to save the “error stack”, as Paul called it.
I tried several times, since the “0x%1” error often solves itself within a few seconds, but to no avail... but it worked right after I closed MS Word (ever though it is a PowerPoint file); I closed it because I saw I had several processes of the software open, and I don't know if it's just a coincidence, but I guess that may be worth mentioning.
Translate
