Error Type In Integration Engine

Hi All,
Please tell me what type of error/exception can occur in the integration engine? Is it only System Exception that can occur or can Application Exception also occur?
Also please tell me what do you mean by the term SALERT.
Thanks,
Abhishek.

hi abhishek,
I. Errors in Integration Engine
a) qRFC Errors
Often in asynchronous scenarios where inbound queues are used, the queues are set to SYSFAIL status and all the messages in the inbound queue are stuck (not processed). Depending on the status of XI processing queues, we can reset a queueu2019s status and trigger processing of messages.
Manual Resend of messages: Use transaction SMQR or SMQ2 to reset the status of queues. As you can see in the following figure, the queue has been marked with a status sysfail.
To be able to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
For automatic qRfc failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues.
b) tRFC Errors
Like qRFC errors one can either manually or automatically initiated processing of messages hanged tRFC calls.
Manual Resend of messages: Use transaction SM58 and check through the list. If necessary, start hanging tRFC calls
under the Edit menu by choosing Execute LUWs.
For automatic tRfC failure recover, schedule the report RSARFCEX for periodic execution.
II. Errors in Adapter Engine
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
regards
kummari

Similar Messages

HTTP error 403 from Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
It looks like these error due to security reason, it seems some authorization profile is missing or may be some other issue,kindly help us at that front.
Thanks and Regards,
Satish

Hi Suraj,
Thanks for the update.We had checked the URL before posting this message,it is picking up correct URL with namespoace, UID and PWD.Exact error that we are getting is as follows:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=pisuper&sap-password=sap$29&sap-client=001&sap-language=EN. Please contact your system administrator.
Here all information are correct.We have checked the SLD check, that is also working fine.Also it is not connectivity related issue, as we are able to transmit XML file to E-Sourcing.
It looks like security issue, but what authorization needs tobe given exactly for HTTP call, we need to know or may be some other issue.
Thanks and Regards,
Satish

HTTP error 403 to Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
Please help.
Thanks and Regards,
Himadri
Edited by: Himadri Chakraborty on Feb 9, 2010 3:35 PM

Time Out Error
In order to get rid of it, Your basis person need to play around with follwing three parameters in order to find an appropriate values as per your hardware sizing and requirement......
icm/conn_timeout
icm/keep_alive_timeout
icm/server_port_< n >
How ever, in general SAP recommandation is as follow....
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600 to allow a maximum processing time of 10 minutes.
Hope this helps !!!
Regards,
J Augastine

Regarding error in the INTEGRATION ENGINE URL

hai guys pls go thru this question carefully,.
when i click on INTEGRATION ENGINE and BUSINESS PROCESS ENGINE IN RWB ,integration engine is in yellow colour status instead of green colour and th result of SELF TEST IN RWB is: Is WEBSERVICE security available? what it mean how can i have my I.E in green colour status?
and the result of self test for BPE is : check the entries from HR control tables? what it mean?
as a result of above errors am not able to test the msg BY SPECIFYING THE url OF I.E and am getting error as:HTTP-404 -not found
hope u understand t he problem pls revert me back with suitable answers

hi
Check this
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Re: ERROR HTTP 404

Max number of retries of error message in integration engine

Hi,
I have a scenario which is generating lot of email alerts if goes in error in SXMB_MONI....
so then i ticked the " suppress multiple alert " checkbox.....but because of this unless i complete one alert in the alert inbox another alert does not come ( considering that 1 alert comes and then after 5 hrs another error occurs for that same interface then that alert will not come unless we clear the previous alert from the alert inbox )
My requirement is everytime that interface goes in error EXACTLY 1 email alert should be generated

Hi,
After you configure the email alerts (without Suppers Multiple values) For every error you can get one email. For example one customer sends data that is failed due to Error "A" at this time you will get an email alert, again other message failed due to error "A" then you will get another email, means for the same error type you are getting multiple emails, to avoid this we can use Suppers Multiple alerts option.
In this case Mail doesn't comes to Alert Inbox also.
Regards,
Venkata Ramesh

