In our case I discovered the SQL Login used to make the call became corrupt (you can test by trying to script a drop/create - should get same error). Issue was resolved by restarted SQL Server service..