It's unlikely that you're having this problem, but Apache 2.0 nearly drove me out of my mind with that exact message because suexec was turned on. Check out my tale of madness here.

-sam