Error when sending by HTTP (error code 200, error text OK)

We receive a quantity of messages everyday that "sometimes", for some
strange reason, seem to fail in XI, with the message:
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>200</SAP:P1>
<SAP:P2>OK</SAP:P2>
<SAP:Stack>HTTP response contains status code 200 with the description
OK System error in parser</SAP:Stack>
We checked out note 871959 but we are in a higher SP release XI 3.0
(14), and the corrections are implemented.
Any other reccomendations?

EXACT, but the interface monitor shows that as an error.
And that's what I need, a good monitoring, that should not appear as an error

Similar Messages

IDoc_02_Error passing data to port-Communication error when sending with HTTP

Hello All,
We are receiving the error "02_Error passing data to port-Communication error when sending with HTTP", when sending the idoc to PI from ECC system.
Observation:
1. Some idocs are failing and immediately after sometime the same type of idocs with different idoc numbers are getting successful.
Eg: Orders. One purchase order is failing at one point of time. later another purchase order is getting successful after some time to the same partner.
2. If i perform the reset of idoc, then it is getting delivered during next scheduled job run.
please help me in resolving the issue.
Regards,
Ch. Venkat.

status 02 is Error passing data to port ...it simply means your port setting has some problem. do configure your port setting and also in partner profile
Thanx and Regards
Arpan Maheshwari

HTTP Receiver Adapter - HTTP client code 110 reason error when sending

Hi,
I am getting the following error when using the HTTP adapter as a receiver to perform an HTTP Post in a destination system :
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Does anyone know what causes this error and more importantly how to trace it ?
Cheers
Colin.

hi Colin,
Check in SMICM if your HTTP service is running. Also in RFC destination one of the parameter (SSL client Certificate) might be wrong which could also cause this problem.
Also check this thread:-
XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Have a look into this SAP Note - 897583
Regards.
Praveen

Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

Hi Exeprts,
My Scenario is mail to ABAP proxy , I have got the bellow error in moni while testing my secnario .
Please help me reslove this .
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Upendra

Hi Mark ,
No error message in attachement . only it daisplay the following information
SAP Library
SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
      SAP NetWeaver Administrator
A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
    System Information
System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
      Services Registry
The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
   User Management
The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
      UDDI Client
The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
   Web Services Navigator
Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
      Web Dynpro
Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.
Regards
Upendra

HTTP 401 Error when sending RosettaNet Message

