Community Forums
Results 1 to 3 of 3

Thread: Digitally Signing not working from command-line Stand-Alone

  1. #1
    Join Date
    Nov 2005
    Location
    Waterloo, ON, Canada
    Posts
    15

    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:
    Code:
    AppId table successfully built
    Started signing FB6.tmp ...
    Property table successfully built
    But on the build machine, it shows:
    Code:
    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. #2
    Join Date
    May 2007
    Location
    Eden Praire, MN
    Posts
    762
    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.

  3. #3
    Join Date
    Nov 2005
    Location
    Waterloo, ON, Canada
    Posts
    15

    Solved

    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •