Error: String could not be parsed as XML

  • Oktober 26, 2019 um 21:07 Uhr #15502
    vicks630
    Teilnehmer

    I just downloaded the plugin and when I put my Amazon Credentials I get this error.
    I don’t know why it doesn’t work.

    Oktober 26, 2019 um 21:19 Uhr #15503
    Timo
    Administrator

    Hi Vick,
    thank you for your request. Which version of ASA do you mean, ASA1 or ASA2? I assume that you mean ASA1, because only there is rarely this error. With the next update it will be fixed, because the PA API 5.0 doesn’t work with XML anymore. The update will be released in the next days.

    Oktober 27, 2019 um 00:13 Uhr #15504
    vicks630
    Teilnehmer

    Yes, it’s ASA1. Thank you! I’ll wait.

    Oktober 29, 2019 um 12:43 Uhr #15505
    vicks630
    Teilnehmer

    Hi, I’ve downloaded the new version of ASA1 an I still get the same error. What can I do?

    Oktober 29, 2019 um 16:28 Uhr #15506
    Timo
    Administrator

    Sorry, the new version was released a bit too early without notices on the setup page about what to do for migrating to PA API 5.0. Another update will be released soon.

    If your AWS is ready for PA API 5.0 you may switch the „PA API version“ option on ASA1’s setup page to „5.0“.

    How to migrate your account (if applicable) you can find in my blog post http://bit.ly/asa2-pa-api-5-0

    Oktober 29, 2019 um 17:15 Uhr #15507
    vicks630
    Teilnehmer

    It still doesn’t work:

    Error: Error calling PA-API 5.0! HTTP Status Code: 503 Error Message: [503] Server error: POST https://webservices.amazon.es/paapi5/searchitems resulted in a 503 Service Unavailable response:

    Oktober 29, 2019 um 19:44 Uhr #15508
    Timo
    Administrator

    Thanks for your feedback. Is your account registered for PA API 5.0? Does it work with the Scratchpad? (https://webservices.amazon.com/paapi5/documentation/play-around-using-scratchpad.html)

    Oktober 30, 2019 um 18:15 Uhr #15514
    Art
    Teilnehmer

    Hi, I have tha same problem wiyh ASA 1 1.4.2: „Error: String could not be parsed as XML“, I didn’t migrated, old api should work today and tomorrow, wha’s the problem?

    • Diese Antwort wurde geändert vor 4 Jahren, 10 Monaten von Art.
    Oktober 30, 2019 um 19:31 Uhr #15518
    Timo
    Administrator

    This is a case that rarely occurs when ASA1 cannot correctly process the XML result of the old API. Sorry, but this won’t get fixed for two days.

    Oktober 30, 2019 um 19:37 Uhr #15519
    Art
    Teilnehmer

    I migrated, but ASA1 1.4.2 blocked all my site with new credentials for api 5, I had to restore an old version of ASA1…. oh my god, what’s happening… I will try new crredentials on another site with ASA1 1.4.2, I will update

    November 3, 2019 um 13:06 Uhr #15541
    Timo
    Administrator

    Could you solve this issue? Currently I have no other error reports about ASA1.

    • Diese Antwort wurde geändert vor 4 Jahren, 10 Monaten von Timo.

Du musst angemeldet sein, um auf dieses Thema antworten zu können.