• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 2174 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No words counted in Studio although there are 40,000 in a package: Argument 0 is out of range

Renate Dockhorn

When opening a package in Studio we are currently facing the problem that no words are counted in a package although there are 40000 in it.

Trados Studio screenshot showing word count statistics with 'Dateien' at 2, 'Gesamtzahl der Woerter' at 0, 'Nicht uebersetzte Woerter' at 0, and 'Nicht ueberpruefte Woerter' at 0.

Whenever this error occurs, we can translate the files and save the TUs in the TMs, but cannot save the changes to the XLIFF which is very annoying. Does anybody have an idea? Please find the error message below.

Thank you very much for your attention and best regards - Renate Dockhorn

Error message in Trados Studio stating 'Argument '0' is out of range. It should be between 1 and 2147483647. Parametername: ChildFileDocuments.Count' with an 'OK' button.

Generated Image Alt-Text
[edited by: Trados AI at 8:10 PM (GMT 0) on 28 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Paul Filkin

    Yes, of course - here it is.

    Fullscreen sdlerror-202028-12h25m44s.sdlerror.sdlerror.xml Download 
    <SDLErrorDetails time="08.02.2020 12:26:30">
  <ErrorMessage>Argument '0' is out of range. It should be between 1 and 2147483647.
Parametername: ChildFileDocuments.Count</ErrorMessage>
  <Exception>
    <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>ChildFileDocuments.Count</ParamName>
    <HelpLink />
    <Source>Sdl.Desktop.Platform</Source>
    <HResult>-2146233086</HResult>
    <StackTrace><![CDATA[   bei Sdl.Desktop.Platform.Validation.WithinRange(Int32 argument, Int32 lowerBound, Int32 upperBound, String name)
   bei Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.SaveChildFilesDocuments()
   bei Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.SaveChildFiles(String outputFile, String[] bilingualFilePaths)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String[] bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Save(IJobExecutionContext context)
   bei Sdl.TranslationStudio.Api.Editor.SaveJobRequest.Execute(IJobExecutionContext context)
   bei Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__47_0()
   bei Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   bei Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.5.2145</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Admin-PC\Admin</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ADMIN-PC</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>33518228 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
  • 0 in reply to Renate Dockhorn

    Thanks

    I think this is due to the project being created with physically merged files.  You might have to go back to your customer and ask them to create the project without physically merging the sdlxliff files first.  There is an open bug for this, CRQ-5898.  Currently it refers to Studio 217 but I'll add 2019 to the ticket and refer to this thread.

    In the meantime you might be able to handle the project by unzipping the package and dealing with the sdlxliff files inside separately.  You can send the translated files back to your client and they can manually replace the ones in their project with your translated version.

    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
  • 0 in reply to Renate Dockhorn

    Thanks

    I think this is due to the project being created with physically merged files.  You might have to go back to your customer and ask them to create the project without physically merging the sdlxliff files first.  There is an open bug for this, CRQ-5898.  Currently it refers to Studio 217 but I'll add 2019 to the ticket and refer to this thread.

    In the meantime you might be able to handle the project by unzipping the package and dealing with the sdlxliff files inside separately.  You can send the translated files back to your client and they can manually replace the ones in their project with your translated version.

    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