Myrelle de Miranda Pacheco 

Myrelle de Miranda Pacheco said:

Interestingly, if I hit "Complete review", it works... sometimes, not always. Can I cry now? 

I know that feeling... let's hope we can  get some relief!

This is a System.NullReferenceException that indicates an attempt to use an uninitialized (null) object took place. Or in other words, the software tried to use something that wasn't set up or ready, and this caused an error.

The error originates from this part:

Sdl.Verification.QAChecker.Processors.ProcessorRegEx.CheckRegEx(QASegmentPair currentSegmentPair)

This means that within the method CheckRegEx of the ProcessorRegEx class in the Sdl.Verification.QAChecker namespace, there's an attempt to reference an object that has not been initialized.  Or in other words, In a specific part of the software, called "CheckRegEx", Studio tried to use something that wasn't set up correctly, leading to a mistake.

So I think we can conclude that the method names suggest that this error occurred while the software was performing a QA check involving regular expressions (RegEx) on a segment pair. These QA checks can take place when you confirm a segment, so the first place I'd look would be the custom regex expressions in your verification settings.  Maybe back them up, then remove them all and see if that helps.

If you don't have any custom checks and we're being misled a little though not being developers ourselves, then try disabling the verification checks just to see if this helps?

Hi Paul , me again!

This problem happened to another project, different from the one, from the other question... but they might be kinda related, if I understood correctly. If you have something wrongly set up, or maybe not even set up, Trados throw an error. Being relatable to when we "confirm" segments, what I can see is that while confirming, Trados check the segment, to show to the translator if (s)he missed a word from the TB, if there's any grammar, any missing tag, any mistake, it will appear within the "Messages window" (where we see the QA messages). 

For this project specifically, I haven't tried anything, just did the revision and did "Complete Review" at the end. Then I went to check anything else later on Xbench. But if you want, I can try to "play" a bit with this project... I'll let you know in any case!

Thanks again

Myrelle

Myrelle de Miranda Pacheco 

Myrelle de Miranda Pacheco said:

if I understood correctly. If you have something wrongly set up, or maybe not even set up, Trados throw an error.

Sometimes... although this would still be a bug as the software should handle thee things more gracefully.

Myrelle de Miranda Pacheco said:

For this project specifically, I haven't tried anything, just did the revision and did "Complete Review" at the end.

Can you try disabling the verification checks?

Hi Paul ,

I have just reopened the project and in Project Settings > Verification > QA Checker 3.0 > Segments verification and disabled every item. It still throws an error about "Reference not set to an object..." however, when in Project Settings > Verification, there are three boxes and I disabled all of them. Then it worked! I could easily confirm the segments, in the revision mode of the project. Let me check one thing....

Hi Paul , me again.

Just to let you know that trying here: in Proj Settings > Verification, if I select "Tag verification" and "Terminology Verifier", I CAN confirm segments. Whenever I select "QA Checker 3.0", it thows me the error "Object reference not set to an instance of an object". BTW, clicking on "Confirm button"! If I hit Ctrl Enter, it crashes. 

With QA Checker 3.0 selected, I went through all the options, selecting one by one and clicking on "Confirm". All times, I had the same error. Just wanted to try this, it could be helpful to identify where the bug is specifically. Hope this can shine a light on where the bug is and how to kill it, hihihihi... 

Thanks for the patience,

Myrelle

Myrelle de Miranda Pacheco 

Excellent... thank you for your patience working through that.  So we have  workaround at least... disable QA checker 3.0.

Can you tell me if you have anything in here in the regular expressions section?

The error message sounded as though it was specific to this part so just checking.

Hi Paul , sorry for the delay in answering, I went for lunch. And now I'm back

In fact, RegEx!! So, in the Regular Expressions, there's a huge list! 

Should I export items?

Should I search for something specific here?

(Cool, huh?)

Myrelle de Miranda Pacheco 

Myrelle de Miranda Pacheco said:

(Cool, huh?)

Very!

Myrelle de Miranda Pacheco said:

