We've struggled with this since day one with the API. Now we are having an issue with SELECT calls.
Received several failed connection attempts at various intervals over the weekend. Most of these are select calls made with the intention of cleaning up DB entries left over after transactions are deleted that could be messing with our report calculations. When I run into this problem, I can generally solve the issue by recreating the table from the Method UI. But I should not have to do that.
To be perfectly clear, we are able to load the WSDL into a PHP SoapClient object. That’s not where the connection error is happening… it’s happening when we attempt to request $soap->MethodAPISelect_XMLV2. Request, and exception data can be provided by email, but I am not posting it here.