Webservices runtimeException when processing message from PI to NWBPM

[former_member187447]

Hi Folks,

I have a BPM scenario where in I am trying to trigger a NW BPM and I am getting the following exception. Please note there is no issue with User nor there is any issue with authorization as the other BPMs in the landscape are working. Also the inbound interface into BPM is defined as inbound stateless (XI30-compatible)

""Delivery of the message to the application using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. FaultException: com.sap.aii.proxy.xiruntime.core.ESPXISystemFaultException: Error encountered during processing of XI request message in inbound ESP; Hint: com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution"

Also when I try to trigger the BPM using WS navigator using the BPM Start URL I am getting the following error message

HTTP/1.1 500 Internal Server Error server: SAP NetWeaver Application Server 7.45 / AS Java 7.50 content-type: text/xml; charset=utf-8 date: Thu, 22 Jun 2017 21:47:29 GMT transfer-encoding: chunked Set-Cookie: <value is hidden> 2ef <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring xml:lang='en'>Invalid WS-RM message. There are no WS-RM headers within SOAP message.</faultstring><faultactor>Server</faultactor><detail><yq1:com.sap.engine.services.wsrm.exceptions.ReliableMessagingException xmlns:yq1='http://sap-j2ee-engine/error'>Invalid WS-RM message. There are no WS-RM headers within SOAP message.</yq1:com.sap.engine.services.wsrm.exceptions.ReliableMessagingException></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> 0

Regards

Kalyan.

[former_member187447 · Accepted solution]

I checked the NWA developer trace and I see I had an issue with the BPM administrator settings, after fixing the expression the issue is fixed.

Regards

Kalyan.