In fact, RegEx!! So, in the Regular Expressions, there's a huge list! 

ok... create a new project with any file.  Then open the file for ranslation, press F8 and see what happens.  Do you still get the error?  If you do then in your project settings (do not do this in your File -> Options) for that new project delete all the rules, then open the file and press F8 again.  Do you still get the error?

Hi Paul 

Sorry for the delay in answering.

I have just done what you said: created a new project with a file .doc of mine, not from the project which had given me problems. Created a TB and a TM for it, but I have also used the TM from the previous project. Then, with the file open, pressed F8 and "Verification complete. No errors were reported". I can indeed confirm all segments, without any issue or delay. However, there are no rules set in "Regular Expressions", as I could see.  

There, in "Regular Expressions", I have added some of the rules you can find by pressing the triangle by "action" button side. Once selected those examples, I went back to the file, did all again, and the same "Verification complete" appeared. No, no errors popped up.

Could it be something with one of the rules set there in the troubled project, specifically? Just guessing

Myrelle de Miranda Pacheco 

Myrelle de Miranda Pacheco said:

Could it be something with one of the rules set there in the troubled project, specifically? Just guessing

It absolutely is. I wanted you to test with al your rules... so it seems as though you got those rules with a specific project?  At least one of them is causing this problem with your project.

If you have time, export the rules from that project and import them into the project you just tested that worked ok.  Then test again.

Hi Paul ,

Sorry for the delayed response. My projects had accumulated, and I'm in a rush to finish the ones that I have to deliver this week. But....

I received two different projects, from two different clients, with even two different language combinations; they thrown the same problem related to Verify Document. When Trados wouldn't just crash... I couldn't go through F8 without receiving an error.

Despite being able to get to the end of the last short project I've just done, without having to deactivate the three items in Verification, whenever I hit "Verify", it took a lot of time to load it all and, at the end, it threw an error related to issues in indexing. 

I'm working right now without using the Verify Document function, doing it elsewhere. For the project I'm dealing with right now, I'm using only the "Terminology verifier" activated, but every time I confirm a segment, it takes at least 10 to 15 seconds to go through and jump to the next.     

UPDATE: 45 minutes after I wrote this, here's the error, again. 

<ErrorMessage>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 Sdl.Verification.TermVerifier.TermVerifierProcessing.HasAnyForbiddenFields(ISegment target, Boolean found, ITermRecognitionHit hit, IEntryTerm term) at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckForbiddenTerms(ISegment target) at Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(ISegment source, ISegment target, Boolean sourceHasRevisions, Boolean targetHasRevisions) at Sdl.Verification.TermVerifier.TermVerifierMain.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.TranslationStudio.Editor.TranslationEditor.SingleParagraphUnitBilingualParser.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.TranslationEditor.SegmentVerifier.Verify(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode) at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.VerifySegment(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode) at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.VerifySegment() at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment() at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute() at Sdl.Desktop.Platform.Implementation.CommandBars.SimpleActionExecuter.Execute(ActionData actionData) at Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message) at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle) at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut) at Sdl.Platform.UI.StudioWindowForm.OnPreviewKeyDown(Keys keys) at Sdl.Platform.UI.GlobalKeysMessageFilter.PreFilterMessage(Message& m) at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified) at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Sdl.TranslationStudio.Application.Launcher.RunApplication() ]]>
</StackTrace>

Myrelle de Miranda Pacheco 

The error seems to be related to 'HasAnyForbiddenFields' so maybe turn off that part of the check for now.

Myrelle de Miranda Pacheco said:

but every time I confirm a segment, it takes at least 10 to 15 seconds to go through and jump to the next.     

Maybe turn off the interactive check and just run the terminology verification at the end.

Myrelle de Miranda Pacheco 

The error seems to be related to 'HasAnyForbiddenFields' so maybe turn off that part of the check for now.

Myrelle de Miranda Pacheco said:

but every time I confirm a segment, it takes at least 10 to 15 seconds to go through and jump to the next.     

Maybe turn off the interactive check and just run the terminology verification at the end.