1. Create a new 64-bit merge module. It can be either x64 or Itanium 2. Add a file 3. Compile. The message 'This merge module does not meet the Windows Installer SDK merge module naming convention. Do you want to fix it automatically?' appears. 4. Click Yes 5. Compile. Again, you receive the message regarding the Windows Installer SDK naming convention.
When the merge module is initially created or opened, it has the following 6 folders in the Directory table: SystemFolder, ProgramFilesFolder, CommonFilesFolder, System64Folder, ProgramFiles64Folder and CommonFiles64Folder. None of these folders have the .<guid> after them as expected in a merge module.
When you click Yes to adhere to the naming convention, all of these directories get the .<guid> added. However, the directories without the .<guid> also get added back. Each time you compile, if you select 'Yes', then another set of directory.guid gets added to the table which can cause many duplicates to appear.
This issue has been fixed in Wise Installation Studio/Express 7 SP1.The fix for this issue will also be included with the next release of Wise Package Studio.
A hotfix was created for the issue in knowledgebase article #33095, which is also regarding merge modules. The code change required for this hotfix, also resolves the issue regarding the Windows Installer naming convention message to constantly appear. Please see article
#33095 to obtain this hotfix.
Workaround (if you are unable to install the hotfix): Select No when prompted. This will leave the directories without the .<guid>. Since they are Windows Installer properties, leaving them without the .guid should should not cause any problems.
Applies To Wise Package Studio 7.0 SP2 Wise Installation Studio 7.0
ID: LB 57565
Logged in Littlebuggy (Altiris - Lindon, Plymouth) database
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Didn't find the article you were looking for? Try these resources.