Problems with Outlook.Application class registry information.

[Frank S]

I have some applications that use the Outlook Object Model. For most customers, the applications
work fine.

However, for a few, the C++ statement "... CreateInstance("Outlook.Application");" fails.

In some of these cases, the problem is caused by left over entries in the registry. It looks like
this may occur if someone installs a new version of Outlook over an older version, and then later
uninstalls (or maybe deletes) the newer version (but I have not verified the exact steps).

By removing the left over entries from the registry, the problem with CreateInstance is corrected.

Is there a Microsoft tool that will ensure that all registry information associated with Outlook is
correct?

Regards,

Frank

 

[Jialiang Ge [MSFT]]

Hello Frank

I once saw similar reports for Word.Applicaiton:

That customer with Word 2003 got the error when his application tried to
create a Word.Application object. The VB6 line 'Set wd = New
Word.Application' gives the error -2147319779 "Automation error Library
not registered". The customer told me that Office 2007 was previously
installed on the computer and was removed and replaced with Office 2003.
After he removed Office 2007 PIA in Control Panel -> Add or Remove Program,
the problem disappears. A lot of community members in NG replied that they
encountered the same issue and the resolution helped them too.

Frank, is this information helpful to you?

A Microsoft tool that may diagnose this kind of problem is

Microsoft Visual Studio 2005 Tools for Microsoft Office System: Microsoft
PSS VSTO 2005 Client TroubleShooter
http://www.microsoft.com/downloads/details.aspx?FamilyID=C9FB6A54-8069-4918-
A6F9-E744928DFAC3&displaylang=en
(if the URL is broken, please search the title in Microsoft download
http://www.microsoft.com/downloads/details.aspx).

Tools can help diagnose potential client-side issues, check the
prerequisites and give suggestions to resolve an issue.

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jialiang Ge [MSFT]]

Hello Frank,

I am writing to check the status of the issue on your side. Would you mind
letting me know the result of the suggestions? If you need further
assistance, feel free to let me know. I will be more than happy to be of
assistance.

Have a great day!

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

 

[Frank S]

The Microsoft PSS VSTO 2005 Client TroubleShooter does not even show information about Outlook 2007,
so it is not much help.

To see the problem yourself, create this registry key (assuming you have a version of Outlook
installed):

HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.6

and then try to use any application that tries to create an instance of "Outlook.Application".

What I would really like to see is for Outlook to ensure that the Outlook type library registration
is correct, without any extraneous information left over from other versions of Outlook.

Regards,

Frank