The specified file could not be signed

Support for all customers who have purchased a PrimalScript product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
User avatar
DiZzyDmon
Posts: 42
Joined: Mon Aug 06, 2007 11:04 pm

Re: The specified file could not be signed

Post by DiZzyDmon » Mon Jan 21, 2019 6:02 pm

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.

User avatar
Alexander Riedel
Posts: 6921
Joined: Tue May 29, 2007 4:43 pm

Re: The specified file could not be signed

Post by Alexander Riedel » Wed Jan 23, 2019 11:46 pm

Thanks for letting us know. If there is anything we can do to help, please let us know.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
DiZzyDmon
Posts: 42
Joined: Mon Aug 06, 2007 11:04 pm

Re: The specified file could not be signed

Post by DiZzyDmon » Mon Jan 28, 2019 10:41 am

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.