Vincenzo Russo 

Can you share the Excel file?

Also, the solution is to repair Microsoft Office so I doubt anyone is going to resolve anything here.

I also tried to repair Microsoft Office, but the issue is not resolved

I dont have the file managed by OneDrive. It's located in my PC. 

Vincenzo Russo 

This:

c:\Users\pfilkin\OneDrive - RWS\Documents\SDL\TESTING\Vincenzo Russo\Glossary.xlsx

Is on my PC too.

Vincenzo Russo 

Maybe you're using a Mac?  Similar issue I think.

Not using OneDrive and not using a Mac

Vincenzo Russo 

Then I have no idea... unless of course you are using a 64-bit version of Microsoft Office?  That could be the other reason.  If it's none of these things then I have no idea.  Maybe a good time to rethink the format of the file in Excel and redo it so the Glossary Converter can work with it more easily instead?

I’m using a 64-bit version of MS Office, since my computer is 64-bit

 Vincenzo Russo 

Just because you can doesn’t mean you should ;-). I also have a 64-bit computer but run a 32-bit version of office.  MultiTerm Convert is an old application and won’t work with the 64-bit version of office.

Only workarounds are don’t use MultiTerm Convert or find a 32-bit version you can complete your studies for this module with.

Paul 

Not to confuse the issue, but I use MultiTerm Convert on a regular basis and because I was concerned about the 32-bit vs. 64-bit information, I had a quick look. I am running 64-bit Office 365. To further complicate things, the file I convert on a regular basis is also located and shared on OneDrive, which is also where MT Convert outputs the converted file. I never had any issues. Had a quick look at the Excel file and didn't see anything that jumped out at me. I was able to start the conversion process with this file from my local Downloads folder (Windows).

Michael Schroeder 

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.

The plot thickens? ;-)

The plot thickens? ;-)

Michael Schroeder 

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 

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:

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.