What it means
Server-side JavaScript in an XPage failed at the line and column shown, most often because a variable was null or a method call failed.
Common causes
- A lookup such as
getDatabase, getView or getDocumentByKey returned null and the next line used it
- A misspelt method or property name, which the editor does not always flag
- The current user lacks access to a database or view the code opens
Quick fixes
- Go to the line and column in the message and check each object for null before using it
- Wrap risky code in
try { } catch (e) { } and log the error so you get a clearer message
- Tick Display XPage runtime error page in the application's XPages properties while testing to see the full stack trace
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.