Sometimes the Product Knowledge for a SCOM alert is not too informative.
Here's what you will need to do. Install the following on a Operations Console
1) Install 2003 Office Web Components
2) Install Office 2003 Word
3) Install Office 2003 Primary Interop Assemblies
4) Install Visual Studio Tools for Office 2005
Here's a question for Microsoft. Why in 2012 are parts of Office 2003 components required for a product released in 2012? No biggie but really? ಠ_ಠ
I tried all of the options you provided with no luck. I finally opened a case with MS and this was their internal KB resolution which fixed it for me:
ReplyDelete1. Go to the directory where the Ops Mgr executables are. Go into the folder named Console, (example: C:\Program Files\System Center\Operations Manager 2012\Console )
2. You will find a file Microsoft.EnterpriseManagement.Monitoring.Console.exe.config. Make a copy of this file named Microsoft.EnterpriseManagement.Monitoring.Console.exe.config.bak
3. Edit Microsoft.EnterpriseManagement.Monitoring.Console.exe.config using Administrator rights. (If you do not have elevated privileges, you will not be able to save the file back to this directory).
4. You will see elements called assemblyBinding. Here is an example:
This is the one you will delete.
Note that the publisherPolicy elements are appearing in pairs. One is inside of the dependentAssembly element; the other is outside. You want to remove the publisherPolicy element that is outside of the dependentAssembly element. So here is what you would have afterward:
5. Do this for all the assemblyBinding elements in the file, removing the second instance that appears after
6. Save the file.
7. Close the SCOM console if it is open. Then start the console and try to edit knowledge.
8. You will now be able to edit the company knowledge with Word 2010.
That didn't work. I'll try again. FYI, this was SCOM 2012 console on Windows 7 64bit, using Word 2010 32bit.
ReplyDelete1. Go to the directory where the Ops Mgr executables are. Go into the folder named Console, (example: C:\Program Files\System Center\Operations Manager 2012\Console )
2. You will find a file Microsoft.EnterpriseManagement.Monitoring.Console.exe.config. Make a copy of this file named Microsoft.EnterpriseManagement.Monitoring.Console.exe.config.bak
3. Edit Microsoft.EnterpriseManagement.Monitoring.Console.exe.config using Administrator rights. (If you do not have elevated privileges, you will not be able to save the file back to this directory).
4. You will see elements called assemblyBinding. Here is an example:
This is the one you will delete.
Note that the publisherPolicy elements are appearing in pairs. One is inside of the dependentAssembly element; the other is outside. You want to remove the publisherPolicy element that is outside of the dependentAssembly element. So here is what you would have afterward:
5. Do this for all the assemblyBinding elements in the file, removing the second instance that appears after
6. Save the file.
7. Close the SCOM console if it is open. Then start the console and try to edit knowledge.
8. You will now be able to edit the company knowledge with Word 2010.
pictures / information missing , can You update ?
DeleteUnfortunately, posting xml in comments just returns blank lines. Just look for the PublisherPolicy=no lines that are immediately after the /dependedentAssembly lines and remove the PublisherPolicy lines. Hope that helps. If someone can tell me how to post xml in a comment, I can do that.
DeletePast as plain text or using script tags or just post a screen shot. ;)
ReplyDeleteAlso, this doesn't appear to work anyway
ReplyDeleteThanks for the posts. Please note the blog refers to having installed Word 2003. Glad you were able to get Word 2010 working (good to know). I am not well versed on Blogger. I will see if I can research with the image embedding.
ReplyDeleteThis is a link to this very subject, should help. I myself have tried this. Running Windows 7, 32bit. 32-bit word 2010. All components installed as instructed, still get the same error with or without this fix. So, mileage may vary.
ReplyDeletehttp://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/aae19511-c886-4d00-8e6f-015707b177f8