Excel 2016 incompatible

Hello,

I downloaded Office Business 2016 and I'm having trouble uploading Excel files to Studio 2014. I read many threads saying that you need to download Studio 2015 in order to use Office 2016. However, Word 2016 is compatible as long as a change .docx into .doc. Why isn't Excel also compatible when I change the files from .xls and .xlsx? Any ideas as to what I'm doing wrong?

Thanks for your help.

Julia

Parents
  • Hi Julia,

    Re-saving the word files as doc. was simply a workaround and not meant as a long time solution.
    SDL resolved this compatibility issue with the release of Studio 2015 (which you have already seen in various other posts I believe).
    Therefore the only way to use fully use Office 2016 would be to upgrade to Studio 2017 (if you do not have 2015 in your account).
    SDL will not be releasing an Office 2016/Studio 2014 compatibility update as far as i'm aware, as official support for Studio 2014 will be retired at the end of June this year.

    Kr

    Steve

    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

  • Hi!

    I have bad news about Studio 2017. It stopped opening Excel 2016 files recently after a routine MS Office 365 upgrade. As far as I know SDL Studio does not like MS Office 365 and while originally it handled Excel 2016 files well, since August I have to save them first to XLS format to be able to work in Studio... Too bad.
    I also have Studio 2014 and 2015 on different machines and configurations they have the same issue... I use fully licensed legal SDL products for years.

    Arterm
  • Hi Paul!

    My joy did not last long. The trick with template folder deletion in SDL Studio 2017 worked only for less than a day. Now the issue returned and whenever I try to save XLSX target file I get the error "object reference not set to an instance of an object" just as before. This does not happen with legacy XLS format. To overcome this I save the XLSX as XLS and then translate in Studio 2017. If I delete the project templates folder it will solve the issue temporarily and I'll loose file format and TM settings in Studio. It is now obvious that this issue emerges when I change XLSX file format parsing settings in SDL Studio 2017. For instance instead of default row-by-row behavior I choose translation by columns... However the same settings do no harm to the legacy XLS handler, only to XSLSX...
  • Here is the stack trace for the error

     

    <SDLErrorDetails time="05.09.2017 9:37:41">
      <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>14.0.0.0</ProductVersion>
        <EntryAssemblyFileVersion>14.1.6284.6</EntryAssemblyFileVersion>
        <OperatingSystem>Майкрософт Windows 10 Домашняя для одного языка</OperatingSystem>
        <ServicePack>NULL</ServicePack>
        <OperatingSystemLanguage>1049</OperatingSystemLanguage>
        <CodePage>1251</CodePage>
        <LoggedOnUser>DUO11\info_000</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>DUO11</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>4070680 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

  • ISSUE FOUND:

    1) I have MS Office 2016 / 365 (click to run)
    2) SDL Studio converted XLSX files using legacy "Excel 2007 v 2.0.0.0" parser instead of the new "SpreadsheetML v. 1" parser even after deleting the "project templates" folder.

    Solution pending...
  • Solution found. I have changed priorities of the parsers and moved the "SpreadsheetML v. 1" filter up in the "File types" list. Now it takes priority over the legacy filter and Studio handles XLSX files again.

    Question 1: Can I disable Excel 2007 v 2.0.0.0 filter altogether?
    Question 2: How does SpreadsheetML v. 1 filter handle rows and columns order? In the legacy filter there is a setting to choose translation order, but not in the SpreadsheetML v. 1...

    Thank you

  • Unknown said:
    Question 1: Can I disable Excel 2007 v 2.0.0.0 filter altogether?

    This can only be achieved in your project templates.  Also make sure you do this in your Global Settings (File -> Options as opposed to Project Settings) so that new project templates you create based on new projects you have created are using your preferred setting by default.

    Unknown said:
    Question 2: How does SpreadsheetML v. 1 filter handle rows and columns order? In the legacy filter there is a setting to choose translation order, but not in the SpreadsheetML v. 1...

    Top left to bottom right, unless it's a Bi-Di language in which case it's top right to bottom left.

    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

  • My first question was actually: is it safe to disable Excel 2007 v 2.0.0.0 filter? I know how to disable it. But does it serve any purpose in presence of SpreadsheetML v. 1 filter?
  • Eventually it will supersede the old one, but until we are 100% confident we are not missing anything important we have left it there. You have already identified one possible advantage in being able to configure the parsing options... maybe there are others. We're hoping for feedback from our customers in the community and this may help shape the options for the new one and also determine when we decide to remove the old one altogether.

    Is it safe? It can't hurt and you won't break anything. But there is always the possibility you'll find an excel file that won't process in the new one but will in the old. We'll obviously fix the new one when we learn of these things... but good to have the backup of the older more seasoned version.

    Does that answer your question?

    Regards

    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

  • Hello ,

    I actually asked the filetype manager already if there were plans to add these in the new filetype and the answer was no. Can you tell me why you need them so I can share your views?

    Thank you

    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

Reply Children