Deployment problem with the MS Web Browser Control
-
We have an issue with using the IE ActiveX control where about 1 in 20 users are expriencing total system lockup when our application loads. The application is being deployed with the following files: AxInterop.SHDocVw.dll Interop.SHDocVw.dll partial.mshtml.dll The partial.mshtml.dll file comes from SharpReader[^], and by all accounts fixed their deployment problems, which are similar to our own. I have extensive trace output in the app, and can verify that the point of lockup is when the web browser control is instantiated. Please note that I am navigating to about:blank in the constructor to ensure the control has a handle. Has anyone else ran into similar problems deploying a C# app with the IE control? if so, any ideas?
-
We have an issue with using the IE ActiveX control where about 1 in 20 users are expriencing total system lockup when our application loads. The application is being deployed with the following files: AxInterop.SHDocVw.dll Interop.SHDocVw.dll partial.mshtml.dll The partial.mshtml.dll file comes from SharpReader[^], and by all accounts fixed their deployment problems, which are similar to our own. I have extensive trace output in the app, and can verify that the point of lockup is when the web browser control is instantiated. Please note that I am navigating to about:blank in the constructor to ensure the control has a handle. Has anyone else ran into similar problems deploying a C# app with the IE control? if so, any ideas?
I doubt this would cause a lockup, but what versions of Internet Explorer are the 1 in 20 users using? If the partial.mshtml.dll was created with a newer version that those few users don't have, and you're trying to use those newer interfaces that don't exist in the MSHTML DOM, this would most likely cause a problem. Your installer should make sure they have the proper version (or higher) of IE.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
-
I doubt this would cause a lockup, but what versions of Internet Explorer are the 1 in 20 users using? If the partial.mshtml.dll was created with a newer version that those few users don't have, and you're trying to use those newer interfaces that don't exist in the MSHTML DOM, this would most likely cause a problem. Your installer should make sure they have the proper version (or higher) of IE.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
I am working closely with one affected user on the issue. He is using Win98SE, with IE 6 SP1. I have added a bunch of trace output to the app, and the total system lockup is happening right after the ActiveX is instantiated, when the control would be receiving a handle I guess. I've tried compiling the app for both 1.0 and 1.1 framework versions, and I've referenced & distributed the entire Microsoft.mshtml.dll assembly. As for the control itself, I am only calling the Navigate method, and catching the OnNavigateComplete2 event - nothing else. Note that I have 26 other people using the app with Win98 + IE 5-6 without problem, but this one fellow is experiencing lockups on both of his Win98 SE systems. Outside of him, who knows how many people have dismissed the app as inoperable and simply not advised me!
-
I am working closely with one affected user on the issue. He is using Win98SE, with IE 6 SP1. I have added a bunch of trace output to the app, and the total system lockup is happening right after the ActiveX is instantiated, when the control would be receiving a handle I guess. I've tried compiling the app for both 1.0 and 1.1 framework versions, and I've referenced & distributed the entire Microsoft.mshtml.dll assembly. As for the control itself, I am only calling the Navigate method, and catching the OnNavigateComplete2 event - nothing else. Note that I have 26 other people using the app with Win98 + IE 5-6 without problem, but this one fellow is experiencing lockups on both of his Win98 SE systems. Outside of him, who knows how many people have dismissed the app as inoperable and simply not advised me!
Man, I don't know. :confused: How much memory does this person have in his machines? I mean, the .NET Framework would throw an exception and exhausting the memory wouldn't lock up the system, but it might appear that way. I doubt this is the problem, though. Have you checked the MS KB? Besides that, all I can think to tell you is to post a message to an appropriate MS newsgroup (msnews.microsoft.com), but I doubt that'll help since replies to more advanced or "odd" problems like this almost never get answered.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
-
Man, I don't know. :confused: How much memory does this person have in his machines? I mean, the .NET Framework would throw an exception and exhausting the memory wouldn't lock up the system, but it might appear that way. I doubt this is the problem, though. Have you checked the MS KB? Besides that, all I can think to tell you is to post a message to an appropriate MS newsgroup (msnews.microsoft.com), but I doubt that'll help since replies to more advanced or "odd" problems like this almost never get answered.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----
Heath Stewart wrote: How much memory does this person have in his machines? One has 64MB, the other 128MB, however my low-end test machine (that runs the app fine) has just 56MB usable RAM (8 MB is taken up by the video card). Heath Stewart wrote: Have you checked the MS KB? Yes. The only possibly related article I could find was a COM import bug in fx 1.0 that was fixed in 1.0 SP1. However, compiling the app for fx 1.1 should have worked around this issue if it was the problem. Heath Stewart wrote: Besides that, all I can think to tell you is to post a message to an appropriate MS newsgroup Have now posted the problem to microsoft.public.dotnet.framework, but as you noted and I've personally experienced, difficult questions seem to get lost in the ether... Thanks for your help anyway Heath