-
Notifications
You must be signed in to change notification settings - Fork 217
FAQs COM Errors
FAQs > COM Errors |
---|
Unfortunately, these normally signify a problem with your local install of Microsoft Office (not OGCS) and often require some level of re-installation or registry fix. 😒
Here we've tried to collate some of the common fixes.
For starters, it's never a bad idea to perform an Office Repair and see if that improves things:-
- Open Control Panel and "Uninstall a Program"
- Select the "Microsoft Office" program and click "Change"
- Select "Quick Repair" and click "Repair"
- Start OGCS
ℹ️ For any registry fixes, the CLSID for Outlook is {0006F03A-0000-0000-C000-000000000046}
🗒️ If there is no solution below for your particular error code, or the solution provided doesn't work, please
0x80004002 - E_NOINTERFACE
0x80004004 - E-Abort
0x80004023
0x80010100 - RPC_E_SYS_CALL_FAILED
0x8002801D - TYPE_E_LIBNOTREGISTERED
0x80029C4A - TYPE__E__CANTLOADLIBRARY
0x80040154 - REGDB_E_CLASSNOTREG
0x80040155 - Interface not Registered
0x800401F3 - CO_E_CLASSSTRING
0x84120009
No such interface supported
This should be fixed with a simple Office Repair.
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.
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}
If you are 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.
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.
This is likely due to a recent install or upgrade/patch of office. Try rebooting. If still no luck, try a repair of Office. Finally, try each step in the registry fixes section below this registry fix.
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.
- Open a cmd window as Administrator (right-click, run-as)
cd c:\windows\Microsoft.NET\Framework\v2.0.50727
regasm <path-to-OGCS>\Microsoft.Office.Interop.Outlook.DLL
This can be a particularly nasty problem. Follow through the steps:
Register Ole32.dll
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:
- Click
Start
, and then typeCommand Prompt
, in appeared list, right-clickCommand Prompt
and selectRun as Administrator
- 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
- For 32 bit Windows:
- In the
RegSvr32
dialog box, clickOK
.
Then fix the interface
Invalid class string
This is usually seen in combination with 0x80004002, so apply the same solution.
Cannot complete the operation. You are not connected.
This was reported to be fixed in Issue #514 with a reinstall of Outlook.
Step through the following sections.
💾 It is always wise to backup your Windows registry before making any manual changes.
Use this table as a reference as guided in the following sections.
Outlook | Version |
---|---|
Outlook 2003 | 9.2 |
Outlook 2007 | 9.3 |
Outlook 2010 | 9.4 |
Outlook 2013 | 9.5 |
Outlook 2016 | 9.6 |
- Access the Windows Registry Editor via
Start
>Run
> TypeCmd
andEnter
> TypeRegEdt32
andEnter
. - Navigate to each of the keys that exist (depends on if using the 32 or 64 bit version of Outlook/Windows):
HKEY_CLASSES_ROOT\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
- Find a
(Default)
entry with the value{00062FFF-0000-0000-C000-000000000046}
- Compare and correct the
Version
value against the Outlook version numbers table.
- Navigate to
HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
- Delete the version keys (e.g.
9.5
) for any version of Outlook that is not installed on your system, based on the version table provided.- For example, if you are not using Outlook 2013 then remove the
9.5
entry. If you are not using Outlook 2010 then remove the the9.4
entry. - DO NOT DELETE the entry for the version that was specified in the last step of the previous fix the interface section.
- For example, if you are not using Outlook 2013 then remove the
- In the previous fix the typelib section, make sure that the registry key value ending with
MSOUTL.OLB
is pointing to a valid file location. The key location should be something likeHKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.6\0\Win64
- We now need to make sure that file is properly registered.
- Download regtlibv12.exe to your computer
- Go the Windows Start Menu and type
cmd
. - In the search results, right-click
cmd.exe
and selectRun as Administrator...
- Change directory to where you downloaded
regtlibv12.exe
, eg:cd %USERPROFILE%\Downloads
- Execute the following command, where
<msoutl.olb file>
is the value taken from step #3:
regtlibv12.exe "<msoutl.olb file>"
.
For example:
regtlibv12.exe "C:\Program Files\Microsoft Office\root\Office16\MSOUTL.OLB"
- Run OGCS.