SOAMANAGER error

[Former Member]

Hello,

Error with SOAMANAGER

NWBC or SOAMANAGER not run properly with IE (for example IE 10) and apperrs the error mentioned above.

If we execute the Tcode SICF_SESSIONS, these are my values:

login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
login/ticketcache_entries_max = 1000
login/ticketcache_off = 0
login/ticket_only_by_https = 0
icf/set_HTTPonly_flag_on_cookies = 3
icf/user_recheck = 1
http/security_session_timeout = 1800
http/security_context_cache_size = 2500
rdisp/plugin_auto_logout = 1800
rdisp/autothtime = 60

SOAMANAGER only works fine with firefox copying the URL, then user/pass it's Ok and we can login on.

But if we execute TCode SOAMANAGER, open IE10 but login and pass crash with the error mentioned.

We have checked several notes:
1617090 - ICF system logon: Logon fails, logon cookie (not works)
2005571 - Warnings when you logon to SAP ABAP system via HTTP.

This system have been created via homogeneus system copy and probably there are values that in my system not needed ?

Take in mind that Tcode SOAMANAGER launch different URL that if we test
service in SICF.
--> SICF: Execute and launch Directly by host (cluster hostname) --> OK
--> Tcode SOAMANAGER: via WebDispatcher using "rules".

The results are:
--> IE10 --> KO with error
--> Firefox --> OK

IE10

Firefox

Regards

[Former Member · Accepted solution]

Hi Victor,

Please check with your basis team this note  1617090 - ICF system logon: Logon fails, logon cookie

Regards.

[Former Member · Accepted solution]

Hi Iñaki,

If you read the message, this note is checked.

Thanks.

[Former Member · Accepted solution]

Hi Victor,

My bad, i only saw the screenshoot and i didn't continue reading. If i understood right your message you can connect using firefox but not with ie10, isn't it?, have you tried with chrome?. Is it mandatory for you to use the IE10?.

Regards.

[Former Member · Accepted solution]

Hi Iñaki,

We can only use IE10.

Thanks Iñaki

[Former Member · Accepted solution]

Hi Victor,

The issue could be related with FQDN definition in your ABAP system. Could you go to the st22 transaction in your ABAP system and to share the exception with us?

Regards.

[Former Member · Accepted solution]

Hi Iñaki,

In ST22 dont registre the error,

Thanks

[Former Member · Accepted solution]

Hi Iñaki,

Can you help me with this problem? Thanks

[Former Member · Accepted solution]

Hi Victor,

Talk with your basis team that they check these recommendations  1936501 - Transaction SOAMANAGER does not work

Regards.