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
- :
- Error Digitally Signing an Install Package
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
Feb 24, 2008
10:26 PM
Error Digitally Signing an Install Package
Hello,
I have created an installer and I want it to work on Vista. The installer runs in Administrator mode but it displays the message
"An unidentified program wants to access your computer"
I understand that you need to digitally sign the install package to make this error go away.
I created a certificate .pfx file using makecert but when I try to build my install package I get:
Started signing certificate.msi ...
Successfully signed and timestamped: certificate.msi
ISDEV : error -6259: Internal build error
What is going on here? I don't have any files called certificate.msi? So what is InstallShield trying to do?
Thanks,
Robert
I have created an installer and I want it to work on Vista. The installer runs in Administrator mode but it displays the message
"An unidentified program wants to access your computer"
I understand that you need to digitally sign the install package to make this error go away.
I created a certificate .pfx file using makecert but when I try to build my install package I get:
Started signing certificate.msi ...
Successfully signed and timestamped: certificate.msi
ISDEV : error -6259: Internal build error
What is going on here? I don't have any files called certificate.msi? So what is InstallShield trying to do?
Thanks,
Robert
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 26, 2008
09:09 AM
InstallShield is signing a temporary msi file so it can populate the MsiDigitalCertificate and MsiPatchCertificate tables to enable elevation-free patching. I'm not sure what is going wrong that you get just the raw internal 6259 error; do you have at least MSI 2.0 on that machine, and plenty of free disk space for your build?