Has anyone else been reciving errors such as these?
2007-12-10 15:55:26 CrmException: An unexpected error occured. Please include this ErrorId if you contact support: X - SalesForceDriver.listAccounts - SalesForceDriver.listUpdatedAccounts
2007-12-10 14:44:12 CrmException: An unexpected error occured. Please include this ErrorId if you contact support: X - SalesForceDriver.getDeletedContacts I have been reciving these quite often as of late.
Also, does anyone know the number we are supposed to contact?
I appologize if this has been answered before in another thread but quite frankly I was not able to find an absolutly definitive answer. We have noticed that when importing Lead and Contact records into SFDC via the API (8.0) and an associated assignment rule that sends an email to the newly added Lead or Contact the email is never sent. I have noticed that this functionality was not enabled in previous releases of the API, but I have been unable to confirm or deny this functionality in 7.0 or above. Has this been enabled since 7.0?
Recently I have been noticing a Connection Reset error being thrown from the SFDC API. Durring night-time hours I have noticed that this error doesn't occur as often. This leads me to belive that the SFDC API is under considerable load durring daytime hours and that this is effecting the rate of return of records from SFDC. Is this a correct assumption? If you need a more specific description of our problem please ask.
I have a question on the return value of a call to QueryResult.getRecords() where the query did not have any returned records. From the documentation we would get in return an instantiated SObject array with length of 0. Is there ever a possibility that this function will return null? Example below.
SoapBinding soapBinding; // Please assume that this is already logged-in. QueryResult queryResult;
For two of our clients, we are getting repeated UNKNOWN_EXCEPTIONs whenever attempting to use the API in any way.
The last successful attempt was on 11/29 (for one client), and 11/30 (for the other).
In both cases, our IP ranges should have pre-populated the known IP list per the new Security settings. I've also verified with one of the clients (the 11/29 client) that our full IP range is present in the new Security settings.
Here's a SOAP error dialog for that client:
Code:
SOAP::Transport::HTTP::Client::send_receive: POST https://www.salesforce.com/services/Soap/u/4.0
Accept: text/xml
Accept: multipart/*
Accept-Encoding: deflate
Content-Length: 681
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
<—xml version="1.0" encoding="UTF-8"–>
<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Header>
<CallOptions>
<client xsi:type="xsd:string">*******</client>
</CallOptions>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<namesp1:login xmlns:namesp1="urn:partner.soap.sforce.com">
<username xsi:type="xsd:string">*****</username>
<password xsi:type="xsd:string">*****</password>
</namesp1:login>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 500 Internal Server Error
Date: Mon, 03 Dec 2007 22:44:33 GMT
Server:
Content-Length: 832
Content-Type: text/xml; charset=utf-8
Client-Date: Mon, 03 Dec 2007 22:44:33 GMT
Client-Peer: 204.14.234.33:443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign International Server CA - Class 3/OU=www.verisign.com/CPS In
corp.by Ref. LIABILITY LTD.(c)97 VeriSign
Client-SSL-Cert-Subject: /C=US/ST=California/L=San Francisco/O=Salesforce.com, Inc./OU=Applications/OU=Terms of use at www.verisign.com/rpa
(c)00/CN=www.salesforce.com
Client-SSL-Cipher: RC4-MD5
Client-SSL-Warning: Peer certificate not verified
<˜xml version="1.0" encoding="UTF-8"™>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://w
ww.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>UNKNOWN_EXCEPTION: An unexpected error occured. Please include this ErrorId if you contact support: 1360156535-4046</faultstring>
<detail>
<sf:fault xsi:type="sf:UnexpectedErrorFault" xmlns:sf="urn:fault.partner.soap.sforce.com">
<sf:exceptionCode>UNKNOWN_EXCEPTION</sf:exceptionCode>
<sf:exceptionMessage>An unexpected error occured. Please include this ErrorId if you contact support: 1360156535-4046</sf:exceptionMessage>
</sf:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Recently I have been noticing a Connection Reset error being thrown from the SFDC API. Durring night-time hours I have noticed that this error doesn't occur as often. This leads me to belive that the SFDC API is under considerable load durring daytime hours and that this is effecting the rate of return of records from SFDC. Is this a correct assumption? If you need a more specific description of our problem please ask.
I get the following error when trying to do a build-clean in the NetBeans IDE:
>deps-jar: >wscompile-init: >sfdc-partner-client-wscompile: >the following naming conflicts occurred: sfdc.DescribeLayout_Type > at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:267) > at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88) > at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63) > at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714) > at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43) > at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22) >error: the following naming conflicts occurred: sfdc.DescribeLayout_Type >Command invoked: wscompile C:\Java\j2sdk1.4.2_08\jre\bin\java.exe -classpath "C:\Java\j2sdk1.4.2_08\lib\tools.jar;C:\Program Files\netbeans-
