• State Suggested Answer
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 432 subscribers
  • Views 10283 views
  • Users 0 members are here
Options
Related

Studio 2017 error "object reference not set to an instance of an object" for all Word files

Anna Schuster

I am getting the error message "object reference not set to an instance of an object" whenever I try to open ANY files from MS Word (2010), including those I previously translated in Studio 2015, as "translate single file" in Studio 2017. I read all related messages on this forum, and none of the solutions seem to help. It is NOT an antivirus problem, sorry. I also ran a repair on Studio 2017 with no results.  Word is still the most used program for my source and target files, so this is very upsetting. Please help, thank you.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul

    Here it is Paul:

    Fullscreen sdlerror-20161214-16h28m24s.sdlerror.xml Download 
    <SDLErrorDetails time="12/14/2016 4:28:29 PM">
  <ErrorMessage>Object reference not set to an instance of an object.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.ProjectApi.Helpers</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.ProjectApi.Helpers.LanguageDirectionHelper.GetCascadeSettings(ILanguageDirection languageDirection)
   at Sdl.ProjectApi.Helpers.LanguageDirectionHelper.CreateCascade(ILanguageDirection languageDirection, ProjectCascadeEntryDataFilterFunction filter, IComparer`1 sort, Boolean readOnly, Boolean refreshCache)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocumentConfirmationStatistics..ctor(TranslatableDocument document, IMultiFileConverter converter)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Load(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Services.JobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
   at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.0.5746.0</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Norwood\Norwood11</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>NORWOOD</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8289384 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
  • 0 in reply to Anna Schuster

    Hi Anna,

    This looks like a problem that has been fixed in CU01 for Studio 2017. You are still running the original Studio 2017. Please run the automatic update for Studio and Multiterm. You should have these versions:

    SDL Trados Studio 2017 - 14.0.5760.1
    SDL MultiTerm 2017 - 14.0.2103.1

    This update was released today.

    Regards

    Paul

    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

  • 0 in reply to Anna Schuster
    Actually, it worked after the update yesterday (hesitantly) but today it is the same story. Same error message, no Word file would open. I have to convert everything to RTF :(
  • 0 in reply to Anna Schuster
    Hi Anna,

    This sounds like you have an installation issue. Please log a case so a support engineer can look at this for you. This can be achieved really quickly using this link:

    http://support.xl8.one

    Just fill in the form, explain that after upgrading to the latest update you are unable to process your docx files, and submit it. Make sure your email address is entered correctly or nobody will be able to get back in touch with you.

    Regards

    Paul

    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

  • 0 in reply to Paul
    Thank you Paul - in the meantime, I deleted the Trados Project file in Documents, and it looks like it helped and it is working now. It did work after I installed Studio 2017, so I wonder if the issues could be caused by all those unpredictable, endless updates in Windows 10. I will turn off automatic updates at least for Office for now, and we'll see how it goes. Thank you for all your help and patience.