I get a return code of 401 when I send a http request to another server. The private
process invokes a "Send Business Messgae" from the PIP3A2_Customer_RN2 public
workflow. In my Transport spec., I have specified the URI as http://192.168.100.150:7001/Quantum
which is the destination machine. The full text of the messages displayed on the
console is shown below. I request is being sent as wlpisystem.
<Dec 10, 2001 5:15:56 PM PST> <Info> <B2B> <<User> ****SendQPARequestTag.java:In
Servlet...> ****SendQPARequestTag.java:In Servlet... <Dec 10, 2001 5:15:56 PM
PST> <Info> <B2B> <<User> ****SendQPARequestTag.java:** **QPA Request: Message=<TextMessage[ID:P<286588.1008033356161.0>,
<?xml version= "1.0" ?><QPARequ...]> sent to JMS queue <com.bea.wlpi.EventQueue>>
****SendQPARequestTag.java:****QPA Request: Message=<TextMessage[ID:P<286588.100
8033356161.0>, <?xml version="1.0" ?><QPARequ...]> sent to JMS queue <com.bea.wl
pi.EventQueue> <Dec 10, 2001 5:15:56 PM PST> <Info> <B2B> <<User> ****SendQPARequestTag.java:**
**After receive queue init:> ****SendQPARequestTag.java:****After receive queue
init: <Dec 10, 2001 5:15:56 PM PST> <Info> <B2B> <<B2B-BPM-Plugin> INFO: Log from
Work flow: Customer_PrivateWF started.> <Dec 10, 2001 5:15:56 PM PST> <Info> <B2B>
<<B2B-BPM-Plugin> INFO: Log from Work flow: Starting Public Workflow: <?xml version="1.0"
encoding="UTF-8"?> <Pip3A2PriceAndAvailabilityQuery> <GlobalPartnerRoleClassificationCode>Customer</GlobalPartnerRoleClassificati
onCode> <ProductPriceAndAvailabilityQuery> <ProductPriceAndAvailability> <ProductLineItem>
<ProductQuantity>5000</ProductQuantity> <productUnit> <ProductPackageDescription>
<unitPrice> <FinancialAmount> <GlobalCurrencyCode>USD</GlobalCurrencyCode> <MonetaryAmount>3.50</MonetaryAmount>
</FinancialAmount> </unitPrice> <ProductIdentification> <GlobalProductIdentifier>QPA88</GlobalProductIdentifier>
</ProductIdentification> </ProductPackageDescription> </productUnit> </ProductLineItem>
</ProductPriceAndAvailability> </ProductPriceAndAvailabilityQuery> <fromRole>
<PartnerRoleDescription> <GlobalPartnerRoleClassificationCode>Customer</GlobalPartnerRoleClassifi
cationCode> <PartnerDescription> <GlobalPartnerClassificationCode>Distributor</GlobalPartnerClassificat
ionCode> <BusinessDescription> <GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode
</BusinessDescription> </PartnerDescription> <ContactInformation> <contactName><FreeFormText>Jane Doe</FreeFormText> </contactName> <telephoneNumber> <CommunicationsNumber>7205286001</CommunicationsNumber>
</telephoneNumber> <EmailAddress>[email protected]</EmailAddress> </ContactInformation>
</PartnerRoleDescription> </fromRole> <toRole> <PartnerRoleDescription> <GlobalPartnerRoleClassificationCode>Product
Supplier</GlobalPartnerRole ClassificationCode> <PartnerDescription> <GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassifica
tionCode> <BusinessDescription> <GlobalBusinessIdentifier>987654321</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode
</BusinessDescription> </PartnerDescription> </PartnerRoleDescription> </toRole><thisDocumentGenerationDateTime> <DateTimeStamp>20010612T154020.123Z</DateTimeStamp>
</thisDocumentGenerationDateTime> <thisDocumentIdentifier> <ProprietaryDocumentIdentifier>myDoc</ProprietaryDocumentIdentifier>
</thisDocumentIdentifier> <GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
</Pip3A2PriceAndAvailabilityQuery>
<Dec 10, 2001 5:15:58 PM PST> <Info> <B2B> <<B2B-BPM-Plugin> INFO: Log fromWork flow: PIP3A2_Customer_RN2 started. > <Dec 10, 2001 5:15:58 PM PST> <Error>
<B2B> <<HTTP-Transport> ERROR: HTTP error during send to http://192.168.100.150:7001/Quantum:
code=401, type=text/html, re sponse=...> <Dec 10, 2001 5:15:58 PM PST> <Info>
<B2B> <<B2B-BPM-Plugin> INFO: Log from Work flow: PIP3A2_Customer_RN2Error sending
message> <Dec 10, 2001 5:15:58 PM PST> <Info> <WLPI> <<wlpirequest> <started>2001-12-10
17:15:58.525</started> <requestor>wlpisystem</requestor> <templateid>1001</templateid>
<template-name>Customer_PrivateWF</template-name> <templatedefinitionid>1001</templatedefinitionid>
<instanceid>27009</instanceid> <actions> </actions> <completed>2001-12-10 17:15:58.525</completed>
</wlpirequest>
<Dec 10, 2001 5:15:59 PM PST> <Info> <WLPI> <<wlpirequest> <started>2001-12-1017:15:58.014</started> <requestor>wlpisystem</requestor> <templateid>1002</templateid>
<template-name>PIP3A2_Customer_RN2</template-name> <templatedefinitionid>1002</templatedefinitionid>
<instanceid>27010</instanceid> <actions> <setvariable time="2001-12-10 17:15:58.014"
variable="fromRole">Customer</se tvariable> <setvariable time="2001-12-10 17:15:58.014"
variable="fromService">Customer Service</setvariable> <setvariable time="2001-12-10
17:15:58.014" variable="toRole">Product Suppli er</setvariable> <setvariable time="2001-12-10
17:15:58.014" variable="toService">Product Sup plier Service</setvariable> <setvariable
time="2001-12-10 17:15:58.014" variable="businessActivityID">Qu ery Price and
Availability</setvariable> <setvariable time="2001-12-10 17:15:58.014" variable="actionCode">Price
and Availability Query</setvariable> <setvariable time="2001-12-10 17:15:58.014"
variable="actionCodeVersion">1.3 </setvariable> <setvariable time="2001-12-10
17:15:58.014" variable="PIP">3A2</setvariable>
<setvariable time="2001-12-10 17:15:58.014" variable="PIPVersion">1.3</setva riable>
<setvariable time="2001-12-10 17:15:58.014" variable="retryCount">1</setvari able>
<setvariable time="2001-12-10 17:15:58.014" variable="isSignal">false</setva riable>
<setvariable time="2001-12-10 17:15:58.014" variable="SERVICE_CONTENT_SCHEMA ">3A2PriceAndAvailabilityQueryMessageGuideline_v1_3.xsd</setvariable>
<setvariable time="2001-12-10 17:15:58.014" variable="DOC_TYPE"><!DOCTYPE Pi p3A2PriceAndAvailabilityQuery
SYSTEM '3A2PriceAndAvailabilityQueryMessageGuideli ne_v1_3.dtd'></setvariable>
<activatetask time="2001-12-10 17:15:58.034" taskid="960254416076" name="wai t
for workflow to timeout"/> <settaskduedate time="2001-12-10 17:15:58.034" taskid="960254416076"
name="w ait for workflow to timeout">2001-12-11 17:15:58.034</settaskduedate>
<activatetask time="2001-12-10 17:15:58.044" taskid="990730869247" name="Sen d
Message"/> <setvariable time="2001-12-10 17:15:58.054" variable="rnProcessInstanceId">T
eleplan10080333568524</setvariable> <setvariable time="2001-12-10 17:15:58.485"
variable="messageCode">401</setv ariable> <marktaskdone time="2001-12-10 17:15:58.485"
taskid="990730869247" name="Sen d Message"/> <setvariable time="2001-12-10 17:15:58.485"
variable="reason">Error sending message</setvariable> <workflowdone time="2001-12-10
17:15:59.697" name="PIP3A2_Customer_RN2"/> </actions> <completed>2001-12-10 17:15:59.697</completed>
</wlpirequest>
<Dec 10, 2001 5:16:00 PM PST> <Info> <WLPI> <<wlpirequest> <started>2001-12-1017:15:56.291</started> <requestor>wlpisystem</requestor> <templateid>1001</templateid>
<template-name>Customer_PrivateWF</template-name> <templatedefinitionid>1001</templatedefinitionid>
<instanceid>27009</instanceid> <actions> <setvariable time="2001-12-10 17:15:56.301"
variable="ProductID">QPA88</setv ariable> <setvariable time="2001-12-10 17:15:56.301"
variable="ProductQuantity">5000< /setvariable> <setvariable time="2001-12-10 17:15:56.301"
variable="ProductUnitPrice">3.50 </setvariable> <activatetask time="2001-12-10
17:15:56.311" taskid="2" name="Start the Publ ic Workflow"/> <setvariable time="2001-12-10
17:15:56.321" variable="PIPInput">[B@7803ee</s etvariable> </actions> <completed>2001-12-10
17:16:00.067</completed> </wlpirequest>
>


