IIRC this error message is throw when an AWS ELB is empty(in my experience). I'd imagine it could be thrown if all servers in the ELB are maxed out.