Many of these are not "errors" in the classic sense; they are "Cancelled by server".
This is working as designed: The server sends two or three tasks of a WU initially* (and further replica if tasks fail at the clients or time out at the clients), and as soon as at least one returned result was validated successfully, the server gives notifications to the remaining clients that their tasks are no longer needed for computation. (The server cannot notify the clients by itself, it needs these clients to send scheduler requests. It will hand these server-side cancellations out via its scheduler replies.)
Edit, the clients abort these tasks then if they weren't started yet. If they were started already, boinc is designed to keep them running and complete them, and the Ibercivis server will give credit if the returned results turn out valid too. I have read one or two complaints that server-side cancellations terminated tasks which were already running, but I have not seen actual evidence of this.
*) The admins made this choice because the project has not yet left its testing phase.
However, those tasks in the list you gave, which are "Error while downloading", failed due to a server-side mistake, as per the link in post #11.
Edit, the download errors make it practically impossible to run Ibercivis on many hosts for the time being (until an admin returns and fixes this). Nevertheless there are still several people able to keep the project running:
https://www.boincstats.com/stats/187/user/list/12/0/0