Printable View
I am receiving this error when I compile my exe. The strange thing is that
it worked just fine tonight up until approx. 8pm. I was building and
testing my app with no problems. Then I just started getting this error. I
tested on other apps that worked before and now getting the same error.
There was a posting in the NG about using an older version of Pokey.exe. I
tried it but still get the error. Anyone have any other suggestions where
to look?
David Ault
It's possible that whatever timestamp server you're using (comodo or
verisign) is temporarily off line. Try specifying the other one. Both URLs
are in the SB documentation.
Jane
Also, double-check that your certificate didn't expire at 8PM tonight ;)
Jane Fleming
David,
I think Jane is right. It sounds like your certificate expired at ~8PM.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
I just experienced the same. Turned out that switching from comodo to
verisign time stamp server corrected it - so his cert may still be valid.
Peter
Hi Peter,
> I just experienced the same. Turned out that switching from comodo to
> verisign time stamp server corrected it - so his cert may still be valid.
Yes, I noticed the same a few minutes ago (using the Comodo timestamp
server). It works fine again now. Perhaps Comodo did a server update.
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
Hello Friedrich
I am having the same problem - switching to Verisign did not help
either. I can do a command-line signing using signtool.exe just fine so
my certificate is still valid.
I started getting this problem about two months ago but have just
disabled the signing process - it is not a showstopper, but I would like
to see it working again.
Regards
Daan Marais
Daan,
> I am having the same problem - switching to Verisign did not help either.
> I can do a command-line signing using signtool.exe just fine so my
> certificate is still valid.
>
> I started getting this problem about two months ago but have just disabled
> the signing process - it is not a showstopper, but I would like to see it
> working again.
There is *NO* problem with code-signing in SetupBuilder.
If your certificate is still valid and all information in your project is
correct, then please check this old (but still valid) thread:
http://www.lindersoft.com/forums/sho...y.exe#post8879
Hope this helps.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
And of course, .PFX is an option if you don't want to rollback your PKEY.EXE
each time a web update is released.
http://www.lindersoft.com/forums/sho...&highlight=pfx
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
Hi Friedrich
I did not mean that there was a problem in SetupBuilder (I have learned
over many years to look for the beam in my own eye first!) - but I
cannot see where I am going wrong, hence my post.
I have also (unsuccessfully) tried the pkey.exe fix (this helped me
before) so I am pretty well stumped.
Never mind, I will give it another bash tomorrow and let you know.
Regards
Daan Marais
Hi Daan,
> I did not mean that there was a problem in SetupBuilder (I have learned
> over many years to look for the beam in my own eye first!) - but I cannot
> see where I am going wrong, hence my post.
>
> I have also (unsuccessfully) tried the pkey.exe fix (this helped me
> before) so I am pretty well stumped.
>
> Never mind, I will give it another bash tomorrow and let you know.
:)
Try to remove the timestamp entry and compile again to make sure your
firewall does not block access to the timestamp server when compiling from
SetupBuilder. If it still fails, make sure you point to the correct (and
not expired) .spc/.pvk files. And make sure you have entered the correct
certificate password in your project.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
Hi Friedrich
Ok, found it: Tools/Options/File locations was pointing to signcode.exe
instead of signtool.exe - I found it by renaming signcode.exe out of the
way and this gave an error so I knew SB6 was using signcode instead of
(as I thought) signtool.exe which worked correctly in a command-line
environment.
Sigh... but at least everything is back to normal now!
Thanks & regards
Daan
Hi Daan,
> Ok, found it: Tools/Options/File locations was pointing to signcode.exe
> instead of signtool.exe - I found it by renaming signcode.exe out of the
> way and this gave an error so I knew SB6 was using signcode instead of (as
> I thought) signtool.exe which worked correctly in a command-line
> environment.
>
> Sigh... but at least everything is back to normal now!
Glad it's working fine now. Thanks for the update!
Friedrich