PRB: "License Information for This Component Not Found" Error

Last reviewed: March 13, 1998
Article ID: Q177799
The information in this article applies to:
  • Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

When you try to add a control to a form, the following message may appear:

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

CAUSE

When a control is installed for run-time use only (such as those installed by an application created with Visual Basic), if the Visual Basic Development Environment is installed onto the same machine afterwards and the existing control is of equal or higher version than that from the CD, the license key for that control is not updated.

RESOLUTION

If the control in question is any of the ones listed below, then find the file Vbctrls.reg in the VB5.0\Tools\Controls folder on the Visual Basic CD- ROM and double-click the file:

   AniBtn32.ocx
   Gauge32.ocx
   Graph32.ocx
   Grid32.ocx
   KeySta32.ocx
   MSOutl32.ocx
   Spin32.ocx
   Threed32.ocx

This will update the design-time licenses for these controls. For more information please, refer to the Readme.txt file in the same folder.

If the control in question is not among the controls listed above, please do the following:

  1. Locate Regsvr32.exe on your machine. Note its path.

  2. Locate the offending OCX file(s), usually found in the Windows\System folder for Windows 95 or Windows\System32 folder for Windows NT.

  3. On the Start menu, click Run.

  4. In the Run dialog box, type the following:

          <Path to RegSvr32>\REGSVR32.EXE /u <Path to OCX>\OCXFILE.OCX
    

    For example:

          C:\Devstudio\VB\REGSVR32.EXE /u C:\Winnt\System32\COMCTL32.OCX
    

    NOTE: If Regsvr32.exe is in the System or System32 folder, the path is optional.

  5. Repeat steps 3 and 4 for each offending OCX.

  6. On Control Panel, click Add\Remove Programs.

  7. Select Visual Basic, and click Add\Remove.

  8. Click Reinstall when the options (Add\Remove, Remove All, Reinstall) dialog box appears.

    If the problem persists, please see the following article in the Microsoft Knowledge Base:

          ARTICLE-ID: Q181854
    
          TITLE     : FILE: Vbc.exe Fixes VB 5.0 Control Installation Problem
    
    

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Set up a Windows 95 or Windows NT machine, Machine A, without Visual Basic 5.0 installed. Then set up a development machine, Machine B, with Visual Basic 5.0 and Service Pack 3 installed.

  2. On Machine B, create a Standard EXE project. Form1 is created by default.

  3. Add the following component (OCX) to the Toolbox:

          Comctl32.ocx
    

  4. Add at least one control from this OCX to Form1.

  5. Compile and save the project.

  6. Create a setup application using the Visual Basic Application Setup Wizard, selecting all default options.

  7. Install the application onto Machine A.

  8. Install Visual Basic 5.0 on Machine A.

  9. Start a Standard EXE project and add Comctl32.ocx to the Toolbox.

    Try to add any of the controls from this OCX, and this error message appears:

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

REFERENCES

For additional information, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q172193
   TITLE     : INFO: List of VB 4.0 Custom Controls Discontinued in VB 5.0

   ARTICLE-ID: Q181854
   TITLE     : FILE: Vbc.exe Fixes VB 5.0 Control Installation Problem
Keywords          : vb5all VBKBCtrl VBKBError kberrmsg
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug kbinfo
Solution Type     : kbpending


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 13, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.