SOAP Api Connection Errors after upgrade to 19.4.17

[Dirtyhair1]

Preconditions (*)

1.Previously had OpenMage 19.4.15 installed with no issues. We updated to 19.4.17 on Wednesday and straight away have had issues connecting by SOAP to our inventory system. We have also been notified that Klaviyo cannot connect to our store either.
2.

Steps to reproduce (*)

1.Update to Openmage 19.4.17 from Openmage 19.4.15

Expected result (*)

1. We should have a clean update with no issues, we tested the site on our staging setup before pushing live and didn't notice anything. On the staging site we don't have these platforms connected though so only found out once pushed to production/live site.

Actual result (*)

1. Dear Systems - inventory system - cannot pull any orders from Magento store into Dear Systems, nor can it push any inventory updates to our Magento store. When we try to force it to do one of these actions, an error comes up which is in the image below:
   
   "Unexpected WSDL element"
2. Klaviyo - email marketing platform - same issue but mainly refers to order/customer data, it is not syncing with Klaviyo and comes up with similar error:
   "Invalid WSDL file at website. Received error message: ":8:37: not well-formed (invalid token)."

Anyone else seeing anything like this?

[fballiano]

would it be possible for you to test the github version of openmage19? there are so many things going on at the moment that the problem could have been solved already?

[fballiano]

It could be this one btw:
#2405

[addison74]

Check this file /app/code/core/Mage/Api/etc/wsi.xml.

If you have in line 8 the following statement targetNamespace="OpenMage" then change it to targetNamespace="urn:OpenMage".

[Dirtyhair1]

Hey guys, thanks for your feedback, fix mentioned above has been applied.

Klaviyo - can sync now so all good, no problems there.

Dear Systems - still having problems but changed message, per below:

“Failed to load orders: SOAP-ERROR: Parsing Schema: can't import schema from 'http://schemas.xmlsoap.org/soap/encoding/'”

So will have to look further.

Appreciate all you guys are doing but did the change that caused this need to be implemented in OpenMage 19.4.x?

I have gone through #2399 and #2405

Just wondering if these kinds of changes should be kept in OpenMage 2.0.x?

[sreichel]

Dear Systems - still having problems but changed message, per below:

“Failed to load orders: SOAP-ERROR: Parsing Schema: can't import schema from 'http://schemas.xmlsoap.org/soap/encoding/'”

This URL works for me. I just found this ... https://community.oracle.com/tech/apps-infra/discussion/648011/schemas-xmlsoap-org-is-not-working.

Just wondering if these kinds of changes should be kept in OpenMage 2.0.x?

This issue/error/bug is not related to 19.4 or 20.x versioning at all. This change was made to validate XML files, that would be okay for 19.x too, but we just have not tested it properly.

My question is, why it takes so long to bring a new release. This problem is known for 3 weeks and i dont know when next release is planned. If we break something in latest release, we should be possible to fix it quickly.

[Dirtyhair1]

@sreichel ok got you. Sorry if that came across wrong, but what I meant was, this change has caused issues in previously fine Magento/OpenMage stores. Anyway, didn’t mean to be rude, just commenting.

Further, I have run the process again and now the error message is changed:

“ Failed to load orders: CommunicationException: Error in deserializing body of reply message for operation 'salesOrderList'.”

I understand what you were saying and I wonder how many other stores have been affected like this. One thing to note is we DON’T have “WS-I Compliant” enabled which was mentioned in #2399

I’m sure this will be an easy fix, but yeah, unexpected issue for sure.

[sreichel]

There was nothing wrong or rude :) This problem exists since some days an should be fixed asap.

[addison74]

From what someone said in another post, the cache must be deleted and it still lasts until it is deleted on the other side.