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

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

10 Replies Latest Replies: 8 Nov 2018 5:54 AM by Paul < 1   2  >
  • Hi

    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/.../
  • In reply to Paul:

    Already did that, didn't help. Studio kept crashing all the time after a reset, a repair, and several other standard remedies. Thanks, though. It's definitely the latest update, which cannot be undone other than uninstalling everything and reinstalling.

    So, what did help was to uninstall the entire product suite and then reinstall the version I originally bought at the beginning of the year, and disabling all automatic updates. 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.

  • In reply to Carola F Berger:

    Hi  

    Carola F Berger
    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.

  • In reply to Paul:

    That's why I posted here. But aside from the reset/repair solution, nobody else has posted anything constructive. And there are tons of similar reports by users with the same setup on this SDL forum, all with no resolution other than to rever to a previous version or to upgrade to 2019 (which I do not want or need).
  • In reply to Carola F Berger:

    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.
< 1   2  >
Related