Import File Integration Error and Warning Messages
Learn about the error and warning messages related to the Import File Integration process, as displayed in the process log, along with their resolutions.
| Type | Message | Cause and Resolution |
|---|---|---|
| Error | Please specify a valid Cobra project. | This error occurs when you do not specify a project ID for an import file integration. To resolve this error, select a valid Cobra project from the project list. |
| Error | Please select a valid Cobra project. | This error occurs when the specified project ID does not exist in the Cobra database. To resolve this error, select an existing project and verify that the project name is correct. |
| Error | The calendar file ‘{0}’ for project ‘{1}’ does not exist. | This error occurs when the project references a calendar file that no longer exists. To resolve this error, assign a valid calendar file to the project using the Project Properties dialog box. |
| Error | You have insufficient rights to perform this action on project {0}. | 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 or select a different project. |
| Error | Please specify a Cobra project. | This error occurs when you have not selected a project. To resolve this error, select an existing project. |
| Error | The project already exists. | This error occurs when you attempt to create a project with an ID that already exists. To resolve this error, assign a different unique project ID or choose to update the project. |
| Error | Please specify an activity file. | This error occurs when no activity file path is provided. To resolve this error, specify a valid path to an activity file. |
| Error | Please select a valid activity file. | This error occurs when the file extension is not .txt, .csv, .xls, or .xlsx. To resolve this error, use a file with a supported extension. |
| Error | Please ensure control account is linked to schedule field. | This error occurs when the Control Account key field 1 (CA1) or the Work Package (WP) field is not mapped to a schedule field. To resolve this error, map the CA1 or the WP field to a valid schedule field. |
| Error | Please specify a calendar file. | This error occurs when a calendar file is not specified. To resolve this error, specify a valid calendar file name. |
| Error | Please enter a valid start date. | This error occurs when a start date is not specified for the new calendar file. To resolve this error, specify a valid start date. |
| Error | The finish date cannot occur before the start date. | This error occurs when the end date in the calendar file is earlier than or equal to the start date. To resolve this error, enter an end date that is later than the start date. |
| Error | CA1 column is required. | This error occurs when the required CA1 field is missing. To resolve this error, map the CA1 column in the Import File Field Mapper page. |
| Error | At least one date field must be selected. | This error occurs when you load control accounts, work packages, or resource assignments without any date fields selected. To resolve this error, map at least one date field on the Import File Field Mapper page. |
| Error | Please specify a default budget class. | This error occurs when no default budget class is specified. To resolve this error, select a valid default budget class. |
| Error | You have insufficient rights to update class {0}. | This error occurs when you do not have update access to the selected budget class. To resolve this error, contact your Cobra administrator to request update access to the budget class or select a different budget class. |
| Error | Please enter a connection name. | This error occurs when you do not specify a connection name. To resolve this error, specify a valid connection name. |
| Error | Could not create the program object. | This error occurs when the program object cannot be opened or initialized. To resolve this error, verify that the program object is properly configured and that you have the necessary permissions. |
| Error | A project name was not specified. | This error occurs when the project name setting is empty. To resolve this error, ensure that a valid project name is specified in the integration settings. |
| Error | The activity data could not be loaded. | This error occurs when Cobra fails to retrieve and process activity data from the import file. To resolve this error, verify that the import file exists, is accessible, and has the correct format. |
| Error | The required field CA1 has not been selected in the activity file. | This error occurs when the required CA1 field is missing in the activity file. To resolve this error, include the CA1 field in the activity file column mapping. |
| Error | Activity ID [ID], Code [CA1] not found in breakdown structure [structure]. | This error occurs when the CA1 code value does not exist in the breakdown structure file. To resolve this error, ensure that all code values in the import file exist in the corresponding Cobra breakdown structure files. |
| Error | Could not get records for structure file [breakfile]. | This error occurs when the SQL query fails to retrieve the breakdown structure records from Codes table. To resolve this error, verify the database connectivity and ensure that the breakdown structure files exist. |
| Error | Could not find the Cobra project [project name] in the header file. | This error occurs when the specified project name is not found in the project table or cursor. To resolve this error, verify that the project exists in Cobra and ensure that the project name is correct. |
| Error | The resource start and finish dates are blank for [keys], ID [ID]. | This error occurs when both FROMDATE and TODATE fields are empty in the resource records. To resolve this error, ensure that all resource records have valid start and finish dates. |
| Error | Invalid Budget Class ‘[CLASS]’ for [keys], ID [ID]. | This error occurs when the CLASS value is not a valid budget class type. To resolve this error, verify that the budget class exists and is defined as a budget class (CLASSTYPE = ‘B’). |
| Error | The CA1 field was not selected in the status file. | This error occurs when the required key field CA1 is missing in the status file. To resolve this error, include the CA1 field in the status file column mapping. |
| Error | The code data could not be grouped. | This error occurs when the SQL SELECT statement fails to create a grouped cursor from TEMPASG data. To resolve this error, verify the SQL syntax, ensure that the TEMPASG cursor exists, and confirm that it contains valid data. |
| Error | No dates were selected in the Activity File. | This error occurs when no date fields have been selected in the activity file. To resolve this error, verify the SQL syntax and select at least one set of date fields in the activity file column mapping. |
| Error | Cannot update estimate dates with early dates. No early dates linked to the status file. | This error occurs when a source date type is selected but the corresponding date fields are not mapped. To resolve this error, map the appropriate date fields in the status file. |
| Error | You must select the PC_COMP field if you wish to update Work Package percent complete. | This error occurs when the PC_COMP field is not selected while you load percent complete directly. To resolve this error, add the PC_COMP field to the status file if you load percent complete directly. |
| Error | Could not retrieve the spread curves. | This error occurs when the SQL query fails to retrieve spread curve names from the COMMON!SPREAD table. To resolve this error, verify the database connectivity, ensure that the SPREAD table exists, and confirm that it is accessible. |
| Warning | There are no activity records found, so activity data won't be loaded. | This warning occurs when the TEMPLNK cursor has zero records after you load activity data. To resolve this warning, verify that the import file contains activity records. |
| Warning | The ID field has not been selected in the activity file. Resources cannot be loaded. | This warning occurs when the ID field is not selected and loading a resource assignment is enabled. To resolve this warning, include the ID field in the activity file column mapping if resources need to be loaded. |
| Warning | The class '[class]' uses pending dates and can only be loaded if you have selected to load pending dates. | This warning occurs when you load baseline dates while the budget class is configured to use pending dates. To resolve this warning, change the load settings to include pending dates or use a different budget class. |
| Warning | The class '[class]' doesn't use pending dates and can only be loaded if you have selected to load baseline dates. | This warning occurs when you load pending dates while the budget class is configured for baseline dates. To resolve this warning, change the load settings to include baseline dates or use a different budget class. |
| Warning | Invalid Forecast Class '[FCSTCLASS]' for [keys], ID [ID]. | This warning occurs when the FCSTCLASS value is not a valid forecast class type. To resolve this warning, verify that the forecast class exists and that it is defined as a forecast class (CLASSTYPE = ‘F’). |
| Warning | Duplicate status records found. Percent Complete values will be taken from the first record in the file. | This warning occurs when multiple status records exist for the same key combination. To resolve this warning, remove the duplicate status records from the import file. |
| Warning | The BE field has not been selected. The CLASS field will be ignored. | This warning occurs when the CLASS field is selected but the BE field is not. To resolve this warning, add the BE field to the status file mapping or remove the CLASS field. |
| Warning | Spread curve '[curve]' on resource '[ID]' has not been defined in Cobra. A Manual spread will be used. | This warning occurs when a specified spread curve name does not exist in Cobra’s SPREAD table. To resolve this warning, define the spread curve in Cobra or use a manual spread. |
| Warning | Invalid field found: '[field name]'. | This warning occurs when a field name ends with a reference suffix but is not recognized. To resolve this warning, remove the invalid field references from the column mapping. |
| Warning | Key fields beginning with spaces were found in the [type] transaction file. These aren't allowed by Cobra, so they will be ignored. | This warning occurs when the key field values begin with leading spaces. To resolve this warning, remove leading spaces from key field values in the import file. |