Business Contact Manager failed to initialize the Common Language

[denmarfl]

Running Outlook 2007; Vista Home prem SP1. When I open Outlook I get
"Business Contact Manager failed to initialize the Common Language Runtime."
I have read the questions on this issue, they address fixes if you are
running XP. I did see a Post at another site to run sfc/scannow, I ran that
it came back reporting no issues. I also read that unlike XP,
Microsoft.Framework.net, which is alledged to cause this issue, is part of
Vista as opposed to separate as it is in XP. I have gone into to the TRUST
CENTER and have DISABLED Business Contact Mgr for Outlook......

Is there a known way to correct this for Vista Users?

 

[marsr]

Running Outlook 2007; Vista Home prem SP1. When I open Outlook I get
"Business Contact Manager failed to initialize the Common Language Runtime."
I have read the questions on this issue, they address fixes if you are
running XP. I did see a Post at another site to run sfc/scannow, I ran that
it came back reporting no issues. I also read that unlike XP,
Microsoft.Framework.net, which is alledged to cause this issue, is part of
Vista as opposed to separate as it is in XP. I have gone into to the TRUST
CENTER and have DISABLED Business Contact Mgr for Outlook......

Is there a known way to correct this for Vista Users?

I am having the same problem. I have been working on it for two days. It
worked initially and then failed. I am thinking of calling tech support.
Will keep in touch.

 

[denmarfl]

From my research it has to do with a May 2007 Microsoft Upgrade for
Microsoft.Net framework. As strange as it seems, this started after I
installed a Microsoft Update dated May '07. I thought it strange that I
would get such as old offering but since my Install is a few months old I
assumed other updates had to be installed before the 5/07 update wjo be
offered. The Update did not read .Net Framework but I would bet it is the
Update that causes this problem.

Be sure when you reply you put a check,ark in Notify me of replied...I did
not get notification of your reply. If I come up with anything I'll post it
back to you as a reply. No sense in both of us contacting Microsoft Support,
so I'll await your results.

 

[Raul Thomas]

Try running the .NET Verification tool to see if it detects and issue with
..NET

http://blogs.msdn.com/astebner/archive/2006/03/21/557525.aspx