Failed to verify document. Index out of range.

Gary Crabb over 8 years ago

Hi All, when I attempt to verify one document (in a package, original doc a PDF) in Studio 2015, I get this:

I've seen a similar thread but it does not appear to be the same problem. Any help much appreciated.

Gary

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Failed to verify document. Index out of range. Hi All, when I attempt to verify one document (in a package, original doc a PDF) in Studio 2015, I get this: https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/pastedimage1484046070283v1.png I've seen a similar thread but it does not appear to be the same problem. Any help much appreciated. Gary
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

0 Jesse Good over 8 years ago

Hi Gary,

Can you click on the floppy disk in the bottom-left corner to save the error details and post them here?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Gary Crabb over 8 years ago in reply to Jesse Good

<SDLErrorDetails time="1/10/2017 12:18:06 PM">
<ErrorMessage>Failed to verify document: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index</ErrorMessage>
<Exception>
<Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<ParamName>index</ParamName>
<HelpLink />
<Source>mscorlib</Source>
<HResult>-2146233086</HResult>
<StackTrace><![CDATA[ at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Sdl.FileTypeSupport.Native.Xml.XmlWriter.StartOfInput()
at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.StartOfInput()
at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallStartOfInput()
at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.SetFileProperties(IFileProperties fileInfo)
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.SetFileProperties(IFileProperties fileInfo)
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.SetFileProperties(IFileProperties fileInfo)
at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.SetFileProperties(IFileProperties fileInfo)
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.SetFileProperties(IFileProperties fileInfo)
at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkFileContainerField* field)
at FrameworkFileContainerField.vv_AcceptFrameworkVisitor(FrameworkFileContainerField* , FrameworkFieldVisitor* visitor)
at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_VisitStartEndField(TmfcReaderImpl* , StartEndField* startEnd)
at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.b_VisitNext(TmfcReaderImpl* )
at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReader.ParseNext()
at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
at Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.PerformNativeVerification()
at Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.Execute(IJobExecutionContext context)
at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
</Exception>
<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>12.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>12.2.5195.7</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 7 Home Premium </OperatingSystem>
<ServicePack>Service Pack 1</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>GaryCrabb-VAIO\Gary Crabb</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>GARYCRABB-VAIO</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>8302448 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jesse Good over 8 years ago in reply to Gary Crabb

Hi Gary,
Thanks for the details.
Is this a very large file?
Also, what happens when you try to save to target?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Gary Crabb over 8 years ago in reply to Jesse Good

Hi Jesse,
About 7,000 words. I've saved a return package without a problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jesse Good over 8 years ago in reply to Gary Crabb

Hi Gary,

Sorry, I meant generating the target translation from the sdxliff file, not the return package. My guess is you cannot generate the target file either.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Gary Crabb over 8 years ago in reply to Jesse Good

That's correct -- same error mssg as above when saving the target. I've had to delivery the job with a note about the problem. Where do you think the problem could lie?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 8 years ago in reply to Gary Crabb

Hi Gary,

I think the problem stems from handling of the original PDF. The solution may be to take the word file that is created when opening the PDF to create the project, tidy it up, and then translate the word file instead of the PDF. Unfortunately this probably means you'll need to go back to your client to get this. My guess is they have the same problem trying to save target so they should be accommodating.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jesse Good over 8 years ago in reply to Gary Crabb

Hi Gary,

Hard to say without seeing the sdlxliff file, but a file needed for generation is missing. If you open the sdlxliff file, I wonder if the internal file is stored inside or there is a path linking to it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Gary Crabb over 8 years ago in reply to Jesse Good

Hi Paul and Jesse,

Thanks for your thoughts. I'll check back with the client and try to find out whether they had any problems generating a target document and running a QA check.

Gary
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Ladislav Hlavatý over 8 years ago in reply to Paul

Unknown said:

I think the problem stems from handling of the original PDF. The solution may be to take the word file that is created when opening the PDF to create the project, tidy it up, and then translate the word file instead of the PDF...

Hi Paul,

I have the very same experience - PDF support is great, but it is much better to use Studio to pre-process PDF into Word, cancel original project, prepare DOCX generated by Studio and only than start new project in Studio - therefore I think an option within Studio to "clean" DOCX (converted from PDF) would make sense and would be very welcome - usually I see a lot of formatting issues, QA issues etc. if working "directly" on PDF, using this intermediate step helps a lot - may be another suggestion for development.

Regards,

Ladislav
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

0 Ladislav Hlavatý over 8 years ago in reply to Paul

Unknown said:

I think the problem stems from handling of the original PDF. The solution may be to take the word file that is created when opening the PDF to create the project, tidy it up, and then translate the word file instead of the PDF...

Hi Paul,

I have the very same experience - PDF support is great, but it is much better to use Studio to pre-process PDF into Word, cancel original project, prepare DOCX generated by Studio and only than start new project in Studio - therefore I think an option within Studio to "clean" DOCX (converted from PDF) would make sense and would be very welcome - usually I see a lot of formatting issues, QA issues etc. if working "directly" on PDF, using this intermediate step helps a lot - may be another suggestion for development.

Regards,

Ladislav
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

0 Paul over 8 years ago in reply to Ladislav Hlavatý

Hi Ladislav,

Seems a sensible suggestion. The other, smart way, the handle PDFs is using InFix which does a great job in the tests I have performed:

https://multifarious.filkin.com/2016/07/28/handling-pdfs-is-there-a-best-way/

I can tell you the developer of InFix has also created a Studio plugin to manage the workflow in a separate view. Should be on the appstore pretty soon.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Gary Crabb over 8 years ago in reply to Paul

To finish up for me here, I asked the client whether she was able to run a QA check on my delivered sdlxliff (in a package). Yes, after her IT dept. used a tool of some kind to divide the file into one or more parts. The QA check on the parts then worked and she could generate the target translation. Pretty unexciting, nothing learned. Topic finished as far as I'm concerned.

Regards
Gary
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Failed to verify document. Index out of range.