cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
odsicto
Level 3

InstallShield 2009

Creating an Installation with InstallShield 2009 Professional and Certifying the Setup.exe worked fine before now I get the next Error:
ASDEV : warning -5032: Failed to sign the setup launcher.

any Idea what can be done to fix this issue ?
Labels (1)
0 Kudos
(8) Replies
rasky74
Level 6

Make sure your url to the timespamp file is correct. Also double check paths and passwords.
0 Kudos
odsicto
Level 3

Rasky74

I use the option: digital certificate file (SPC or PFX) .
After browsing to the file and pasting the password.

I get the message:
ISDEV : warning -5032: Failed to sign the setup lancher

This has nothing to do with wrong link or password.

Do you have any suggestion what can cause this?
0 Kudos
rasky74
Level 6

Will it sign any of your files or the msi and not the setup.exe?
0 Kudos
yamakamyar
Level 6

I use the following steps to sign coe:

1. Media folder -> Releases
2. Select the Release then select Signing tab.
3. Digital certificate file (SPC or PFX) textbox = myVerisignCodeSigning.pfx
4. Certificate password textbox = mypassword (type it rather than paste)

5. Check sign setup.exe and Window INstaller package.

IS this what you are doing?
0 Kudos
yamakamyar
Level 6

IS someone else linked to the certitifcate and using it while you were compiling? Does someone has the certificate open?
0 Kudos
odsicto
Level 3

Hi Yamakamyar,

I'm using 2 ways to do this:
1. Using the Release Wizard and when the screen is displayed to select the
*.pfx and type the Password.
2. Is what you meantion.

It used to work but now it's failing ?

Any Idea what can be done to fix this ?
0 Kudos
rasky74
Level 6

I just remembered something. I always have to install the certificate on my machine (especially if you are using stand alone build).
0 Kudos
yamakamyar
Level 6

1. Try Copy your certificate from the current folder to another folder then update accordingly your Installer with new location.

Still having error?

2. Try downloading a new certificate. The one you have might be corrupt.

Will this fix your issue? Try them.

😉
0 Kudos