Sign Up ›
  • Sylvia Gise 7
  • NEWBIE
  • 0 Points
  • Member since 2015
  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 3
    Questions
  • 1
    Replies
1 replies

Intermittently receiving: An internal server error has occurred after successful asynch callout

Receiving this error using basics of force.com application includng VF page, Apex Controller class, VF components (which contain addiitional components). Approximately 70% of the time the call is successful the rest of the time the error is received. Specific call is an Apex ActionFunction with a REST based web service call.
Complete error displayed: An internal server error has occurred An error has occurred while processing your request. The salesforce.com support team has been notified of the problem. If you believe you have additional information that may be useful in producing or correcting the error, please contact Salesforce Support. Please indicate that URL of the page you were requesting, any error on the page as well as any other related information. We apologize for the inconvenience. Error ID: 819438129-231215 (-1412509758)
1 replies

Performance impact since TLS 1.0 shut off

Comparison between our production org and a test org seems to be indicating that network traffic, the callouts to internal services are about 3 x longer. In fact, almost all “traffic” from Salesforce to the browser is also 3 x longer.

The timing seems to align with Salesforce upgrade of TLS in all sandbox org’s which was done over the weekend of June 25. One thought was our 2 way SSL. Do we need to reimport a higher level of certificate into our org’s? Cannot find anything related to what we are seeing, i.e. no suggestions or best practices, etc... have been found on the discussion forums or other searches.
4 replies

JavaScript remoting with continuation is not invoking the callback method

All development and test Salesforce instances are experiencing some form of the following, we have confirmed that functionality was impacted / problem not observed until 7/6:

Visualforce Remoting Exception: Error parsing json response:
'Unexpected token <'.  Logged in?
 
xhr.responseText=
"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<body onload="document.forms['workerForm'].submit()">
<form  action="https://pmic--Dev12.cs41.my.salesforce.com/visualforce/session" id="workerForm" method="post" name="workerForm" ><input type="hidden" name="url" id="url" value="https://pmic--dev12--c.cs41.visual.force.com/apexremote" />
</form>
</body>
</html>"

This is happening when using the Continuation for both JavaScript remoting and action functions.

Issues are intermittent... appear to be permission related... perhaps... because if a user with admin or admin like access logs in "as" the test account that encounters the problem, the problem is not observed. However, when logging in directly using that test account the problem is encountered. In one instance there have not been any code changes implemented by our internal team since 6/30, the organization worked correctly on 6/30, 7/1 and then on 7/5 it has been confirmed that until at least 3:30pm (central) fuctionality was correct. However, on 7/6 the above error began to be received.

Any suggestions or insights would be greatly appreciated...
 
4 replies

JavaScript remoting with continuation is not invoking the callback method

All development and test Salesforce instances are experiencing some form of the following, we have confirmed that functionality was impacted / problem not observed until 7/6:

Visualforce Remoting Exception: Error parsing json response:
'Unexpected token <'.  Logged in?
 
xhr.responseText=
"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<body onload="document.forms['workerForm'].submit()">
<form  action="https://pmic--Dev12.cs41.my.salesforce.com/visualforce/session" id="workerForm" method="post" name="workerForm" ><input type="hidden" name="url" id="url" value="https://pmic--dev12--c.cs41.visual.force.com/apexremote" />
</form>
</body>
</html>"

This is happening when using the Continuation for both JavaScript remoting and action functions.

Issues are intermittent... appear to be permission related... perhaps... because if a user with admin or admin like access logs in "as" the test account that encounters the problem, the problem is not observed. However, when logging in directly using that test account the problem is encountered. In one instance there have not been any code changes implemented by our internal team since 6/30, the organization worked correctly on 6/30, 7/1 and then on 7/5 it has been confirmed that until at least 3:30pm (central) fuctionality was correct. However, on 7/6 the above error began to be received.

Any suggestions or insights would be greatly appreciated...
 
1 replies

Performance impact since TLS 1.0 shut off

Comparison between our production org and a test org seems to be indicating that network traffic, the callouts to internal services are about 3 x longer. In fact, almost all “traffic” from Salesforce to the browser is also 3 x longer.

The timing seems to align with Salesforce upgrade of TLS in all sandbox org’s which was done over the weekend of June 25. One thought was our 2 way SSL. Do we need to reimport a higher level of certificate into our org’s? Cannot find anything related to what we are seeing, i.e. no suggestions or best practices, etc... have been found on the discussion forums or other searches.