(103) JCO_ERROR_LOGON_FAILURE System received an expired SSO ticket on BOBJ & BW

[former_member209962]

Hi Friends

Our SSO connection in IDT Tool is not consistent some time connection test is successful and some time its giving error as system received an expired SSO Ticket on xxx.xxx.xx.xx (this is our BW system).

We have SSO configured between BW and BI and it was working fine but suddenly from last two days ts giving issue, we have not changed any thing from our side.

there is one dashboard which is like main report (p&l and balance sheet of the company) this dashboard is consist of Bex queries becasue of this issue data is not comming properly in dashboard (BI Launchpad) some queries are getting executed and for some quries its showing error as system recived expired sso ticket.

We check the SSO certificate and its valid till 2024.

If we make connection type pre-define then no issue everything works fine but we cannot use connection pre-define as authorizations are controlled from BW.

when i check the log in bobj server i see error as

When we check the log we find the complete error as

Hostname:13516:100.27:1|CjvESq0_SEmKhmFW8bmAPkw13009|||||||||||Initialization of destination custom_0fd7a8ba-c185-4d0a-b96e-e7e24e02f034_4 failed: System received an expired SSO ticket on 192.168.30.150 sysnr 00 com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination custom_0fd7a8ba-c185-4d0a-b96e-e7e24e02f034_4 failed: System received an expired SSO ticket on xxx.xxx.xx.xxx sysnr 00

And when i check BW trace file dev_w i see below error.

ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080] N {root-id=35393245364634373539324536463437}_{conn-id=00000000000000000000000000000000}_0 N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080] N {root-id=35393245364634373539324536463437}_{conn-id=00000000000000000000000000000000}_0 N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c 1080] N {root-id=35393245364634373539324536463437}_{conn-id=00000000000000000000000000000000}_0

Our BI version 4.2 sp2 Version: 14.2.2.2066.

OS:win 2008

sso certificate is valid and some time it works fine and some time not kindly advice.

Thanks

Tabrayz

[former_member209962]

Hi Tim,

Issue is solved!

Problem was system was not joined in Domain hence it was not in sync with domain controller and there was time diffrence between BW & BO server.

Once system joined in domain the time sync was perfect and sso is stable.

Thanks

Tabrayz

[BasicTek]

More important that re-configuring STS is what happens when you test 1767629? You can test from webi or IDT, it's very important to determine if STS is failing or if the problem is with SAP secondary credentials.

[former_member209962]

Hi Tim,

Thanks for your reply i reconfigure STS as per note 1670073 but still same issue 5 times connection test in IDT is successfull then again it fails with same error system received expired sso.

Thank

Tabrayz

[BasicTek]

That error does not always mean the same thing, There are 2 types of SSO so 1st verify STS is working with KBA 1767629. Do it on a consistent report (and user) you know is set to SSO. If you verify STS is working then test the problematic report the same way (via enterprise alias) and see the result. If it works the issue is not with STS/SSO and either user related or with the report itself. If the test shows STS fails then you probably need to reconfigure per KBA 1670073

Regards,

Tim