Last week my laptop prompted me to upgrade PrimalScript. I did so, afterwards I was able to sign scripts in PrimalScript using my Entrust code-signing certificate.
But nothing (uninstall/reinstall of both PrimalScript and the code-signing certificate) helped my virtual machine.
I tried the PowerShell console commands in your last reply, no luck on the virtual machine. It doesn't recognize my code-signing certificate as a code-signing certificate.
The commands work just fine on the laptop - it recognizes the code-signing certificate (same exact one as in use on the virtual machine) as a code-signing certificate.
There's definitely something goofy going on, but it's probably not anything to do with the Sapien software.
The specified file could not be signed
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: The specified file could not be signed
Thanks for letting us know. If there is anything we can do to help, please let us know.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: The specified file could not be signed
I opened a ticket with Entrust, who issued the certificate to me in February 2018. They were able to get it (re)set up and working (again) on my virtual machine, now I am once again able to sign code (including with PrimalScript).
So this was definitely nothing to do in particular with PrimalScript. Sorry to have bothered you.
So this was definitely nothing to do in particular with PrimalScript. Sorry to have bothered you.