on 12-04-2011 10:57 AM
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
Hi,
Simply replace Z with "" in mapping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
perform full mode cache refresh and try.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
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
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
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.