Installation .EXE files with custom prerequisites are not signed during compile

Article:TECH12946  |  Created: 2006-03-15  |  Updated: 2007-01-08  |  Article URL http://www.symantec.com/docs/TECH12946
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Issue



Installation executables (Single-file, External, or WebDeploy) do not have a digital signature, even though the Digital Signatures page is configured.  The installation .MSI file is signed.

Environment



Wise for Windows Installer 6.2
Wise Package Studio 6.01

Cause



 


Solution



This issue is fixed in Wise Installation Studio/Express 7.0 and Wise Package Studio 7 SP2.

Workaround:

  1. Go to the Prerequisites page in the Installation Expert view.
  2. Finalize the list of custom prerequisites.
  3. Click Edit Script.
  4. A warning will display. Click Yes. The installation may compile. The custom prerequisites script will open in WiseScript Express.
  5. Do not make any changes, just close WiseScript Express. Back in Wise for Windows Installer, the custom portion of the Prerequisites page will be disabled. This is necessary.
  6. Open Windows Notepad.
  7. From the File menu in Notepad select Open.
  8. Change Files of Type to All Files.
  9. Browse to your installation project directory and open the .WSE file associated with your project. It will usually be named the same as your .WSI project file. This will open the .WSE in text format.
    A few lines from the top of the script you should see the line for "Extra Flags".
    Existing Line:
           Extra Flags=00000000000000000000010100000000
  10. Modify the line to read:
           Extra Flags=00000000000000000001010100000000
    Basically, you will replace the 20th "0" with a "1".
    If the Extra Flags line does not exist, add it exactly as shown above between "item: Global" and the first "end" statement.
  11. From the File menu in Notepad, select Save.
  12. Close Notepad.
  13. In Wise for Windows Installer, Compile the installation.
  14. Use signcode.exe from a command prompt to sign your installation executable.
    signcode.exe -spc "<path to .spc file>" -v "<path to .pvk file>" -t http://timestamp.verisign.com/scripts/timstamp.dll "<path to installation executable>

Once steps 1–13 are complete, you will only need step 14 to sign the .EXE going forward (after each Compile). The only way you will need to repeat all of the steps is if the .WSE script is deleted, or reset using the Reset Script button on the Prerequisites page.

If you receive the following error when trying to execute the installation, you will need to perform steps 6–14 again: "Could not Initialize Installation. File size expected=nnnnn, size returned=nnnnn".


Supplemental Materials

SourceDEFECT
ValueLB 47093
DescriptionLogged in Littlebuggy (Altiris - Lindon, Plymouth) database

Legacy ID



20699


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


Terms of use for this information are found in Legal Notices