Tuesday, May 13, 2008

Solve Error The remote procedure call failed. (Exception from HRESULT: 0x800706BE) in Microsoft.Office.Interop service

This solution is with respect to WSS 3.0 and MOSS 2007
This error usually come when your machine or server where MOSS 2007 or WSS 3.0 is installed has not application pool identity rights in "IIS WAMREG admin Service" in dcomconfig.add application pool identity to launch and activation permission.

Note:when you are using Microsoft.office.interop service in Workflow ,there is chances of this error.Because your application pool identity is NETWORK Service user by default and workflow run under system account ,so this time you need to change application pool identity Network service user to system account.

Monday, May 12, 2008

100% Guarntee to Solve DCOM Error in MOSS 2007 or in WSS 3.0

Here is the post that will help you to solve DCOM error in MOSS 2007 or in WSS 3.0 while development.
some time you are dealing with Microsoft.Office.Interop service which is one type of DCOM.
check in event viewer error will be like this

Computer: computer name
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

The highlighted CLSID is for "IIS WAMREG admin Service" in dcomcnfg.

OK to solve this error follow the steps
  1. in RUN write dcomcnfg open DCOM Config
  2. in component service right click on My computer and select properties.
  3. in it Default properties section tab make sure that "enable DCOM on this computer is selected"
  4. now select DCOM security tab "Launch and activation section" click on EDIT default add user which gives you error in above error case user is NT AUTHORITY \NETWORK Service so add that user here. assign it Local launch and local activation permission.click ok
  5. now explore DCOM config below my computer and find IIS WAMREG admin Service and right click select properties in security section in Add user for Local launch and activation section.
  6. same thing find NETMAN in it and repeat same thing for it
  7. now restart iis
  8. it should work now generally in we need to give rights for Application pool identity user, by default it is NETWORK SERVICE user.
  9. check WSS_WPG group NETWORK SERVICE User is added or not
  10. now it should work
Special Thanks to :

Mike Hanley's Blog