freeze at CreateInstance when trying to get acedao version

Question

Hello,

while running our program, we noticed a change in behavior after updating MS Office within the Insider program to version 2106.
Problem appears at point "hr = dbEngine.CreateInstance(__uuidof(DBEngine));" where the function stops work.

CsVersion GetAceDaoVersion()
{
                CsVersion ver;
                LPTSTR lpszFilePath = "acedao.dll";

                HRESULT hr = ::CoInitialize(NULL);
                if (hr != S_OK)
                {
                               return ver;
                }

                _DBEnginePtr dbEngine;
                hr = dbEngine.CreateInstance(__uuidof(DBEngine));
                if (hr != S_OK)
                {
                               return ver;
                }

                ver.LoadInfoFromFile(lpszFilePath);
                return ver;
}

Has anyone noticed a similar problem or change?

Answer 1

Hi,
I have the same problem.

In my PC there are two versoins "acedao.dll" (x86) 16.x:

• c:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\ACEDAO.DLL
• c:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\

After you install the Microsoft Office update, the Microsoft Office program component in the registry (HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{CD7791B9-43FD-42C5-AE42-8DD2811F0419}\InprocServer32) is frozen.
If I reinstall the Microsoft Access 2016 database engine ([https://www.microsoft.com/en-us/download/details.aspx?id=54920][1]), the program works fine.

I tried to download the latest beta version of Office 2108 (14315.20008) but the freeze problem is still the same.

Zdenek

Answer 2

A similar problem is in MS Office 2019, version 2107 (14228.20204). When I start my application, I get the following message:

The fix is ​​a reinstallation of the Microsoft Access 2016 database engine.

Does anyone have a similar problem?

Answer 3

Fixed:
https://support.microsoft.com/en-us/office/error-the-operating-system-is-not-presently-configured-to-run-this-application-when-when-trying-to-use-the-access-database-engine-dao-api-from-a-non-microsoft-office-application-c551294a-6f4e-4af5-a89f-e79e232b9898?ui=en-US&rs=en-US&ad=US

Answer 4

I am having a nearly identical problem on SQL Server Linked servers and have posted the issue here: https://feedback.azure.com/d365community/idea/fc1456dd-b7a3-ec11-a81c-6045bd7d1bee