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.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Solved
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
‎Apr 23, 2018
01:43 PM
Digitally Signing not working from command-line Stand-Alone
Digitally signing works properly in my development environment, but fails on the build machine (where it is using SAB). What could be the issue?
On development machine, I can run via IsCmdBld.exe and it shows:
But on the build machine, it shows:
There are no other error details. How can I go about troubleshooting this?
The pfx file is in the same place on both machines. I have even tried copying the exact files from my development box to the build machine.
The only difference I can think of between the environments is that my development box has the full installation of InstallShield, while the build machine has the SAB version of it.
On development machine, I can run via IsCmdBld.exe and it shows:
AppId table successfully built
Started signing FB6.tmp ...
Property table successfully built
But on the build machine, it shows:
AppId table successfully built
Started signing F7E5.tmp ...
ISDEV : fatal error -1027: Failed signing F7E5.tmp
There are no other error details. How can I go about troubleshooting this?
The pfx file is in the same place on both machines. I have even tried copying the exact files from my development box to the build machine.
The only difference I can think of between the environments is that my development box has the full installation of InstallShield, while the build machine has the SAB version of it.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 26, 2018
09:05 AM
I sign with both Full and SAB versions. Verify that you are using a fixed path for the certificate rather than a relative path... which would change for SAB machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 26, 2018
10:16 AM
It was not a problem with the relative paths, nor was it an issue with Full vs. StandAlone.
The issue was that I had SP2 installed on my development machine, but the SAB did not have SP2 installed.
The issue was that I had SP2 installed on my development machine, but the SAB did not have SP2 installed.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)