This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 22, 2014
02:19 PM
Error -7184 when Merging Modules
I've ported a project from IS2010 to IS2014 where code was developed using VS2008. I had the port working, but then installed VS2010 SP1. Now, I get error -7184 when merging modules:
Merging modules...
Merging Microsoft Component Category Manager Library: D:\InstallShield\IS2014\Modules\i386\COMCAT.MSM
Merging MFCDLL Shared Library - Retail Version: D:\InstallShield\IS2014\Modules\i386\MFC42.MSM
Merging MFCDLL Shared Library - Retail Version: D:\InstallShield\IS2014\Modules\i386\MFC42U.MSM
Merging Microsoft (R) C++ Runtime Library: D:\InstallShield\IS2014\Modules\i386\MSVCP60.MSM
Merging Microsoft (R) C Runtime Library: D:\InstallShield\IS2014\Modules\i386\MSVCRT.MSM
Merging Microsoft OLE 2.40 for Windows NT(TM) and Windows 95(TM) Operating Systems: D:\InstallShield\IS2014\Modules\i386\OLEAUT32.MSM
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "?"
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "21BA~1|?"
(about 12 lines of this)
I tried changing the redistributables to eliminate some older modules that will not be needed, but I still get the error, but with a different merge module, for example:
Merging modules...
Merging Microsoft Component Category Manager Library: D:\InstallShield\IS2014\Modules\i386\COMCAT.MSM
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "?"
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "21BA~1|?"
The various msm files in my local IS2014 modules folder are the same as in the Program Files (x86)\Common Files\Modules folder. It seems that perhaps something in VS2010 SP1 has incompatible msm files?
Merging modules...
Merging Microsoft Component Category Manager Library: D:\InstallShield\IS2014\Modules\i386\COMCAT.MSM
Merging MFCDLL Shared Library - Retail Version: D:\InstallShield\IS2014\Modules\i386\MFC42.MSM
Merging MFCDLL Shared Library - Retail Version: D:\InstallShield\IS2014\Modules\i386\MFC42U.MSM
Merging Microsoft (R) C++ Runtime Library: D:\InstallShield\IS2014\Modules\i386\MSVCP60.MSM
Merging Microsoft (R) C Runtime Library: D:\InstallShield\IS2014\Modules\i386\MSVCRT.MSM
Merging Microsoft OLE 2.40 for Windows NT(TM) and Windows 95(TM) Operating Systems: D:\InstallShield\IS2014\Modules\i386\OLEAUT32.MSM
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "?"
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "21BA~1|?"
(about 12 lines of this)
I tried changing the redistributables to eliminate some older modules that will not be needed, but I still get the error, but with a different merge module, for example:
Merging modules...
Merging Microsoft Component Category Manager Library: D:\InstallShield\IS2014\Modules\i386\COMCAT.MSM
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "?"
ISDEV : error -7184: The FileName column of the File table includes characters that are not available on code page 1252: "21BA~1|?"
The various msm files in my local IS2014 modules folder are the same as in the Program Files (x86)\Common Files\Modules folder. It seems that perhaps something in VS2010 SP1 has incompatible msm files?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 29, 2014
12:45 PM
I needed to configure the build to use UTF=8 on the build tab for the release.