This content has been marked as final. Show 2 replies
so do you say the error occurs on your login page?
If you have already ruled out hidden, display only and read only items, another reason for that error could be if the page hasn't been completely loaded before you submit the page (for example: click the login button). The error will occur if the hidden item p_page_checksum hasn't been retrieved yet by the browser, because in this case it will send an empty value to APEX if the page gets submitted and you will see the error.
Can that be the case in your scenario where you randomly get the error?
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Yes, on my login page, which is very odd. Not much going on there except the rendering of 2 items (login and password).
I had read Joel's post on this error, about the page not rendering fully before being submitted, but felt this was very unlikely in this situation since the page is so light. The probability of a user putting in user name and password and hitting submit before the page was fully rendered seems improbable?
I have not seen the error myself, have been unable to reproduce, but it has been logged in my error table a few times (using an error handling routine), and reported a few times by users.
So, since writing this post, I have found 1 item on my Page 0 that was both hidden and protected. Nothing in my login page touches that item, but I have since set it to not protected.
But if that had been the issue, I would have expected:
"Session state protection violation: This may be caused by manual alteration of protected page item P0_XYZ. If you are unsure what caused this error, please contact the application administrator for assistance"
"Page protection violation: This may be caused by manual alteration of protected page items. If you are unsure what caused this error, please contact the application administrator for assistance." ?
Or maybe both messages are equivalent?
I will keep watching my error log table, and see if that resolved my issue! If not, I may reach out to you again.