Damon, did you activate full debugging of SQL queries in AOLServer? It eats up a lot of disk space, but it's invaluable when trying to figure out things like this. You want to turn on the "Verbose" and "LogSQLErrors" options, once for each of the three database pools, similar to how it's configured in my "main" pool here:
ns_section ns/db/pool/main
ns_param MaxIdle 1000000000
ns_param MaxOpen 1000000000
ns_param Connections 5
ns_param Verbose On
ns_param ExtendedTableInfo On
ns_param LogSQLErrors On
(I'm not sure what ExtendedTableInfo is, but I'm a big fan of verbose error logs, so I keep it on as well.)
The "no rows returned" error probably means that there's something wrong with the SQL query, but it might also point to a problem with your database connection. Show that to us, and it'll be easier to figure out what the problem is.
