Error Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK

Facebooktwittergoogle_pluslinkedintumblr

This error occurs when trying to send a message from the PI to the BPMN. It can also occur the first time you’re calling the BPMN. The reason behind this is that the user requires a password change. Therefore, if you log on to the user administrator account, you will be asked to change the password. Obviously, you need to log in and change the password, then use the updated password for the service. But that would only delay the onset of the problem. Instead, enter the user administrator account and change the user to a technical user, instead of an assisting user. If you are using the standard user for this, then whenever you’re calling the service, a password change will be required within 3 months (or whatever is stated by your password policy). So if you stick to the regular user, you’ll face the same error in three months’ time, and you will have to fix it. This is why it is best to change the standard user to a technical user, which doesn’t require a password. Also use the error check statement, which makes it easier to see what invalid content has been found.

rsz_image

Message status set to DLNG 09-04-2015 07:51:36.220 Information Delivering to channel: CC_SOAP_Receiver 09-04-2015 07:51:36.221 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean 09-04-2015 07:51:36.221 Information XISOAP: XI message received for processing 09-04-2015 07:51:36.222 Information SOAP: Request message entering the adapter processing with user Guest 09-04-2015 07:51:36.222 Information SOAP: Target url: http://localhost:50000/MessagingSystem/receive/JPR/XI 09-04-2015 07:51:36.222 Information XI packaging (bulk mode) is not enabled. Switching to normal processing…. 09-04-2015 07:51:36.336 Error Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK 09-04-2015 07:51:36.336 Error SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK 09-04-2015 07:51:36.344 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK 09-04-2015 07:51:36.344 Error SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK 09-04-2015 07:51:36.348 Error Exception caught by adapter framework: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK 09-04-2015 07:51:36.350 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK 09-04-2015 07:51:36.355 Information The asynchronous message was successfully scheduled to be delivered at Thu Apr 09 07:56:36 CEST 2015 09-04-2015 07:51:36.355 Information Message status set to WAIT 09-04-2015 07:56:36.361 Information Message status set to TBDL 09-04-2015 07:56:36.370 Information The message was successfully retrieved from the send queue 09-04-2015 07:56:36.370 Information Retrying to send message. Retry: 1 09-04-2015 07:56:36.376 Information Message status set to DLNG 09-04-2015 07:56:36.379 Information Delivering to channel: CC_SOAP_Receiver

 

Facebooktwittergoogle_pluslinkedintumblr

Comments are closed.