Microsoft Project XML Schedule Integration Error and Warning Messages

Learn about the error and warning messages related to the Microsoft Project (MSP) XML Schedule Integration process, as displayed in the process log, along with their resolutions.

Type	Message	Cause and Resolution
Error	Invalid output directory passed to Project XML reader.	This error occurs when the cOutputPath property is set to a non-empty value that does not point to an existing directory. To resolve this error, ensure the output directory exists before invoking the process.
Error	Couldn’t extract the MSP XML Project data.	This error occurs when the XML dump operation fails while Cobra attempts to extract project data from the Microsoft Project file. To resolve this error, verify that the MSP file is not corrupted, ensure proper file permissions, and confirm that the XML extraction component is properly initialized.
Error	The project file {filename} does not exist.	This error occurs when the specified project file path does not exist in Cobra during field validation. To resolve this error, verify that the project file path is correct and that the file exists at the specified location. Also, check network paths and mapped drives.
Error	The schedule link field {field_name} is not defined in the schedule.	This error occurs when the specified link field name cannot be found in the LNKFLD table during the validation of the control account, work package, milestone, and forecast class fields. To resolve this error, define the link field in the Microsoft Project schedule or verify that the field name is spelled correctly in the configuration.
Error	The schedule link field {field_name} is not a valid type.	This error occurs when the link field found is not the appropriate type for the context. To resolve this error, select a link field of the appropriate type (activity versus resource level) for the intended use.
Error	No projects found in the MSP datasource.	This error occurs when the MSPPROJECT table has zero records, which indicates that no projects exist in the data source. To resolve this error, verify that the MSP data source contains valid project data and that the database connection is functioning properly.
Error	The link to the class field in the schedule has not been defined.	This error occurs when the INTG_RESASG_BUDGET_CLASS_FIELD setting is empty, which indicates that there is no link field configured for the budget class mapping. To resolve this error, configure the budget class field link in the integration settings.
Error	The code file {name} cannot be converted to a fixed significant breakdown structure. Every level must have a fixed length and no separator.	This error occurs when the Cobra breakdown type is BDNCODETYPE_FIXEDSIG and the link field is not in a fixed format. To resolve this error, configure the MSP link field to use fixed lengths without separators or change the Cobra breakdown structure type.
Error	Every level must be the same length as the corresponding level of the Cobra breakdown structure.	This error occurs when the level lengths in the MSP link field for fixed significant breakdown structures do not match the level lengths defined in the Cobra breakdown structure. To resolve this error, adjust the level lengths so they match exactly between MSP and Cobra breakdown structures.
Error	Could not retrieve the MSP resource information.	This error occurs when the SQL query to retrieve resource data (NAME, UID, STANDRATE from the RESOURCE table) fails during rate file loading. To resolve this error, verify the database connectivity, ensure the RESOURCE table exists and has proper permissions, and check for data corruption.
Error	Could not retrieve the MSP task information.	This error occurs when the SQL query to retrieve task data fails during activity data loading. To resolve this error, verify that the TASK table exists with the proper structure, check the database connectivity, and ensure sufficient permissions.
Warning	Empty codes were found in code file {filename}.	This warning occurs when the process detects empty code values during code file validation. To resolve this warning, review the MSP schedule to ensure all required codes are populated.
Warning	{count} duplicates of the following codes were found in code file {filename}: {code_list}.	This warning occurs when the process detects duplicate code values during code file validation. To resolve this warning, review and eliminate duplicate codes in the MSP schedule to ensure data uniqueness.
Warning	The separator(s) ‘{separators}’ in code file {filename} will be removed to convert to a fixed significant breakdown structure.	This warning occurs when punctuation characters (separators) in the MSP code file are detected and automatically removed during the conversion to a fixed significant breakdown structure. To resolve this warning, no action is required; however, review the converted codes to ensure the removal of separators produces the desired result.
Warning	The separator(s) ‘{old_separators}’ in code file {filename} will be replaced with ‘{new_separator}’ to convert to a punctuated significant breakdown structure.	This warning occurs when separators in the MSP code file that do not match Cobra’s separator are replaced during the conversion to a punctuated significant breakdown structure. To resolve this warning, no action is required; however, verify that the separator replacement produces the expected results in the converted codes.
Warning	Skipping Task ID ‘{task_id}’: Empty {date_type} were found.	This warning occurs when a task has empty date fields for the selected source date type while Cobra loads the activity. To resolve this warning, review the Microsoft Project schedule to ensure all required dates are populated for tasks.