I've seen a similar post in the past and the issue seems to be located at the database level
I did a research and the issue seems to come from a MSSQL data-source.
I would engage the DB admin on this.
Thinking you're right - a few hour later the issue was corrected and the file started working again. Thanks!