I have received a response saying they can only help me with installation and license. I think this is part of the installation, but not sure. The fact remain that there is some kind of bug/defect with the product that I just installed and need to get it fixed so I can use the product I purchased. Still hoping that someone find a solution.

I am having the same issue and I have installed Freshstart at the suggestion of your tech people at the ATA Conference last week. However, it did NOT fix the issue. I am hoping to get help from the installation people since this is been going on just since I installed 2019. I went back to using 2017 because it was extremely slow and cumbersome to work with 2019 with this error message popping up every minute.

Since I am not the only one with this issue, has anyone figured out the way to fix this once and for all?

Hi Chantal Keable Keene

Can you share the full error message for us?  Click on the smalll disk symbol and save the error stack to your desktop, then just attach the file to this thread:

It would also be useful to know what you are doing when this happens, and also that you have installed the very latest version of Studio 2019 and MultiTerm:

SDL Trados Studio 2019 SR2 - 15.2.4.1693

SDL MultiTerm 2019 - 15.0.4.56053

Hi Chantal Keable Keene,

I asked one of our developers to have a look at your stack trace and we are thinking the problem must have been caused by a specific font you might have used in Editor. Do you recall changing the font under Options-> Editor-> Font adaptation? We suspect you might have used a special font installed locally on your machine.

To solve this, you could try to reset to defaults. Under the path mentioned above Options-> Editor-> Font adaptation, select Reset to defaults and then OK, close and reopen Studio and let us know if it worked.

Thank you,

Maria

No, I don't recall installing and/or changing the fonts at all.  But, I will reset those settings to default, just in case. Trying to cover all the bases.

I also did install the newer version (15.2.4.1693) this weekend, but I have not used it yet because I only want to use it for a small project in case the error comes back. As soon as I get a small project, I will give it a try and hope that all is fixed.

Thank you for following up. I will keep you posted in the next couple of days.

I am using Studio 2017. I frequenly got this error message in my current translation too. In the beginning I could solve it as you: save, close and re-open the document. But the problem re-occured later and at some point it was impossible to go on with the translation, because the error message immediately came up again as I re-opened the document and tried to type the same word again. My solution was to turn off the AutoSuggest Dictionary (which I have generated  from a very large TM). Did you use an AutoSuggest Dictionary? I tried several times to turn on and off the AutoSuggest Dictionary and the problem re-occured only with the AutoSuggest Dictionary turned on, so I am pretty sure this is causing the problem.

Update: the problem continues, so it wasn´t the solution anyway

Hey Gyus, just read and followed the suggestions solving this problem with Studio 2019 SR02 and Windows 2010 (both up to date automatically) mentioned above and would like to share my resume/solution to it with you (apparantly this is not going to work for all of us):

1: renaming the folder: no change. Error message displays from time to time, might be related to hitting some particular key-combos, but since I type a lot I couldn't figure it out. Fortunately recent changes to the doc are saved!

2. installing and running "Fresh SDL-App": Studio showed the "Wrong Parameter"-Message by hitting the first key, so it got even worse!!! Besides it took forever to start up Windows 2010 and Studio 2019. Don't even know if the App was actaully working correctly.It was just displaying the name of the folders of Studio 2019 and the Multiterm. Deinstalled instantly.

3. Actually the problem occured since I installed the Q&A Setting-App and the Multiterm-App (as requested by the client). I had similar experiences with installing the Grammar- and Number-Checker-Apps (Studio just freezes, my CPU is running at max., just have to shut down Studio using the task manager): Deinstalling these Apps solved my problems for now (just crossing fingers), though I don't understand why they won't like to work properly???

How I handled this: I received an Excel-file of the latest Multiterm-Changes for my Languange-Pair and I am applying the QA-Check at the very end of the project with the Q&A-App-Setting (just in case I missed sth during the translation, but we all know which Q&A-Problems might occur, so I am confidently working on the doc w/o the clients settings :o))

>Resume: If not absolutely necessary (and actually as a freelancer I don't really need the Apps and Multiterm I mentioned here as there are workarounds, not as convenient as the Apps might be, but at least less stressfull and annoying as when the Apps don't work) just deinstall additonal apps and the Multiterm and run Studio 2019 as per your license (in my case the Freelancer-Version). Any addition seems to cause several problems like the one discussed here and elsewhere (errore messages and freezing). Its a pitty but thats my experience in the past year with Studio 2019 and I wasted a lot of time following troubleshootings that did not solve the problem at all. Honestly I am not a Crack in running my PC and I don't want to be. Just seeking to get my job done as smoothly as possible: w/o interferring Apps it seems to work :o)

Happy translating and all the best to all of you :0)

Note: I am not saying that the apps and Multiterm are bad guys, they just don't work for me and seem to be the cause of my troubles, as the problems occured after installing and disappeared, as soon as I deinstalled them! Why, I cannot say!

Hi Nicole Beate Kampik Kijewski

Were you keeping MultiTerm up to date as well as Studio? If not, that could cause you problems.

All the best,

Ali

Hi Ali,

thanks for your reply. Yes I am (was) up to date with Studio 2019 SR2 15.2.5.2145 and MultiTerm 2019 15.0.5.56289.

Yesterday I was trying the troubleshooting Maria Sarau was recently suggesting to Chantal in this thread, since I have been working on a different project w/o getting this dubious error message. Proofing that at least in my case the problem must be File/Project related.

So I was resetting the Font (in the Editor-Option) to default settings and I was able to work on the files w/o problems, firstly w/o MultiTerm 2019, than later I dared to reinstall MultiTerm 2019 again and guess what: it is still working just fine, yeaaah.

I am more than happy now, as you can imagine ;O)

Many many thanks to all of you, who suggested and shared solutions!

You're just awesome ;O)

Best wishes,

Nicole

Hi Nicole Beate Kampik Kijewski 

I'm so glad to read that all is working well for you now!

All the best,

Ali