Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Successfactor Login interface error

Hi,

I am using PI 7.4 single stack to integrate successfactor and ECC.

when i am using soap axis channel SFSF_Soap_Adapter_Axis_Login_Response, i am not getting the response. it is throwing below error.

###########################################################################################

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

<!-- Call Integration Server -->

-<SAP:Error SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

<SAP:P1>200</SAP:P1>

<SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>

<SAP:P3/>

<SAP:P4/>

<SAP:AdditionalText>--SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END Content-ID: <soap-bae3bf0c344a11e5a4c90000006e6e1e@sap.com> Content-Type: text/xml; charset=utf-8 Content-Disposition: attachment;filename="soap-bae3bf0c344a11e5a4c90000006e6e1e@sap.com.xml" Content-Description: SOAP <SOAP:Envelope xmlns:SOAP=&#39;http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><sap:ReliableMessaging xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand=&#39;1&#39;><sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging><sap:DynamicConfiguration xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand=&#39;1&#39;><sap:Record namespace=&#39;http://sap.com/xi/System/HTTP' name=&#39;SetCookie&#39;>BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; path=/; HttpOnly, JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; Path=/sfapi</sap:Record></sap:DynamicConfiguration><sap:System xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand=&#39;1&#39;><sap:Record namespace=&#39;/xmlvalidation&#39; name=&#39;SYNC_RESPONSE_BEFORE_MAPPING&#39;>1</sap:Record></sap:System><sap:Diagnostic xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand=&#39;1&#39;><sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand=&#39;1&#39;><sap:Hop timeStamp=&#39;2015-07-27T10:30:55Z&#39; wasRead=&#39;false&#39;><sap:Engine type=&#39;BS&#39;>EDV311</sap:Engine><sap:Adapter namespace=&#39;http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp=&#39;2015-07-27T10:32:03Z&#39; wasRead=&#39;false&#39;><sap:Engine type=&#39;AE&#39;>af.pid.nakpidv1</sap:Engine><sap:Adapter namespace=&#39;http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:MessageId></sap:Hop><sap:Hop timeStamp=&#39;2015-07-27T10:32:07Z&#39; wasRead=&#39;false&#39;><sap:Engine type=&#39;AE&#39;>af.pid.nakpidv1</sap:Engine><sap:Adapter namespace=&#39;http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>bad7e494-344a-11e5-c0e0-0000006e6e1e</sap:MessageId></sap:Hop></sap:HopList><sap:Main xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' versionMajor=&#39;3&#39; versionMinor=&#39;1&#39; SOAP:mustUnderstand=&#39;1&#39;><sap:MessageClass>ApplicationResponse</sap:MessageClass><sap:ProcessingMode>synchronous</sap:ProcessingMode><sap:MessageId>bad7e494-344a-11e5-c0e0-0000006e6e1e</sap:MessageId><sap:RefToMessageId>55b52c99-3d54-1da6-e100-0000ac14650e</sap:RefToMessageId><sap:TimeSent>2015-07-27T10:32:07Z</sap:TimeSent><sap:Sender><sap:Party agency=&#39;http://sap.com/xi/XI' scheme=&#39;XIParty&#39;></sap:Party><sap:Service>BC_SFSF</sap:Service></sap:Sender><sap:Receiver><sap:Party agency=&#39;http://sap.com/xi/XI' scheme=&#39;XIParty&#39;></sap:Party><sap:Service>EDV311</sap:Service></sap:Receiver><sap:Interface namespace=&#39;http://sap.com/xi/SFIHCM01'>SFSFSessionHandlingLoginQueryResult_Out</sap:Interface></sap:Main></SOAP:Header><SOAP:Body><sap:Manifest xmlns:sap=&#39;http://sap.com/xi/XI/Message/30' xmlns:xlink=&#39;http://www.w3.org/1999/xlink'><sap:Payload xlink:type=&#39;simple&#39; xlink:href=&#39;cid:D7B3B5D60B3F3138A68E32077514C9F7&#39;><sap:Name>document-0</sap:Name><sap:Description>unspecified document</sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope> --SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END Content-ID: <D7B3B5D60B3F3138A68E32077514C9F7> Content-Disposition: attachment;filename="document-0.xml" Content-Type: text/xml; charset=utf-8 Content-Description: document-0 <?xml version="1.0" encoding="UTF-8"?> <ns1:loginResponse xmlns:ns1="http://sap.com/xi/SFIHCM01"><result><sessionId>$Version=0; BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; $path=/,$Version=0; JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; $Path=/sfapi</sessionId><msUntilPwdExpiration>2009135746</msUntilPwdExpiration></result></ns1:loginResponse> --SAP_bae6e5b3-344a-11e5-a1f3-0000006e6e1e_END-- </SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace=""/>

<SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.) </SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

###########################################################################################

it is going into above error but it has the proper response in the additional text(session ID.JPG)

if i take above response and test it in log out interface,it is also failing with same error but it has correct response in the additional text.

--SAP_7a8687f0-344b-11e5-9e28-0000006e6e1e_END Content-ID: <B9E6A2B3FDDB7AE0BF1567C6700D5401> Content-Disposition: attachment;filename="document-0.xml" Content-Type: text/xml; charset=utf-8 Content-Description: document-0 <?xml version="1.0" encoding="UTF-8"?> <ns1:logoutResponse xmlns:ns1="http://sap.com/xi/SFIHCM01"><result>true</result></ns1:logoutResponse> --SAP_7a8687f0-344b-11e5-9e28-0000006e6e1e_END


is there any change required in channel SFSF_Soap_Adapter_Axis_Login_Response? did anyone have this error before?

unfortunately i am not able to monitor the messages in PI(Error in single stack Message monitoring tool).

Regards,

Muni

logout result.JPG (35920 B)
logout.JPG (54104 B)
session ID.JPG (73526 B)
replied

I could see that issue was with dynamic header SetCookie is length more than 200. That is why it is failing in ECC. Same error did not happen in PI as it is in latest version and SP.

sap:DynamicConfiguration xmlns:sap=&#39;http://sap.com/xi/XI/Message/30'SOAP:mustUnderstand=&#39;1&#39;><sap:Record namespace=&#39;http://sap.com/xi/System/HTTP'name=&#39;SetCookie&#39;>BIGipServerP_PERFORMANCEMANAGER012.SUCCESSFACTORS.EU-80=!Qb35bxWVQClJSaPehJNTD7EYqYeaC51zB0C93QiJUqh3h7XbikKac2THNei6/tgJy0vaPTBCjvAyQzE=; path=/; HttpOnly, JSESSIONID=6886020214A518D2481773B7539A7D95.DC12BIZXSFAPI01; Path=/sfapi</sap:Record></sap:DynamicConfiguration>

Using Adapter-Specific Message Attributes in the Message Header - SAP NetWeaver Process Integration - SAP Library

Told the same to SAP support.SAP suggested to implement noteĀ  #2028742 - XI runtime: Enhancing the dynamic header for Success Factors.

Now interface is working fine.

It would have been much better if the ECC error gives proper error description.



Thanks Pavan for your help.


Regards,

Muni

2 View this answer in context
Not what you were looking for? View more on this topic or Ask a question