NW Gateway Client Problem

[Former Member]

Hi experts,

I have a problem when executing my web service. it gave me the following Error.

HTTP Send failed: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.

Message no. /IWFND/COS_SUTIL100

I can access my service through REST client in chrome.

Please help me on what I should do on this.

and let me know if you need more information.

Thank you so much.

-Martin-

[kammaje_cis · Accepted solution]

Hi Martin,

Strange error. It has to do something with security/single sign on.

In the browser , it prompts you to enter user ID and password, but Gateway Client usually signs in using SSO. Are you executing GW Client in your HUB system?.

May be any more info from error log would help.

Thanks

Krishna

[Former Member · Accepted solution]

I agree with you. It strange

Yes, I am executing my GW client in my HUB system.

in another thread, somebody says it could relates to my setting on 'SAP System Alias'

this is my configuration right now

SAP System Alias : LOCAL

Description : Local System Alias

Local GW : X

For Local App : X

RFC Destination : None

Software Version : DEFAULT

if it relates to the SSO. Currently I put the User ID that has ALL auth in SICF transaction.

My question - when I access my service through gateway client, do they use my user ID OR user ID that I configured in SICF ? i believe chrome uses User ID in SICF transaction, that is why it is working.

if they use my user ID - is there any specific roles that I need to execute the client ?

Thank You !

[kammaje_cis · Accepted solution]

May be you need to remove the userID given in SICF and try once.

It does not look like authorization error, rather some conflict.

[Former Member · Accepted solution]

Thanks Krisna. I removed the user ID in SICF and i still got the same error.

What is the authorization that I need - other than developer and admin ?

is there anything else ?

Thank You,

-Martin-

[Wolfgang_Mayer · Accepted solution]

Hello Martin,

did you resolve the issue?

Regards

Wolfgang

[Benedikt3 · Accepted solution]

Hi Wolfgang,
I have the same issue.

could you solve it?

[Wolfgang_Mayer · Accepted solution]

Hi Benedikt,

not yet.

Regards

Wolfgang

[Former Member · Accepted solution]

Hi Wolfgang,

sorry I just saw your message.

Yes, my problem is solved.

Basically our Basis people solved this problem for me.

Let me know if you have this problem.

Maybe i can ask basis on how they solve it.

Regards.

[Former Member · Accepted solution]

Hello,

We are having the same issue. The service can be executed with https from browser but it fails from Gateway Client with the error HTTP Open Failed: ARGUMENT_NOT_FOUND  Message No. /IWFND/COS_SUTIL100.

Can you please confirm how you resolved it?

Thanks,

Amandeep

[Former Member · Accepted solution]

Hi Amandeep Aggrawal,

do you have solved this problem?

If yes, can you explain how.

login/create_sso2_ticket = 2 doesn't work for me

Thank you very much.

Regards

[EkanshCapgemini · Accepted solution]

Hi Mattia,

The profile parameters needs to be set as followed: Profile Parameters - SAP NetWeaver Gateway - SAP Library

Regards,

Ekansh

[Former Member · Accepted solution]

Thank you Ekansh for you answer, my systems are already set as you suggest but didn't work.

I don't know if the problem is because i have enabled only the https connection.

[Andre_Fischer]

Hi Martin,

since I ran into the same problem I posted a blog about how to solve it

Best Regards,

Andre

[challojuravi]

Thank you Mr.Andre Fischer  

My issue has been resolved good guidance

Ravi.Challoju

[Former Member]

I changed parameter login/create_sso2_ticket from 3 to 2 and it solved this problem for me.

[Former Member]

Hi Jeroen,

how do you change it and where ?

thank you

[former_member183924]

Hi Fatsah,

that's a system parameter for your NetWeaver server. Use transaction RZ10 to change it.

--

Steffen

[Joseph_BERTHE]

Hi,

When you change the profile parameters do not forget to restart the server

It will solve your problem.

Regards

[Former Member]

Hi jeroen,

i changed login/create_sso2_ticket from 3 to 2 and it solved my problem.

thank you