It was the case-sensitivity indeed. The error message, however, is pretty misleading.
Usually, when the syntax is wrong, the command is simply displayed as is without being executed, so I thought it might be a bug...