Traditional Versioning Feature Classes in Database Causes Scheduled Models to No Longer Run Successfully

[ArmstKP]

After we versioned, archived and tracked edits on a number of our feature classes, any scheduled models that used these feature classes, will no longer run successfully.  I have also tried creating a new model and publishing the new model and it will fail as well.

Is the versioning actually causing this, by way of locks?  If so, would the locks have to be removed and would the database have to be compressed, every time, before the scheduled model is run?

The error received: