Run error ActiveX component can't create object
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2012
04:40 AM
06-16-2012
04:40 AM
Run error ActiveX component can't create object
Hi,
I am executing scripts in testcomplete. I am receiving "run error ActiveX component can't create object" while creating an object in the script
Please let me know how to fix this issue.
I have a .dll file where can i add it in testcomplete ?
Thanks,
kanya
I am executing scripts in testcomplete. I am receiving "run error ActiveX component can't create object" while creating an object in the script
Please let me know how to fix this issue.
I have a .dll file where can i add it in testcomplete ?
Thanks,
kanya
3 REPLIES 3
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2012
11:15 PM
06-17-2012
11:15 PM
Hi Kanya,
Please clarify what object you want to create. Post your script here and specify on which code line the error appears. Also, please let me know which OS you have.
--
Dmitry Nikolaev
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
Dmitry Nikolaev
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2015
05:22 AM
06-11-2015
05:22 AM
var object = Connect.Sys["Browser"]("chrome");
This line when run through visual studio give me the error "Cannot create ActiveX component"
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2016
07:22 AM
08-05-2016
07:22 AM
@mithileshmaurya wrote:var object = Connect.Sys["Browser"]("chrome");
This line when run through visual studio give me the error "Cannot create ActiveX component"
I had the same issue when trying to use Connected apps on some environments.
The root cause of the issue was that TestComplete DLLs referenced in my C# project had lower version (TC10) than the TestComplete version installed on the environment (TC11).
After updating the referenced DLLs to the ones from TC11 the problem was fixed.
