Windows Installer error 1911 in VBAHELPFILES_EN merge module

Article:TECH7830  |  Created: 2005-09-07  |  Updated: 2005-09-12  |  Article URL http://www.symantec.com/docs/TECH7830
Article Type
Technical Solution

Issue



Windows Installer error 1911: "Could not register type library for file APC60.dll. Contact your support personnel." results from adding the VBAHELPFILES_EN merge module to and .MSI installation.

Environment



Any Windows Installer version
Any Windows Operating System

Cause



This error indicates that the file in question (generally a .DLL) is referenced in the TypeLib table, and the Windows Installer cannot register this file using via the TypeLib table. The TypeLib table is used to register ..TLB files. 1911 errors are generated when other file types are referenced in this table. 

Solution



There are two ways to resolve this issue:


  1. The best way to resolve this would be to remove the entry from the table in the .MSM otherwise each time the .MSM is added to an installation package because it is a merge module and will only show up in the MSI.

    Error 1911 - Could not register type library for file [2]. Contact your support personnel.
    This generally occurs when the file specified in the error message is in the TypeLib table, but the RegisterTypeLibraries action cannot register the file.

    NOTE: Wise Solutions Technical Support, with the assistance of Wise customers, has compiled information concerning Microsoft Windows Installer error messages. This article is provided for reference. Although specific solutions are outlined, there may be multiple causes for some of the Windows Installer errors, and the solutions discussed may not resolve the error in all circumstances.
    *****

    Type library files contain type library information for various other files to be installed on the machine. In most situations, this information is only useful for applications that link to development objects such as COM servers.

    If you do not need to register your type library file, navigate to the Setup Editor, select the Tables tab, then select the TypeLib table. Locate the file indicated in the error message. Right-click on the row containing this file and select Delete Row(s). Save, compile, test, and run. The error message should now be gone.

    If you need type library information for a specific application to be available to Visual Basic or other programming/scripting language in order to interface with the object easily, then you need to clear the row from the TypeLib table as above and register the type library file manually. To do this, use a custom action to call the Windows utility Regtlib.exe and pass the name of the type library as an argument.

    The best method for calling this custom action is to use the 'Execute Program from Installation' custom action sequenced after the InstallFinalize action in the Execute Immediate sequence. By using this type of custom action, where Regtlib.exe will be stored in the binary stream, you will ensure that the Regtlib.exe utility is available to each target machine.

    On the Details tab of the Execute Program from Installation dialog enter the following information:

    *Custom Action Name: Any name you wish - use to self-document the installation

    *Executable File: The location of Regtlib.exe on the development machine. When the installation is compiled, Regtlib.exe will be incorporated into the binary stream.

    *Command Line Arguments: any command line switches and the path to the type library file.

    It is not necessary to change any options on the Properties tab.

    Please consult Microsoft for information about the Regtlib.exe utility.

    *****
    The full error messages for 4-digit Windows Installer error codes can be found in the Windows Installer SDK. More information may also be available at Microsoft's web site .

    Wise Solutions will continue to add information to this article as it becomes available. If you have additional information that you believe would contribute to the value of this article, please enter it in the comment field associated with this Knowledgebase article.

Legacy ID



1620


Article URL http://www.symantec.com/docs/TECH7830


Terms of use for this information are found in Legal Notices