SB Error

[NewsArchive]

I'm getting an error when I try to compile. The strange thing is that the
file has not changed. Old script.

Error is always at the same place. See images attached.

Turned off anti virus.

What's happening here? Thanks!

Lynn Howard

[NewsArchive]

Lynn,

> I'm getting an error when I try to compile. The strange thing is that the
> file has not changed. Old script.
>
> Error is always at the same place. See images attached.
>
> Turned off anti virus.
>
> What's happening here? Thanks!

Error -1 means that the Microsoft Authenticode code-signing process failed.

It's one (or more) of the following:

1. The certificate that you are using in this specific compiler directive
line expired

-and/or-

2. The certificate configuration information that you are using in this
compiler directive line is incorrect (e.g. wrong password)

-and/or-

3. If you timestamp then "something" blocks access to the timestamp server

-and/or-

4. The file is already code-signed and you have not enabled the "Skip if
file is already code-signed" option

-and/or-

5. The "zippdf.exe" PE Header is invalid and Microsoft Authenticode does not
like it.

Hope this helps a bit.

Friedrich

[NewsArchive]

Thanks Friedrich!

I'll chew on that a while.

Lynn

[NewsArchive]

Recompiled zippdf.exe and all works now.

Must have been #5 - Microsoft didn't like the header.

Thank you Sir!

Lynn

[NewsArchive]

> Recompiled zippdf.exe and all works now.
>
> Must have been #5 - Microsoft didn't like the header.
>
> Thank you Sir!

You are welcome, Lynn!

Friedrich

[NewsArchive]

BTW are other folks having problems with code signing and AVG?

I have to turn AVG off to get an error free compile of SB.

Lynn

[NewsArchive]

Lynn,

> BTW are other folks having problems with code signing and AVG?
>
> I have to turn AVG off to get an error free compile of SB.

Not that I am aware of. I would suggest to report this to AVG so they can
fix the bug.

What you can do is to add the code-signing tool and the sb7.exe compiler to
the AVG "exclusion list" to disable real-time monitoring. This should work
around the AVG bug.

Friedrich

[NewsArchive]

Ive noticed some timeouts when connecting to the authenticode servers on
and off lately, but Im not sure if its due to issues on my end or theirs.
You see a fair # of goog results on the topic, so Im not alone there. Not
sure if this could cause what Lynn is seeing.
--

Mark Riffey
http://www.rescuemarketing.com
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, US Bank, Marketing Profs & Business Week read it,
maybe you should too.

[NewsArchive]

Thanks guys!

Lynn

[NewsArchive]

Mark,

> Ive noticed some timeouts when connecting to the authenticode servers
> on and off lately, but Im not sure if its due to issues on my end or
> theirs. You see a fair # of goog results on the topic, so Im not alone
> there. Not sure if this could cause what Lynn is seeing.

The Verisign and Comodo timestamp servers are very reliable. They can
handle quite a few million transactions per second.

BTW, in SB8 Final we have the following improvements / changes to deal with
timeout issues:

---
IMPROVEMENT: IDE: Add CODESIGN_DELAY #pragma to set the delay (in number of
seconds) between each timestamp trial. Defaults to 5.

IMPROVEMENT: IDE: Add CODESIGN_TSTRIALS #pragma to set the maximum number of
timestamp trials until success; defaults to 5.

CHANGE : IDE: The default delay between each code-signing timestamp
trial increased from 0 to 5 seconds.

CHANGE : IDE: The default maximum number of timestamp trials until
success increased from 1 to 5.
---

Lynn recompiled the original .EXE and that fixed the problem. So it seemed
to be caused by a "corrupt" PE Header.

Friedrich