I was able to resolve the logging by giving the LOCAL_MACHINE/Users group more permission on the file-system tree where RAD is installed (C:\Program Files\IBM\SDP\
). I have found that when I run RAD "as administrator" in Windows 7, the logging problem I had went away.
Perhaps I should have done more granular analysis to figure out precisely which directory at a lower level might've needed different/more permissions, rather than changing it for all of the RAD install tree; but this works for me at the moment.
UPDATE 11.22.2013
I think the ultimate culprit was Windows 7 UAC. Apparently, applications installed within the default "Program Files" or "Program Files (x86)" directories receive extra security constraints when UAC is fully enabled. Running the server in Debug and the Console logging seem to need permission to modify things that Windows 7 feels like shouldn't be modified without elevated privileges. By either NOT installing RAD in the default Program Files or Program Files (x86) directories, OR completely disabling UAC, the problem is resolved. Disabling UAC could be considered risky, so the solution for me was to reinstall RAD outside of the default Program Files locations.