Logon popup during SPROXY call

[Former Member]

Hello *,

I receive a Logon popup during SPROXY call (on our ECC System) as well as by executing the connection test.

Logon protocol shows an authentication problem (401) to the server.

The RFC Destination "SAP_PROXY_ESR" works fine. Connection test HTTP Response 200 OK.

Any idea why we get this popup?

Many thanks in advance!

Jochen

[Former Member · Accepted solution]

Hi,

SAP_PROXY_ESR is required if parameters not maintained in exchange profile.

So let it be there.

Try with the path prefix as /dir.

[Former Member · Accepted solution]

Hi All,

Many thanks again for your help!!!

No RFC connections are locked respectively the user.

SLD check all in green.

In different Environment like Development it works fine with prefix /rep.

Please correct me but I thought its required to have the connection SAP_PROXY_ESR for receiving ERS content.

Many thanks in advance!

Jochen

[Former Member · Accepted solution]

Hi Jochen,

Make sure the User that you are using to connect has the roles for XI.

You could give SAP_XI_ADMINISTRATOR_ABAP & SAP_XI_ADMINISTRATOR_J2EE roles in the PI system to the User.

Now it should work.

Regards,

Ankesh

[Former Member · Accepted solution]

Hello All,

Many thanks to you again for professional help!

The problem is solved!

The cause for that issue was related to the HTTP connection SAP_PROXY_ESR which wasn't required for that configuration.

There is already in place <SID>CLNT<Client>INT (des://<SID>CLNT<Client>INT).

Regards,

Jochen

[marksmyth]

Hi Jochen

SAP_PROXY_ESR is used if you do not have an Exchange Profile (and by extension a full XI system). If you have configured the ECC system as a proxy Business System, then you already have an SM59 destination created to connect to the XI.

See the notes below for further info on this destination:

1) #1105427 Checking the connection data for the Enterprise Repository

2) #1060626 Proxy generation for ESR objects without exchange profile

Regards

Mark

[marksmyth]

Hi Jochen

Do you actually use the SAP_PROXY_ESR destination for the proxy communication? Is this the RFC destination that you have configured in trx sxmb_admin -> Integration Engine Configuration -> Corresponding Integ. Server -> dest://<RFC_DESTINATION>?

If no, then you can probably delete the SAP_PROXY_ESR destination. I don't think it is required if you have another RFC destination configured in this locaiton.

Regards

Mark

[Shabarish_Nair]

check SLDCHECK tcode - is it all in Green?

also maintain the right parameters in SLDAPICUST and also check if the user given in the destination are locked.

[Former Member]

1. Check the user.

2. Check path prefix in RFC destination PROXY_ESR is /dir.

Revert if it still doesnt work.

[Former Member]

Many thanks to both for replay!

The Prefix for SAP_PROXY_ESR is /rep.

The communication user ist not PIAPLLUSER. We using a generic User like "Z_ATTIHJUERT".

This user is used as well as in all other environments like Development and Production.

We facing that issue only in Integration and we aren't able to find out differences.

Many thanks in advance!

Jochen

[Former Member]

What is your R/3 or ECC version?

Try with both the Username and Paswword maintained in CAPS.

eg:

UserName :Z_ATTIHJUERT

pwd: Z_PASSWORD

Regards

Jai

[Former Member]

Hi,

When you do connection test, you have told that it is asking the logon details.

Check the User "PIAPPLUSER" might be locked, Unlock the user

Regards

Seshagiri

Edited by: N V Seshagiri on Apr 13, 2010 4:36 PM