cancel
Showing results for 
Search instead for 
Did you mean: 

Web Service sync error

former_member440449
Participant
0 Kudos

Hi Gurus,

I have a proxy to WS sync interface.

This interface was working all time in 2 different enviroments, and now exactly the same interface is failing in one of the 2 enviroments. It sounds crazy but it's a fact!!

When we send a message to the WS, we get the next error in response:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Inbound Message 
  --> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIAdapterFramework</SAP:Category> 
  <SAP:Code area="MESSAGE">GENERAL</SAP:Code> 
  <SAP:P1 /> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden</SAP:AdditionalText> 
  <SAP:Stack /> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Why is this happening?

I compare interfaces from both eviroments and they are exactly the same. Also, they are using the same URL.

The only difference is the system number.

Anyone has any idea of where can I check for this? Please remember that a few weeks ago this was working fine and there was no modification done.

Thanks in advance.

Regards.

Accepted Solutions (1)

Accepted Solutions (1)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

> Why is this happening?

403 error is user or password (login credentials) is invalid. Nothing wrong with interface. Please make sure you test with the right user credentials. Hope that helps.

Answers (2)

Answers (2)

former_member440449
Participant
0 Kudos

The issue was solved using https instead of http to call the WS.

I don't understand why in the other enviroment it is working with http and in this one not.

Thanks for all your help.

Former Member
0 Kudos

Hi,

this error usually comes when URL is incorrect or the adapter is not correctly deployed.

MAke sure the URL you are using is same as mentioned in the WSDL.

There are a lot of similar thread available on SDN such as :

Please let us know if you dnt find your answer in these threads..