- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: SigningHelper: error 0x80072efe while attempting to sign file
- 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
Hello,
I am facing signing error:
SigningHelper: error 0x80072efe while attempting to sign file
My build was working fine till 31 dec 2020. After year change all my installshield builds giving me this error. I tried to sign my exe manually with pfx file which worked fine. But the same signing is not working with installshield. Please suggest me on this. If not the resolution just let me know what this error code means.
Thanks in advance.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @theone_sumit,
Check your time stamp URL configured in the settings.xml, if you are using old symantec or verisign then you need to update Settings.xml file in <InstallShield_InstallPath>/Support/0409 with new URLs
Before:
<DigitalSignature Timestamp="http://timestamp.verisign.com/scripts/timstamp.dll"/><DigitalSignature TimestampRFC3161="http://sha256timestamp.ws.symantec.com/sha256/timestamp"/>
After:
<DigitalSignature Timestamp="http://timestamp.digicert.com"/><DigitalSignature TimestampRFC3161="http://timestamp.digicert.com"/>
Also install the digital signing patch if you are configured to sign using Digicert server and using older version of InstallShield:
More information on this patch can be found at the below link:
https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShiel...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @theone_sumit,
Check your time stamp URL configured in the settings.xml, if you are using old symantec or verisign then you need to update Settings.xml file in <InstallShield_InstallPath>/Support/0409 with new URLs
Before:
<DigitalSignature Timestamp="http://timestamp.verisign.com/scripts/timstamp.dll"/><DigitalSignature TimestampRFC3161="http://sha256timestamp.ws.symantec.com/sha256/timestamp"/>
After:
<DigitalSignature Timestamp="http://timestamp.digicert.com"/><DigitalSignature TimestampRFC3161="http://timestamp.digicert.com"/>
Also install the digital signing patch if you are configured to sign using Digicert server and using older version of InstallShield:
More information on this patch can be found at the below link:
https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShiel...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Many thanks !!! Its working fine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Can someone repost the correct links?
These links are dead.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
hi,
I have installshield 2020 R3 installed, the setting.xml seems fine, but still get the warning , is there anything else required here?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Are you seeing this error after any update installed in the machine like windows update or any security software anti virus update? Please check the updates installed?
Try to import the certificate to trusted root and then try to sign the installer and then try signing using (refer screenshot)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
We have several kb installed on April, and May, they are : KB2565063, KB4087371, KB3022398,KB5001078,KB4535680,KB4589210,KB5001402,KB5001347,KB2504637.
And for importing the certificate , i think i am doing correctly.
Seems the warning does not impact the signing process on msi, but still annoyed by this kind of warnings.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @kshu_statestre,
Thank you for your post.
Does this issue occur on more than one build machine? Or so far, only this single build machine?
Does this issue occur every time? Sometimes? Or only this one time?
Does this issue occur with all projects? Some projects? Or only this one project? Even a new test project?
On which date does your digital certificate expire?
To confirm, have you tried all the previous suggestions on this thread?
Could you please provide a verbose build log that captures the issue?
Here is a link to documentation about how to generate a verbose build log:
https://community.flexera.com/t5/InstallShield-Knowledge-Base/Verbosely-Log-a-Command-Line-Build/ta-p/4625
Please let me know if you have any questions or concerns. Thank you for your patience and cooperation.
Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
1. the issue only happens on this machine, since we only installed 2020 R3 and activated it on one machine.
2. it occurs every time when I start build the basic msi project.
3. occurs to one project.
4. the certificate expires till 2025.
5. verb log:
Started signing certificate.msi ...
SigningHelper: error 0x80072ee7 while attempting to sign file
ISDEV : warning -1027: A warning occurred while signing certificate.msi. See the build log for details.
Performing Upgrading and Patching Validation
Started signing *********.msi ...
SigningHelper: error 0x80072ee7 while attempting to sign file
ISDEV : warning -1027: A warning occurred while signing *******.msi. See the build log for details.
Setup.exe created
Started signing ********.exe ...
SigningHelper: error 0x80072ee7 while attempting to sign file
ISDEV : warning -1027: A warning occurred while signing ********.exe. See the build log for details.
Windows validation is disabled. To enable Windows validation: on the Tools menu, click Options and select the Validation tab.
Automatic update notification disabled
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Please remove the signing details and then re- add signing details and then try again, if you have selected "Sign files in packages " to YES change it to NO and then try once and see it works or not.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Already did several times. but no luck.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
that is interesting , after I changed it to Yes, and then changed it to No again, the error finally gone.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Great! good to hear it fixed the issue.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)