SAP PI Basis error messages stuck in ECC

[Former Member]

Well met

Problematic:

Messages are stuck in ECC with the scheduled green flag they don't reach XI/PI

Background

We recently did a full copy of our production environment (ERP) to our quality environment, (ERX) afterwards the messages that go

ECC(ERX) > PI(PIX) > Oracle stopped working they are stuck with a scheduled status the messages that go the other way

Oracle > PI(PIX) > ECC(ERX) are working correctly as intended.

Things verified so far

ECC

sxmb_admin >Integration engine (ok) verified

sldapicust > test (ok)

sldcheck > (ok) Connection to SLD works correctly

smq2 > deleted all ques new ones are stuck

SPROX_CHECK_IFR_RESPONSE (ok) date understood

SPROX_CHECK_HTTP_COMMUNICATION > (ok) HTTP communication functioning

SPROX_CHECK_IFR_CONNECTION > (ok) functioning correctly data understood

SPROX_CHECK_IFR_ADDRESS > (ok) OK: Address maintained

sm59 > SAP_PROXY_ESR rfc tested ok

Did a search on the site but couldn't find anything else that answered my problem

Thanks in advance for your help

[Former Member]

Thanks for the help the problem has been solved

[Harish]

Hi Gustavo,

thanks for closing the thread, can you please also share the solution of problem?

regards,

Harish

[Former Member]

Certainly

in sm59 our RFC connection SAP_PROXY_ESR in the technical options we had in the path prefix

/rep

instead of

/sap/xi/engine?type=entry

which was preventing the ECC system to connect to PI

[prem_a]

Hi Gustavo,

In SMQ2 please activate/unlock the queues which have messages in stuck status. I hope the messages are in READY status in these queues.

Regards

Prem A

[Former Member]

Hi Prem A

I deleted all the ques in SMQ2 the new messages are still stuck, there is no "bad message" that is making the rest stuck.

[Harish]

Hi Gustavo,

It seems the problem is in RFC destination. Please check all the rfc destination which are pointing to PI.

regards,

Harish

[Former Member]

Hi Harish

Checked the RFC destinations in SM59 they are pointing to the right direction with the right user,

user is not blocked and has enough privileges