I found the response to the problem. I summarize the solution in the following point :
1- when you connect to a standalone content services server via the webservices api, you get a single String as cookie and to upload a document to server you use the same single cookie.
2- bu when you connect to cluster content services via the webservices api, you get an Array of String as cookies and to upload a document to server you need to transform the array of cookie into a single String cookie to be able to be authenticated by the http server, look to the following code
String cookie="";
     for(int i=0;i < connection.getCookie().length;i++) {
          cookie = cookie + connection.getCookie() +";";

HTTP response code 500 : Error during Sender Agreement Determination

I am trying a simple file to file scenario and messages are not being received in Integration Server.
Through communication channel monitoring, i have received the below error message.
Error Transmitting the message to
endpoint http://<hostname>:50000/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:
Received HTTP response code 500 : Error during Sender
Agreement Determination.
Can you please help
Regards
Harish

Hi Harish,
http://<hostname>:50000/sap/xi/engine?type=entry
it should be http://<hostname>:8000/sap/xi/engine?type=entry not 50000 as port It should be your HTTP port...please .make the changes !!
In SXMB_ADM transaction under Integration engine configuration please change the settings to http://<hostname>:8000/sap/xi/engine?type=entry
make sure with your basis team that ur http port is 8000 or 8001 ..as per that make the necessary changes..
Regards,

HTTP Status Code 200 Received But Error During Response Parsing

Hi Experts,
We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We searched other threads but could not get any solution. Please provide suggestions.
Thank You.
Regards,
Anandan

the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically and as a result , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
We have done the following activities in order to solve this problem....
increase the value of icm/HTTP/max_request_size_KB to 512MB
                                    icm/wp_roll_timeout   to maximum
                                    HTTP TIMEOUT to 1800 sec
                                   icm/wp_roll_timeout   to maximum
                                     mpi/total_size_MB to maximum
                                   mpi/buffer_size to maximum
and then increased the maxthreadcount ,maxcontentlength using config tool...
and also increased the java heap size to maximum....
After doing everything ,the file has been successfully processed....
the problem has been resolved...

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>

RFC error when sending logon data

Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.*       Start profile START_DVEBMGS00_erptest                                                                                *
#.*       Version                 = 000006                                                                                *
#.*       Generated by user = BASIS                                                                                *
#.*       Generated on = 30.12.2010 , 15:40:55                                                                                *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created                          by: BASIS        24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created                          by: BASIS        24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created                          by: BASIS        24.12.2007 23:53:27
MS = msgserver.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created                          by: BASIS        25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created                          by: BASIS        25.03.2004 08:37:47
#old_value: 3                                 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created                          by: BASIS        16.06.2007 17:35:41
#old_value: 2
#changed: BASIS         14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created                          by: BASIS        10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value:                                   changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000                        changed: BASIS 20.04.2005 17:17:01
#old_value: 0                                 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000                        changed: BASIS 28.03.2005 23:17:11
#old_value: 2                                 changed: BASIS 29.03.2005 12:09:14
#old_value: 0                                 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created                          by: SAP*         08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created                          by: ALPER        13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created                          by: BASIS        27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created                          by: BASIS        30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created                          by: BASIS        30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created                          by: BASIS        30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created                          by: BASIS        18.05.2005 09:20:25
#old_value: 90                                changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created                          by: BASIS        20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS         03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created                          by: BASIS        20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS         03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS         30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS         03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created                          by: BASIS        08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS         03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:34:46
#old_value: 5000                              changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created                          by: BASIS        08.07.2003 20:33:56
#note 103747
#old_value: 10607                             changed: BASIS 08.07.2003 20:34:58
#old_value: 10000                             changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076                              changed: BASIS 28.06.2005 19:36:21
#old_value: 5735                              changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra   by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0

Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP

Hello my name is Arkaitz.
I have this error *"INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP (error code: 110, error text: )"*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DD351E48-7EED-DA5D-E100-0000AC1D4E74</SAP:MessageId>
<SAP:RefToMessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:RefToMessageId>
<SAP:TimeSent>2008-05-05T15:59:00Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>ECYR</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BSBWC_35</SAP:Service>
<SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_1</SAP:Interface>
<SAP:Mapping />
</SAP:Receiver>
<SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_2</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <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">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2008-05-05T15:59:00Z" wasRead="false">
<SAP:Engine type="BS">BSBWC_35</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2008-05-05T16:02:50Z" wasRead="false">
<SAP:Engine type="IS">is.00.EMSXIL601PRE</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20080505</SAP:Date>
<SAP:Time>175900</SAP:Time>
<SAP:Host>emmbwl501pre</SAP:Host>
<SAP:SystemId>BWC</SAP:SystemId>
<SAP:SystemNr>22</SAP:SystemNr>
<SAP:OS>Linux</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>ES78914719V</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal>
<SAP:PipelineElementId>FEC5B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_INTEGRATION_SERVER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="420">SND_CENTR</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>198</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>198</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>52</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.452389</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="emmbwl501pre">20080505155900.454147</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
<SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.454636</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
<SAP:Timestamp type="end" host="emmbwl501pre">20080505155901.884062</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = BWC</Trace>
<Trace level="1" type="T">client = 420</Trace>
<Trace level="1" type="T">language = S</Trace>
<Trace level="1" type="T">user = ES78914719V</Trace>
<Trace level="1" type="Timestamp">2008-05-05T15:59:00Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4E111D481C55742CE10000000AD2202B</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= Dest://SAPISU_XII</Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Can you help me?
thank

Hi,
I think it is the problem with your HTTP connection used by ABAP proxy. so when your PI system tries to connect to ECC using HTTP it fails to connect.
Regards,
Indranil
Award points if applicable

Error when sending message: 403 Forbidden....sender si file

hi...
here iam working with File to IDoc scenario
file is picking from a particular source but its is not showing any messages in SXMB_MONI and in IDX5 (outbound) or in RWB.
when i check test my message in RWB its is showing Error when sending message: 403 Forbidden.
can anyone explain me this problem plz...
all my DESIGN and CONFIGURATION is fine....
its urgent...
THX..
john wesly

Hi John
403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
for more details on error code follow the link
http://www.web-cache.com/Writings/http-status-codes.html
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm
first try to solve problem by making CACHE refresh
either by directory
Check whether you have given the right credentials. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
steps to restart J2EE engine
1) run transaction SMICM
2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
Thanks
sandeep sharma
PS ; if helpful kindly reward points

