Installshield Build Error -1027

Title

Summary

"Error -1027: Failed signing [1]"

Symptoms

When building a project with Installshield, the following error may occur:

"Error -1027: Failed signing [1]"

[1] is a placeholder that contains the filename, such as Data1.cab, that could not be signed.

Cause

There is a problems with the digital signature. Check the digital signature information (digital keys and password) provided for the current release. See below for potential solutions.

Resolution

The File Does Not Support the Hash of the Signature
Starting from IS 2015, InstallShield signs the files with the same hash of the certificate that is specified. Certain files do not support a SHA-256 certificate and will cause this error to occur. Currently, the workaround is to use a SHA-1 certificate or to exclude the files that cannot be signed with a SHA-2 hash.

The Digital Signature Password Specified During the Build is Incorrect
Verify the password entered for the digital signature in the Digital Signature panel of the Release Wizard is accurate. Note this password is case-sensitive. If in doubt, contact the digital signature issuer or certificate authority, such as VeriSign, for the correct password.

Another way to verify if the password is accurate is by manually calling the utility "signtool.exe" to sign a file. This file is located, by default, in <PROGRAMFILES>\InstallShield\<Product>\Support. Additional information on the command-line parameters to pass to digitally sign a file can be found in the Signing Software with Netscape Signing Tool 1.1. If the signing process fails using this method as well, it is safe to assume that the password is incorrect.

One or More of the Digital Signature Files is Missing

Verify that .spc and .pvk files were entered for the digital signature in the Digital Signature panel of the Release Wizard.

The Digital Signature Files Have Expired and are, therefore, Invalid.
Digital Signatures are Only Valid for a Limited Time and Can Cause this Error When Expired. If the digital signature has expired, contact the digital signature issuer, such as VeriSign, to purchase a new digital signature. The "signtool.exe" utility can be used to manually sign a file, to ensure it works correctly. This would easily determine if the problem is caused by an expired or incorrect password or for some other reason.

The Digital Signature Syntax Entered Into the "Build Your Release" View is Incorrect

The information entered in the Digital Signature panel of the Release Wizard must be accurate for the signing to complete properly. Make sure the URL specified is accurate, and the .spc and .pvk files specified are located in the path indicated.

The File "Signtool.exe" is Not Present on the Build Machine

When building from the command-line utility IsSaBld.exe (InstallShield 2008 and older) or IsCmdBld.exe (InstallShield 2009 and later) on a Standalone build machine and the file "Signtool.exe" is not present on the build machine.

Search for the file "signcode.exe" in the <PROGRAMFILES>\InstallShield\StandaloneBuild directory. If this is not present, manually copy it to this location from one of the following sources:

- A machine that has the full version of the InstallShield IDE installed. This file can be found in the following location: <PROGRAMFILES>\Macrovision\<Product>\System.
- The InstallShield CD. Perform a search in Windows to locate this file on the CD itself.

The Caps Lock Key is Enabled

Disable the Caps Lock key.

EV Code Signing Certificate May Be Corrupted
If you are trying to sign using an EV digital certificate and you are seeing this build error occur, you may want to try checking the value of the following registry key using 'regedit.exe'.

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Cryptography/Providers/SafeNet Smart Card Key Storage Provider/Aliases

Now the value should be 'eToken Base Cryptographic Provider', but you may see 'eToken Base Cryctographic Provider' (...where there is a 'c' instead of a 'p'). If this is the case, change the 'c' to a 'p' so it reads 'Cryptographic', then save your changes and reboot the system. Now if you try building your project with the EV digital certificate, it should work as expected.

Additional Information

Further details on VeriSign may be found at the VeriSign Website.

Additional information on digital signing can be found in the InstallShield Help Library document Digital Signing and Security.

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Summary

Symptoms

Cause

Resolution

Additional Information

Related KB Articles

Files

Please wait...

Summary

Symptoms

Cause

Resolution

Additional Information

Related KB Articles

Related Articles

Please wait...

Case id: 00001065