I got follow error when trying to edit Product Knowledge of SCOM Rule Failed to launch word. Please make sure Microsoft word is installed. here is the error message: the server threw an exeption (exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) I have the same error months before and uninstalled the KB2251419 due of the thread http://social.technet.microsoft.com/Forums/en/operationsmanagerauthoring/thread/b2c679f3-d971-4fc9-b07a-983bf95e8c7b Now i have the same problem, but there isn't KB2251419 to uninstall. We have a lot security updates since then. Does somebody have an idea to solve the problem generally ? Lehugo

Make sure you install VSTOR with the same language that your Office installation is.. And I think the only supported Office is Professional.mats.w | www.opsmode.com

Hi I've put together a collection of links which might be useful - I think though that Mats has identified the probably issue. http://systemcentersolutions.wordpress.com/category/knowledge-base/ Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

We have Office 2007 Professional Plus ans SCOM 2007 R2 CU2. Last year after installing vstor.exe i could edit the Product Knowledge. After KB2251419 was installed on my PC i had the problem (exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)). After that i deinstalled the KB2251419 months ago the problem was solved i could edit the Product Knowledge again. Last week i tried to edit the Product Knowledge again and got the same error (exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT) again. Since then there are a lot of office security updates on my PC. All the sercurity updates are installed automatically from SCCM in our company. I have deinstalled the vstor.exe and installed vstor.exe (german) like the language of my office but got the same error. It seems that a certain office security update like KB22551419 was the reason but what ? Due of this error no product knowledges can be edited and added anymore in SCOM. Lehugo

To check if it is caused by the Office update, you can perform a system restore to the date when the issue did not happen and then try to install them one by one to check the results.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

we are in a big company. All the microsoft security updates are installed automatically on our PCs. That means that if i'll find out the reponsible security update and deinstall it the next cumulative office update will come and i have to look for the solution again. When microsoft want that SCOM User have to use Word in order to edit product knowlegde they have to have a solution for their custormer otherwise they have to give SCOM User the possibility to choose another editor (like Open Office, wordpad etc. ) to edit the product knowledge Lehugo

Hi Lehugo. I'm the person who answered the question in the thread you linked to in your first post. On my Win7 machine, KB2251419 was automatically reinstalled by desktop support, and I can no longer edit Knowledge again. Oddly enough, on my XP machine, the update was also automatically reinstalled, but I can still edit Knowledge. I use Word 2007 on both machines. I agree that the current implementation for editing Knowledge is very klunky. Sorry I can't be of more help.Layne

I have done the same workaround like you did. Because of the fact that we don't have any influences to the security updates on our PCs (Vista :(( ) i installed Word 2007 on one of our Windows 2003 test server without any office updates. From there i can edit knowledge now. My frustration grows every day about the inflexibility of the product. Lehugo

I see the same issue upon trying to edit Product Knowledge from the Authoring Console. We run Windows XP with Office 2007, VSTOR is installed in the same language as the Office Pro is. No KB2251419 is listed in the appwiz. I haven't found any solution for this yet too, guess the best chance we have is to edit the plain XML Files of the Management Packs to include Product Knowledge or is there any chance that MS Devs care for this issue ? Regards Marco

it seems that not so much SCOM user use the SCOM function "product knowledge". Because of that i don't see any chance that the MS Devs will fix the issue. Summary: 1. If you want to edit product knowledge you need Microsoft Office Word. 2. If you have Word you can edit product knowledge, but you never should install security updates or service packs for Office Word on your PC otherwise you can't edit product knowledge anymore. Lehugo