EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Timestamp failed (83 970)

Posted: 01/13/2012 07:33:06
by DZIV  (Standard support level)
Joined: 12/08/2011
Posts: 4

Hello, I'm trying to sign XML in XAdES-T format, but I keep getting an error that says:
"Timestamp failed (83 970)", no reply from server.

SBB help defines the following steps for time stamping of XML documents:

  • First, create an instance of ElXAdESSigner class and initialize it's properties.
  • To timestamp the signature, you need to use TSPClient property of ElXAdESSigner class.
  • Use ElFileTSPClient or ElHTTPTSPClient classes, which will perform the timstamping. The timestamp request is created automatically by ElXAdESSigner when the signing is performed.
  • Set ElHTTPTSPClient.URL property if you want to use HTTP(S) transport.
TElXAdESSigner xSigner = new TElXAdESSigner();
xSigner.XAdESVersion = SBXMLAdES.Unit.XAdES_v1_4_1;

if (cbTimestamp.Checked) //if timestamping
    TElHTTPTSPClient TSPClient = new TElHTTPTSPClient();
    TElHTTPSClient HTTPClient = new TElHTTPSClient();
    TSPClient.HTTPClient = HTTPClient;

    TSPClient.HTTPClient.SSLEnabled = false;

    if (SignatureHelpers.KoristiProxy) //if uses proxy
        TSPClient.HTTPClient.UseHTTPProxy = true;
        TSPClient.HTTPClient.HTTPProxyHost = SignatureHelpers.ProxyServer;
        TSPClient.HTTPClient.HTTPProxyPort = int.Parse(SignatureHelpers.ProxyPort);
        TSPClient.HTTPClient.HTTPProxyUsername = SignatureHelpers.ProxyUser;
        TSPClient.HTTPClient.HTTPProxyPassword = SignatureHelpers.ProxyPassword;

    TSPClient.URL = cbTimeStampingURL.Text.Trim();
    TSPClient.HashAlgorithm = SBConstants.Unit.SB_ALGORITHM_DGST_SHA1;

    xSigner.TSPClient = TSPClient;
    xSigner.IgnoreTimestampFailure = false;


signer.XAdESProcessor = xSigner;

  • signer - istance of TElXMLSigner class.
  • http://inoa.net/tsa - TS url, no authentication is required.
Error happens on:
signer.Save(ref SigNode);

What am I doing wrong? :(
Posted: 01/13/2012 07:42:24
by Vsevolod Ievgiienko (Team)

Thank you for contacting us.

It seems that you use invalid TSA URL because the server returns 404 Not Found error.
Posted: 01/13/2012 08:01:57
by DZIV  (Standard support level)
Joined: 12/08/2011
Posts: 4

I'm sorry. TS service url is: http://inoa.net/ca/tsa. It works in Adobe Acrobat.

Posted: 01/13/2012 08:07:00
by Vsevolod Ievgiienko (Team)

You posted http://inoa.net/tsa URL above but Adobe Acrobat uses http://inoa.net/ca/tsa that works.
Posted: 01/13/2012 08:21:40
by DZIV  (Standard support level)
Joined: 12/08/2011
Posts: 4

Thank you for replaying so quickly. Regardless of my typing error, it still does not work.

Something, somewhere in code is causing this problem, but what?
Posted: 01/13/2012 08:28:00
by Vsevolod Ievgiienko (Team)

I was able to sign an XML using http://inoa.net/ca/tsa TSA with our demo that is located in \EldoS\SecureBlackbox.NET\Samples\C#\XMLBlackbox\Signer folder. Please compare your code to demo code to find out the reason of error.
Posted: 01/13/2012 08:52:25
by DZIV  (Standard support level)
Joined: 12/08/2011
Posts: 4

Simple signer returns the same type of error. The only thing I can conclude is that the problem lies somewhere in our network, and not in the source code.

Thank you for your help :)



Topic viewed 1872 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!