Skip to Content
0

NW BPM issue : Reason: com.sap.aii.proxy.xiruntime.core.ESPXISystemFaultException

Oct 31, 2016 at 01:57 PM

423

avatar image

Hi,

I have the same version of NW BPM deployed in dev and quality system. ESR objects in both the systems are also same. However the BPM works perfectly fine in dev system but it throws the below error in quality system:

=============================================================

Message could not be processed. Reason: 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: Unexpected uriID /{http://abc.net/pi/SWCV/Message}asInterfaceName. Found: BindingData null, interface

==============================================================

I referred https://archive.sap.com/discussions/thread/3533962 , https://archive.sap.com/discussions/thread/3773998 and https://wiki.scn.sap.com/wiki/display/TechTSG/PI+Messages+are+not+delivered+to+SAP+NetWeaver+BPM?original_fqdn=wiki.sdn.sap.com but it does not help resolve my issue.

Could you please help with your inputs?

Edited : I receive "Invalid Response Code: (503) Service Unavailable..." error when I try to test the service from NWA->SOA->Application and Scenario Communication->Single Service Administration

Regards,

Vishal

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Praveen Gandepalli Oct 31, 2016 at 03:15 PM
0

Hi Vishal,

Normally this error means PI sending the message but BPM process is which needs to receive this message is not running.

  • BPM is not running
  • The PI receiver interface and BPM start event interface is different

Regards,

Praveen.

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Thanks for your response.

Re-transported ESR and ID contents from dev to quality systems to avoid any differences.

Created the NW BPM from scratch. Deployed and successfully tested it in dev. Immediately deployed the same in IX1.

However I am still facing the same issue.

================================================================================

Message could not be processed. Reason: 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: Unexpected uriID /{http://abc.net/pi/SWCV/Message}asInterfaceName. Found: BindingData null, interfaceMapping null interfaceDefinition null

SOAP: Response message contains an errorApplication/JAVA_PROXY./APPLICATION_FAULT - null

==================================================================================

Any pointers to resolve this issue?

Regards,

Vishal

0

There is one difference between Dev and Quality "Single Service Administration"

Dev:

Quality:

When I try to ping the WSDL URL for Quality system, I get 503 service unavailable:

You have requested an application that is currently stopped.

How do I overcome this issue?

Regards,

Vishal

dev.jpg (39.0 kB)
quality.jpg (36.9 kB)
0

Any inputs on overcoming this issue?

Regards,

Vishal

0
Praveen Gandepalli Nov 01, 2016 at 06:11 AM
0

Hi Vishal,

Make sure all the applications and services running in QA server. Try to restart the POQ server and see.

Regards,

Praveen.

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Thanks Praveen for your inputs. 2 Java applications were in failed status. The deployed BPM was one of them. Tried stop☆t , restarting this application but the status is still "Failed to Start". Is restarting the server is the only option left?

PFB the log record details:

Regards,

Vishal

log.jpg (125.1 kB)
0

What is the other application, try to start the other application may be that one is dependent on this application, i think is better to restart the system.

0

Hi Praveen,

Even server restart did not help. Tried undeploy and deploy from "Deployment" perspective.

Below is the log from NWDS. Would you be able to help with this?

====================================================================

S U M M A R Y

~~~~~~~~~~~~~~~~~~~

Successfully deployed: 0

Deployed with warnings: 1

Failed deployments: 0

~~~~~~~~~~~~~~~~~~~

1. File:C:\Java Workspace.jdi\LocalDevelopment\DCs\demo.sap.com\BPM_Name\_comp\gen\default\deploy \demo.sap.com~BPM_Name.sda Name:BPM_Name Vendor:demo.sap.com Location:localDevelopment Version:20161031164838 Deploy status:Warning Version:NEW

Description:

1. Exception has been returned while the [demo.sap.com/BPM_Name] was starting.

Warning/Exception :[ ][ASJ.dpl_ds.006153 Error occurred while starting application [demo.sap.com/BPM_Name]: It is not started successfully on server nodes [XXXX751, XXXX752, XXXX750].

In order to bring the server in consistent state stop operation will be performed.

Error occurred on server XXXX751 during startApp of demo.sap.com/BPM_Name : Error during execution of StartRemoteCommand transactionId=b79d14fa4bf01000802ec14b23ff308f userName=sappiuser appId=demo.sap.com/BPM_Name tid=24 initiator=XXXX750 null

Error occurred on server XXXX752 during startApp of demo.sap.com/BPM_Name : Error during execution of StartRemoteCommand transactionId=b79d14fa4bf01000802ec14b23ff308f userName=sappiuser appId=demo.sap.com/BPM_Name tid=24 initiator=XXXX750 null] Result Status:Warning

============================================================================

Regards,

Vishal

0