mapping error lock the queue

[former_member745782]

hello everybody,

We recently migrated from XI3.0 to PI 7.1.

We have some interfaces "file to idoc" working in EO quality of service.

Using PI 7.1 when we have a mapping error the queue is locked and all messages after first are in queue and don't arrive to destination.

When we used XI 3.0 we didn't had this situation.

I also tried to uncheck the flag "Maintain Order at Runtime" in Interface Determination but i still to find queue locked and messages in error in SMQ2.

The error in SMQ2 is:

"Syntax error in program SAPLSXMSALERT"

any suggestion?

thanks in advance

Alessandro

[Former Member]

Hi Try changing the Quality of service to EOIO and check. This should work by assigning a specific queue.

Goto ST22 tx and check the dump. U would probably get a hint of the exact issue.

Thanks,

[iaki_vila]

Hi Alessandro,

Check in st22 if you have a dump with RFC_NO_AUTHORITY

Regards,

[former_member745782]

seem the problem is in Alert Configuration.

But i cannot open Alert configuration page because i have a problem on FQDN.

Any suggestion?

[Former Member]

The hint is to deactivate the specified alert rule.

Otherwise talk to your abap guys. They will find something in ST22. I assume you did something to your alerting functionality (enhacement or modification).