cancel
Showing results for 
Search instead for 
Did you mean: 

Interface failing at call Adapter Step in sxmb_moni

Former Member
0 Kudos

Hi

I am using PI 7.0..with File to RFC Scenario.

Getting Error in SXMB_MONI at call adapter status...

The following is the error fro moni

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

<SAP:P1>500</SAP:P1>

<SAP:P2>Internal Server Error</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Caught an DatetimeFormatException in <sap:Main><sap:TimeSent> = 2011-12-03T18:52:04Z: invalid format</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>HTTP response contains status code 500 with the description Internal Server Error Error while sending by HTTP (error code: 500, error text: Internal Server Error)

I have checked the RFC connections ...its working...

Do i missing any post installation configuration...its PI 7.0

Please suggest to solve this issue..

Regards

Abhishek

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Simply replace Z with "" in mapping.

Former Member
0 Kudos

Hi

The Date Time is the Header information..not in my payload

My Test Scenario has fields as Customer, Name1,Name2 and Country

Regards

Abhishek

Former Member
0 Kudos

Hi

Have you seen this:

[;

Regards.

Former Member
0 Kudos

Hi

I have already checked this...still same error......

i think this is related to server settings..let me raise this message in Netweaver forum

Regards

Abhishek

Former Member
0 Kudos

Hi

There is a class called CL_HTTP_CLIENT and I think that class is being called so you can put a external breakpoint to debug it and see where that timestamp is being set.

Regards.

rajasekhar_reddy14
Active Contributor
0 Kudos

perform full mode cache refresh and try.

Former Member
0 Kudos

Hi Raja shekhar

i have done the complete cache refresh...CPA cache refresh (mode=full) successfully executed in 10188 milliseconds.

but still same error..

What is the meaning of the error "Could not parse XMBMessage due to Caught an DatetimeFormatException in <sap:Main><sap:TimeSent> = 2011-12-04T14:34:19Z: invalid format"

Where to check this DateTime Format?

Regards

Abhishek

Former Member
0 Kudos

Hi

I just experienced this problem in my PI system, its happening because of the offset that exists in time stamp, as far as I remember they put Z if there is no time difference(because of time zones), if there is a time difference they put that time difference such as 5:00 for 5 hours. In that case your timestamp would be 2011-12-04T14:34:19T:5:00

So you gotta remove that Z from timestamp, if you give me more details, I can help you removing that.

Thanks.

Former Member
0 Kudos

Hi

Thanks for your reply

How to remove this Z.

Please let me know what more details you need ...

PI Abap Timezone : UTC +3 (Timezone maintained by STZAD )

PI Java TimeZone : GMT+03 (Timezone in server)

I have tested a File2File Scenario also...it is also failing in Call Adapter step with the same error...

The following is the Trace from moni..

<Trace level="3" type="T">URL = http://abcpid:50000/MessagingSystem/receive/AFW/XI</Trace>;

<Trace level="3" type="T">User = PIISUSER</Trace>

<Trace level="3" type="T">Cached = X</Trace>

<Trace level="3" type="T">Creating HTTP-client</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Security: Basic authentication</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<Trace level="1" type="T">HTTP Multipart document length: 13862</Trace>

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="3" type="T">HTTP-client: response received</Trace>

<Trace level="3" type="T">HTTP-client: checking status code...</Trace>

<Trace level="3" type="T">HTTP-client: status code = 500</Trace>

<Trace level="3" type="T">Deserializing message object...</Trace>

<Trace level="3" type="System_Error">HTTP-client: error response= com.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Caught an DatetimeFormatException in <sap:Main><sap:TimeSent> = 2011-12-03T18:47:33Z: invalid format</Trace>

<Trace level="3" type="T">HTTP-client: closing...</Trace>

Regards

Abhishek

Former Member
0 Kudos

Hi

If its happening at receiving side, create a mapping and remove Z,

if this error is happening in sender side, you need to tell me whats the sender type, is it IDOC? HTTP? File? or proxy?

Regards.

Former Member
0 Kudos

Hi

Its happening on Receiver side..

Its File to RFC Scenario..

Sender file Adapter has successfully picked the file..but the message is failing in moni before it reaches RFC adapter.

Same error occurs in File2File test Scenario..its failing in moni...

The datetime format is the saptime in the header details...do you want me to map using dynamic configuration?

please suggest me a solution..its Urgent..

Regards

Abhishek

abhradeepbasu
Participant
0 Kudos

Check your adm parameter for both PI and ECC system, whether rightly configured or not.

Former Member
0 Kudos

Hi

If its happening in receiver side, create a mapping and remove the Z.

Let me tell you what I did, I used substring function and get first 19 chars(time stamp is 19 chars up to Z) and concat it with -00:00 to reset the offset.

Regards.