HRESULT E_FAIL Error?

[Mertli Ozgur Nevres]

Hi all, i have a program which is using AxWebBrowser. It was working well under .net framework 1.1. But after upgrading .net framework 2.0, at SOME systems, i receive the error below: System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. at SHDocVw.IWebBrowser2.Navigate(String URL, Object& Flags, Object& TargetFrameName, Object& PostData, Object& Headers) at AxSHDocVw.AxWebBrowser.Navigate(String uRL, Object& flags, Object& targetFrameName, Object& postData, Object& headers) does anyone know why it occurs, and how can i fix that problem? thanks. ozgur.nevres

[Dave Kreskowiak]

On these "SOME" systems, do they have IE 6.0 SP1 or greater installed? Under .NET 1.0 and 1.1, only IE 5.0 was required. This changed to IE 6.0 SP1 under .NET 2.0. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

[Mertli Ozgur Nevres]

Thank you, i'll ask it to our clients. But one of our client who is getting this error, has aldready installed ie7.0 Beta. Does it cause the same problem? ozgur.nevres

[Dave Kreskowiak]

You'll have to test it. But that's when you tell the customer that since IE7 is a Beta product, you won't support that configuration. After all, how can you support your application when a component that it needs is not stable. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

[Mertli Ozgur Nevres]

"But that's when you tell the customer that since IE7 is a Beta product, you won't support that configuration." it is not easy as you say :-) But now i am using .net2.0's WebBrowser component and it is working without a problem. Thanks for your care ozgur.nevres

[Dave Kreskowiak]

Mertli Ozgur Nevres wrote:

it is not easy as you say

Sure it is! You tell them that your code will be tested and supported when IE7 is released. You can't be held responsible for any performance or stability issues because they're using unstable and unsupported software from another manufacturer that your code depends on. If your customer insists on using it with IE7, they're on their own. You tell them what the terms of support are. They don't get to dictate that to you because, after all, they're not writing the code, you are. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome