Magento Soap Error - Premature end of data in tag definitions line 2

4
votes

My client is using Unleashedsoftware.com to connect to a Magento Store. But it gives this error.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
        <SOAP-ENV:Fault>
            <faultcode>WSDL</faultcode>
            <faultstring>
                SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://www.domain.com/index.php/api/v2_soap/index/wsdl/1/' : Premature end of data in tag definitions line 2
            </faultstring>
        </SOAP-ENV:Fault>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

When browsing http://www.domain.com/index.php/api/v2_soap/index/ Firebug gives me “500 Internal Service Error”.

When I browse http://www.domain.com/index.php/api/v2_soap/index/wsdl/1/, I am getting valid XML data.

I checked the server log files and it seems like:

[Thu Aug 30 22:22:25 2012] [warn] [client 92.92.92.92] mod_fcgid: stderr:  in /home/doaminuser/public_html/lib/Zend/Soap/Server.php on line 762

I been searching for couple of days now and today I tried to duplicate the entire site to another test server, and it seems to be working! So that seems to be a server issue.

Please, anybody got any idea what could be the issue?

Is there any better way of debugging this issue, any sample code or debugging tips.

Magento version is 1.6.2

Thank you.

5
apimagentosoapwsdl
Have you been able to solve the issue ? - Subrata
As @AlanStorm pointed out, "It's probably a server configuration issue of some kind". So I had to move on to a dedicated server. The 'curl' command indicated that, the request was not completed. So I assumed the server wasn't capable of processing such a request. I know this was not a solution. Please post any updates if you find anything. - bjjn

5 Answers

3
votes

There's lots of times where Magento's SOAP API fails due to problems your Magento server has communicating with itself.

That is, PHP's SOAP implementation requires that the SOAP server itself fetch the WSDL file via http, and a local network configuration issue gets in the way of Magento fetching it's own WSDL.

You can debug this by SSHing into your Magento server, and running the following command

curl -l 'http://www.example.com/index.php/api/v2_soap/index/wsdl/1/' > /tmp/wsdl.xml

and then examining the wsdl.xml file. Because you're performing this from your web-server, you may get different results than when you're performing it from your local browser.

0
votes

I had a similar problem when calling the URL http://www.store.com/index.php/api/v2_soap/?wsdl
After some time I received the message 500 - Internal Server Error and a Premature end of script headers message in the apache error log.
After a whole day of research I figured out, that the Timeout-Directive of the Apache module (configured in httpd.conf on a Linux environment) was set to "20" which caused the server to send the 500 error after 20 seconds. The problem is, that in my case the Magento system needs a longer time to "crawl" through all wsdl.xml files in order to build the WSDL-output (if you are using Magento SOAPv2). Maybe you should check your Timeout Directive..hope that helps.

0
votes

"I have memories of this. What worked for me was to put the hostname in /etc/hosts on the server plus the www alias on 127.0.0.1 However, in this instance the server was in the building rather than in some ISP place and the LAN had Windows computers on it. Windows users had downloaded lots of trojan-virus-porn things that were spending the whole time spamming the network so the real problem was with the Windows computers on the network, not with the server or with Magento. After fdisking the PC's the problem was solved."

Thank You I've been struggling for 2 days with this on magento 1.6 and Windows Server 2008 adding this line to the hosts file (C:\Windows\System32\drivers\etc) solved the issue for me:

127.0.0.1   www.Domain.com

also remember to fix your magento soap (role) because the Roles Resources doesn't save in 1.6 unless you fix this file:

MagentoRoot\app\code\core\Mage\Adminhtml\Block\Api\Tab\Rolesedit.php

replace this:

if (array_key_exists(strtolower($item->getResource_id()), $resources) && $item->getPermission() == 'allow') {

with this:

if (array_key_exists(strtolower($item->getResource_id()), $resources) && $item->getApiPermission() == 'allow') {
0
votes

In my case the issue was the Mod_Security rule "PHP Easter Egg Access" was enabled. Rule ID: 380800

Once disabled, the api access worked.

An indicator was in the Apache log file:

Jun 19 09:15:52 httpd[1024961]: [error] [client xyz.xyz.xyz.xyz] ModSecurity: [file "/usr/local/apache/conf/modsec/99_asl_jitp.conf"] [line "116"] [id "380800"] [rev "1"] [msg "Atomicorp.com WAF Rules - Virtual Just In Time Patch: PHP Easter Egg Access"] [data "phpe9568f35-d428-11d2-a769-00aa001acf42"] [severity "CRITICAL"] Access denied with code 403 (phase 2). Pattern match "php(?:e9568f3[56]-d428-11d2-a769-00aa001acf42|b8b5f2a0-3c92-11d3-a3a9-4c7b08c10000)" at REQUEST_URI. [hostname "www.yoursever.com"]...

Magento version: 1.7.0.2
PHP version: 5.3.26

More information about the PHP Easter Egg Access rule: http://www.atomicorp.com/forums/viewtopic.php?f=3&t=5057
http://www.0php.com/php_easter_egg.php

For those wanting a quick test script to replicate the issue (useful when trying to convince your hosting provider that it's a problem on their end), use:

<?php
   $server = new SoapServer("http://<url to your magento shop>/index.php/api/v2_soap/index/wsdl/1/");
?>

This is the line in /lib/Zend/Soap/Server.php that triggers the error.

In my case if you browsed to:
http://< url to your magento shop >/index.php/api/v2_soap/index/wsdl/1/
the xml was fine, but if you ran the above php script on the server, the error was given.

0
votes

This error most often appeared for me while omitting www for domain given in Magento SOAP url. Url has to match base url specified in the Magento config.