First of all, thanks to Eugene and Ken for the support in the last days.

That's a Tricky one: In the Samples of SBB, i'm using the TinySigner (PDF), in VB.Net (VS 2010) to sign a PDF File using a TimeStamp server. In fact, it's a page in a web server who redirects to a TimeStamp Server. And all works fine.

So, I copied the code to my project, made some minor ajustments in it and... error. When I try to reach tha page that makes the redirect, the error is 8204 (Invalid Signature, I guess). When i try to reach the TimeStamp Server directly I got the 83970 error (TSP No Reply, I guess).

With the same certificate, with the same file, on TinySigner... All runs good, no errors, signed sucessfully, in both cenarios.

I tried to implement (Thanks to Ken) OnHTTPError and OnHTTPRedirects Handles to find out, but without success until now. What can possibily wrong? I'm sending an attachment with the errors trace, and i'll send some code in a reply here.

Most likely you didn't initialize CRL and OCSP retrievers, which could lead to impossibility to collect revocation information or to validate server certificates. Please search the source code of the sample for "Initialize" and you'll understand what to do.

I've mislead you a bit. Those calls are Register*** , but they are also not present in the sample. So I am afraid your only option is to find the differences with the sample - it can happen that your components (such as TElHTTPTSPClient and TElHTTPClient) are not linked together and TElHTTPTSPClient can't retrieve the timestamp.

SSLEnabled property should not affect component behavior unless your server's URL doesn't contain a protocol. If you specify server URL without a protocol (no http:// or https://) and port, then the component doesn't know how to connect (with or without SSL).

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.