I remember that in 8.5 beta 2 there was an application-wide setting which would produce detailed error messages in the browser window instead of just printing generic Http error numbers. Unfortunately I can’t remember where I had to enable this option. Either I’m having a personal memory leak here or this option is gone … Could someone please help me out?
Thanks in advance!
-Lothar
Subject: Have you ‘Display default error page’ set?
Try setting ‘Display default error page’ set in the Application Properties. That’ll give you a stack trace when that exception happens again. Then the issue might become clearer.Regards,
Paul.
Subject: Tried already, but without success
That was the setting I had in mind, but since the dumb old Error 500 kept appearing even after setting the option I thought that maybe I had been mistaken…
Now I tried again in my xpage, same result (error 500). Then I tried in a brand new xpage in the same db with some simple JS error built into a computed field, still same result. then I copied over that new xpage into a brand new db, set the default error page option, and - voila!- instead of error 500 the stack trace is displayed!!
To go into detail: the db, that’s NOT showing the stack trace error page is the same that I used in beta 2 and which back then wuold show me those detailed error messages.
What could be the reason that’s prohibiting the detailed error messages to show up?
Subject: Those 500 errors…
So it’s an existing Beta 2 db inside the Gold which is causing problems. This shouldn’t be a problem even though .
And it’s building OK inside Designer? And you’ve done a clean (selecting Project Clean… from the main menu in Designer) of the Application? Other than that I’m not sure why you’re not getting the stack trace now in the Gold.
Do you want to send on the app to me (paul_hannan@ie.ibm.com) to see if I can reproduce your issue?
Lump hammer solution:
If all else fails, you could try copying out all of the design elements from beta2 app to a new application. It’s drastic and probably what you don’t to go after but you’ll be on a cleaner base I reckon.
Regards,
Paul.
Also, there’s a nice article on those XPages error and why a user might be hitting them here - Troubleshooting HTTP errors when working with XPages
Subject: I’ll give it a try this afternoon…
Thanks, I’ll try what you suggested asap!
Just for info: the db is a test app I built along Chris Toohey’s “Harness the power…” tutorial. So it’s basically a personal directory with some extras built into it.
The errors that are causing the error 500 pages are built in on purpose in order to show advanced options in some workshop, so in this special case I WANT those errors to happen 
I’ll post an update after having tried what you suggested.
Subject: Clean didn’t help…
database is on its way…
Subject: I have the same problem, but above solution did not worked…
Any idea what is the next step?
It works fine on all downloaded samples. But on our database that doesn’t work.