You are currently working on UAT 

  • State Verified Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 429 subscribers
  • Views 5418 views
  • Users 0 members are here
Options
Related

Error message "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." when confirming segments in Studio 2019

Marco Petz

Hello,

 

I just installed Studio 2019 and now I get the error "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt." when I try to confirm segments. The same happens when I try to verify the translation, and the error information points to the QAChecker. However, if I uncheck all verification options, I still can't confirm the segments and get the same error message.

The application is fully updated and I tried a Repair Installation and several other workarounds I found in this forum. Nothing seems to work.

This is the error report:

Fullscreen sdlerror-20181125-19h52m3s.sdlerror.xml Download 
<SDLErrorDetails time="25.11.2018 19:52:12">
  <ErrorMessage>Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.Verification.QAChecker</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   bei Sdl.Verification.QAChecker.Processors.ProcessorRegEx.CheckRegEx(QASegmentPair currentSegmentPair)
   bei Sdl.Verification.QAChecker.Processors.ProcessorRegEx.Process(ISettingsBundle settingsBundle, QASegmentPair currentPair)
   bei Sdl.Verification.QAChecker.QACheckerProcessing.Verify(QASegmentPair currentPair)
   bei Sdl.Verification.QAChecker.QACheckerMain.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SingleParagraphUnitBilingualParser.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   bei Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.VerifySegment(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.VerifySegment()
   bei Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment()
   bei Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute()
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
   bei Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
   bei Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
   bei System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   bei System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   bei System.Windows.Forms.Control.WmKeyChar(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.0.1.36320</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 8.1 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>PETZ-PC\Marco Petz</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>PETZ-PC</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16657604 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Does anybody have an idea?

Thank you all!

Marco
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello ,

    Could you clarify whether you are working on a single file translation or a project please?
    And whether you are using a template and/or Termbase or not-
    If you are using Termbase- If you remove the Termbase, are you now able to verify the file?

    Oana Nagy | QA Engineer | RWS Group

  • 0 in reply to Oana Nagy

    Hello Steven,

    thank you for your quick reply! Your answer made me think, so I tried something else. So far, I have opened three different projects in Studio 2019:

    1. Groupshare project with TMs and Termbases: The error message keeps coming, and I am not allowed to remove TMs/Termbases.

    2. Single file project (xliff file - Right click - Translate with SDL Trados Studio) without any TMs/Termbases: It works! When I add TMs and Termbases afterwards, there is no problem at all.

    3. Single file project with selecting TMs during project creation: The error message appears. When I remove the TMs, the error message disappeares and everything is fine. When I add TMs/Termbases afterwards, still everything is fine.

    To me, it looks like the problem is related to TMs when they are integrated during project creation. I could avoid that and add TMs/Termbases afterwards, but I still can't work on my Groupshare project that was created by the Client, since I do not have the rights to remove/add TMs and Termbases.

    Does that make things a bit clearer?

    Thanks!

    Marco
Reply
  • 0 in reply to Oana Nagy

    Hello Steven,

    thank you for your quick reply! Your answer made me think, so I tried something else. So far, I have opened three different projects in Studio 2019:

    1. Groupshare project with TMs and Termbases: The error message keeps coming, and I am not allowed to remove TMs/Termbases.

    2. Single file project (xliff file - Right click - Translate with SDL Trados Studio) without any TMs/Termbases: It works! When I add TMs and Termbases afterwards, there is no problem at all.

    3. Single file project with selecting TMs during project creation: The error message appears. When I remove the TMs, the error message disappeares and everything is fine. When I add TMs/Termbases afterwards, still everything is fine.

    To me, it looks like the problem is related to TMs when they are integrated during project creation. I could avoid that and add TMs/Termbases afterwards, but I still can't work on my Groupshare project that was created by the Client, since I do not have the rights to remove/add TMs and Termbases.

    Does that make things a bit clearer?

    Thanks!

    Marco
Children
  • 0 in reply to Marco Petz

    Hello

    Thanks for the clarification- this helps us move one step closer to finding the actual cause.

    As the issue is arising with both GS projects, and when you create your own projects- ...But NOT when you use the single file translation option, I would be inclined to think maybe the issue is stemming from the use if an incorrect (maybe from a previous Studio version?)'project template'. 

    Could you maybe create a new test project and ensure that the default template is being used please.

    Trados Studio screenshot showing the 'Create a New Project' window with 'Use Settings from' dropdown menu open, highlighting 'Default (Default project template for new users)' option.

     

    Now in regards to the GS issue, this I think is something else (that needs investigating) as you will receive a package (with template etc) and access the clients TB's/TM's online rather than locally on your machine so i find it hard to make a connection at this time between local and GS projects,

    Oana Nagy | QA Engineer | RWS Group

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:43 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Oana Nagy

    Hello Steven,

    I guess you have found the problem. I created a test project as you said, and a different project template (an old one?) was set as default. So I used the one you mentioned, and verification worked fine.

    So this problem is solved.

    Regarding the Groupshare project, I will have to work on it without verification (I finally found the button to turn off verification for manual confirmation) and see if the problem persists with upcoming projects. At least I can work again fluently and go ahead with my projects.

    So thank you very much for your help! I expected to struggle with this problem for a couple of days at least - but no, you solved in a few hours.

    I am much obliged!

    Marco