• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 12217 views
  • Users 0 members are here
Options
Related

Error Message: Value cannot be null. Parameter name: g

AnonymousUser

Hello everyone.

I'm getting this error message "Value cannot be null. Parameter name: g" when I try to prepare a specific docx for translation.

Does anyone know how to solve this?

Thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Jesse Good
    Hi, Jesse.
    I'm sorry for the late reply, but it was the first time a posted a question here and I didn't get any notification for your answer (by the way, how can I do that?).

    I'm using Trados 2015, so O tried the option you suggested, but unfortunately it didn't work.

    Here are the details of the error message:

    <SDLErrorDetails time="16/10/16 11:21:17">
    <ErrorMessage>O valor não pode ser nulo.
    Nome do parâmetro: g</ErrorMessage>
    <Exception>
    <Type>System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>g</ParamName>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[ em System.Guid..ctor(String g)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Services.IllustrationParserProcessorService.GetIndexPositions(IEnumerable`1 paragraphUnits)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Services.IllustrationParserProcessorService.ProcessIllustrationParagraphs()
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Services.IllustrationService.DisplayIllustrationProperties(IllustrationControlDataObject dataObject)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Consumers.Parser.IllustrationConsumer.Consume(Entity entity)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Routes.Parser.AlternateContentRoute.Handle(Entity entity)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Routes.Parser.WordDispatchRoute.Handle(Entity entity)
    em lambda_method(Closure , IMessage )
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Infrastructure.Dispatcher.Publish(IMessage message)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Services.ParserService.Publish(Entity parsedEntity)
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Services.ParserService.Parse()
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Core.Parser.DocumentParser.Parse()
    em Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word.Parser.DocxParser.ParseNext()
    em Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
    em Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
    em Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
    em Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile)
    em Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
    </Exception>
    <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>12.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>12.2.5195.7</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>2070</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>PAULAAMARAL7E8C\Paula</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>PAULAAMARAL7E8C</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>2883104 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>
  • 0 in reply to AnonymousUser
    Hi Paula,

    Sorry for the late reply.
    It appears that there are certain illustrations in the Word File causing the problem.

    Here are two things you could do:
    Workaround 1:
    1. Convert from docx to doc (2003 format) and try to read that into Trados.
    When the translation is finished, you could convert back to docx format.

    Workaround 2:
    Does the file have a lot of illustrations?
    To narrow down the problem you could do the following:
    1. Make a back-up copy of the Word File
    2. Try to delete half the document.
    For example, if the file is 50 pages long, delete pages 26 through 50.
    3. Try reading the file into Trados.
    4. If it works, you know the problem exists between pages 26 through 50.
    If it doesn't, try deleting pages 1 through 25 instead.
    5. By repeating the above process, you can narrow down which pages are causing the problem.
    * This is a very tedious task, but in the end you can track down the problem area.

    Also, feel free to post the file here or send me a private message with the file and I will gladly try to track down the problem for you.
  • 0 in reply to Jesse Good
    Hi, Jesse.
    Thanks for your help, but I had to manage to do it by copy/paste of the whole text, because I had a tight schedule. Fortunately, it wasn't a big document!
    If ever I get faced with that problem again (and I sure hope not!), I'll bear in mind what you have just suggested and give you some feedback.
    Thanks again.
    Kind regards from Lisbon,
    Paula