Blog

CodePartners Blog

rss


What to Do When Error HRESULT E_FAIL Returns from a Call to a COM Component

SHARE THIS
Facebook twitter linkedin Print Print
Print Email

By Derek Du

For a recent project, we figured out a way to use Windows.Forms.WebBrowser in an Asp.net application, and I have written a blog about it. Later we found that after the application had run for a while, it would throw out an exception from the web application that prevented the application from using the web browser control until the application pool was restarted. The error message was “Error HRESULT E_FAIL has been returned from a call to a COM component.” 

Some of us believed that it was because of some bugs in the WebBrowser control itself. Some said it was due to some communication error with the underlying transaction manager, and a solution for that is to configure the MSDTC (Distributed Transaction Coordinator) in the following way. 
 

Originally, I didn't think this was it. Although I was using TransactionScope in my code, the WebBrowser control was not part of the transaction. But, after I configured it this way, the error never happened again.  

I hope someone can give me a more convincing explanation as to why this error occurred.

Below are all the steps for configuring MSDTC. 

 
 

 

 

 

References:

Enable Network DTC Access

Error HRESULT E_FAIL has been returned from a call to a COM component 



Comments are closed.
On July 25, 2013 in Development [Post:by]
Tagged With: Asp.net, COM component, HRESULT E_FAIL, MSDTC, Web Browser Control, Windows Form / 37075 Views

Search

Categories

Archives