ODBC Importer - excel error

itbsdbor

Member
Version 16.0.4.2161 (64 bit) 02.146743

Trying to connect to an excel file in ODBC Importer, but it is throwing this error:

PL/SQL Developer error: [FireDAC][Phys][ODBC][Microsoft][ODBC Excel Driver] Operation is not supported for this type of object.

It had worked fine when I last used it on Dec 08 2025.

What I have tried: reboot, install Microsoft Access 365 Runtime (which I loaded new MS ODBC drivers), removed/re-added ODBC drivers in MS ODBC setup). I also emailed Allround Automations support yesterday and today, but have not yet heard back.

Any thoughts on what I can try next to resolve?
 
Could it be that you are running into this issue?


If so, can you try the workaround?
 
Could it be that you are running into this issue?


If so, can you try the workaround?
We were able to work around the issue with a registry key edit. I do think rolling back to prior version would work as well. Thank you for pointing us in the right direction!
 
We were able to work around the issue with a registry key edit. I do think rolling back to prior version would work as well. Thank you for pointing us in the right direction!
Hello, could you please say, which registry key have you edited? I've tried MS supported workaround and it doesn't work for me.
 
Ran into this same error on Jan 6, 2026 after running Windows updates:

[FireDAC][Phys][ODBC][Microsoft][ODBC Excel Driver] Operation is not supported for this type of object

when attempting to import data from Excel via an ODBC connection. Looks like it was a Microsoft update from Dec 9, 2025 that was the culprit.

Error showed up on a W11 machine that has Office365 and a W10 machine (receiving extended updates) that has Office 2021 Pro LTSC.


Fixed the issue by rolling Office back to pre-update version via command window...

Rolled Office365 on W11 back to pre-Dec 9 version (16.0.19426.20170) (open cmd window as admin and run script):
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.19426.20170

Rolled LTSC on W10 back to Nov. 11 Office version (16.0.14334.20402) and turned off Office updates (open cmd window as admin and run script):
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.14334.20402


itbsdbor: Please advise on the reg key edit you are referencing. Thanks!

Couple of questions for the community:
Q1: What is the KB that caused the issue?
Q2: How do we find out MS has fixed the issue? (i.e. when MS fixes it, what is the KB that fixes the problem)
 
Last edited:
Back
Top