Trados crashes without message after update to 2019 S1

Question

Today I used Trados 2019 S1 after installing the update yesterday. After working about 1 hour I wanted to add a word to the Microsoft spell check via Trados but Trados closed without any message - just disppeared. After I started it again all my work was lost. I was not asked whether I want to open a newer version - it simply did not exist. I verified the problems a while (after creating a TM in case that happens again) but until now the directory ..\OneDrive\Document\Studio 2019\Autosave stays empty. Just to avoid misunderstanding; Atosave was always checked and I even changed it from 10 to 5 minutes and it always worked before this new Servicepack 1. 
 Meanwhile I have removed any protection from the onedrive dirctory and subdirectory and even shared it to prevent further bad experience. 
 Also when I started Trados 2019 S1 after the crash the Deepl Plugin was closed as "unknown plugin" and I also received a failure message of a memory error. But this computer is just a couple of month old and has 16 Giga Ram and SSDs (M2 and a 1 Terra Samsung SSD). 
 After starting Trados and Windows again all seems to work now (execpt autosave but Deepl.) 
 I am a bit afraid to experience the next Trados crash. 
 By the way I did a RAM check without any negative result. I have disabled Onedrive in Windows 10 Pro as well. 
 Any idea how to solve solve this problem or any bad experience with this new Servicepack? 
 Thank you 
 Peter

Paul Filkin · Answer

Hi Peter Peters 
 
There seems to be a lot of potential problems here so I think you should log a support case so an engineer can look at this installation issue. This can be achieved really quickly using this link: 
 
 gateway.sdl.com/liveagentlicensing 
 
You have two options: 
 
1. Submit a case using a webform 
2. Use live chat to get a licence reset 
 
You want to use the first option and make sure that you refer to this thread so the teams can see what you have tried already. 
 
Regards 
 
Paul

Alison Field · Answer

To all of you who have reported the same as Peter... because this has happened since you installed the latest version, you should follow the instructions given by Paul Filkin earlier in this thread: 
 There seems to be a lot of potential problems here so I think you should log a support case so an engineer can look at this installation issue. This can be achieved really quickly using this link: gateway.sdl.com/liveagentlicensing You have two options: 1. Submit a case using a webform 2. Use live chat to get a licence reset You want to use the first option and make sure that you refer to this thread. 
 Select 'installation' at the Case Type dropdown memory and be sure to give your correct email address so the teams can reply to you. 
 It will be helpful to the teams if they can find a common denominator that is causing this. Everyone's setup and environment is different so the more information the help team get, the more likely they will refer this to the development team so it can be resolved in a new update. 
 All the best, 
 Alison

Alireza Nadry · Answer

I finally found the solution :) 
 After a lot of actions, such as installing/uninstalling different versions, disabling/enabling various features (e.g. MS Word Spelling/Hunspell), I found that it relates to Translation Memory. You just need to disable upLIFT fragment recall , and voila, It works like a charm. 
 This problem has nothing to do with SR1 update or even the Trados version (it happens on 2017 version as well). I think it happens in complex files, such as Script files.

Alison Field · Answer

Peter Peters would you mark Alireza Nadry 's answer as correct, so future users can see it. 
 Alireza Nadry , this is excellent. 
 As most of my work involves reviewing translations, I have the fragment recall/repair functionality turned off as follows: 
 File>Options: 
 
 and... 
 
 Project Settings: 
 
 and 
 
 It is worth noting that Project Settings always overrule the profile settings made via File>Options. 
 All the best, 
 Alison

Alison Field · Answer

Hi Thomas Langer 
 That's useful to know, thank you. I've been compiling a list of settings to change, that can help if Studio is running too slowly and/or crashing. I will add this item also. 
 Put simply... if you want Studio to run as smoothly as possible then turn off any feature/functionality that you don't need beyond the basic settings. Also, make sure it is up to date and that MultiTerm is also up to date. 
 All the best, 
 Ali

Trados Studio > 1. Trados Studio

Trados crashes without message after update to 2019 S1