I'm getting 'SOAP server not reachable' error when trying to send a SOAP request. This happens on all computers here. However, I'm able to ping the server without any problems. Is there a way to get a quick glance on whether the server is really temporarily unavailable so I'd know where (and if) to start troubleshooting?
I've used URL passed after logging in (https://na0-api.salesforce.com/services/Soap/u/6.0 - it's Enterprise account), and also tried using http instead of https without any luck. Everything worked just fine last week - 'SOAP server not reachable error' started this morning.
When I receive SForce SOAP reply to a query, characters are included in the SOAP body that often break XML structure, especially when placed inside the tag brackets. With HEX editor, I've noticed that characters are placed on regular intervals, so I doubt they are random. Here's the example of the SOAP reply:
HTTP/1.1 200 OK Server: sfdc Cache-Control: private Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked Date: Fri, 06 Jan 2006 22:56:22 GMT
3f59
... and then 3ff8 is added (with line feed and carriage return before and after) after every 6400 bytes. I've also tried to capture TCP stream, and repeating 3ff8 shows up there as well. Here's the header of my SOAP request if that helps:
POST /services/Soap/u/6.0 HTTP/1.1 User-Agent: 4D SOAP client Content-Type: text/xml; charset=utf-8 Host: na0-api.salesforce.com Connection: Close SoapAction: "" Content-Length: 5076
Any ideas, hints, or pointers why those characters show up? Thanks,
I'm working on a 4D SOAP web service that uses SForce 'query' to retreive data. The problem is that half of the objects are 'unretreivable' due to the error: "The returned XML is incorrect. : Complex types are not parsed in this version."
Most of the errors are elaborated as: "error at line X, column Y: The input ended before all started tags were ended. Last tag started was 'sf:Body'", although I have several "expected equal sign" and "expected end of tag" errors as well.
Are there any XML cases and/or exceptions that might cause this?
We've never had any problems of this type with test databases, but only with real large accounts, so I'm suspecting that something unusual (special character? tag?) in SOAP reply is causing this.
I'm getting 'SOAP server not reachable' error when trying to send a SOAP request. This happens on all computers here. However, I'm able to ping the server without any problems. Is there a way to get a quick glance on whether the server is really temporarily unavailable so I'd know where (and if) to start troubleshooting?
I've used URL passed after logging in (https://na0-api.salesforce.com/services/Soap/u/6.0 - it's Enterprise account), and also tried using http instead of https without any luck. Everything worked just fine last week - 'SOAP server not reachable error' started this morning.
When I receive SForce SOAP reply to a query, characters are included in the SOAP body that often break XML structure, especially when placed inside the tag brackets. With HEX editor, I've noticed that characters are placed on regular intervals, so I doubt they are random. Here's the example of the SOAP reply:
HTTP/1.1 200 OK Server: sfdc Cache-Control: private Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked Date: Fri, 06 Jan 2006 22:56:22 GMT
3f59
... and then 3ff8 is added (with line feed and carriage return before and after) after every 6400 bytes. I've also tried to capture TCP stream, and repeating 3ff8 shows up there as well. Here's the header of my SOAP request if that helps:
POST /services/Soap/u/6.0 HTTP/1.1 User-Agent: 4D SOAP client Content-Type: text/xml; charset=utf-8 Host: na0-api.salesforce.com Connection: Close SoapAction: "" Content-Length: 5076
Any ideas, hints, or pointers why those characters show up? Thanks,
I'm working on a 4D SOAP web service that uses SForce 'query' to retreive data. The problem is that half of the objects are 'unretreivable' due to the error: "The returned XML is incorrect. : Complex types are not parsed in this version."
Most of the errors are elaborated as: "error at line X, column Y: The input ended before all started tags were ended. Last tag started was 'sf:Body'", although I have several "expected equal sign" and "expected end of tag" errors as well.
Are there any XML cases and/or exceptions that might cause this?
We've never had any problems of this type with test databases, but only with real large accounts, so I'm suspecting that something unusual (special character? tag?) in SOAP reply is causing this.
