Quantcast
Channel: Internet Explorer Web Development forum
Viewing all articles
Browse latest Browse all 3527

ActiveX control is not working with IE11

$
0
0

Hi,

I am facing a very weird problem with my already working .Net application that has stopped working with IE11. In my application I have an ActiveX control build in 64 bit platform     that resides under both folder "C:\program Files\OWAConfig.ocx" and "C:\program Files(x86)\OWAConfig.ocx" , when i am running this control on IE11 browser , I am getting an Error "Automation Server can't create an object". I have investigated the problem and I found that activeX control and HTML page are handled as content process in IE11 that runs as 32 bit browser application. Since my control is built in 64 bit that’s why 32 bit browser is not supporting 64 bit ActiveX control. I tried few solution to run IE browser in 64 bit, but that also didn’t work for me. The tried solutions are-

  1. Adding a new registry key “tabProcGrowth” as string and I have fixed it with 0 value. This caused my ActiveX control working but the problem with this is if I am trying to browse any other application directly from IIS, I am not able to open it. And also I don’t know if this registry setting may harm the system in any way.
  2. There is an option in IE settings, Internet Options->Advanced ->enable enhanced protected mode-> restart the system, and I read somewhere that this setting will set the browser to run in 64 bit. But it also didn’t work for me.

So is there any way to open IE11 as 64 bit so that I can run my ActiveX control without getting “automation server can’t create object”. I don’t want to change my application to build itself as 32 bit as on other browser it is working fine.

Waiting for early response.                                                                                                                   

Regards

Sonam



Viewing all articles
Browse latest Browse all 3527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>