-
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
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}
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, 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:
- http://synqit.com/0x80040155-error-howto
- Step 1 at https://www.fieldstonsoftware.com/support/support_gsyncit_8002801D.shtml
- In the previous steps, make sure that the registry key value ending with
MSOUTL.OLB
is pointing to a valid file location. - 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.
Invalid class string
This is usually seen in combination with 0x80004002, so apply the same solution.