CLSID 0006F03A-0000-0000-C000-000000000046 or IClassFactory failed due to the following error: 800706ba - Outlook Crash - Troubleshoot

Issue: (Outlook crashes with the below error)
Error message: Creating an instance of the COM component with CLSID {0006F03A-0000-0000-C000-000000000046} from the IClassFactory failed due to the following error: 800706ba The RPC server is unavailable. (Exception from HRESULT: 0x800706BA). Error trace:

We have explained a similar issue when application crash with the same CLSID error.

The above post is specific to any application which ceases to function or crashes abruptly.
The below explanation is with respect to Outlook


  1. Possible reason Outlook was busy processing other request or took long enough to launch.
  2. Corrupt outlook updates.

Handling such issue using code:
This has been explained in the above link as well.

Handle this error in a Try-Catch activity - in such a way that if the error occurs again, instead of the crash, you will catch the exception and execute a specific code (like killing the application process and start it again).

Further, Troubleshoot steps for Outlook:

  1. Outlook/Help/Check for Updates.- Check for any updates and install the updates.

  2. If (1) fails , It may be easier to adopt the work around to repair the Outlook environment. - Online repair from the Control panel

  3. Disable all other Outlook add-ins: Outlook Tools menu | Options | Other tab | Advanced Options | COM Add-Ins | uncheck the items. If this solves the problem, then re-enable one add-in at a time until the problem reappears. It could be one of the add-in which get launched when outlook event starts.
    For Example: Screenshot of Add-ins

  4. Reinstall Outlook. Uninstall then reinstall Outlook fully as a last resort ( note do not simply reinstall - you must uninstall Outlook first then reinstall it ). Do not uninstall the Office package as a whole, just select Outlook to uninstall.

The above troubleshoot steps for Outlook should solve the issue.

Explaining further the issue: (This may be an issue, however , avoid this as of now I have shared just for information sake. )
As per Microsoft blog, this may also result due to windows updates too.
You can also reach out to your windows server team to check if there are any pending windows updates for the affected server.

Additionally, you can also look for information in posts of the forum with an error related to mentioned CLSID.