Multiterm Convert. Error: The conversion option could not be initialised properly. The file cannot be opened in Microsoft Excel.

Hi! 

I tried to create a termbase from an MS Excel glossary using MultiTerm Convert, but when I start the conversion and select the input file and click Next an error message appears: "The conversion option could not be initialised properly. The file cannot be opened in Microsoft Excel". 

I already saw the RWS Support Guide (https://gateway.sdl.com/apex/communityknowledge?articleName=000008785), but the issue is not resolved.

My Pc version: Windows 10 Home 22H2

Multiterm version: Multiterm SR2 17.2.2.2737

Trados version: Trados Studio SR2 17.2.9.18688

Error message in MultiTerm Convert stating 'The conversion option could not be initialised properly. The file cannot be opened in Microsoft Excel.' with an OK button.



Generated Image Alt-Text
[edited by: Trados AI at 9:45 AM (GMT 0) on 18 Mar 2024]
emoji
Parents Reply Children
  •  

    Well... you got me doubting myself and also the technical team so I tested on my personal laptop just now where I have never actually tried to use Convert before.  I get this very same error and cannot use it.  On my work laptop, I have a 32-bit install and everything is fine.  Maybe check your Excel... just for my own sanity!

    1. Go to the 'File' menu in the top left corner and select it.
    2. Select 'Account' or 'Office Account' on the bottom left side of the menu.
    3. Under 'Product Information,' click on 'About Excel'.
    4. In the dialog that opens, you will see either:
      • 64-bit if you are running a 64-bit version.
      • 32-bit if you are running a 32-bit version.

    Microsoft Excel for Microsoft 365 MSO (Version 2402 Build 16.0.17328.20124) 32-bit product information dialog box with a red arrow pointing to the 32-bit version information.

    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


    Generated Image Alt-Text
    [edited by: Trados AI at 8:54 AM (GMT 0) on 22 Mar 2024]
  • The plot thickens? ;-)

    Screenshot of Microsoft Excel for Microsoft 365 MSO version 2308 build 16.0.16731.20542 64-bit about page, showing software license terms and copyright warning.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 9:30 AM (GMT 0) on 22 Mar 2024]
  •  

    Thickens indeed!  You seem to have achieved something we cannot!  I have no explanation for this at the moment but will start an investigation to see if anyone has any thoughts on why you might be able to achieve this.  Can you advise whether there is anything else we should know about your setup... using a VDI for example?  Technically it is possible to have access to a 32-bit version of Excel despite running a 64-bit version of Office.

    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
  •   

    Nothing really remarkable. I notice the build numbers are different but that's just a detail. No magic on this end, VDI or anything else. Been using the same workflow for years, the entire time we've been using M365. Until recently -- probably 6-12 months -- was using the old MultiTerm Convert from 2019; this was also running without any problems. Now using Convert from 2022. I've got MTD 2022 installed but never use it. Just checked and it's one version back I think:

    Screenshot showing MultiTerm Desktop 2022 version update prompt, with the latest version 17.2.3.2795 available for download and the current version 17.2.2.2737 installed.

    Studio 2022 is up to date.

    I use MTD 2019 instead for the simple reason that it allows me to create a view with my own background (there's a forum entry about that somewhere). Every month I export our termbase and create a brand new one based on it (catalog items included). This is the easiest way with our approval process. All of this is done using MTD 2019. Not sure that would affect Convert however.

    Granted, I did not carry out the conversion of the file above all the way through, got it to the "Set up fields" step but from what I understand, I made it past the error phase which was right at the beginning when selecting the input file.

    Can't think of any limitations / special features of Excel. Works as I would normally expect with no extra/missing bells or whistles.

    If there's anything else you would like to know, please just holler.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 6:14 AM (GMT 0) on 25 Mar 2024]