ERROR Integration Engine configuration

hi all, i have an error. en sxmb_adm -->Integration Engine configuration y configured next parameters:
rol:Integration Server
corresponding Int. Server: http://<server>:<port>/sap/xi/engine?type=entry
When press in SL buttom, and error occure: No Access to SLD at present.
What should i Do?
Rgds
Message was edited by:
        Rodrigo Pertierra
Message was edited by:
        Rodrigo Pertierra

all RFC ping fine.. when execute TC SLDCHECK i get this:
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SAPSLDAPI_XD0
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   <server>
port number: <port>
user       : sldduser
Use transaction SLDAPICUST if you wish to maintain the SLD server access dat
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     4
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id:      LCRSAPRFC_XD0
gateway host:
<server>
gateway service: sapgw01
Testing the RFC connection to the SLD java client...
RFC ping was successful
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call terminated sucessfully
Retrieved value of
section   = Connections
parameter = com.sap.aii.ib.server.connect.webas.r3.ashost
-> value =
Summary: Connection to the XI Profile works correctly
In transaction SXMB_ADM-->Integration engine configuration , when i do a check get this
Current Configuration (local):
@5F@     Role of Business System: Integration Server
@5F@     Client 200 is Integration Server
@8S\QURL@     Corresponding Integration Server: http://<HOST>:<PORT>/sap/xi/engine?type=sender
System Landscape:
@5C\QErrors@     No access to system landscape at present
r
     Comparison of Current Configuration with System Landscape
@5B\QOK@     Role of Business System: Current Configuration = System Landscape
Message was edited by:
        Rodrigo Pertierra
Message was edited by:
        Rodrigo Pertierra

Mail-Adapter Integration Engine Error during parsing of SOAP header

Hello,
we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
pi.RecoverableException: Received HTTP response code 500 : Error during
parsing of SOAP header.
Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
response code 500 : Error during parsing of SOAP header.
Retries exceded, set message
4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
Has somebody else the same problem and solved it or any idea what the matter could be?
Thanks for your help
Christian

Hi Reddy,
We´ve got the following scenario:
Exchange-Server (is always up)
XI Mail-ReceiverAdapter
I use IMAP4 to access the Outlook-Email-Box
Everything works fine. But some Emails aren´t processed.
I think it´s a problem between adapterframework and the integration engine?
There is no difference between the emails?
If you´ll need further informations ask me?
Thanks

Generated Proxy Error: System not configured as XI Integration Engine

Dear all,
Using transaction SPROXY I generated a proxy on a Message Interface.
This generated as well a method and the associated class.
When I run it, trying to send data through all this, I get the following error:
<b>System not configured as XI Integration Engine</b>
Here is the model I got on another thread, in order to catch the error text:
DATA: l_sys_exception TYPE REF TO cx_ai_system_fault.
*...proxy call
catch CATCH CX_AI_SYSTEM_FAULT into l_sys_exception.
write: l_sys_exception->errortext.
Anyone has any idea where this error commes from?
I am mostly wondering whether the problem comes from my outbound system or XI configuration?
Thanks a lot, have a nice day!
Isa.

check this thread
https://forums.sdn.sap.com/click.jspa?searchID=2727912&messageID=1877263

Error: System not configured as XI Integration Engine

Hi All,
I a getting this following error in RWB-->message monitoring -->adapter engine -->audit log
"2007-11-29 09:28:45 Error Received XI System Error. ErrorCode: SYSTEM_NOT_CONFIGURED_AS_XMB ErrorText: ErrorStack: System not configured as XI Integration Engine
2007-11-29 09:28:45 Error Transmitting the message to endpoint http://p2p:8003/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SYSTEM_NOT_CONFIGURED_AS_XMB:.
what might be the possible errors..
regards,
Rajesh

