Assertion ticket blues in RFC between ABAP and J2EE

[Former Member]

I am integrating BI Java on one system with BI on another system.

There is a JCO RFC provider on the J2EE side and a corresponding RFC on the ABAP side.

But...when I test the RFC connection from ABAP it fails. In the trace of the workprocess I see this:

N create_AuthenticationAssertionTicket was called.

N *** ERROR => Sign failed with rc = 5. [ssoxxsgn.c 327]

N *** ERROR => uResult=22. [ssoxxsgn.c 330]

N Unknown signer. Security profile does not contain the correct private key.

N *** ERROR => DefaultSign failed with rc=1441801. [ssoxxsgn.c 373]

N *** ERROR => Ticket creation failed with rc = 1441801. [ssoxxkrn.c 493]

N *** ERROR => dy_signi_ext: ticket creation failed [sign.c 10651]

A TH VERBOSE LEVEL FULL

In the RFC trace I can see this:

RFC> AssertionTicket create failure

The connection was automatically created executing the BI Java template.

Any suggestions on what is wrong here?

-AD

[Former Member]

Creating a new PSE solved the problem....