Developer acecss key requested on executing proxy

[former_member194786]

Hi Guys,

We just upgraeded our SAP PI system from PI 7.11 to PI 7.3.

After upgrade we have regenerated the proxy for one of the existing custome development (File to Proxy sceario). Now we are facing 2 wierd issues:

1. On trying to execute the proxy from SPROXY, for testing purpose, we are being prompted to enter the developer key.

2. When testing the interface end-to-end, messages get stuck in queue (SMQ2) with the error: "Screen output without connection to user.".

We have tried to regenerate the proxy (dummy change in interface), but no good. Have tried transporting to the QA system but we are getting same error there as well. All other existing interfaces seem to work fine, i.e. we are not being prompted to enter developer or access key or the error message in SMQ2.

Our backend system was upgraded as well.

Any ideas will be appreciated.

Regards,

Sanjeev.

[Former Member · Accepted solution]

1. On trying to execute the proxy from SPROXY, for testing purpose, we are being prompted to enter the developer key.

you have to ask developer , is theer any maintain security for accessing the Sproxy......

2. When testing the interface end-to-end, messages get stuck in queue (SMQ2) with the error: "Screen output without connection to user.".

might be the reason is authorizations for the user that you are using for Proxy communication between XI and your R/3 system.

refer :

http://www.saptechno.com/sap-notes.html?view=sapnote&id=502122

http://www.sapnet.ru/abap_docu/ABENRFC_SYS_FAIL.htm

[former_member194786 · Accepted solution]

Hi Bhavanisankar,

I have checked with developer and Basis and there is no additional security maintained for the object or in the system.

Regarding the authorization, we have checked and the same user works perfectly for other interfaces and in the previous environments as well.

Appreciate your quick response.

Regards,

Sanjeev.

[former_member194786 · Accepted solution]

Hi Guys,

Has anyone come across this?

Regards,

Sanjeev.