Hi Rajesh,
you can go through these chek steps
1)go to SLD-->Business systems...and check the role of business system Web AS ABAP (tht was created during installation)...check if the role is integration server
2) go to sxi_cache and in the menu tool bar goto "GoTo" and click AE cache and see if the link is fine? whether the link in sxi_cache for AE cache is showing green traffic signal and also perform a delta refresh.
3)Check whether your business system is tied to the integration server in SLD.
4)In the transaction sxmb_adm -> Integration Engine Configuration can you check whether that role has been defined as Integration Server.
hope these checks will solve your problem
Thanks
sandeep sharma
PS:If helpful Plz reward points
Also you may check whether in specific configuration you may need to add Category as Runtime Engine_Type and current value as HUB.

Communication error when sending PI message from Integration Engine to AE

Hi Experts,
we currently installed and configured PI 7.3 system. Even I run post installation PI configuration several times, we are still facing error when Integration engine sends message to messaging system. ( my scenario: I send test message to IE directly, avoiding AE )...
It might look easy: but even adding PIISUSER full authorization and system restart, the result is the same. I don't know if it could have connection but I also get HTTP 200 instead of HTTP 500 when testing INTEGRATION_DIRECTORY_HMI destination.
Thanks for any help.
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
- 
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="1" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="1" type="T">URL = http://xxx:xxxx/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="1" type="T">User = PIISUSER</Trace>
<Trace level="1" type="T">Cached =</Trace>
<Trace level="1" type="T">Security: Basic authentication</Trace>
<Trace level="1" type="T">Serializing message object...</Trace>
<Trace level="1" type="T">Tuning - AFW_MAXREQUESTCONTENTLENGTH 2000000000</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 2948</Trace>
<Trace level="1" type="T">Timeout: 0</Trace>
<Trace level="1" type="T">HTTP-client: request sent</Trace>
<Trace level="1" type="T">HTTP-client: response received</Trace>
<Trace level="1" type="T">HTTP-client: status code = 401</Trace>
<Trace level="1" type="System_Error">Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)</Trace>
</Trace>

Hi,
So this password change in Exchange Profile + su01 transaction + system restart didn't help.
I increase trace level, and this is even more detailed log in pipeline step Call Adapter.
We also find out that when message arrive to IE we have in java log three entries:
LOGIN.FAILED
User: N/A
IP Address: xxx
Authentication Stack: sap.com/com.sap.aii.af.ms.app*MessagingSystem
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT ok          exception             true       Received no SAP Authentication Assertion Ticket.
2. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false                 true
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          exception             true       Authentication did not succeed.
This log is logged under J2EE_GUEST User.
LOGIN.OK
User: SLD_CL_PIQ
IP Address: xxx
Authentication Stack: sap.com/com.sap.lcr*sld
LOGIN.OK
User: SLD_CL_PIQ
IP Address: xxx
Authentication Stack: sap.com/com.sap.lcr*sld
Last two logs are logged by SLD_CL_PIQ user.
Thanks for any help!

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
- 
<Trace level="2" type="T">no values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="2" type="T">no values in cache (lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="1" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="1" type="T">URL = http://xxx/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="1" type="T">User = PIISUSERA</Trace>
<Trace level="1" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="1" type="T">Security: Basic authentication</Trace>
<Trace level="1" type="T">Serializing message object...</Trace>
<Trace level="1" type="T">Tuning - AFW_MAXREQUESTCONTENTLENGTH 2000000000</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 2941</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="1" type="T">Timeout: 0</Trace>
<Trace level="1" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="1" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="1" type="T">HTTP-client: status code = 401</Trace>
<Trace level="3" type="System_Error">Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)</Trace>
</Trace>
</Trace>

INTEGRATION ENGINE CONFIGURATION ERROR

Hi all,
I configured integration server through SXMB_ADM,but i'm getting error..
Current Configuration (local):
Role of Business System: Integration Server
Client 000 is Integration Server
Corresponding Integration Server: http://xxx:yyy/sap/xi/engine?type=entry
System Landscape:
Errors No access to system landscape at present
Comparison of Current Configuration with System Landscape
regds,
vasanth.

