SDL Trados Studio 2017 error message when creating a project with .docx files : Object reference not set to an instance of an object!

Hi,

I am getting the error message "object reference not set to an instance of an object" whenever I try to create a project with certain .docx files (it does not happen with all .docx files).

Can anyone suggest a solution please?

<?xml version="1.0"?>
-<SDLErrorDetails time="19/10/2017 09:35:11">
<ErrorMessage>Riferimento a un oggetto non impostato su un'istanza di oggetto.</ErrorMessage>
-<Exception>
<Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<HelpLink/>
<Source>Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word_2</Source>
<HResult>-2147467261</HResult>
-<StackTrace>
-<![CDATA[ in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word.Services.ContextInformationService.ProcessContextAndStructureInformationForParagraphStyles(String name)
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word.Consumers.Parser.ContextInformation.ParagraphStylesContextInformationConsumer.Consume(Entity entity)
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word.Routes.Parser.ContextInformationRoute.Handle(Entity entity)
in lambda_method(Closure , IMessage )
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Infrastructure.Dispatcher.Publish(IMessage message)
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Services.ParserService.Publish(Entity parsedEntity)
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Services.ParserService.Parse()
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Parser.DocumentParser.Parse()
in Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word.Parser.DocxParser.ParseNext()
in Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
in Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
in Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
in Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile)
in Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]>
</StackTrace>
</Exception>
-<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>14.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>14.1.6329.7</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1040</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>DESKTOP-9AV9UIO\Jacques Friggieri</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>DESKTOP-9AV9UIO</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>12491632 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>

Parents
  • Hi  

    Thanks for sending in the file.  I have the same problems as you with all versions of Studio and all variants of the DOCX filetype.  We isolated the problem and have given the file to development to fix.  It's logged with this number for your future reference: LF-3631

    The file we gave to development contains only this so it is completely anonymised:

    What's in here causing the issue I'm not sure.  Removing these parts didn't help, but there is something in the underlying XML that the development team will resolve.  Until then you'll have to use your old workaround and hopefully a fix won't be too far away.

    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

Reply
  • Hi  

    Thanks for sending in the file.  I have the same problems as you with all versions of Studio and all variants of the DOCX filetype.  We isolated the problem and have given the file to development to fix.  It's logged with this number for your future reference: LF-3631

    The file we gave to development contains only this so it is completely anonymised:

    What's in here causing the issue I'm not sure.  Removing these parts didn't help, but there is something in the underlying XML that the development team will resolve.  Until then you'll have to use your old workaround and hopefully a fix won't be too far away.

    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

Children
No Data