SAP CPI Odata adapter error 'WstxUnexpectedCharException'

[Muska18]

Hello SAPians,

While trying to connect with S4Hana Public cloud through Sales Order Odata v2 API , I'm getting the WstxUnexpectedCharException error ,attached the image below.

Our odata API url - https://XXXX/sap/opu/odata/sap/API_SALES_ORDER_SRV/A_SalesOrder.

I am stuck here now for a few days trying, googling, checking help documentation, but there is no clear description/explanation available.

Can someone help me here . 

Regards,

Muskan

SAP Integration Suite  OData API  SAP BTP, ABAP environment SAP S/4HANA Cloud Public Edition 

[Ryan-Crosby]

Check the logs to see the URL that is being invoked because it indicates an incorrect & character at position 128.

[Vivek88]

Have you solved this? if yes, please let me know wat u did?

[Dinu]

You have to create a communication user and use that for the integration. You can find several resources in the community and in other SAP assets for this.

[SeanGibbs]

Is this confirmed to be the issue? I am getting the same error in a different scenario but I am having the authentication working.

[Dinu]

The error is becasue the response is not valid xml. The usual cause is authentication failure. In this case the response code is 200 with html content.

[Dinu]

You are seeing this issue because authentication is failing. The server is responding with a page to login. The adapter is failing to parse the html page.

Solution is to fix authentication. 

[Muska18]

Thank you for the reply

[Muska18]

Hi Dinu

We are passing the required authentications, you could see that in Screenshot below

we are getting the same unexpectedcharacterexception error

but when we are using local emdx file it is accepting the Connection, but the iflow gets fail in the triggering throwing same error.

Could you highlight if we are doing something wrong??

[Dinu]

You have to create a communication user and use that for the integration. You can find several resources in the community and in other SAP assets for this.

[carlosrpereira]

One of the your query parameters was not preceded by "&", you will need check your endoint call to find it.