This issue may occur when an update is applied to a server, but a database with scheduled queues configured has not had database revisions from the update run on it.
 
To resolve this issue, log in to all attached database to ensure database revisions from the update are run.