SYSTEM ERROR IN JDBC - XI - SOAP -

Hi All
Actually i am through a JDBC -> XI-> SOAP (webservice)->XI -> FIle scenario using BPM, its mapping for the first half i.e JDB -> XI -> SOAP is like - Data uses the JDBC adapter , initially passes the JDBC outbound async interface , then it enters into IP(BPM) through abstract async interface (service for BPM: "requestservice_IP" ).Mapping takes place outside the BPM so message type passes through "sync abstract" interface (mapping takes place here) and finally to SOAP adapter(request reciever and sends response ) i .e webservice.
Data is mapped properlly and but problem lies in SOAP adapter, as it recognises the webservice but it is not processing it further .So only mapping takes place from JDBC datatype to SOAP datatype but data is not able to poston to the available webservice mentioned in SOAP target URL.
In SXMB_MONI , upto the mapping for first half its ok but for SOAP adapter its showing ERROR CATEGORY - MESSAGE and ERROR ID - GENERAL

Hey all more info regarding the persistent problem is in here
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please have a look at it

Similar Messages

System Error in Message Monitoring -Proxy to SOAP async scenario

Hi All,
My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
but in related Soap Receiver communication channel i can see the below Error
"2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
Please help , what could be the problem.
Thanks in Advance.
Jyoti

Hi Jyoti,
>Is there any specific setup required at Provide side while moving to Acceptance system
I dont think so.
Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
Regards,
Udo

Fehler javax.xml.rpc.soap.SOAPFaultException: System Error

Hi,
I tried to create a web service with XI with the help of the blog: Invoke Webservice using SAP XI under https://weblogs.sdn.sap.com/pub/wlg/2292. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] When I create the web service with the url from the tutorial: http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel> the url is not found. If I use the proposed url I got the error: Fehler javax.xml.rpc.soap.SOAPFaultException: System Error.
What could be the problem?
Thank you!
Julia
Message was edited by: Julia Seifert

RWB = runtime Workbench
when you start integration builder you 4 choices (Integration Repository, Integration Directory, System Landscape Directory and Runtime Workbench)
Go their and on the next Webpage on the first link "Comp. Monitioring"
Go to "Integration Server" and their to Adapter Engine
you will get another window below.
Go their on button Adapter Monitoring and we will get a overview which are working and which not.
Hope this helps!
Regards Matt

Javax.xml.rpc.soap.SOAPFaultException: System Error

i am trying to use java proxy to run a web service which activates a FM. when i excute the java program i get:
javax.xml.rpc.soap.SOAPFaultException: System Error
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:735)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:857)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:1091)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1439)
     at sap.press.com.xi.MI_JavaProxyStartWorkflowSyncOutBindingStub.MI_JavaProxyStartWorkflowSyncOut(MI_JavaProxyStartWorkflowSyncOutBindingStub.java:82)
     at sap.press.com.xi.SendJavaProxy.main(SendJavaProxy.java:38)
does anyone know what the causing it?

RWB = runtime Workbench
when you start integration builder you 4 choices (Integration Repository, Integration Directory, System Landscape Directory and Runtime Workbench)
Go their and on the next Webpage on the first link "Comp. Monitioring"
Go to "Integration Server" and their to Adapter Engine
you will get another window below.
Go their on button Adapter Monitoring and we will get a overview which are working and which not.
Hope this helps!
Regards Matt

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

BPM - JDBC adapter - How to trigger system errors thro' adapters?

I have designed the BPM in following way :
1. Receive step - Receive Asynchronous message
2. Defined the Block - DB
3. Send step 'A' to JDBC - inside the Block-'DB' - Acknowledgement-Transport, Exceptions System Error-'DB', Receiver from-Send context.
4. Created an exception handler and Selected 'DB' as exception handler for the property of the exception handler branch.
5. Inserted the Send step-'B' to Mail inside the exception handler branch by using the mail receiver adapter.
We want send the message to update database by using JDBC adapter but if it fails to update database then we want send an e-mail to outlook.
Due to some problem we are not able to receive confirmation for the update of database in the "SEND" step-'A' and it is not red flag error it means it is not system error in Tcode-SXMB_MONI. Does anyone can help me to get a system error triggered by the JDBC adapter which would basically throws up the red flag and tells XI that the message could not be delivered successfully to database and the message would route to "SEND" step-'B' to send an email to outlook?
Thanks in advance!
Mrudula

Hi Sarvana,
I have defined the all the mandatory fields in the BPM.
Following is the error log if you could help me in resolving it.
Thanks in advance!
MESSAGE ID: com.sap.aii.ib.sbeans.oa.rb_all.RUNTIME_EXCEPTION_OCCURED
com.sap.aii.utilxi.swing.framework.FrameworkException: Runtime error (RuntimeException). See details
     at com.sap.aii.ib.gui.editor.XiDocument.checkConsistency(XiDocument.java:780)
     at com.sap.aii.ibrep.gui.bpm.BusinessProcessDocument.checkConsistency(BusinessProcessDocument.java:479)
     at com.sap.aii.ib.gui.editor.XiDocument.checkObject(XiDocument.java:799)
     at com.sap.aii.ib.gui.editor.CheckObjectCommand.execute(CheckObjectCommand.java:38)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:196)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:134)
     at com.sap.aii.utilxi.swing.framework.CommandAction.actionPerformed(CommandAction.java:69)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.AbstractButton.doClick(Unknown Source)
     at javax.swing.AbstractButton.doClick(Unknown Source)
     at com.sap.plaf.frog.FrogMenuItemUI$ClickAction.actionPerformed(FrogMenuItemUI.java:960)
     at javax.swing.SwingUtilities.notifyAction(Unknown Source)
     at javax.swing.JComponent.processKeyBinding(Unknown Source)
     at javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(Unknown Source)
     at javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(Unknown Source)
     at javax.swing.JMenuBar.processBindingForKeyStrokeRecursive(Unknown Source)
     at javax.swing.JMenuBar.processKeyBinding(Unknown Source)
     at javax.swing.KeyboardManager.fireBinding(Unknown Source)
     at javax.swing.KeyboardManager.fireKeyboardAction(Unknown Source)
     at javax.swing.JComponent.processKeyBindingsForAllComponents(Unknown Source)
     at javax.swing.JComponent.processKeyBindings(Unknown Source)
     at javax.swing.JComponent.processKeyEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)
     at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.AccessibleKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
     at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)
     at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)
     at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

Payload at Adapter for System Errors - SOAP receiver adapter

Hi Everybody,
I am working on an Idoc to SOAP asynchronous scenario.
There are connection issues between SOAP adaper and the target webservice.
I need to capture the Idoc number from the message payload for the Erroneous messages at the adapter for the System errors.
Is there any way of capturing field values from the payload (Say, Idoc number) at the SOAP receiver Adapter level.
Helpful answers will be rewarded points.
Thanks & Regards,
Zabiulla

Hey,
I think you need to implement a module inorder to get the payload at receiver adapter module.
As far i concern you can not directly refer the payload in adapter in receiveer communication channel unless you have your own module, which gets the payload. Check the Modules tab in the communication channel and also regarding how to get the payload for error information, follow the steps mentioned in the below link, which gets the payload in file. hop it will resolve your issue.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/writepayloadtoafilefromAdapter+Module
Regards..
Prasanna..

SOAP:Server, System Error SystemError , code MESSAGE.GENERAL /code

Hi!!!
I am testing a webservice and I am getting the following error
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>MESSAGE.GENERAL</code>
               <text/>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Kindly help me with the same.
Thanking all of you in anticipation
Regards,
Kiran

Hi Michal,
Thanks for your prompt response. The above stated error is what I got after accessing it from soapUI.
I tried to access it from the browser and it gave the following message
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thanks for your help.
Regards,
Kiran

Catch system error in sync soap sender

I fear this is not possible in standard.
Refer to this blog to understand the fault messages and why you canot capture System Error Messages,
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
Regards
Bhavesh

Hey all more info regarding the persistent problem is in here
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please have a look at it

JDBC to SOAP to trigger Web Service in PI XI

Hello Experts,
My scenario is: SystemA -
> JDBC adapter -
> PI -
> SOAP Adapter -
> SAP.
Sender side (JDBC) works file, I can see the payload in the sender structure and the converted payload for the receiver side.
I am testing the webservice using the "WS Navigator" and it works perfectly, I enter my WSDL and I can see my receiver structure, fill the fields, execute the webservice and it runs my program inside the SAP.
But when I execute the complete scenario using PI (I mean, send the data from system A via jdbc adapter and etc) it doesn't execute my program in the SAP side.
The runtime workbench looks fine, no error messages but PI doesn't trigger the webservice.
Am I missing some step?
I did:
1 - Create remote enabled Function Module in SAP side;
2 - Created webservice using SE37
3 - Configure the webservice in SOAMANAGER
4 - Dowload WSLD from SAP
5 - Upload WSLD in PI ESR
6 - Created the further elements
7 - I did the configuration in the Integration Directory using the wizard and SOAP adapter as receiver
Everything looks fine but PI doesn't trigger the webservice.
Should I create proxy for this new Service Interface I created doing the upload of the WSDL or it is no necessary once I created the webservice and did the SOAMANAGER steps?
Any idea?

Solved.
After check the answers from SDN colleagues I discovered that "yes" I had to create the proxy in this case.
After that I could see the scenario triggering the webservice and my application in SAP.
Thanks for the help.
Ricardo.

System Error!!

Hi Everybody
I am implementing JDBC ->SOAP->FILE(XML) scenario using BPM where the
the values from the database are posted to the webservice and the webservice sends a response to the XML File , I am done completely with design and configuration but i am not able to receive the response from the webservice to the file actually i am getting system error in the synchronous send step in the BPM.
The status in moni says system error restart not possible and the workflow shows sync send step in error (red color).
I am using a free webservice whose URL is:-
http://webservices.imacination.com/distance/Distance.jws

HI
I have done everything from my side for implimenting JDBC ->XI ->SOAP ->XI ->FILE(XML) scenario and in MONI i can find two prominent errors :
1. There is system error in "synchronous send" step of BPM and
2. <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<<b>SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code></b>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

" SYSTEM ERROR" with ERROR CATEGORY: Message and ERROR ID : GENERAL

HI all
I m doing JDBC -> XI -> SOAP -> XI -> FILE ( XML) scenario .I have implemented it using BPM .
But ,In MONI , i am getting a "SYSTEM ERROR " with "ERROR CATEGORY : MESSAGE" and "ERROR ID : GENERAL" .and
One thing more is there my all adapters are active (JDBC,FILE) in runtime workbench but SOAP adapters i am not able to see it there as its services are not defined in there .Is this problem is because SOAP adapters are not defined in runtime workbench ?

Hi Colin
I are using SP 3.0
I have checked the Communication channel monitoring and Adapter monitering also but in mine case when i want to see the SOAP adapter in adapter monitoring , the SOAP ICON is disabled there ,so i am not able to see whats the status of my SOAP adapter i have used in my scenario
Thanks and Regards
Abhishek

System Error in Message Monitoring while it shows checked flag in SXMB_MONI

Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
Regards

System is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05     Information     Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05     Information     SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05     Information     SOAP: completed the processing
2010-05-10 13:15:05     Information     SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05     Error     SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06     Error     The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution.

System Error in Comm channel monitoring of RWB

Dear all,
I have a Proxy to webservice scenario (HCM-PI-SuccessFactors). At receiver side i am using SOAP AXIS adapter. In RWB, the status of the channel is green and running. But when i ping the channel, it shows System Error.
I have made changes in respective communication channels, activated and cleared the cache. Still same error.
Later taken complete restart of system. Still same error.
How to overcome this ?
Note : 1) End to end scenario is working fine
2) Among the three trusted certificates installed, status of one certificate is showing warning (status: which will expire on may 5).
Regards
Uday

Hi Hareesh,
Thanks for you input. I have used the standard swc SFIHCM01. Here it is mentioned that it is applicable for SWC MESSAGING SYSTEM SERVICE 7.31 as shown below
What does this MESSAGING SYSTEM SERVICE mean exactly. In general is it our PI system.
plz correct me if i am wrong
Regards
Uday

Catching System Error Message in Abap Proxy.

Hi all,
I want to know whether it is possible to catch the system error message from SXMB_MONI in proxy scenario's.
The error i am getting is :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Service is not active</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Is it possble to catch the above message text.
Regards,
Keith

Hi Keith,
Check this forums also should be definitely help u..
Error message handling in Integration Process
and
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm
also refer
Check this weblog once ... sure it will give u an idea..
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
and also go through this
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Regards,
Sridhar

SYSTEM ERROR IN JDBC - XI - SOAP -

Similar Messages

Maybe you are looking for