Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

mci32.ocx license problem

46 views
Skip to first unread message

mpe...@pclink.com

unread,
Jan 12, 1998, 3:00:00 AM1/12/98
to

I recently reinstalled Visual Interdev and VB 5 after my system crashed.
After installing VB 5, I installed sp2.

My problems is whenever I try to use the multimeda control, I receive the
following error message:

"License information for this component not found. You do not have the
appropriate license to use this functionality in the design environment"

How can this be? What can I do about it?

Thanks

-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet

Bruce Halpern

unread,
Jan 13, 1998, 3:00:00 AM1/13/98
to

I have the same type of problem with:
--------------
License information for this component not found. You don't have an

appropriate license to use this functionality in the design environment
(Error 429)

You are not a licensed user of the ActiveX control. This error has the
following cause and solution:

You tried to place an ActiveX control on a form at design time or tried to
add a form with an ActiveX control on it to a project, but the associated
information in the registry could not be found.

The information in the registry may have been deleted or become corrupted.
Reinstall the ActiveX control or contact the control vendor.

Line 13: Cannot load control tbToolBar; license not found.

Comctl32.ocx

------------------
This is after removing and reinstalling VB50 over 5 times. With SP3,
Win95a. I read that RegClean can be responsable for this problem, so I got
the v4.1a and did not run it after installing VB50 (yet again) but the
problem still persists and I can't use VB5!

Anyone who knows how to fix this and/or edit the registry to remove and/or
fix this problem, I will be in your debt forever.

Bruce Halpern
baha...@pipeline.com

(I will also be posting this problem as a separate post, sorry if it is a
repeat)


mpe...@pclink.com wrote in message <884623620....@dejanews.com>...

Bruce Halpern

unread,
Jan 13, 1998, 3:00:00 AM1/13/98
to

I just found the answer in a post about a similar question:

-----------------
Double-click on the .REG file in the Tools\Controls directory
of your
install CD.
--
Jonas
TRION Technologies (www.trion.com)
------------------------
Bruce Halpern
baha...@pipeline.com


----------------------------------------------------------------------------

Douglas Marquardt

unread,
Jan 14, 1998, 3:00:00 AM1/14/98
to

Hi Bruce:

>License information for this component not found. You don't have an


>appropriate license to use this functionality in the design environment

>(Error 429)


I had this confirmed by MS support staff -- this is a bug in the VB5 setup.
If you already have a vb application installed with any of the Service Pack
controls, and then try and install VB5, it will not properly update the
registry with license info for that control. One workaround is to
unregister and delete/move the ocx and then reinstall VB5 (and the latest
service pack).

Hope this helps,

Doug.


J.Scholten

unread,
Jan 14, 1998, 3:00:00 AM1/14/98
to

I had the same problem and got the solution from this group.

First uninstal vb5.0 restart, then
create a dir called c:\ocx copy all the *.ocx files from windows\system
to this dir, then instal vb50 restart, run the servicepack, restart,
copy all of the *.ocx files back to windows\system if asked file exist
overwrite select no, on my computers it worked.
regards,
Hans Scholten


Douglas Marquardt heeft geschreven in bericht ...

Dan Doucet

unread,
Jan 19, 1998, 3:00:00 AM1/19/98
to

I'm having a similar problem but it's with the Connection Designer.
MSCONDES.DLL is the file in question and I receive the License error
described in the previous messages. I tried your fix (double clicking the
REG file) but that didn't seem to do anything.

Originally I didn't even have access to the Designer in the components
window however I ran regsvr32.exe on MSCONDES.DLL and that at least gave the
option on the designers tab in the components window.

Have you heard anything related to this problem? Is it the same problem as
the OCX licensing problem? Any help would be greatly appreciated.

Dan Doucet
ddo...@nbpower.com

Bruce Halpern wrote in message ...

0 new messages