Error while sending by HTTP

Bom dia
Gostaria de saber quais são os motivos que levam uma mensagem síncrona, a retornar o erro: Error while sending by HTTP (error code: 500 , error text: Internal Server Error). Tenho em mente que possa ser por o receiver estar down mas não tenho a certeza, alguém me pode ajudar?
Obrigado,
Rúben Catrona

Bom dia Rúben,
Por ser uma comunicação síncrona acredito que deva ser externo, porém não dá para afirmar visto que o PI também se comunica internamente por HTTP.
Dê mais detalhes do que está realizando.
Você consegue fazer o mesmo teste diretamente no servidor destino (sem PI) através de outra ferramenta?
Outro teste seria aumentar o log na SMICM para 3, fazer a comunicação síncrona, voltar o nível de trace para 1. E analisar o log da SMICM procurando pela resposta 500.
Atenciosamente, Fernando Da Ró

Having a constant error when downloading latest update for Illustrator CC, error message: Adobe Illustrator CC Latest Updates (December 2014) Installation failed. Error Code: U44M1P7

Having a constant error when downloading latest update for Illustrator CC, error message:
Adobe Illustrator CC Latest Updates (December 2014) Installation failed. Error Code: U44M1P7

U44.. update error http://forums.adobe.com/thread/1289956 may help
-more U44.. discussion http://forums.adobe.com/thread/1275963
-http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
-http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html

