Unable to create MSI: Error during Build

CChong · ‎Jun 18, 2003

Help Please???

I'm using AdminStudio 5.01, and during the build process, I recieve an error in the log (see below). The process never continues pass the build log, and I am unable to build the MSI file. Any suggestions?

Thanks in advance,

Curtis

Wednesday, June 18, 2003 10:40:18AM
Starting conversion
Creating Developer project: E:\AdminStudio Shared\Domino.doc\Packaged\Lotus Domino.Doc Desktop Enabler.ism
Reading repackager output file
Loading registry entries
Creating components for the files captured
Mapping registry information to the Advertising tables
Mapping typelib data from registry information to the TypeLib table
Undefined typelib '{000204EF-0000-0000-C000-000000000046}': no component exists for file '%SystemFolder%\MSVBVM60.DLL'. This may result in ICE33 warnings.
Undefined typelib '{EA544A21-C82D-11D1-A3E4-00A0C90AEA82}': no component exists for file '%SystemFolder%\MSVBVM60.DLL'. This may result in ICE33 warnings.
Mapping COM data from registry information
Undefined CLSID '{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}': no component exists for file '%SystemFolder%\MSVBVM60.DLL'. COM registry entries for CLSID '{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}' will remain in the Registry table because file '%SystemFolder%\MSVBVM60.DLL' was not listed in the .inc file list. This may result in ICE33 warnings.
Mapping Application IDs from registry information and writing to the AppId table
Mapping ProgIDs from registry information
Writing to the Class table
Mapping file extensions and MIME types from registry information to the Extension and Mime tables
Mapping shell extension verbs from registry information to the Verb table
Writing to the ProgId table
Mapping application paths from registry information
Mapping environment variables from registry information to the Environment table
Processing .INI file changes and writing to the IniFile table
Applying merge modules
An unknown error occurred
Conversion completed with 3 warning(s).
Output file:
Log file created: E:\AdminStudio Shared\Domino.doc\Packaged\Build Log.txt

praveenl · ‎Jun 18, 2003

In the Repackager IDE, under the Repackaged Output | Advanced Settings node, uncheck the 'Replace files with merge modules whenever possible' and rebuild the msi. See if that works.

CChong · ‎Jun 18, 2003

Thanks.... This worked perfectly. Is this a bug or a feature?

praveenl · ‎Jun 18, 2003

It should worked either way. Some users do not want merge modules to be included. Hence the option. But if you need the packaged MSI with merge modules in it and the msi fails to build, its a bug.