function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
thoriyasthoriyas 

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

I am seeing this error when I try and build my application. Is this something in the Salesforce side?
 
Your help is much appreciated.

An internal server error has occurred An error has occurred while processing your request. The salesforce.com (http://salesforce.com" target="_blank) 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 (https://help.salesforce.com/apex/hthome" target="_blank). 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 (http://salesforce.com" target="_blank)!

Error ID: 1812804321-418638 (-1300335745)
 
Thanks,
Sagar
 
Sr.Salesforce Developer
+91 9033336822
Best Answer chosen by thoriyas
Gordon Engel 7Gordon Engel 7
Whenever you see an Internal Server Error you should contact Salesforce Support. 

In this case it appears that the component namespace is null, causing an exception, but I don't know if that's within your ability to influence.

All Answers

Gordon Engel 7Gordon Engel 7
Whenever you see an Internal Server Error you should contact Salesforce Support. 

In this case it appears that the component namespace is null, causing an exception, but I don't know if that's within your ability to influence.
This was selected as the best answer
thoriyasthoriyas

Thanks for the reply Gordon!

I have looked at the component and all of them have namespace. How do you know that this is namespace null issue ?

Thanks,

Sagar

Gordon Engel 7Gordon Engel 7
I looked at the internal Salesforce log corresponding to that ISE number, You typically cannot diagnose this type of problem without help from Salesforce Support.
thoriyasthoriyas
Thanks Man, It's work now... It was namspace issue. Thanks!