Forum Discussion

StwKubak's avatar
StwKubak
Copper Contributor
Jun 24, 2021

freeze at CreateInstance when trying to get acedao version

 

Hello,

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

 

  1. CsVersion GetAceDaoVersion()
  2. {
  3. CsVersion ver;
  4. LPTSTR lpszFilePath = "acedao.dll";
  5. HRESULT hr = ::CoInitialize(NULL);
  6. if (hr != S_OK)
  7. {
  8. return ver;
  9. }
  10. _DBEnginePtr dbEngine;
  11. hr = dbEngine.CreateInstance(__uuidof(DBEngine));
  12. if (hr != S_OK)
  13. {
  14. return ver;
  15. }
  16. ver.LoadInfoFromFile(lpszFilePath);
  17. return ver;
  18. }
     

     

    Has anyone noticed a similar problem or change?

3 Replies

Sort By
  • Zdenek_K's avatar
    Zdenek_K
    Copper Contributor
    Aug 26, 2021
    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
  • Mijel's avatar
    Mijel
    Copper Contributor
    Jul 07, 2021
    I have exactly the same issue with Office 365 Version 2106 (Build 14131.20278). My 32bit C++ program freezes at line
    dbEngine.CreateInstance(__uuidof(DBEngine))
    and never returns.
  • Evan's avatar
    Evan
    Copper Contributor
    Jun 25, 2021

    Hello StwKubak 

     

    Sorry to hear this is happening to you. If this is still happening, we'd suggest reproducing the issue and then report it through the app via the steps listed on this page. If this is affecting your daily work, you might want to switch off of the Insider build until the issue is resolved. You would have to uninstall Office and reinstall it to get back on a production build.

     

    Thanks,

    Evan

Resources