Error when sending message: 500 Internal Server Error

Hi
IE is not accepting any messages,
when I try to send the messgae to the IE ( using RWB) i am getting the below error " Error when sending message: 500 Internal Server Error".
following things what i have noticed.
1. Pipleline URL is fine, both in the BS of XI and in the RFC destnation which i am maintaing on the IE admin) URL is "http://<host>:8000/sap/xi/engine?type=entry"
2. SICF all the XI serivess are up and running, i am able to test these service.
3. The http port is active ( SMICM )
Pls note the error is 500 Internal Server Error
regards
Nisar

I think in a simple term 500 can be said as "the request cannot be processed curretnly", these options mentieoned by you are not applicable in my case.
This generally occurs due to load problem or if you are on an SP less than 12 or even if there is an administration problem---I am on PI7.0 , what are the administration problem you are talking about?
1 Check Table Space is enough. ---i had installed server recently & very few interface running.
2 Server licence Date or Time. In this case change system date and restart server.---i have recently installed server.
3 Check the service pack levels on your XI. If it is obsolete upgrade it with latest versio----Can u explain more on this?
Try restart the java stack(XI Server) and follwing services.
com.sapii.af.app ---I am not passing trough Adater framework, so i dont think this service will matters....
com.sapii.cpa.af.app.---CPA cahe is done sucessfully, as i said i am not passsing through adapter framework.
basically for a simple HTTP post what might cause 500 error if all necessary services are up and running?
regards
Nisar

Error when sending by HTTP (error code 200, error text OK)

Similar Messages

Maybe you are looking for