General COM Errors Related To Microsoft Office Especially Outlook

News Knowledge Base
1

General COM errors related to Microsoft Office especially Outlook. 0x80004002 - E_NOINTERFACE 0x80004004 - E-Abort 0x80004023 0x80010100 - RPC_E_SYS_CALL_FAILED 0x8002801D - TYPE_E_LIBNOTREGISTERED 0x8002802B - TYPE_E_ELEMENTNOTFOUND 0x80029C4A - TYPE__E__CANTLOADLIBRARY 0x80040154 - REGDB_E_CLASSNOTREG 0x80040155 - Interface not Registered 0x800401F3 - CO_E_CLASSSTRING 0x84120009

Issue Description: General COM errors related to Microsoft Office especially Outlook.

  • 0x80004002 - E_NOINTERFACE
  • 0x80004004 - E-Abort
  • 0x80004023
  • 0x80010100 - RPC_E_SYS_CALL_FAILED
  • 0x8002801D - TYPE_E_LIBNOTREGISTERED
  • 0x8002802B - TYPE_E_ELEMENTNOTFOUND
  • 0x80029C4A - TYPE__E__CANTLOADLIBRARY
  • 0x80040154 - REGDB_E_CLASSNOTREG
  • 0x80040155 - Interface not Registered
  • 0x800401F3 - CO_E_CLASSSTRING
  • 0x84120009


Root Cause: Missing respective Registry keys.

