cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy to Proxy sync scenario

0 Kudos

Hi all,

I am facing "CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" issue in QAS server, wherein everything is fine in DEV.

need suggestions...

from my side , every config related thing checked again n again(HTTP & RFC etc)

                      ID re-imported.

                      RD & ID also re-created.

                      PI & ECC cache cleared.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Thanks Everyone,

The issue has been resolved, after clearing SLD Cache and recreating all the objects of ID.

thanks all for your support

pvishnuvardan_reddy
Active Contributor
0 Kudos

Ayush,

Glad to hear your issue has been resolved.

Can you please close this thread discussion.

Answers (5)

Answers (5)

former_member186851
Active Contributor
0 Kudos

Hello Ayush,

check whether proper receiver system is assigned after transport to QAS.

Check in sproxy whether the Service interface is active.

0 Kudos

Hi Raghu,

its fine, but once more i will do

regards

Ayush

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Ayush,

I assume the settings in ECC are good for client proxy communication to PI system. Please cross check the settings in ECC like sxmb_adm, sproxy etc and in PI system(no sender channel is required since it is a proxy).

Also, please validate the data is matching or deviating with the message type declared in ESR or not.

iaki_vila
Active Contributor
0 Kudos

Hi Ayush,

Have you tried to check your scenario from test tool in integration directory?

Regards.

0 Kudos

Hi Vila,

in test configuration only it fails at receiver agreement and give the mentioned error above.

regards

Ayush

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Ayush,


in test configuration only it fails at receiver agreement and give the mentioned error above.

Did you have a receiver agreement created?

Regards,

Mark

0 Kudos

ya ofcourse

Former Member
0 Kudos

Hello Ayush,

Kindly check 2 things:

1. RFC connection via SM59, where I believe connection type should be H. Also check authorization check.

2. Please run the t-code SLDCHECK in ECC and see if you get any error. If there is error, kindly run the t-code RZ70.

Thanks,

Kind Regards,

Souvik

0 Kudos

Hi Souvik,

Done with the stuffs, Nothing new to do... pls. help with more suggestions...

Former Member
0 Kudos

Hello Ayush,

Just one question, guess its the case of outbound proxy, so have you generated the outbound proxy ? If yes, then the corresponding outbound service interface should turn green.

Kind Regards,

Souvik

0 Kudos

Hi Souvik,

Ya, Its green.

regards,

Ayush

iaki_vila
Active Contributor
0 Kudos

Hi Ayush,

A few points:

- Check the SICF service is active on the ECC.

- Check the ID has the QAS business components.

- Check user/password in your receiver channel.

- Check the SMQ1/SMQ2 queues on the PI (if PI is dual stack) and ECC.

- Check st22 transaction on the PI (if PI is dual stack) and ECC.

- Any other exception in the monitoring?

Regards.

0 Kudos

Hi Vila,

went through your suggestions, nothing helped , any other suggestions..???

regards

Ayush

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Ayush,

I assume the error you are getting is no receiver determined for the message.

Please cross check your ID objects whether it is yielding any receiver or not.

Most of the times, the issue with the source structure.