• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 7 replies
  • Subscribers 182 subscribers
  • Views 2044 views
  • Users 0 members are here
Options

Glossary Converter Issues

Sameh Elsharkawy

The best OpenXchange application in my opinion and really deserves the Academy Award (Oscar) if there is one in the terminology management industry. Only two things:
1. With files that have over 45 K entries, we get an error, and no matter how we increase the MaxLocksPerFile value, it does not work.
2. The alternative of using xdt and xml works, though it is an old painful process.
3. The problem is in the new version of the Glossary Converter App this XDT and XML feature has been removed, and that is indeed sad!
I hope Gerhard manages to fix all of the above soon.

All the best.
Sameh Ragab

Changed to a question
[edited by: Paul at 3:44 PM (GMT 0) on 15 Mar 2022]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • +1

    Sameh Elsharkawy said:
    3. The problem is in the new version of the Glossary Converter App this XDT and XML feature has been removed, and that is indeed sad!

    Where has it been removed?  Are you sure that you, like many others I have seen, have just not understood how this version works?  Here you can see, in the latest version, I still have all the options.  The new UI gives me the ability to create multiple "profiles" for the conversion if I wish.  But all options are still there... including SDL Translation Memory which many users contact me about to tell me I'm wrong and it's not there anymore!

    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

    emoji
  • 0

    Sameh Elsharkawy said:
    1. With files that have over 45 K entries, we get an error, and no matter how we increase the MaxLocksPerFile value, it does not work.

    This is more likely to be a problem due to the limitation of Multiterm which is still needed under the hood.  I've copied the full extract from the help Gerhard provides on this issue for users who have it.  Perhaps the full detail will have something in here to help.

    File sharing lock count exceeded

    When converting very large files to sdltb, you may get a crash with the error File sharing lock count exceeded. Increase MaxLocksPerFile registry entry. This appears to be be a bug in MultiTerm or MS Access. Note that this is not about whatever version you have in your regular Office installation, but about an old version that comes as part of MultiTerm.

    From the original, now disappeared Microsoft KB article:

    ----------------------------------------------------------------------------------------------------------------

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 How to back up and restore the registry in Windows

    Steps to  increase the maximum number of locks per file:

    1. Click Start, and then click Run.
    2. Type regedit, and then click OK.
    3. Locate the following registry key depending on your Access installation:
      • For Windows 32 bit

    HKEY_LOCAL_MACHINES\SOFTWARE\MicrosoftJet\4.0\Engines\Jet 4.0

      • For  Windows 64 bit

    HKEY_LOCAL_MACHINES\SOFTWARE\Wow6432Node\MicrosoftJet\4.0\Engines\Jet 4.0

    1. In the right pane of Registry Editor, double-click MaxLocksPerFile.
    2. On the Edit DWORD Value dialog box, select Decimal.
    3. Modify the value of the Value data box as required, and then select OK.

    Note that this method changes the registry setting for all applications that use Microsoft Jet database engine version 4.0.

    ----------------------------------------------------------------------------------------------------------------

    I used a value of 40,000 to convert a termbase with 170,000 entries, so that could be a starting point.

    Once the registry is set, before the conversion, reboot your machine, to ensure that any potential locks are released.

    This method does not always work, but has a good success rate.

    I also had reports that these steps may help:

    • Increase locks as above
    • Use the Converter to create xdt/xml files
    • Use MultiTerm to create a new termbase based on the xdt file
    • In MultiTerm, import the xml file

    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

    emoji
  • 0 in reply to Paul

    Hi Paul,

    To start with, I hope you are doing great!

    ***************

    Where has it been removed?  Are you sure that you, like many others I have seen, have just not understood how this version works?  Here you can see, in the latest version, I still have all the options.  The new UI gives me the ability to create multiple "profiles" for the conversion if I wish.  But all options are still there... including SDL Translation Memory which many users contact me about to tell me I'm wrong and it's not there anymore!

    ************

    in reply to the above, do you really think that after all of those years, I would not really understand how this works? I have been doing a training to the WB team members over the past month and I have explained the tool to so many of them already, but this option was not at all found in the version I had, which should be new! Now I downloaded the most recent one, and it seems that Gerhard updated this file format.
    emoji
  • 0 in reply to Paul

    Actually Gerhard's help instructions are not sufficient and have to be amended, I believe! 

    **************

    HKEY_LOCAL_MACHINES\SOFTWARE\MicrosoftJet\4.0\Engines\Jet 4.0

      • For  Windows 64 bit

    HKEY_LOCAL_MACHINES\SOFTWARE\Wow6432Node\MicrosoftJet\4.0\Engines\Jet 4.0

    ****************

    On my colleagues PC's at the Worldbank, and at my end as well, the above is not found at all, but instead, the MaxLockPerfile is found in:

    \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Access Connectivity Engine\Engines\ACE

    So please kindly report this to him to add in the instructions. I have updated the value to 100000 and it still gave me the error. I changed it to 40000 as Gerhard says, but still the same thing Paul, the same error. 

    Only the XDT and XML method works, but that brings us again to the dark ages of using Multiterm to create a termbase, so it is not convenient at all in 2022! Hope that makes sense.

    Sameh
    emoji
  • 0 in reply to Paul

    ************

    including SDL Translation Memory which many users contact me about to tell me I'm wrong and it's not there anymore!

    ***************

    Indeed Paul it was not there at all. So the solution for them to be able to see those options now is to completely uninstall Glossary Converter, and get the most updated version and install it again. Only then, it will show those options.

    Sincerely,

    Sameh
    emoji
  • 0 in reply to Sameh Elsharkawy

    Using the XDT and the XML approach worked without a problem, at least for the 50K sheet I tested today. I hope with larger ones, it would not be an issue!

    Sameh
    emoji
  • 0 in reply to Paul

    Dear Paul,

    I reinstall the glossary converter plugin today and it works like magic. Yesterday I tried with Sameh and I did not have that option. Many thanks for your responsiveness and support. 

    Osama, World Bank.
    emoji