-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal Server Error on tableGridStandalone page #25
Comments
Might be relates to Summer '17. Or even worse something org specific. Please be so kind and open a case with Salesforce support and ask them what the provided error Id means. |
Thanks for the quick response. But salesforce won't allow to open case regarding development related issues. |
I see. They don't provide support as described here: https://salesforce.stackexchange.com/questions/120242 Ask them if they help you if they use my Premier Support. I could even open a case for that. I'm might have no time to fix the issue for you (remember: this is open source ;-) but at least we should know and document the root cause of such error. |
Thanks. I have logged a case with salesforce support regarding this issue. |
Let me know what they find out. |
They have checked server logs and replied error message SQLException while executing plsql statement, ThreadName: /apex/tableGridStandalone. Since this tool is not from salesforce they cannot provide support on it. I have asked the log for the exception since I'm not getting this exception in my log. |
SQLException while executing plsql statement is a Java error from the Salesforce backend. I can't do nothing about it. I also can't reproduce it on my end. Sorry I can't help here. I leave it open. Maybe somebody else knows what's going on here. |
This tool works fine in sandbox. When I deployed it to production it runs into An internal server error has occurred any time when I do sorting, pagination etc. I have limited records to 1000, 100, and 10 even. Still it runs into the same error.
The text was updated successfully, but these errors were encountered: