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
- :
- Re: InstallShield 2009
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 09, 2009
07:05 AM
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 ?
ASDEV : warning -5032: Failed to sign the setup launcher.
any Idea what can be done to fix this issue ?
(8) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2009
03:26 PM
Make sure your url to the timespamp file is correct. Also double check paths and passwords.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2009
04:16 AM
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?
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?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2009
07:55 AM
Will it sign any of your files or the msi and not the setup.exe?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2009
07:11 PM
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?
1. Media folder -> Releases
2. Select the Release then select Signing tab.
3. Digital certificate file (SPC or PFX) textbox =
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?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2009
07:24 PM
IS someone else linked to the certitifcate and using it while you were compiling? Does someone has the certificate open?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 14, 2009
04:05 AM
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 ?
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 ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 14, 2009
09:30 AM
I just remembered something. I always have to install the certificate on my machine (especially if you are using stand alone build).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 14, 2009
01:53 PM
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.
😉
Still having error?
2. Try downloading a new certificate. The one you have might be corrupt.
Will this fix your issue? Try them.
😉