Actual Cost Integration Error and Warning Messages

Learn about the error and warning messages related to the Actual Cost Integration process, as displayed in the process log, along with their resolutions.

Type	Message	Cause and Resolution
Error	Please select a valid project.	This error occurs when you have not selected a project, the selected project name is empty, or the project does not exist in Cobra. To resolve this error, select a valid project.
Error	The calendar file ‘{0}’ for project ‘{1}’ does not exist. Please update the calendar file on the Project Properties screen.	This error occurs when the calendar file assigned to the project does not exist or has been deleted. To resolve this error, assign a valid calendar file to the project using the Project Properties dialog box.
Error	Please select a valid project.	This error occurs when you do not have write access to the selected project. To resolve this error, contact your Cobra administrator to request write access to the project.
Error	Please specify an actual cost file to import.	This error occurs when you choose to import from an actual cost file but do not specify a CSV file. To resolve this error, select a valid CSV file that contains actual cost data.
Error	Cannot locate actual cost file.	This error occurs when the specified actual cost file path cannot be found or when the specified actual cost file path includes characters that are not allowed in the Windows file paths. To resolve this error, ensure the file path is correct and that the file exists at the specified location or remove the invalid characters from the file path.
Error	Please select a valid file type for actual costs.	This error occurs when the actual cost file does not have a .csv extension. To resolve this error, select an actual cost file with a .csv extension.
Error	Please specify a connection name.	This error occurs when you choose to import from a database but do not specify a connection name. To resolve this error, specify a valid connection.
Error	Please select a valid connection.	This error occurs when the specified connection name cannot be found or does not correspond to an actual cost integration connection. To resolve this error, select a valid actual cost integration connection.
Error	The following fields have been selected more than once.	This error occurs when you select the same Cobra field for multiple columns on the Field Mapper page. To resolve this error, ensure each Cobra field is mapped to only one column.
Error	Both ‘Result’ and individual result names may not be selected as columns.	This error occurs when you select both the generic DATA_TYPE and specific resource result fields on the Field Mapper page. To resolve this error, select either a generic DATA_TYPE or a specific resource result field. Do not select both.
Error	The result value must be selected with the result.	This error occurs when you select a DATA_TYPE field but not a DATA_VALUE field on the Field Mapper page. To resolve this error, select a DATA_VALUE field for a DATA_TYPE field.
Error	The result must be selected with the result value.	This error occurs when you select a DATA_VALUE field but not a DATA_TYPE field on the Field Mapper page. To resolve this error, select a DATA_TYPE field for a DATA_VALUE field to identify the result type.
Error	You must define the Control Account field to map the import data.	This error occurs when the Control Account key fields (CA1, CA2, and CA3) are not mapped on the Field Mapper page. To resolve this error, map the Control Account key fields on the Field Mapper page based on the project configuration.
Error	You must define the Work Package field to map the import data.	This error occurs when the Work Package (WP) key field is not mapped on the Field Mapper page and you are loading at the work package level. To resolve this error, map the WP key field on the Field Mapper page.
Error	You must define the Cost date field to map the import data.	This error occurs when you select the Use Cost date to define Control Account or Work Package dates option on the File Selection page but do not map the Cost date field on the Field Mapper page. To resolve this error, map the Cost date field on the Field Mapper page or clear the Use Cost date to define Control Account or Work Package dates option on the File Selection page.
Error	Please specify a class.	This error occurs when you do not select a default class or do not map the Class field on the Field Mapper page. To resolve this error, select a default class or map the Class field on the Field Mapper page.
Error	Please select a valid class.	This error occurs when the selected class on the Class and Results page does not exist for the project at the appropriate level (control account or work package) and type (Actual). To resolve this error, select a valid actual cost class that exists in the project.
Error	The user doesn’t have view and update rights to the selected class.	This error occurs when you do not have update access to the selected cost class on the Class and Results page. To resolve this error, contact your Cobra administrator to request update access to the cost class.
Error	Please specify classes to be excluded.	This error occurs when you select the Select Classes to exclude checkbox on the Included Costs page but do not specify any classes. To resolve this error, specify at least one class to exclude or clear the Select classes to exclude checkbox on the Include Costs page.
Error	Invalid exclusion class.	This error occurs when one or more classes selected to exclude on the Included Costs page do not exist in the project. To resolve this error, ensure that only valid classes are selected on the Include Costs page.
Error	The user doesn’t have view and update rights to the excluded class ‘{0}’.	This error occurs when you do not have update access to one or more classes to exclude on the Class and Results page. To resolve this error, contact your Cobra administrator to request update access to the classes or remove the classes to which you do not have update access.
Error	Please specify an exclusion file.	This error occurs when you select the Exclusion file checkbox on the Included Costs page but do not specify an exclusion file path. To resolve this error, specify an exclusion file path or clear the Exclusion file checkbox on the Include Costs page.
Error	Cannot locate exclusion file.	This error occurs when the specified exclusion file path cannot be found or when the specified exclusion file path includes characters that are not allowed in the Windows file paths. To resolve this error, ensure the file path is correct and that the file exists at the specified location or remove the invalid characters from the file path.
Error	Please specify a valid exclusion file type.	This error occurs when the exclusion file does not have a .csv extension. To resolve this error, select an exclusion file with a .csv extension.
Error	Please specify a table to load actual cost data.	This error occurs when you select the Connection Name option but do not specify a connection name on the File Selection page. To resolve this error, select a database table from the connection.
Error	Could not connect to the schedule database.	This error occurs when the UseConnection parameter is enabled and the database connection fails to initialize. To resolve this error, verify the database connection parameters, check network connectivity, validate database credentials, and ensure that the database service is running.
Error	Program {0} could not be opened.	This error occurs when the project does not exist in Cobra or cannot be accessed. To resolve this error, verify that the project exists in the database, check file permissions, ensure that the project is not corrupted, and confirm that the project is not locked by another user.
Error	Couldn’t extract the sub {0} information from the MULTPROG table.	This error occurs when the SQL query fails while attempting to retrieve the subproject list for a master project from the MULTPROG table. To resolve this error, check the integrity of the MULTPROG table, verify that master-subproject relationships are properly defined, ensure database connectivity, and validate SQL permissions.
Error	Could not connect to specified data source.	This error occurs when the connection object fails to establish a database connection. To resolve this error, verify the connection string configuration, check database service availability, validate connection credentials, and review firewall settings.
Error	Could not get a list of tables found in the database.	This error occurs when the SQL query fails while attempting to retrieve the list of tables from the database. To resolve this error, verify that the database permissions allow querying system tables, check the connection validity, and ensure the database user has the appropriate privileges.
Error	Could not extract the data from the table ‘{0}’.	This error occurs when the SQL query fails while attempting to SELECT data from the specified database table. To resolve this error, verify that the table exists, check SQL permissions, validate the table name spelling, and ensure that the connection is active.
Error	Cannot run SQL statement. There is no connection to a data source.	This error occurs when RunSQL is called while the connection ID is 0 or negative, indicating no valid database connection. To resolve this error, establish a valid database connection before attempting SQL operations.
Error	Couldn’t get the program header information for program ‘{0}’.	This error occurs when the SQL query fails while attempting to retrieve the project record from the PROGRAM table. To resolve this error, check the integrity of the PROGRAM table, ensure database connectivity, and validate SQL permissions.
Error	Program ‘{0}’ not found in the program header table.	This error occurs when the specified project does not exist in the PROGRAM table. To resolve this error, verify that the project name is spelled correctly, check that the project has been created in Cobra and validate case sensitivity.
Error	Couldn’t retrieve the code values.	This error occurs when the SQL query fails while attempting to retrieve CAWP-level code field definitions from the CODEFIELD table. To resolve this error, verify the integrity of the CODEFIELD table, check the database connection, and validate SQL permissions.
Error	Couldn’t retrieve the resource assignment code values.	This error occurs when the SQL query fails while attempting to retrieve resource assignment code field definitions from the CODEFIELD table. To resolve this error, verify the integrity of the CODEFIELD table, check the database connection, and validate SQL permissions.
Error	No Transaction File Created - Canceling	This error occurs when the CreateTRN method returns false, indicating a failure to create the transaction file structure. To resolve this error, check the file system permissions, verify disk space availability, validate the temporary directory path, and review the parameters passed to the CreateTRN method.
Error	An error occurred while attempting to create the transaction file - Canceling	This error occurs when CreateTRN succeeds but the THIS.lErr flag is set during the process. To resolve this error, review the error log for specific creation issues, check the file system permissions, verify data integrity, and validate the transaction file structure requirements.
Error	Error opening transaction file.	This error occurs when the actual cost file cannot be opened for processing. To resolve this error, verify that the actual cost file exists at the expected path, check that it is not locked by another process, validate file permissions, and ensure the file is not corrupted.
Error	Error opening exclusion file.	This error occurs when the exclusion file cannot be opened as specified. To resolve this error, verify that the exclusion file path is correct, ensure that the file exists, check the file permissions, and confirm that the file format is valid.
Error	Error: Transaction file closed by user process.	This error occurs when the actual cost file is no longer open, likely due to external code or user action closing it. To resolve this error, ensure that no external code closes the actual cost file during processing, check for user interruptions, and validate file locks.
Error	You must define the {0} fields when the “Auto-create missing {1} during actual cost integration” option is selected.	This error occurs when the Auto-create missing Control Account or Work Package option on the File Selection page is selected but the actual cost file is missing one or more required key fields. To resolve this error, add the missing key field columns to the actual cost file or clear the Auto-create missing Control Account or Work Package option on the File Selection page.
Error	Error in transaction file structure: CA1 field not found.	This error occurs when the required CA1 field is not defined in the actual cost file. To resolve this error, add a CA1 column to the actual cost file and ensure its data type is set to character.
Error	Error in transaction file structure: CA2 field not found	This error occurs when the required CA2 field is not defined in the actual cost file but the project uses CA_ID2. To resolve this error, add a CA2 column to the actual cost file and ensure its data type is set to character.
Error	Error in transaction file structure: CA3 field not found.	This error occurs when the required CA3 field is not defined in the actual cost file but the project uses CA_ID3. To resolve this error, add a CA3 column to the actual cost file and ensure its data type is set to character.
Error	WP field not found.	This error occurs when the required WP field is undefined in the actual cost file during loading at the work package level. To resolve this error, add a WP column to the actual cost file and ensure its data type is set to character.
Error	CECODE field not found.	This error occurs when the required CECODE field is either not of character type or is not defined in the actual cost file. To resolve this error, add a CECODE column to the actual cost file and ensure its data type is set to character.
Error	CLASS field not found.	This error occurs when the actual cost file has the CLASS field enabled but it is either not of character type or is not defined. To resolve this error, add a CLASS column to the actual cost file and ensure its data type is set to character, or disable the CLASS field usage.
Error	VALUE field not found for format 2 file.	This error occurs when the actual cost file is in Format 2 (which includes the DATA_TYPE field) but the required DATA_VALUE field is missing. To resolve this error, add a DATA_VALUE column to the actual cost file for Format 2 files.
Error	No defined results for {1} found in Format 1 file. (Defined Results: {2}).	This error occurs when the Format 1 actual cost file does not contain any result field columns that match the project’s defined results. To resolve this error, add result field columns (for example, ACWP, BCWP, BCWS) to the actual cost file so they align with the project’s result definitions.
Error	Errors found in transaction file structure. No Actuals Loaded.	This error occurs when one or more structural errors are encountered during validation. To resolve this error, review and correct all structural errors identified in the previous error messages.
Error	The {0} ‘{1}’ defined in the Transaction File is a master {0}. Only {0}s and sub{0}s can be defined in the Transaction File.	This error occurs when the actual cost file contains a project defined as a master project. To resolve this error, remove entries for the master project from the actual cost file or process the subprojects individually.
Error	SQL Error opening CLASSES file.	This error occurs when the SQL query fails while attempting to retrieve actual class definitions from the CLASSES table. To resolve this error, verify the CLASSES table integrity, check the database connection, and validate SQL permissions.
Error	Actual class ‘{0}’ passed as parameter not found in CLASSES file.	This error occurs when the specified actual class parameter does not exist in the CLASSES table for the project. To resolve this error, verify that the class name is correct, check that the class is defined for the program, and validate that the class type is ‘A’ (actual).
Error	Actual class ‘{0}’ is not at the {1} level.	This error occurs when the actual class level (control account or work package) does not match the specified class level parameter. To resolve this error, use an actual class defined at the correct level or change the class level parameter to match the class definition.
Error	SQL Error opening CAWP.	This error occurs when the SQL query fails while attempting to retrieve CA/WP records from the CAWP table. To resolve this error, verify the CAWP table integrity, check the database connection, and validate SQL permissions.
Error	Could not make {0} cursor updateable.	This error occurs when the MakeCursorUpdateable function fails, preventing updates to CAWP records. To resolve this error, check database permissions for update operations, verify the cursor structure, and ensure that proper key fields are defined.
Error	SQL Error opening CALCDETL.	This error occurs when the SQL query fails while attempting to retrieve calculation detail records from the CALCDETL table. To resolve this error, verify the CALCDETL table integrity, check the database connection, and validate that the calc file exists.
Error	Invalid date - Invalid or empty.	This error occurs when the COST_DATE field in the record is empty or contains an invalid date value. To resolve this error, ensure all records have valid COST_DATE values in the proper date format.
Error	Invalid date - later than Status Date.	This error occurs when the COST_DATE field in the record is later than the project’s current status date. To resolve this error, correct the COST_DATE so it is on or before the status date or update the project’s status date.
Error	Invalid date - eariler than first calendar date.	This error occurs when the COST_DATE field in the record is earlier than the calendar’s minimum (start) date. To resolve this error, correct the COST_DATE so it falls within the valid calendar date range or adjust the calendar’s start date.
Error	Could not save changes to CAWP File. ({0}).	This error occurs when SQLTABLEUPDATE fails while attempting to save new or updated CAWP records to the database. To resolve this error, check the database connection, verify update permissions, review the system error message, and validate data integrity constraints.
Error	The user doesn’t have view and update rights to the classes: {0}.	This error occurs when some excluded classes are automatically removed because you do not have update access. To resolve this error, no action is required—classes without update access are automatically excluded from processing.
Warning	The result field ‘{0}’ in the transaction file is not numeric and will be ignored.	This warning occurs when a result field defined in the actual cost file is not of numeric type. To resolve this warning, change the field to a numeric type in the actual cost file or remove it. Processing will continue but the field will be ignored.