none
CoCreateInstance failed with REGDB_E_CLASSNOTREG in office 365 outlook. But it works fine with outlook 2013 and outlook 2016 Professional Plus RRS feed

  • Question

  • Hi,

    CoCreateInstance failed with REGDB_E_CLASSNOTREG in Office 365 outlook. But it works fine with Outlook 2013 and Outlook 2016 Professional Plus.

    What could be the reason that CoCreateInstance  does not work with Microsoft Office 365?

    Please someone help me by suggesting what needs to be done.

    Thanks,


    thopulou Associate Software Engineer

    Wednesday, September 19, 2018 9:33 AM

All replies

  • According to my research, Is it possible that it's a COM system path problem of Office 365 outlook? You could use Orca tool to test it. Please refer to these links:

    CoCreateInstance CLSID_IConverterSession fails with Office 2016

    x64 outlook2016 and CoCreateInstance error 0x80040155 on win10

    Hopefully it helps you.

    Best Regards,

    Simon


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread.

    Wednesday, September 19, 2018 1:21 PM
    Moderator
  • Which COM object are you creating? Outlook.Application?

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Wednesday, September 19, 2018 4:10 PM
  • Did you solve your problem? if your issue is still exist then let us know about that, we will try to suggest you further to solve the issue.

    Regards,

    Simon


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread.

    Tuesday, September 25, 2018 10:42 AM
    Moderator
  • Hi Dmitry,

    This is how we are creating Translation Object to convert EML to MSG

       //Create MIMEToMSG component to convert EML to MSG
       hr = m_pTranslate.CoCreateInstance(CLSID_MIMEToMSG);

    There is a little twist here. we check with customer and the issue is there in Outlook 2016 MSO (16.0.4266.1001) 32-bit  as well.

    Does updating Microsoft Office will cause this kind of issue?


    thopulou Associate Software Engineer

    Wednesday, September 26, 2018 5:45 AM
  • Hi Simon,

    The issue is not resolved yet.

    The issue happens to only few Customers and they see this in Outlook 2016.

    Some suggestions would be of great help.

    Thanks


    thopulou Associate Software Engineer

    Wednesday, September 26, 2018 5:48 AM
  • If you are using Click-to-run or Windows Store version of Outlook, IConverterSession COM object would not be externally accessible - it is only visible inside the sandbox created when Outlook runs.

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Wednesday, September 26, 2018 2:21 PM
  • You can still use IConverterSession in your own app, but you have to activate C2R registry redirection to use the correct registry keys for COM. 

    // see also https://stackoverflow.com/questions/46557849/cocreateinstance-clsid-iconvertersession-fails-with-office-2016/57500982#57500982

    HMODULE jitv = ::LoadLibrary(TEXT("jitv.dll"));

    if (jitv) { FARPROC efv = ::GetProcAddress(jitv, "EnableFullVirtualization"); if(efv) efv(); // call CoCreateInstance(guid::CLSID_IConverterSession) // and do your work } if (jitv) FreeLibrary(jitv);

    Thursday, August 15, 2019 4:32 AM
  • HI Michael,

    does it still work for you? It fails for me in the latest (December 2019) builds of Outlook.


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Friday, December 20, 2019 3:51 AM