MultiTerm 2017 produces lots of errors

I am new to MultiTerm and I want to use it to import a bilingual Excel file into a termbase, but I am only running into errors so far.

It starts with creating the termbase. I select the bilingual glossary preset with two languages, Dutch and English (both the main languages, not specific localisations). At the end of the wizard, I get the following error: “De objectverwijzing is niet op een exemplaar van een object ingesteld.” (Object reference not set to an instance of an object). I have pasted the error log below:

<SDLErrorDetails time="22-3-2017 18:08:13">
  <ErrorMessage>De objectverwijzing is niet op een exemplaar van een object ingesteld.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.MultiTerm.Core.Common</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   bij Sdl.MultiTerm.Core.Common.DataContainers.TermbaseStatus..ctor(ITermbaseInfo info)
   bij Sdl.MultiTerm.Studio.Editor.TermbaseService.CreateTermbase(ITermbaseInfo info)
   bij Sdl.MultiTerm.Studio.Editor.Actions.TermbasesView.CreateTermbaseAction.Execute()
   bij Sdl.Desktop.Platform.Implementation.CommandBars.StaticAction.Execute()
   bij Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass3.<ExecuteAction>b__2()
   bij Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   bij Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   bij Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute()
   bij Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e)
   bij Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e)
   bij Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
   bij Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
   bij Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
   bij Infragistics.Win.UltraWinToolbars.ToolMenuItem.OnClick()
   bij Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.DoClickProcessing(MouseEventArgs e)
   bij Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.OnMouseUp(MouseEventArgs e)
   bij Infragistics.Win.TextUIElementBase.OnMouseUp(MouseEventArgs e)
   bij Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
   bij Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
   bij Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
   bij Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
   bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bij System.Windows.Forms.Control.WndProc(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL MultiTerm</ProductName>
    <ProductVersion>MultiTerm14</ProductVersion>
    <EntryAssemblyFileVersion>14.0.2165.2</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 7 Home Premium </OperatingSystem>
    <ServicePack>Service Pack 1</ServicePack>
    <OperatingSystemLanguage>1043</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>QWERTZ\Maurits</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>QWERTZ</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>6183084 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Next I use MultiTerm Convert to convert my bilingual Excel file. I set one column to Dutch and another to English, again using the main language and not a localisation. That works without errors, but when I import the .mtf.xml file into the term base, I get more errors, with the following log:

Import log information

General information:
Import definition name: Default import definition
Termbase name: Empires & Puzzles
Import file: D:\Vertaalwerk\***edited***_Termbase_NL 2e versie.mtf.xml
Import log file: D:\Vertaalwerk\***edited***_Termbase_NL 2e versie.mtf.log
Exclusion file:
Allow over-complete entries: false
Allow incomplete entries: true
Ignore sub-languages: true
Full reorganization: false

Import Options:
Import all entries: Add import entry as new

Original Entry Number    Action    Entry Number in Termbase
-1    Does not conform to the target termbase definition.
   Reason: Kan de uitvoertabel I_EN niet vinden.
   Source: MultiTerm140.Server.Termbase14.0

The last four lines are repeated a lot of times (probably one time for every entry). The reason translates to “Can't find output table I_EN.” The log file concludes with the following:

Total entries processed: 0
Total entries added: 0
Total entries merged: 0
Total entries omitted: 0
Total entries written to the output file: 0

Import process started: 22/03/2017 18:21:31
Import process ended: 22/03/2017 18:21:46

Can someone help me to get this working? An obvious possible explanation is a mismatch between the language versions, but I have taken extra care to use the main languages, and not a localisation.

  • I am not sure if it is related, but opening or selecting the termbase often leads to the following error:

    <SDLErrorDetails time="22-3-2017 18:55:31">
      <ErrorMessage>Er is een fout opgetreden tijdens het parseren van EntityName. Regel 1, positie 115.</ErrorMessage>
      <Exception>
        <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
        <LineNumber>1</LineNumber>
        <LinePosition>115</LinePosition>
        <SourceUri />
        <HelpLink />
        <Source>System.Xml</Source>
        <HResult>-2146232000</HResult>
        <StackTrace><![CDATA[   bij System.Xml.XmlTextReaderImpl.Throw(Exception e)
       bij System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
       bij System.Xml.XmlTextReaderImpl.ParseEntityName()
       bij System.Xml.XmlTextReaderImpl.ParseEntityReference()
       bij System.Xml.XmlTextReaderImpl.Read()
       bij System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
       bij System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
       bij System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
       bij System.Xml.XmlDocument.Load(XmlReader reader)
       bij System.Xml.XmlDocument.LoadXml(String xml)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.XsltHelper.TransformStatistics(String xml)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList.ShowTermbaseInfo(ITermbase termbase)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList.AddCatalogueItem(tCatalogueObjectType objectType, Object catalogueObject)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueList._CatalogueService_TypeSelected(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       bij Sdl.MultiTerm.Studio.Common.Interfaces.TypeSelectedHandler.Invoke(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       bij Sdl.MultiTerm.Studio.Catalogue.CatalogueService.SelectType(tCatalogueObjectType type, Object catalogueItem, TermbaseStatus termbase)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueTree.RefreshSelection(tCatalogueObjectType type)
       bij Sdl.MultiTerm.Studio.Catalogue.ViewParts.Controls.CatalogueTree.treeInventory_AfterSelect(Object sender, TreeViewEventArgs e)
       bij System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
       bij System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
       bij System.Windows.Forms.TreeView.WmNotify(Message& m)
       bij System.Windows.Forms.TreeView.WndProc(Message& m)
       bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
      </Exception>
      <Environment>
        <ProductName>SDL MultiTerm</ProductName>
        <ProductVersion>MultiTerm14</ProductVersion>
        <EntryAssemblyFileVersion>14.0.2165.2</EntryAssemblyFileVersion>
        <OperatingSystem>Microsoft Windows 7 Home Premium </OperatingSystem>
        <ServicePack>Service Pack 1</ServicePack>
        <OperatingSystemLanguage>1043</OperatingSystemLanguage>
        <CodePage>1252</CodePage>
        <LoggedOnUser>QWERTZ\Maurits</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>QWERTZ</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>6183084 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

    The error message translates to: “An error occurred while parsing EntityName. Row 1, position 115.”

  • I'm experiencing exactly the same error and need to import and use a TB right now! =S
    Please provide a solution ASAP, SDL. Thanks.
  • Import or convert? Have you tried using the Glossary Converter?

    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

  • Of course I did, I've done the process described by Maurits and I'm getting exactly the same errors as Maurits.
  • But he didn't use the Gkissary Converter. You should try it.

    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 

    ok... let's try and walk through what we know and provide a little more detail here.  I have to go on the detail from Maurits as Diana has not provided any, so apologies now if this isn't suitable or isn't taking into account how experienced you both are.

    Unknown said:
    I am new to MultiTerm and I want to use it to import a bilingual Excel file into a termbase

    My first question would be, based on the fact you used the template in MultiTerm to create a bilingual glossary, is do you really need that level of complexity?  The Bilingual template is not exactly simple and includes a lot of fields you may not ever need.  This brings me onto the next problem which relates to your Excel spreadsheet.  How complex is this and do you think it contains the same structure as the Bilingual glossary you created?  I think it would be helpful if you reviewed this article to understand why this is important:

    https://multifarious.filkin.com/2016/10/17/square-pegs-in-round-holes/

    Sometimes, especially if you only wish to convert a spreadsheet, it makes sense not to use the templates provided, and instead create the definition based on the contents of exactly what you are trying to convert.  In fact if you are just trying to convert a spreadsheet to a termbase and not import the spreadsheet into an existing termbase then it probably makes a lot more sense to use the Glossary Converter.  I am not talking about MultiTerm Convert here, I'm referring to the tool on the AppStore which allows you to drag and drop your spreadheet and have it converted directly to a termbase with little fuss.  This article may be useful if you are not familiar with this tool:

    https://multifarious.filkin.com/2015/12/09/feature-rich/

    Unknown said:
    but I am only running into errors so far.

    Please can you first make sure that you have these versions for Studio and Multiterm:

    SDL Trados Studio 2017 - 14.0.5821.4
    SDL MultiTerm 2017 - 14.0.2165.2

    If you do then perhaps try a reset of MultiTerm first.  

    You may have to do a Studio reset and it might help. 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\MultiTerm14

    If this doesn't help then I suggest you log a support case.  For licensing or installation issues that prevent you from working we have a route for all customers to get help. This can be achieved really quickly using this link:

    http://support.xl8.one

    Just fill in the form and submit it. Make sure your email address is entered correctly or nobody will be able to get back in touch with you.

    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