Outlook 2007 from C# - COM exception, TYPE_E_LIBNOTREGISTERED
Solution 1
This can also happen, when you have uninstalled an office 2013 installation and you return to office 2010. There might be some registry keys and dlls left, which cause the office application to load the wrong dll(s).
Here is the fix: http://www.fieldstonsoftware.com/support/support_gsyncit_2013.shtml
Solution 2
Office is not properly installed on that machine. You can verify that with Regedit.exe, navigate to HKEY_CLASSES_ROOT\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
to verify the type library GUID (should be {00062FFF-0000-0000-C000-000000000046}), then to HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
to verify that the type library is indeed properly registered, using the correct type library version number. The latter part should be the problem.
If the target machine runs a 64-bit version of Windows, try setting the Project + Properties, Build, Platform Target to x86.
Solution 3
If you attempt to access Outlook from Visual Studio and get the error:
TF400424: Failed to send to Microsoft Outlook: Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063001-0000-0000-C000-000000000046}' failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)).
Do the following:
- Using the Registry, 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 below. 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 the "9.4" entry. DO NOT DELETE the entry for the version that was configured in Step #1
Outlook 2007 ==> 9.3
Outlook 2010 ==> 9.4
Outlook 2013 ==> 9.5
Related videos on Youtube
PK.
Updated on April 17, 2022Comments
-
PK. about 2 years
I'm trying to make a program that would open new Outlook 2007 message.
I've referenced from COM tab Microsoft Outlook 12.0 ObjectLibrary.
These items showed up in references in VS:
Microsoft.Office.Core Microsoft.Office.Inerop.Outlook
Now I try to invoke following code:
var _outlookInstance = new Microsoft.Office.Interop.Outlook.Application(); var _message = (OutlookApp.MailItem)_outlookInstance.CreateItem(OutlookApp.OlItemType.olMailItem);
where OutlookApp==Microsoft.Office.Interop.Outlook namespace.
While invoking second line of listing I keep getting this exception: (InvalidCastException)
Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063001-0000-0000-C000-000000000046}' failed due to the following error: Library unregistered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)).
That code worked well for Outlook 2003 on my other station.
I'll be grateful for any ideas how to solve it.
-
Lex Li about 14 yearsOn Windows x64, learn about WOW64 registry (support.microsoft.com/kb/896459)
-
PK. about 14 years@nobugz: about that second step: when I navigate to that location value stored in there says "value not set". is that a problem? should it be set to a specyfic value? if so what value shoud be there. In child nodes of HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046} a have some emty values as well. shoud they be set?
-
user1703401 about 14 yearsWell, that explains why it doesn't work. No idea what happened, chase the "not properly installed" angle. Maybe your registry is toast, try it on another machine.
-
SliverNinja - MSFT over 11 yearsAwesome find - deleting
HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.5
did the trick! This is an error with the Office 2013 uninstaller. -
Gabe over 11 yearsGood find, that fixed my problem +1
-
shookdiesel over 11 yearsTurned out to be the build platform for me. Thanks!
-
Doigen over 9 yearsThat didn't work for me, as there was no excessive 9.5 field. In my case, the problem was that when I downgraded to Outlook 2010 I have modified the installation location (i.e. not in the default ProgramFiles folder). However, windows didn’t update accordingly the value in ‘HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.4\0\win64’ After manually updating the value and pointing it to the right location, the problem was resolved.