Adminstudio Repackager stuck at Processing .INI file when creating .msi
I´m creating a msi package of a simple application, and I´m using monitoring option to create a package (not snapshot method), and the build process is stuck at "Processing .INI file changes and writing to the IniFile table". It stays there forever, no hdd activity is seeing. I´ve been using AdminStudio before, and I remember that I never could do a succsessfull msi package using monitoring method, I always used snapshot method. But now I´m required to use monitoring.
Entire job log:
Starting conversion ...
Creating InstallShield project: C:\Packages\MSI_Package\KMPlayer.ism
Creating InstallShield project: C:\Packages\MSI_Package\KMPlayer.Context.ism
Reading repackager output file
Loading registry entries
Applying language 'English (code 1033)' to the project
Creating components for the files captured
Mapping registry information to the Advertising tables
Mapping typelib data from registry information to the TypeLib table
Mapping COM data from registry information
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
Or it could be that it is an .ini file, but it doesn't conform to .ini files standards Installshield is expecting and therefore hangs.
Normal .ini files usually have square-bracketed heading sections followed by settings underneath:
I've seen it before where something isn't quite right and it can't be added to the INIFile table.
The solution is to treat the .ini file as a standard file, so that it isn't in the INIFile table. I think there is an option in the Repackager to set this (somewhere), or you could let the monitoring finish and remove the entry for the offending .ini file. Build and then edit the MSI and add the .ini file in as a flat file.
Hope that helps,