Heya Ken...
<p>
The thing to do, is watch the log while you generate the error. Almost universally, "Query was not a statement returning rows" can be the result of many different, and more specific, problems. Normally, the server's error log will display the more specific problem.
<p>
Overall, the process involves running a shell on the server machine in question and running "tail -f servername-error.log". Then, you try to cause the problem again, and watch what happens in the log. So if you have a server running on port 1234 whose name is "foo", then you'd cd to the place on your server where the aolserver logs are kept, and run "tail -f foo-error.log".
