SOAP Sender : Unauthorised HTTP 401 error

[Former Member]

Hi,

I have a scenario for SOAP-> XI -> ABAP Proxy.

The application is posting a XML message into an inbound XI interface and this has previously worked ok.

However, they are now getting an HTTP 401 error - Unauthorised.

Are there some services that need to be running to enable this scenario to work ?

Also, does anyone have a idea of anything else I could check within XI ?

XI 3.0 on Web AS 6.40 SP16

Cheers

Colin.

[Former Member · Accepted solution]

Hi ,

check this weblog...may be it ll help you...

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

sekhar

[Former Member · Accepted solution]

Hi,

It seems the URL is now requesting a username/password.

This did not used to be the case. Why would this change ?

What user id/password would be used anyway ?

Where do you supress this so a username/password is not requested ?

Cheers

Colin

[udo_martens · Accepted solution]

Hi Colin

Why would this change? The user is may be blocked because of 3 wrong logons?

What user id/password would be used anyway ? Assumedly nothing at XI changed; the change was 95% at R/3.

Where do you supress this so a username/password is not requested ? Dont take a dialog user for the SM59 destination. Take a system user.

Regards,

Udo

[Former Member · Accepted solution]

Hi,

The messages are not even making it into XI.

The HTTP error code is going back to the user who is sending the message into the SOAP adapter.

This is what makes it a bit strange.....

Kind regards

Colin.

[Former Member · Accepted solution]

Hi Colin

Did you solve this, we are having the same problem.

Regards Morten

[Former Member]

Hi Coling

Check this

Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER

u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>

u2022 If the error is in Adapter Engine

u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.

u2022 May be wrong password for user XIISUSER

u2022 May be wrong password for user XIAFUSER

u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message

Regards

Abhishek Mahajan

[Former Member]

Is your system landscape directory setup correctly? I ran into this issue because my "pipeline url" for the XI system in the SLD was linked incorrectly, and consequently the adapter was trying to connect to the wrong location, and it bounced back with a 401 error. Maybe it's something to look into, just a thought.

[agasthuri_doss]

Hi,

1) This might cause due to wrong permissions.

2)Try with this Login XIISUSER

3)Tcode SICF -> Default_host -> sap -> xi

( Check right password for the user id )

Regards

Agasthuri Doss

[udo_martens]

Hi Colin,

assumedly something very bad happend to the user of the RFC destination. Check at XI (IB Directory, SM59) which user was used. Check at R/3 (SU01) if the user is blocked or deleted or lost some rights.

You should have entries in SMQ2.

Regards,

Udo