SCOM 2012 – Editing Product Knowledge Issues – “Could not load file or assembly ‘Microsoft.Office.Interop.Word’

Up until a few days ago, I have had nothing but constant grief trying to get the “edit” button to work with product knowledge in System Center Operations Manager 2012 since deploying the product. It has yet to be a priority.  So, spending any more than a few minutes on Google searching for this in the past hasn’t been very productive.

Here is the problem in detail:

After installing/satisfying the prerequisites, you will receive the inevitable message:

Edit Product Knowledge Error

After SCOM 2012 was deployed , I created a new custom monitor and attempted to add product knowledge and first received the error. This week, now a couple of months out from deploying SCOM 2012, I’m to the point where I do not want any further custom monitors created without having the ability to provide some knowledge information. So, off a “Google-ing” I go.

Now, let’s outline some important information. Review the prerequisites before passing go.

These tidbits are critical:

  • The Operations console must be installed on a 32-bit computer. Adding and editing company knowledge must be done on this computer.
  • Microsoft Office Word 2003 with the .NET Programmability feature, or Microsoft Office Word 2007 or Office Word 2010 Professional edition (Standard edition is not supported.
  • Only the 32-bit version of Word 2010 is supported. The knowledge template will not work with the 64-bit version of Word 2010.
  • Microsoft Visual Studio 2005 Tools for Office Second Edition Runtime at You must use this version of the Visual Studio 2005 Tools for Office.

I overlooked the first issue.

I already have all that on my management VM and management VDI. Both are Windows 7, 32-bit machines. I look at these two machines and verify the other prerequisites have been met. Indeed they were. I try to edit company knowledge, same problem.

After several days of searching, I finally found this post from June 18, 2012:

I gave that a try and BANG! Worked.

Now, those that know me know I’m as stubborn as a mule and my thick head says to try it on my laptop.  Here comes the mean old buzzer a screaming away from the game of “Operation”.

Rule #1: “The Operations console must be installed on a 32-bit computer. Adding and editing company knowledge must be done on this computer.”

So, that was wasted time.  I have to use my management VM or my VDI.

Just a word of advice:  double and triple check the following as there will be MULTIPLE lines to delete.


Make SURE you have a backup of the original config and make SURE you only delete the lines FOLLOWING the /dependentAssembly  tag!