Resolution:

  1. Navigate to the Studio --> Tools --> "Repair Tool for Microsoft Office"
  2. Click "Generate Repair Plan" as shown below.
  3. Check mark the appropriate options and then click on 'Run Repair Actions' as shown below:
  4. It will automatically detect the office installation setting related to Excel, Outlook, Word, Power Point.
  5. It will repair the Microsoft 365 and Office programs.
  6. Now, please try reproducing the issue (up on finishing the repairing session). If persist, follow the below steps.
    1. If Studio is not available, try using "Repair an Office Application".
    2. Try reproducing the issue.
  7. If issue persists, check the Event Viewer Logs up on reproducing the issue and look for COM Errors as described below:
    1. 0x80004002 - E_NOINTERFACE : No such interface supported.
      • This should be fixed with a Office Repair Tool.
    2. 0x80004004 - E-Abort
      • This often relates to Outlook either not being ready to service OGCS connecting to it, or your corporate policies are preventing connection. The error should now be avoidable from v2.6.0, which allows for a delayed startup of OGCS to help with the first issue, or enters a reduced functionality mode to avoid being blocked.
    3. 0x80004023
      • As per Issue 160:
        • It is actually an Office installer/uninstaller issue. I used to have Outlook 2010, and then upgraded to 2013. Unfortunately, Office did not uninstall some old registry when it upgraded. One was 64-bit the other was 32-bit. So I had to launch the 32-bit regedit and delete/rename the entry in: HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}
    4. 0x80010100 - RPC_E_SYS_CALL_FAILED
      • If in a corporate Exchange environment and have recently changed your network Active Directory account password, check that you have also updated the cached password for your Exchange account in Outlook.
    5. 0x8002801D - TYPE_E_LIBNOTREGISTERED
      • This may happen if you have uninstalled Outlook 2013 and reinstalled an older version, or installed Lync 2013 alongside Outlook 2010. These types of situation require registry fixes. One user reported needing to delete the registry keys and reinstall Office.
    6. 0x8002802B - TYPE_E_ELEMENTNOTFOUND
      • This is likely due to a recent upgrade of Office. Try rebooting and then a repair of Office. If still no luck, see if any other previously affected users on Issue #999 can help or troubleshoot further.
    7. 0x80029C4A - TYPE__E__CANTLOADLIBRARY
      • This is likely due to a recent install, upgrade/patch or downgrade of Office. Try rebooting, a repair of Office and if still no luck, the following registry checks.
      • Search for Invalid Registry Key: If you have upgraded or downgraded the release of Office (eg from 2013 to 2016 and back again), the following is worth checking.
        1. Go to Start > Run > Type regedit and press Enter. It will open the Windows Registry.
        2. Click on HKEY_CLASSES_ROOT and press Ctrl+F to search for the Outlook CLSID: {0006F03A-0000-0000-C000-000000000046}
        3. Find the result for the folder name matching the CLSID, likely HKCR\CLSID\{0006F03A-0000-0000-C000-000000000046}
        4. Expand the folder and click on TypeLib. On the right-hand side you will see a default key entry which will be another CLSID - copy this CLSID for next step (eg {00062FFF-0000-0000-C000-000000000046}.
        5. Now type typelib on your keyboard to navigate to HKEY_CLASSES_ROOT\TypeLib.
        6. Click on the TypeLib folder and then press Ctrl+F and search for the other CLSID key which you copied in step 4.
        7. Once you find the CLSID, expand it you will see one or more folders with a version number, eg 9.5.
        8. Expand each version number folder and all the sub-folders. Make sure you know if you have 32-bit or 64-bit Office.
          1. For 32-bit Office, make sure you only have Win32 folders and remove any Win64 folders.
          2. For 64-bit Office, make sure you only have Win64 folders and remove any Win32 folders.
          3. For the correct folder, it will contain a Default key with a file path value - using Windows Explorer, check that this file path actually exists. If the file does not exist, delete the folder.
        9. For example, if HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.5\0\Win32 points to C:\Program Files\Microsoft Office\Office15\MSOUTL.OLB and that file does not exist, delete the registry key Win32 folder.
        10. Similarly, for Outlook 2016 64-bit, the configuration should appear as below with a valid path to MSOUTL.OLB:
        11. General Registry Fixes:
          • Finally, if you did not find any invalid registry keys, try each step in the registry fixes section below.
    8. 0x80040154 - REGDB_E_CLASSNOTREG : Class not registered.
      • Assuming you do actually have Outlook installed on the machine you are running OGCS from(!), then it would seem Outlook is not registered properly.
        • A verified fix has not been reported (aside from uninstalling Office and reinstalling) by affected users, so please do report back if the below makes any difference or you find another solution.
          1. Open a cmd window as Administrator (right-click, run-as)
          2. cd c:\windows\Microsoft.NET\Framework64\v2.0.50727
          3. regasm \Microsoft.Office.Interop.Outlook.DLL
            • eg regasm %LOCALAPPDATA%\OutlookGoogleCalendarSync\app-2.8.0-beta\Microsoft.Office.Interop.Outlook.DLL
    9. 0x80040155 - Interface not Registered
      1. This can be a particularly nasty problem. Follow through the steps: Register Ole32.dll
      2. Make sure part of Microsoft Office (the Ole32.dll file that is located in the %windir%\System32 folder) is registered correctly in the Windows registry:
      3. Click Start, and then type Command Prompt, in appeared list, right-click Command Prompt and select Run as Administrator
        1. In Command Prompt window type the following command and press Enter
          • For 32 bit Windows: regsvr32.exe %windir%\System32\Ole32.dll
          • For 64 bit Windows: %systemroot%\SysWoW64\regsvr32.exe %windir%\SysWoW64\Ole32.dll
        2. In the RegSvr32 dialog box, click OK.
        3. Then follow the 3 steps through below from "Fix the Interface" to "Ensure MSOUTL.LIB is Registered" (the final step usually being the most important).
    10. 0x800401F3 - CO_E_CLASSSTRING : Invalid Class String
      • This is usually seen in combination with a subsequent second error. If a simple reboot and/or Office Repair doesn't stop the error, follow the guidance for fixing the second COM error reported.
    11. 0x84120009 : Cannot complete the operation. You are not connected.
      • This was reported to be fixed in Issue #514 with a reinstall of Outlook.

Contact UiPath Product Support: If issue persists, create UiPath Support Ticket for further troubleshooting.

Ensure to provide / attach the below list of details in ticket being created,

  1. From the same machine, share the Event Viewer logs: ETVX Logs.
  2. Confirm if there is a Proxy Setup.
  3. Are there any firewall rules that are getting block - check with your IT.
  4. Also, please share us the UiPath Diagnostic Tool Logs.
  5. What is the version of Office (Excel, Outlook, Word, PowerPoint).