Page 2 of 2

Re: The specified file could not be signed

Posted: Mon Jan 21, 2019 6:02 pm
by DiZzyDmon
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.

Re: The specified file could not be signed

Posted: Wed Jan 23, 2019 11:46 pm
by Alexander Riedel
Thanks for letting us know. If there is anything we can do to help, please let us know.

Re: The specified file could not be signed

Posted: Mon Jan 28, 2019 10:41 am
by DiZzyDmon
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.