May 2008 Entries

You may have discovered this when you were attempting to rummage through Internet Explorer's help files, or perhaps you've just downloaded a help file from another vendor with the *.chm file type. In either case you'll see something that looks like this:


This was  either caused by a Microsoft Security upgrade or by installing Microsft Windows Server 2003 SP1 which included changes to the InfoTech protocol that blocked the ability to view remote content.

To correct this, execute the following steps:

  1. Navigate to the *.chm icon.
  2. Right-click on the icon
  3. Click Properties.
  4. Click unblock.


The most comprehensive guide to outlining the steps on what to do to find out is provided by Microsoft, located on their website under : , but here's a cheat-sheet version to keep handy!

XP or Windows Server 2003

  1. Click Start>Run
  2. Type sysdm.cpl . Click OK
  3. Click the General tab.
  4. Look at the operating system.

If the operating system has an x64 in it, then you are running a 64-bit version. If you do NOT see this, you are running the 32-bit version.


  1. Click Start. Type system in the Start Search box.
  2. Click system in the Programs list.
  3. Look at the operating system.

The System type under System value will show either 64-bit or 32-bit.

There are several reasons why the Business Contact Manager (BCM) might not load, rather than guess, the best thing to do is to have BCM generate a log file so you can analyze the problem more methodically! How cool is that ?

Here's what you need to do to invoke logging in BCM:

  1. In Outlook, go to the Help Menu
  2. Click on About Business Contact Manager for Outlook.
  3. A window will open, in this window click on the checkbox to enable logging for BCM.
  4. The log file that get's generated is located under: c:\Users\YourName\AppData\Local\Temp\BCMLog_Vx.log

Open the file and have a look around! This should help you determine what the trouble is without a lot of guess work!


If you are seeing the message: Business Contact Manager failed to initialize the Common Language Runtime. ECall methods must be packaged into a subsystem module, BCM isn't really the trouble. You are getting this message because on or around April 11, 2008 an automatic update from Microsoft downloaded a damaged component of the Microsoft .NET Framework 2.0. 

 On the bright side, today is May 20, 2008 and a patch has already been downloaded on an automatic update. You'll just have to repair it!

To repair the damaged .NET 2.0 component, execute the following steps:

For XP:

  1. Click on Start>Settings>Control Panel
  2. Double-click on Add or Remove Programs icon
  3. Select Microsoft .NET Framework 2.0
  4. Click Change/Remove
  5. Choose Repair.
  6. Restart computer

For Vista:

.NET Framework 2.0 is completely integrated into Vista, so it can't be uninstalled/repaired the same way as it can in XP. In the case of Vista, you'll have to run sfc (system file checker).

  1. Click on Start, type cmd in the Start Search Box. [don't press enter yet]
  2. Right-click cmd.exe in Programs list in search results, click Run as Administrator
  3. In command window, type sfc/scannow  -- press enter.

If this still doesn't fix your issue, please look for .NET 2.0 SP1 on . There will be two versions out there, one for 64-b and one for 32-b. If you aren't sure which version of the operating system you're running on, follow the instructions listed by Microsoft here: