• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 192 subscribers
  • Views 2443 views
  • Users 0 members are here
Options
Related

The entry number does not exist in this termbase.

Daniel Hug

I am trying to batch edit a termbase and get the error "The entry number does not exist in this termbase." I just reorganized the termbase, it seems to be working fine in general.

  • What does this error mean for the general health of the termbase?
  • What information (multimedia files?) will I lose if I export to TMX or Excel and re-create the termbase?
  • Can I fix this problem in MultiTerm?

Here's the stacktrace:

Fullscreen sdlerror-2020221-13h57m2s.sdlerror.xml Download 
<SDLErrorDetails time="21-Feb-20 13:57:13">
  <ErrorMessage>The entry number does not exist in this termbase.</ErrorMessage>
  <Exception>
    <Type>System.Runtime.InteropServices.COMException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ErrorCode>-2147220940</ErrorCode>
    <HelpLink />
    <Source>MtTermbase</Source>
    <HResult>-2147220940</HResult>
    <StackTrace><![CDATA[   at Sdl.MultiTerm.TMO.Interop.EntryContentClass.get_Content()
   at Sdl.MultiTerm.Studio.Editor.Actions.Tasks.BatchAction.EditActions.Execute(Int32 entryID)
   at Sdl.MultiTerm.Studio.Editor.Actions.Tasks.BatchEditWizard.BatchEditJobRequest.Execute(IJobExecutionContext context)
   at Sdl.MultiTerm.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__46_0()
   at Sdl.MultiTerm.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   at Sdl.MultiTerm.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 MultiTerm</ProductName>
    <ProductVersion>MultiTerm15</ProductVersion>
    <EntryAssemblyFileVersion>15.0.5.56289</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>danielhug</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ABCD</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16776172 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Daniel
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I'm not sure what this means for the general health of the termbase... it might be a bug over the top and not a problem with the termbase at all.  We did see this in an earlier release and it was resolved by working with the flags layout instead of the default.  Can you try that?

    Unknown said:
    What information (multimedia files?) will I lose if I export to TMX or Excel and re-create the termbase?

    If you export to Excel, or maybe better MultiTerm XML/XDT, you won't lose multimedia files.  If you have created hyperlinks in the descriptions you will probably lose them unless you stick with MultiTerm XML/XDT.

    A good tool if you do a lot of this kind of stuff is Excelling MultiTerm on the appstore from Kaleidoscope.  It's not free, but it's an excellent tool to fixing issues and working with your termbases via Excel.

    Unknown said:
    Can I fix this problem in MultiTerm?

    Probably not unless it is an issue not affecting the database.  I'd recommend you take this one up with Support.

    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

  • 0 in reply to Paul

    Working with the flags layout did not help. I ended up exporting to MultiTerm XML, creating a new termbase with the onld one as a template and importing the entries. Everything seems to have been imported, including hyperlinks and multimedia objects (of which there are many) - only one recently created fitler definition is missing.

    The batch edit function is working for the new termbase, so that's fine. I still get the same term with the same ID displayed thrice in the Hitlist (only one specific term), but that does not seem to affect functionality.

    I don't have a support contract, and this does not look like an installation case...

    Daniel
Reply
  • 0 in reply to Paul

    Working with the flags layout did not help. I ended up exporting to MultiTerm XML, creating a new termbase with the onld one as a template and importing the entries. Everything seems to have been imported, including hyperlinks and multimedia objects (of which there are many) - only one recently created fitler definition is missing.

    The batch edit function is working for the new termbase, so that's fine. I still get the same term with the same ID displayed thrice in the Hitlist (only one specific term), but that does not seem to affect functionality.

    I don't have a support contract, and this does not look like an installation case...

    Daniel
Children