Hi Vasanth,
You are getting this error because the Pipeline URL parameter defined for the XI Business System in SLD is either empty or different than the one defined in "Integration Engine Configuration" in the TCode: SXMB_ADM.
Check the same. I hope this provides you a solution.
Regards.
Praveen

Java.lang.Exception error during XML validation by Integration Engine

Hi professionals,
We are trying to use XML validation by the Integration Engine.
Step 1:
We created an appropriate directory structure where we had to store the structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is
assigned.
Step 2:
We also changed the references in the xsd to exclude all the subdirectory references.
e.g folder1/folder2/abc.xsd is become abc.xsd only
Step 3:
We stored both xsdu2019s (schema xsd and referenced xsd to the directory created in step 1)
Step 4:
We changed the directory and xsdu2019s permissions to 777 (we chose 777 for testing purpose).
Step 5:
We changed the property schema validation of the sender agreement to Validation by Integration Engine.
Step 6:
We checked RFC destination for AI_VALIDATION_JCOSERVER on AS ABAP and AS Java and establish an successful connection test.
RESTULTS
The result of those steps is an error message in the message monitor of PI with the error tekst:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XML_VALIDATION_INB">CX_XMS_SYSERR_VALIDATION</SAP:Code>
<SAP:P1>java.lang.Exception</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
<SAP:Stack>System error occurred during XML validation</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please assist in how to solve this issueu2026.
Regards, Sjaak.

I would suggest follow Appendix A to know the exact path and since you have one XSD referring other XSD check the steps mentioned in Appendix B .... there seems to be some error in referencing ...Appendix A and B are on page 12 & 13 of this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true
Regards,
Abhishek.

Error while testing message from Integration Engine.

Hi,
Trying to send message to Integration engine from RWB, using test mesage tab in Integration engine.
I pasted the payload(IDOC payload) , entered sender service, interface name and namespace and also username and password. Selected quality of servie as Exactly once.
While sending the message getting the following error - "Error while sending".
What could be possible reasons for this error.
Thanks.

Hi,
Please check the following possibilities:
1. Make sure you have selected integration Engine oprtion and not the adapter engine.
2. The USERID and password should be correct.
Please let me know if you still face the problem.
Regards,
Shwetambari.

Error in integration Engine

Hi All,
In integration Engine im getting error as "Exception occurred during XSLT mapping of the application".
when i tried to test the mapping its showing the warning as "javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: Could not execute operation on Java Object. -> java.lang.reflect.InvocationTargetException at "
Please help me reagrding this issue to proceed further!!!

Hi,
Can u please explain the problem little detail...
Are u getting this error in SXMB_MONI??
If yes then can u copy the source payload and check it in the Message Mapping once??
If problem is coming from mapping... try to analyze.. else u can put now vtz exactly the prblm is..
Babu

Error In Runtime Workbench (Integration Engine)

Hi All,
I have an issue with the PI Netweaver 7.0 SR3.We change the client from 001 to newclient by following SAP NOTE.
Everything is happening fine except while i use Transaction SXMB_IFR and then Run Time Work Bench in component monitoring Integration Engine is not in Healthy State,Its showing Yellow Signal and a message is like this
Is Web service security available?
Description :Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)
Also Business Process Engine is also Showing Yellow Signal as
Schedule Background Job for Missed Deadlines
    Schedule Background Job for Work Items with Errors
    Schedule Background Job for Event Queue
    Schedule background job for clearing report
    Schedule Background Job for Shared-Memory Update of Container Fa
    Schedule Background Job for Deadline Monitoring
So please suggest how to proceed to fix these issues.
Thanks,
Gagan Deep Kaushal

Hi,
for WS security please have a look at this page (last question)
http://help.sap.com/saphelp_NW04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/content.htm
you can also try my answer from:
Re: RWB Integration Engine status yellow
BTW
this cal stay yellow and it does not mean that XI/PI will not work
Regards,
Michal Krawczyk
Edited by: Michal Krawczyk on Nov 29, 2008 1:11 PM

Error Type In Integration Engine

Similar Messages

Maybe you are looking for