Studio 2017 keeps crashing since the last SR1 update without warning or error messages - I suspect a division by 0

Question

Studio 2017 keeps crashing since the last SR1 update without rhyme, reason, warning, or preceding error messages, which is seriously disrupting my workflow. I run Studio 2017 SR1 - 14.1.10014.38031 on Windows 7 with all the latest Windows, Java and .NET updates. Looking at the log files, I suspect a division by 0 in an internal process, because every single one of the log files ends like this: 
 WARN [2018-11-06 10:31:44,945] CommandBarExtensionRegistry - Command bar with path 'ProjectsView_ProjectsListViewPart_ContextMenu' does not exist within parent command bar 'window'. 
 WARN [2018-11-06 10:31:44,945] CommandBarExtensionRegistry - Command bar with path 'help' does not exist within parent command bar 'window'. 
 WARN [2018-11-06 10:31:44,945] CommandBarExtensionRegistry - RibbonTab '' does not exist in the current context (it is referred to by command bar item 'LanguageCloudAction'). 
 WARN [2018-11-06 10:31:44,945] CommandBarExtensionRegistry - Command bar with path 'TranslationStudio.File.NewMenu' does not exist within parent command bar 'TranslationStudio.HomeRibbon'. 
 INFO [2018-11-06 10:31:47,348] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - begin async initializing for document EP2466442 claims.docx.sdlxliff 
 INFO [2018-11-06 10:31:47,379] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - Begin the termbases initalization. The number of calls to the server = 0 
 ---- end log file, another log file below 
 INFO [2018-11-06 10:29:36,011] ActionService - Finish#Id=cf0c540d-6f82-4a7d-83b4-b197ee1e448c#Name=ConfirmAndMoveToNextUnconfirmedSegmentAction#ProcessName=SDLTradosStudio#PhysicalMemorySize=518541312#VirtualMemorySize=440311808#ThreadCount=64#HandleCount=2060#GdiHandleCount=1603#UserHandleCount=889#TotalProcessorTime=00:11:12.6763120 
 INFO [2018-11-06 10:29:36,744] Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseProvider - RecognitionComplete - the number of calls to the server = 0 
 ---- another random log file before the crash ends 
 WARN [2018-11-06 09:29:28,395] CommandBarExtensionRegistry - Command bar with path 'ProjectsView_ProjectsListViewPart_ContextMenu' does not exist within parent command bar 'window'. 
 WARN [2018-11-06 09:29:28,395] CommandBarExtensionRegistry - Command bar with path 'help' does not exist within parent command bar 'window'. WARN [2018-11-06 09:29:28,395] CommandBarExtensionRegistry - RibbonTab '' does not exist in the current context (it is referred to by command bar item 'LanguageCloudAction'). 
 WARN [2018-11-06 09:29:28,395] CommandBarExtensionRegistry - Command bar with path 'TranslationStudio.File.NewMenu' does not exist within parent command bar 'TranslationStudio.HomeRibbon'. 
 INFO [2018-11-06 09:29:30,096] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - begin async initializing for document EPA-119 239_Com_ 71(3) + 2056 + DREX claims.docx.sdlxliff 
 INFO [2018-11-06 09:29:30,096] Sdl.TranslationStudio.Editor.Terminology.ProjectTermbasesLoader - Begin the termbases initalization. The number of calls to the server = 0

Paul · Answer

Hi Carola F Berger 
 
I would carry out a reset. You could use this app for the reset and this will also explain what you will lose by carrying out a reset before you do it: 
 
 appstore.sdl.com/.../ 
 
But if you'd rather do this manually then rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio: 
 
c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0 
 
So the path would become this: 
 
c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0_old 
 
If you can't find this folder then you need to unhide your hidden files/folders: 
 
 www.howtogeek.com/.../

Paul · Answer

Hi Carola F Berger 
 Unknown said: There is clearly something wrong with the latest update, since I am by far not the only person with that very same problem, as evidenced by replies to a Facebook post. 
 People complaining on FB without aproaching SDL to find out where the problem is really coming from doesn't give us any evidence of anything I'm afraid. I have every sympathy with people having difficulties with the software but they really should make use of the appropriate channels to get them sorted so that the reasons for the issues are properly explained and documented. 
 There are plenty of users working with the latest SR1 update in 2017 and they don't have issues like this. There are many things that could be the cause of problems and they need to be investigated properly to be able to provide a proper solution for those circumstances.

Paul · Answer

Unknown said: And the reason people post on Facebook is because one usually receives an answer within minutes or hours, whereas "proper channel" forums such as this one here move at a glacial pace. 
 Perhaps not a glacial pace, but point taken. It's still the only place where you will get your posts seen by the product management team, development team, or other people who may be able to help when you don't get your problem solved on Facebook. I do see the FB pages and I think this forum also sees a lot more posts and most of the time, certainly weekdays, the questions are answered pretty fast.

Paul · Answer

Hi Evelyna Radoslavova

Perhaps, when it happens again, you can report it here and provide the following details:

1. version number of Studio (full number)
2. version number of Multiterm (full number)
3. List of plugins you have installed in Studio from the appstore
4. List of applications you have added to the navigation pane in the Studio welcome view
5. AV software used and confirmation that it is up to date and you have verified Studio is properly whitelisted
6. Details of the error that is thrown... not just the title.

Then we have a good start to try and figure out what may be happenning in your case.

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

Paul · Answer

Hi Evelyna Radoslavova 
 You said this: 
 Unknown said: 3. No new plugins installed between the time Studio was working fine and the time it started randomly crashing. There is nothing in the Add-Ins menu. 
 Do you have any apps that you have installed into Studio 2017 from the SDL AppStore or anywhere else at all? 
 Aside from that I think you need to upgrade MultiTerm. That could cause a problem for you because you should be running this version with the version of Studio have installed: 
 SDL MultiTerm 2017 SR1 - 14.2.6.23639 
 Please try that when you get a chance and see whether this improves things.

Trados Studio > 1. Trados Studio

Studio 2017 keeps crashing since the last SR1 update without warning or error messages - I suspect a division by 0