function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
BriscoBrisco 

EndPoint URL no longer active

We were connecting to the SalesForce endpoint with the following URL:
http://www.salesforce.com/servlet/servlet.SoapApi
(old version of the API).

Since this morning, that URL no longer seems to be valid.

Anyone know if this is permanent? If so, is there a new URL?

Thanks,
Mike
SuperfellSuperfell
should still work, how is it "no longer valid" what failure conditions are you seeing ?
BriscoBrisco
"(500)Internal Server Error" appears in our Tomcat stack trace. Nothing's changed on our end (that I know of). I was hoping it was something as simple as the endPoint url changing.
benjasikbenjasik
Sounds like an error on the Salesforce side. Please log a case for us with more details.

The endpoints do not change for backwards compatibility reasons.
BriscoBrisco
Not sure if this will help, but looking at the stack trace some more, I see the following:

AxisFault
faultCode: 0
faultString: No such column; cf_00N30000000c9m4; on entity; account

I've been on a manhunt looking for some reference to this column ID and have come up empty so far...
SuperfellSuperfell
That's a known bug in winter '06, the fix is going out soon.
BriscoBrisco
Gah! Do you know if that's for custom fields only or all fields?
BriscoBrisco
Another issue we're having is no matter which account number we query on for an account, we're always getting the same record back.
Is this also a known bug?

Thanks for the help,
Mike
SuperfellSuperfell
it affects queries that query for custom fields via the old (2.0) soap api.

can you post the query that's causing you to always get the same row ?
BriscoBrisco
Here's the code, where accountno is the id we're passing in.

filter[0] = lFactory.makeSimpleFilter("id", accountno, "equals");
Calendar jc = Calendar.getInstance();
jc.set(1950,10,6);
org.w3c.dom.Element value = (org.w3c.dom.Element)binding.query("filter", "account", 20, new java.lang.String[]
{"name", "ownerID", "accountPhone", "accountFax", "url", "billingStreet", "billingCity",
"billingState", "billingPostalCode", "billingCountry", "createdDate", "createdByID", "lastModifiedDate",
"lastModifiedByID"},
filter, null, jc, false);
org.w3c.dom.NodeList nodes = XPathAPI.selectNodeList(value, "/value/valueMap/*/text()");

for (int i = 0; i < nodes.getLength(); i++) {
org.w3c.dom.Node vNode = nodes.item(i);
if (nodes.item(i) != null) {
lMap.put(nodes.item(i).getParentNode().getNodeName(), nodes.item(i).getNodeValue());
}
}
RichardRichard


Brisco wrote:
Not sure if this will help, but looking at the stack trace some more, I see the following:

AxisFault
faultCode: 0
faultString: No such column; cf_00N30000000c9m4; on entity; account

I've been on a manhunt looking for some reference to this column ID and have come up empty so far...




We are seeing the same error. Thread posted over in the General Development area.


The column is one of your custom fields on the account entity. This is the name returned by the "describe" request in the 2.0 API.


Looks like its time to upgrade our code to the newest API version.
RichardRichard


SimonF wrote:
it affects queries that query for custom fields via the old (2.0) soap api.

can you post the query that's causing you to always get the same row ?


We are seeing similar behaviour against Contact and Account. I've just posted details over in the General Development area and am raising a support case. We are not using custom fields tho.
BriscoBrisco
We just upgraded to the latest API and it solved the problems. With all the sample code and documentation, it was a pretty easy transition.