Build Warning -1027 Not Issued When Timestamp Not Generated

[#1]

Summary

Prior to IS 2015, when a build fails to create a timestamp for the signature, a build warning -1027 is issued. Starting from IS 2015 however, no warning or error appears even if the resulting build has no timestamp on the signature.

Symptoms

Prior to IS 2015, when a build fails to create a timestamp for the signature, a build warning -1027 is issued. Starting from IS 2015 however, no warning or error appears even if the resulting build has no timestamp on the signature.

Cause

This behavior is caused by an issue with InstallShield 2015.

Steps To Reproduce

Steps to Reproduce:

1. File > New > Basic MSI project.
2. Add a file to the project.
3. In the Releases view, add a new release.
4. Select the Release and go to the Signing tab.
5. Configure the release to sign setup.exe in the Sign Output Files option.
6. Add a sample certificate either through the store or by browsing to the pfx file.
7. Build the release.
8. Right click the setup.exe, choose properties, and under the Digital Signatures tab, verify that a timestamp exist.
9. Disconnect the build machine from internet and rebuild the project.
10. Recheck the Digital Signatures tab in the properties of the rebuilt setup and verify that the timestamp is missing.

Resolution

This issue has been resolved in InstallShield 2016.

[Guy_Clements]

I've started getting the same thing with InstallShield 2016. Not sure when this started as signing still occurs - just not with a timestamp which throws -1027 warnings.

Signing from CLI works fine when I use the cert authority URL.

Anyone else seeing this?

Guy