We have managed to find the error in the database and repaired it.

The site is back online now :)