Following standard update methods the aforementioned error appeared.

Earlier updates (7.27- 7.29) following the same methodology have taken place with no issues.

Thanks.

Comments

gnorf’s picture

Status: Active » Closed (fixed)

This issue can be dismissed, turns out something was wrong with either web server or structure at the time of update. New update based on standard methodology attempted and no issues detected before/during/after update.

Thanks.