# List of error messages found in audits (log) The messages generated by the system and shown in the log section of an audit job are those listed here below. **Level 1 - Data** * Sublevel - File | **ERROR CODE** | **DESCRIPTION** | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | MSG1001 | Missing file record in some of the repositories: disk, DB temporary tables, DB final tables, ingestion folder, or object XML. | | MSG1002 | Duplicated file. | | MSG1003 | File hash is not equal for the original file and all its copies. | | MSG1004 | The file size is not equal for the original file and its copies. | | MSG1005 | The file has no name registered. | | MSG1006 | The file has no hash registered. | | MSG1007 | The file has no size registered. | | MSG1008 | The file name registered in the database (field ‘fileName’) is not equal to the file name specified in the relative path set in the ingestion job. | | MSG1009 | Error in data read from the object XML: the file has no name (empty name) in the XML. | | MSG1010 | Error in data read from the object XML: the file has not hash in the XML. | | MSG1011 | Error in data read from the object XML: the file has an impossible size (negative number) in the XML. A file size must be 0 or greater. | | MSG1012 | Error in data read from the DB: the file has an impossible size (negative number) in the XML. A file size must be 0 or greater. | | MSG1013 | Error in data read from the DB: the file has no relative path (empty value) in the database. | | MSG1014 | Error in data read from the DB: the file has no hash in the database. | | MSG1015 | Error in data read from the object XML: the file has an incorrect dataformat value. | | MSG1016 | Error in data read from the object XML: the file has an incorrect date for characterization. | | MSG1017 | Error in data read from the object XML: error reading the dataformat validator. | | MSG1018 | Error in data read from the object XML: error reading the validation status (incorrect status). | | MSG1019 | Error in data read from the object XML: the file has an incorrect date for validation. | | MSG1020 | Error in data read from the object XML: error reading the value of the file dataformat (incorrect value). | | MSG1021 | Error in the ingestion XML data: incorrect characterization date. | | MSG1022 | Error in data read from the object XML: incorrect dataformat validator. | | MSG1023 | Error in the ingestion XML data: incorrect validation status. | | MSG1024 | Error in the ingestion XML data: incorrect validation date. | | MSG1025 | Error in database data: dataformat value incorrect for a file. | | MSG1026 | Error in database data: incorrect characterization date. | | MSG1027 | Error in database data: incorrect dataformat validator. | | MSG1028 | Error in database data: incorrect validation status. | | MSG1029 | Error in database data: incorrect validation date. | | MSG1030 | Error in data: hash is empty for the file in the ingestion path. | | MSG1031 | Error in data: size of file in ingestion path lesser than 0. | | MSG1032 | The dataformat value is not equal in all repositories. | | MSG1033 | The characterization date is not equal in all repositories. | | MSG1034 | The file dataformat validator is not equal in all repositories. | | MSG1035 | The validation status is not equal in all repositories. | | MSG1036 | The validation date is not equal in all repositories. | | MSG1038 | Some dataformat values or characterization dates are not found for a preservation plan in which this is mandatory. | | MSG1039 | Some dataformat validation values or validation dates are not found for a preservation plan in which this is mandatory. | | MSG1041 | Some dataformat validation data exists for files with no characterization data. | | MSG1042 | A combination of characterization and validation values has been found, which is not registered in the database. | | MSG1043 | Missing valid validation status for some files that must have them. | | MSG1044 | Missing valid validation or non-validation for a file that must have one of these two validation statuses. | * Sublevel - Folder | **ERROR CODE** | **DESCRIPTION** | | -------------- | ------------------------------------------------------------------------------ | | MSG1101 | The object has a missing folder in some of the repositories. | | MSG1102 | The object has a duplicated folder in some of the repositories. | | MSG1103 | The folder has no name. | | MSG1104 | The folder has different names registered in the database and the object path. | | MSG1105 | Error in object XML data: the folder name is empty. | | MSG1106 | Error in database data: the folder path is empty. | * Sublevel - Metadata | **ERROR CODE** | **DESCRIPTION** | | -------------- | ----------------------------------------------------------------------------------------------------------------------------- | | MSG1201 | Inconsistent metadataset: the use of descriptors from more than one metadata schema in the metadataset has been detected. | | MSG1202 | A mandatory descriptor is missing in the metadataset. | | MSG1203 | A mandatory unique descriptor is missing in the metadataset. | | MSG1204 | The metadata descriptor does not have a valid number format (must be 0 or positive integer). | | MSG1205 | Duplicated metadata descriptor. The indicated descriptor cannot have multiple values due to its type (unicity or versioning). | | MSG1206 | The metadata identifier does not exist in some of the repositories. | | MSG1207 | The metadata descriptor does not exist in some of the repositories. | | MSG1208 | The metadata value is not equal in all repositories. | | MSG1209 | The metadata descriptor does not exist (the iecode for the metadata schema does not exist). | * Sublevel - XML | **ERROR CODE** | **DESCRIPTION** | | -------------- | -------------------------------------------------------------------------------------------- | | MSG1301 | An incorrect label was found in the LIBSAFE internal XML, or this is an incorrect structure. | **Level 2 - Object** * Sublevel - Object | **ERROR CODE** | **DESCRIPTION** | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | MSG2001 | The object does not exist in some of the repositories. | | MSG2002 | The object has no data or does not exist in some of the repositories. | | MSG2003 | The content of the object is not equal in all the repositories. | | MSG2004 | The object has no identifier. | | MSG2005 | The object has no name. | | MSG2006 | Error in reading the LIBSAFE object XML: the file has an unknown attribute. | | MSG2007 | Error in reading the ingestion XML: the file node exists, but there is no file in it. | | MSG2008 | Error in reading the ingestion XML: there is more than one file node. | | MSG2009 | Error in reading the ingestion XML: a file node has no subnode list. | | MSG2010 | Error in reading the ingestion XML: a file node does not exist and the object has an associated characterization set by the preservation plan. | | MSG2011 | All files have not been characterized and the preservation plan sets characterization as mandatory for all files. | | MSG2012 | Error in reading the ingestion XML: there is a file node, while the preservation plan has no characterizer associated to it. | * Sublevel - Object XML Data | **ERROR CODE** | **DESCRIPTION** | | -------------- | ----------------------------------------------------------------------------- | | MSG2101 | There is no reference to the object in the disk XML. | | MSG2102 | The file name of the object XML does not exist in the database for an object. | | MSG2103 | LIBSAFE object XML incomplete or malformed. | * Sublevel - Metadata | **ERROR CODE** | **DESCRIPTION** | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | MSG2201 | The folder which should have the metadata XML does not exist. | | MSG2202 | The metadata XML is incomplete or malformed. | | MSG2203 | The file name of the LIBSAFE metadata XML is incomplete or malformed. | | MSG2204 | The metadata XML does not exist for the object. There must be at least one of these files for the object (one for each metadataset). | | MSG2205 | Error in the numerical sequence of metadataset identifiers. This sequence must be continuous and start at 1. | | MSG2206 | The object has no LIBSAFE metadataset. It is mandatory for it to have at least one, even if empty. | | MSG2207 | Incorrect identification of the number of metadatasets in the ingestion folder. The object ingestion folder must have one only metadataset file. | | MSG2208 | The metadata XML file is not found in the ingestion folder. The ingestion folder should always have a metadata XML generated by the explorer module, when applying the metadata filter. It is possible for this file to be empty. | | MSG2209 | There is more than one metadata schema in the ingestion job. It is mandatory that there is one only metadata schema for each ingestion job. | | MSG2210 | The value for the field ‘isLastMetadataset’ is incorrect. A metadata value belonging to the latest metadataset must have this value set to true, but a value has been detected to have it set to false. | | MSG2211 | The value for the field ‘isLastMetadataset’ is incorrect. A metadata value not belonging to the latest metadataset must have this value set to false, but a value has been detected to have it set to true. | **Level 3 - System** * Sublevel - Preservation Plan | **ERROR CODE** | **DESCRIPTION** | | -------------- | --------------------------------------------------------------------------------------------------------------- | | MSG3001 | The disks associated to the preservation plan are not found. | | MSG3002 | There are no storage groups associated to the preservation plan. | | MSG3003 | An object identifier in the pending audit job belongs to more than a preservation plan. | | MSG3004 | The object identifier in the pending audit job does not have an associated preservation plan (in the database). | | MSG3005 | There are no associated characterizers for a preservation plan that has mandatory characterization. | * Sublevel - Database | **ERROR CODE** | **DESCRIPTION** | | -------------- | -------------------------------------------------------------------------------------------------------------------------- | | MSG3101 | Integrity fail in database. A database ID does not exist or has more instances than those allowed (duplicated registries). | | MSG3102 | Object duplicated in the database. | | MSG3103 | Folder name duplicated in the database for different objects of an only ingestion job. | | MSG3104 | Object identifier malformed or invalid. | | MSG3105 | The object identifier indicated in the disk, XML or ingestion folder does not exist in the database. | * Sublevel - System Repositories | **ERROR CODE** | **DESCRIPTION** | | -------------- | ---------------------------------------------------------------- | | MSG3201 | A set of objects does not exist in some of the repositories. | | MSG3202 | A set of objects is empty in some of the repositories. | | MSG3203 | Object not ingested; it is present only in the ingestion folder. | * Sublevel - Disk | **ERROR CODE** | **DESCRIPTION** | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | MSG3301 | The LIBSAFE disk XML file does not exist in the disk. | | MSG3302 | An object present in the disk is not registered in the database. | | MSG3303 | The estimated disk used space does not belong to the real disk used space. | | MSG3304 | There are inappropriate files in the object root folder. This folder should only keep LIBSAFE XML files on files and folders, as well as the preserved objects. | | MSG3305 | The information kept in the redundancy\_info node is incorrect. | | MSG3306 | Error mounting the disk; the disk could not be mounted. | | MSG3307 | Error unmounting the disk; the disk could not be unmounted. | | MSG3308 | Error accessing the disk. | | MSG3309 | The LIBSAFE disk XML file name is incomplete or malformed. | | MSG3310 | The LIBSAFE disk XML file is incomplete or malformed. | | MSG3311 | The object should not be in the disk, according to the system registry. The database information is taken as the true information. | | MSG3312 | The file dataformat registry was not found in the database. | * Sublevel - Audit Job | **ERROR CODE** | **DESCRIPTION** | | -------------- | ----------------------------------- | | MSG3401 | Audit job with no objects to audit. | * Sublevel - Ingestion Job | **ERROR CODE** | **DESCRIPTION** | | -------------- | ---------------------------------------------------------------------------------------------------------------- | | MSG3501 | The ingestion job has already been done. The referred objects have already been preserved in the LIBSAFE system. | * Sublevel - Metadata | **ERROR CODE** | **DESCRIPTION** | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | MSG3601 | The ingestion job uses more metadata than what is specified by the metadata schema defined in the preservation plan. | | MSG3602 | This object’s metadata descriptor has a value already present in another object. As this descriptor is of unicity, the situation implies an error in the system. | | MSG3603 | The metadata descriptor value you are trying to register in the system belongs to a unicity descriptor that already has that value in the system. | | MSG3604 | The metadata descriptor identifier does not belong to any LIBSAFE identifier (does not belong to any metadata schema). | | MSG3605 | Inconsistent database configuration: there is no metadata schema configured for the preservation plan. Detected in the ingestion audit job. | | MSG3606 | The metadata descriptor for the object audited in the ingestion is of the unicity type, but has a value that is already registered in the system. | | MSG3607 | The metadata descriptor belongs to several types at the same time. A metadata descriptor can only belong to a type at a time. These are: mandatory, unicity, and versioning. | | MSG3608 | The metadata schema has more than one unicity descriptor. A metadata schema can only have one unicity descriptor. | | MSG3609 | The metadata schema has more than one versioning descriptor. A metadata schema can only have one versioning descriptor. | | MSG3610 | The metadataset is empty. A metadataset belonging to an evolution job must have a value for at least one descriptor. | * Sublevel - Versioning | **ERROR CODE** | **DESCRIPTION** | | -------------- | -------------------------------------------------------------------------- | | MSG3701 | Inconsistency between the static and the dynamic versioning of the object. | | MSG3702 | Object version associated to an inexistent object group. |