Closed
Bug 206587
Opened 21 years ago
Closed 21 years ago
ActiveX error cannot create control {00000000-0000-0000-0000-000000000000}
Categories
(Core Graveyard :: Embedding: ActiveX Wrapper, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: euston, Assigned: adamlock)
References
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.10 [en]
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507
Full error message is "Could not create control
{00000000-0000-0000-0000-000000000000} Check that is has been installed on your
computer and that this page correcty references it." This error started popping
up after a failed install of spider.ocx activex control used by the company I
work for (it is used by the web interface for Test Director). The error comes up
when accessing a page that uses activex (such as www.advfn.com), stops the
browser, and will not continue until you hit OK. This can happen several times
before the page finishes loading. Makes Mozilla usable but intensly irritating.
I've installed new versions etc, with no change. i think the ActiveX config is
broken within mozilla, but don't know how to fix. Does not affect Opera or
Explorer running on same machine. The control listed (000000) is not listed as
being installed anywhere.
The bug is that a) the control should be removable b) ActiveX controls in
general are not editable within the browser
Reproducible: Always
Steps to Reproduce:
1. Access test director. Spider.ocx will attempt to install
2. error spider.ocx not found. Test director will not run. This is a test
director fault. (it only works with netscape 4 and explorer)
3. afterward, activex error occurs when accessing www.advfn.com
Actual Results:
see above
Expected Results:
allow you to delete the broken control
can supply config files, screen shots, registry bits etc as required. (i'm a
professional tester)| Reporter | ||
Comment 1•21 years ago
|
||
Sorry - hit reload button, and an extra bug (#206588) created. Please delete this one.
Comment 2•21 years ago
|
||
*** Bug 206588 has been marked as a duplicate of this bug. ***
This has already been fixed, but the precompiled plugin on my site has not been updated for a while because all the code is in a massive state of flux.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
QA Contact: mdunn → ashishbhatt
| Reporter | ||
Comment 4•21 years ago
|
||
Sorry to re-open this, but I have just upgraded to Mozilla 1.4RC, and this is still a problem. ie, it is still not fixed. Why doesn't 1.4rc have the fix? (if indeed it is fixed)
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
It is fixed, I checked in the fix to not show that particular error a long time ago. However as I said in comment 3, the binary on my site is old and contains the issue. It doesn't matter what version of Moz you use with it since the problem is in that plugin not Moz. The binary will be updated when I have the time to fix bug 203704. I will also intend to produce a special version COM connect enabled version of the plugin for 1.4, but I'm waiting for the final release before doing that.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 6•21 years ago
|
||
For anybody who has this problem, I have a fix I worked out myself in the end. Although Adam has not put the fix into Mozilla's 1.4 install, you can get rid of it by re-installing the plugin with the following link : http://mozillako.hypermart.net/activex/ Click in "install activex plugin" - and it will fix the problem. I'm not sure if the reason this works is because it installs the newer plugin code, but it fixes the problem I've had for months thats been driving me up the wall.
Updated•12 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•