What log files and info to check when RRC views get an error 500 when selected in v4.0?
Accepted answer
A 500 server error is a very generic message and in and of itself, not informational at all.
You'll typically want to look at the server/logs/rm.log for clues as to the real cause, though sometimes it may also end up leading you to look at the server/logs/jts.log file if the problem is further down inside the server.
Before that however, do have a look at the "show details" as shown in your screenshot. It will occasionally include a log entry "key" so that you can use to quickly locate the origin of the problem in the rm.log.
You'll typically want to look at the server/logs/rm.log for clues as to the real cause, though sometimes it may also end up leading you to look at the server/logs/jts.log file if the problem is further down inside the server.
Before that however, do have a look at the "show details" as shown in your screenshot. It will occasionally include a log entry "key" so that you can use to quickly locate the origin of the problem in the rm.log.