Error " Object reference not set to an instance of an object" when trying to create a new termbase (MultiTerm 2015 SR2)

Hi, 

I am new to using this software and I would greatly appreciate your help. I am trying to create a new termbase in MultiTerm 2015 Desktop SR2.

I follow all the steps as indicated in the tutorials and after clicking the "Finish" tab I get the following message: "Object reference not set to an instance of an object". I am currently using Windows 10.

Any suggestions?

Thanks,

Marina

  • Hi Marina,

    The object reference error name is very generic and we would really need the full stack trace underneath it to be able to investigate this further.  So attaching the error stack as the xml file you get when you click here is helpful:

    You can add an image by replying with the rich formatting options here:

    However, I think it would be worth trying a reset first as this often cures errors like this that we may not be able resolve off the back of one error message anyway.  Rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart MultiTerm:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL MultiTerm\MultiTerm12

    Maybe this will resolve the problem for you.  But if not share the error stack and we can look at this again.

    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

  • Hi Paul,

    Thank you for the the prompt reply. Managed to solve the first issue, however I still have a few teething problems, I have attached the file as you suggested. Can you help me with this

    Thanks,

    Marina

    <SDLErrorDetails time="27/11/2016 13:48:18">
      <ErrorMessage>XSLT compile error.</ErrorMessage>
      <Exception>
        <Type>System.Xml.Xsl.XslLoadException, System.Data.SqlXml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
        <SourceUri />
        <LineNumber>165</LineNumber>
        <LinePosition>35</LinePosition>
        <HelpLink />
        <Source>System.Data.SqlXml</Source>
        <HResult>-2146231998</HResult>
        <StackTrace><![CDATA[   at System.Xml.Xsl.Xslt.XsltLoader.LoadStylesheet(XmlReader reader, Boolean include)
       at System.Xml.Xsl.Xslt.XsltLoader.Load(XmlReader reader)
       at System.Xml.Xsl.Xslt.XsltLoader.Load(Compiler compiler, Object stylesheet, XmlResolver xmlResolver)
       at System.Xml.Xsl.Xslt.Compiler.Compile(Object stylesheet, XmlResolver xmlResolver, QilExpression& qil)
       at System.Xml.Xsl.XslCompiledTransform.LoadInternal(Object stylesheet, XsltSettings settings, XmlResolver stylesheetResolver)
       at System.Xml.Xsl.XslCompiledTransform.Load(XmlReader stylesheet)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.XsltHelper.ApplyTransformation(String xml, String xslt)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList.ShowTermbaseInfo(ITermbase termbase)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList.AddCatalogueItem(tCatalogueObjectType objectType, Object catalogueObject)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList._CatalogueService_TypeSelected(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       at Sdl.MultiTerm.Studio.Common.Interfaces.TypeSelectedHandler.Invoke(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       at Sdl.MultiTerm.Studio.Catalogue.CatalogueService.SelectType(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueTree.RefreshSelection(tCatalogueObjectType type)
       at Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueTree.treeInventory_AfterSelect(Object sender, TreeViewEventArgs e)
       at System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
       at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
       at System.Windows.Forms.TreeView.WmNotify(Message& m)
       at System.Windows.Forms.TreeView.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
        <InnerException>
          <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
          <LineNumber>165</LineNumber>
          <LinePosition>35</LinePosition>
          <SourceUri />
          <HelpLink />
          <Source>System.Xml</Source>
          <HResult>-2146232000</HResult>
          <StackTrace><![CDATA[   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
       at System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)
       at System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(Int32 pos, String expectedToken1, String expectedToken2)
       at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
       at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
       at System.Xml.XmlTextReaderImpl.ParseAttributes()
       at System.Xml.XmlTextReaderImpl.ParseElement()
       at System.Xml.XmlTextReaderImpl.ParseElementContent()
       at System.Xml.XmlTextReaderImpl.Read()
       at System.Xml.XmlTextReader.Read()
       at System.Xml.Xsl.Xslt.XsltInput.ReadTextNodes()
       at System.Xml.Xsl.Xslt.XsltInput.ReadNextSibling()
       at System.Xml.Xsl.Xslt.XsltInput.MoveToFirstChild()
       at System.Xml.Xsl.Xslt.XsltLoader.LoadInstructions(List`1 content, InstructionFlags flags)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadLiteralResultElement(Boolean asStylesheet)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadInstructions(List`1 content, InstructionFlags flags)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadLiteralResultElement(Boolean asStylesheet)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadInstructions(List`1 content, InstructionFlags flags)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadLiteralResultElement(Boolean asStylesheet)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadInstructions(List`1 content, InstructionFlags flags)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadTemplate(NsDecl stylesheetNsList)
       at System.Xml.Xsl.Xslt.XsltLoader.LoadRealStylesheet()
       at System.Xml.Xsl.Xslt.XsltLoader.LoadDocument()
       at System.Xml.Xsl.Xslt.XsltLoader.LoadStylesheet(XmlReader reader, Boolean include)]]></StackTrace>
        </InnerException>
      </Exception>
      <Environment>
        <ProductName>SDL MultiTerm</ProductName>
        <ProductVersion>MultiTerm12</ProductVersion>
        <EntryAssemblyFileVersion>12.2.1629.0</EntryAssemblyFileVersion>
        <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
        <ServicePack>NULL</ServicePack>
        <OperatingSystemLanguage>1033</OperatingSystemLanguage>
        <CodePage>1252</CodePage>
        <LoggedOnUser>MARINA\Marina</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>MARINA</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>4102508 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

     

     

  • Hello Marina,

    If you solved the first problem is this the error stack you attached? Or are you still seeing this message as your "teething problems"? Can you explain what these problems are and when the message is appearing?

    Thanks

    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

  • Hi Paul,

    Sorry for not being clear enough.

    I have resolved the first problem ("Object reference not set to an instance of an object") by changing the folder (I presume the problem was the fact that User contains an "&", so now I am using a different folder).

    I am currently able to create a new termbase. Once created, I select Termbase Management and the Error I attached above appears (XSLT compile error).

    If I select File - Open termbase, I can see my newly created termbase there, but that's all. Whatever i press, the same Error message appears.

    I must be doing something wrong?

    Regards,
    Marina
  • Hi Marina,

    > I presume the problem was the fact that User contains an "&"

    I think this might be causing the second error also.
    Do you have any other paths using "&"? I suggest eliminating any use of "&" altogether.

    I hope that helps.

    Jesse
  • Hi Jesse,

    Thanks for your reply.

    From:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL MultiTerm\MultiTerm12, USERNAME – contains an “&” and cannot be changed. Trados and Multiterm are installed on this USERNAME containing an “&”.

    For the first problem, “object error”, the path was changed so the termbase is saved elsewhere. This change enables me to save a termbase without error.

    Now for the second problem – what do you suggest? Should I uninstall Multiterm and its components and install it from a different user? If I do this what happens with Trados? Will it work?

    Regards,

    Marina

  • Hi Marina,

    It is the same PC right? In that case, I think you can just login a different account and you should be able to use Multiterm.
    So no need to uninstall anything.
    (* I'm not 100% sure, but I think this is how it works)
  • Hi Marina,

    I guess you could try changing your username as described here:

    www.opentechguides.com/.../win10-change-account.html

    I'm reliably informed that most programs rely on Windows to give the path to special locations so they don't hardcode this, or add anything at install prevent you making a change. Maybe worth a try to avoid having to use different login names for different applications.

    Worse comes to worse you can put it back as it was (keep a record of the original!).

    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