Vote 380  points

Paul McGurn

"An internal server error has occurred" - in Visualforce, just show us the error

Salesforce Platform, Apex & Visualforce, Developer Tools

When we are working in super-complicated code implementations, we see this: 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 of help in reproducing or correcting the error, please contact Salesforce Support. Please indicate the URL of the page you were requesting, any error id shown on this page as well as any other related information. We apologize for the inconvenience. Thank you again for your patience and assistance. And thanks for using salesforce.com! Error ID: 1458724295-2433 (-1376090290) Very, very frequently. It's because we're pushing the platform past the foresight of the implemention in regards to error handling. We'd like to know what the actual underlying error/stacktrace is. Troubleshooting code when we get to this point is an utter nightmare, because all we can do is trial and error until it goes away, or until it can throw an error that Salesforce was prepared to handle in the user-facing programming interfaces. I can understand a reluctance to show the stack trace when it comes to non-Visualforce pages for security reasons, but in our own code, we expect to see mroe helpful debugging info.

3 years ago · 12 Comments ·Merge Idea · Report Abuse

Latest Comment from Product Management

Andrew Waite

 This type of error is a result of a bug in the salesforce code base. Yes it's true that in many cases you can find ways to avoid hitting that code path but unless you have a decent understanding of the salesforce implementation/code base the stack trace wouldn't help you. Having worked on both sides I speak from experience.

As the message indicates, salesforce does get notification when this occurs (it actually goes to development) but it always helps to have a reproducible case to fix it so when this happens if you have one it's best to notify support with that information so we can address the issue as quickly as possible.

I certainly understand the frustration, I have been there and it's no fun flying blind but what we could show really wouldn't make the solution visible.  If you hit this again and have a reproducible case please notify us. At the very least we may be able to suggest a workaround for you while we address our bug.

My apologies for your inconvenience. 

BFear, try enabling developer mode (checkbox on User).  We use this setting to determine whether you want the extended error messaging.
 

3 years ago · Report Abuse

1 to 10 of 12 | Next Page

Ideas

Apps

Questions

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce.com takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.