• State Suggested Answer
  • Replies 18 replies
  • Answers 5 answers
  • Subscribers 434 subscribers
  • Views 9345 views
  • Users 0 members are here
Options
Related

Object reference not set to an instance of an object when exporting excel files

Sandra Iannotti

Dear all,

 

I am using a Pro license of Studio and all of a sudden, I can no longer export target files when the working format is Excel.

I have Windows 10 and the Office 2016 - Studio 2015. It was working fine for the last year and a half but now I am getting this error. When I received the update message, I thought it would solve the problem but it didn't.

Regarding the file type settings, I tried everything: moving settings up and down, ticking/unticking.

Only saving in xls does work SOMETIMES. Still, this is not an option for me as I use Studio as a PM and cannot waste all this time saving files in a different format.

Can someone please advise?

Ps. I am not sure this can be related but I first experienced the issue after I installed the Plug in "xliff convert". I deactivated it though.

Best regards,

Sandra
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Evzen Polenka
    I wouldn't be able to tell you what update message it was in detail. But the system asked me to update, switched off and restarted. My colleague had an update on his 2017 on the same day.
  • 0 in reply to Sandra Iannotti

    Hello Sandra,

    I think the updates you are referring to are quite possibly one of the multitude of Windows 10 updates in the last couple of weeks.

    If you could post the full error stack please, this may help us identify the issue easier.

     

    I notice that you mentioned you are working as PM and as I cannot find a license under your name, would I be correct in assuming you are working for a company as an internal translator/PM (using a Studio 2015 Pro)?

    If so, you may want to ensure you have ADMIN rights, then delete the previously installed app and reset Studio-

    A very easy way of resetting your Studio application, would be via the following (free) app on the SDL App store- SDL Freshstart

    https://appstore.sdl.com/language/app/sdl-freshstart/876/ (again- admin rights are required).

    Lydia Simplicio | 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 Lydia Simplicio

    Fullscreen sdlerror-2018420-16h41m28s.sdlerror.xml Download 
    <SDLErrorDetails time="20/04/2018 16:41:37">
  <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.FileTypeSupport.Filters.Excel</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.UpdateDocumentFile(XsltArgumentList argsList, XslCompiledTransform xslTransform, XPathNavigator child)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateXsltFiles(XsltArgumentList argsList, FileMap rule, XPathNodeIterator iter, Boolean isUpdate, String targetFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateContentType(String xslFileNamesPath, Boolean isUpdate, String filePath, String filterStr, String targetFilePath, Boolean isCalledByRelsTableIteration)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.serviceBackward()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentParser.Update()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentExtractImpl.Update(DocumentCollection srcCollection, String filename, String tgtFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.WriterImpl.EndOfInput()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.ExcelWriter.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallEndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnEndFile()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__2(ISdlXliffStreamContentHandler handler)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.ProjectApi.AutomaticTasks.NativeFileGenerator.GenerateFiles(ContentRestriction restriction, Boolean preview, Int32 filePercentBase, Int32 filePercentFactor)
   at Sdl.ProjectApi.AutomaticTasks.GenerateTargetTranslation.GenerateTargetTranslationTask.ProcessFile(IExecutingTaskFile executingTaskFile)
   at Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>12.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>12.3.5281.10</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>2057</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>BLOCKS\Sandra</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>BLOCKS</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8217732 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
  • 0 in reply to Sandra Iannotti
    Hi Steven,

    I cannot say if it was a Windows update but I remember Trados restarting due to this update message. Anyway, it doesn't matter if we find a solution :)
    My license was indeed purchased by my company. If I use this Freshstart app, will all my settings go lost? That is the reason why I would prefer not to uninstall Studio.
    Thanks,
    Sandra
  • 0 in reply to Sandra Iannotti

    Hi there, I'm actually having exactly the same issue as Sandra:

    I'm using SDL Trados Studio 2015 on a Mac (osSierra 10.12.6) with Parallels Version 11.2.3 (32663) and Windows 10, MS Excel Version 11.2.3 (32663).

    For a few days now, Studio won't save any target file when it comes to translating MS Excel files. I always get the error message "Zieltext konnte nicht gespeichert werden. Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." (Target text could not be saved. The object reference has not been set to an object instance).

    As a matter of fact I cannot translate any Excel files anymore. Maybe this is down to some recent update of Office not being compliant with Studio? My computer says I have the latest versions of Studio and MS Excel...

    Does anyone have a solution to this issue? It is pretty annoying, since I'm blocked for Excel for no clear reason.

    Update: I've run SDL FreshStart as suggested above, however, it still won't save my target XLS file...

    Thank you
  • 0 in reply to Katrin Wedding

    Hi   

    If you are having problems saving the target file from an existing SDLXLIFF already translated then the problem could be related to the corruption of the temp files used by Studio when you are working.  This can be caused by antiv-virus software, or clean up tools for example.  The way to check this is as follows:

    1. Open the original source excel file for translation as a new project and immediately try to save the target.  If it works then the problem I mentioned is most likely the issue
    2. If it doesn't work then the problem may be with Studio not being able to handle the Excel properly and this could be because of a problem with the Excel file, or because of a bug in Studio.  You can try splitting the source file and handle it in parts until you find the problem part, or try saving the Excel in a different version.  So XLS as XLSX for example.

    If you followed this and at 1. the file worked then your resolution is this:

    1. Create a project with the source Excel file
    2. Perfect Match against the previous translation (if you have Professional), and if this fails, or you have the Freelance version then create a new TM and import the previously translated SDLXLIFF into it.  Pre-translate your project and save the file

    See if any of this helps?  If not can you send me your original source Excel file and your translated SDLXLIFF?  If that's oj email them to pfilkin@sdl.com

    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
    Hi Paul,

    I have tried FreshStart too and didn't solve the issue.

    I am going to send you an email because I had already tried everything you suggested. In my case the target file doesn't save at all, not even before we translate.
    It does work with xls files.

    Best,
    Sandra
  • 0 in reply to Sandra Iannotti

    Hello @Sandra Iannotti,

    Thanks for the error message. This most certainly confirms there is a problem with Excel somewhere along the line.

    Are you able to work with Excel files outside of Studio without any issues? If not- then i would try repairing the office installation.

    When repairing or resetting Studio, you basically have three options (and should start with option 1)

     

    Using the Freshstart app will allow you to reset/repair- but should this not help you can restore the settings as they were- nothing lost.

    (No need to uninstall/reinstall).

    Please back up your settings/templates anyway (best practise), beforehand as then you can re-import these once everything is fixed.

    Lydia Simplicio | 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 Lydia Simplicio
    Hi Steven, no error in Excel at all. I can use it normally.
    While running Freshstart I deselected the folder containing the custom settings and clicked "Repair studio"
  • 0 in reply to Sandra Iannotti
    Hi ,

    Thanks for sending me the files. This is what I did:

    1. Open the source Excel in Studio using the new Excel filetype and not the older one you have used
    2. Perfect matched the file from your sdlxliff (everything was translated)
    3. Saved target

    I sent you the target file.

    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