What I did (I didn’t encounter those ERRORs myself) is after upgrading to 2.2:
perhaps that did the trick…`?