Primavera Web Service Schedule Integration Error and Warning Messages
Learn about the error and warning messages related to the Primavera Web Service Schedule Integration process, as displayed in the process log, along with their resolutions.
| Type | Message | Cause and Resolution |
|---|---|---|
| Error | Please enter a connection name. | This error occurs when you do not provide a connection name for the integration. To resolve this error, enter a valid connection name in the connection settings. |
| Error | Invalid connection specified. | This error occurs when the specified connection name does not exist in Cobra’s connection registry. To resolve this error, select an existing shared connection or create a new valid connection. |
| Error | This connection type is no longer supported. Please create a new connection. | This error occurs when the Microsoft Project Database file connections are deprecated. To resolve this error, create a new connection using a supported connection type. |
| Error | Please select a schedule project. | This error occurs when no scheduled project is selected from the scheduling system. To resolve this error, select a valid scheduled project from Primavera P6. |
| Error | Invalid schedule project specified. | This error occurs when the selected schedule project name does not exist in Cobra. To resolve this error, ensure that the schedule project name matches an existing Cobra project. |
| Error | Calendar file '{0}' is missing for project '{1}'. | 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 or recreate the missing calendar. |
| Error | You have insufficient rights to update project '{0}'. | This error occurs when you do not have write access to the specified project. To resolve this error, contact your Cobra administrator to request write access to the project. |
| Error | Project already exists. | This error occurs when you attempt to create a project with a name that already exists. To resolve this error, choose a different project name or select the existing project instead of creating a new one. |
| Error | Please select baseline or pending dates when loading budget resource assignments. | This error occurs when you cannot load the budget without selecting dates. To resolve this error, select Baseline dates, Pending dates, or both. |
| 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 | Project name must be set before continuing. | This error occurs when the project name setting is empty or not configured. To resolve this error, ensure the project name is configured in the integration settings before running the process. |
| Error | Unable to find details for project {project_name}. | This error occurs when the web service call to GetProjectDetails() returns no results. To resolve this error, verify that the project name exists in Primavera P6 and that you have access to the project. |
| Error | SQL error selecting list of {criteria_type}. | This error occurs when GetTaskCursor() fails to create the task cursor. To resolve this error, check the database connection and verify that the field mappings are correct. |
| Error | No code field specified for filtering. | This error occurs when the INTG_FILTER_SCHEDULE_CODE_FIELD setting is empty. To resolve this error, configure the schedule code field in the integration settings. |
| Error | Error creating temporary table LinkPRG. | This error occurs when CreateTemplateTable() fails to create the LINKPRG temporary table. To resolve this error, check your write access to the temporary directory and verify that disk space is sufficient. |
| Error | Error creating temporary table LinkCD. | This error occurs when CreateTemplateTable() fails to create the LINKCD temporary table. To resolve this error, verify write access, check disk space, and confirm accessibility of the BREAKDWN template table. |
| Error | SQL Error selecting Activity data. | This error occurs when GetTaskCursor() fails during status loading. To resolve this error, check the database connection and verify that activity field mappings are correct. |
| Error | SQL error selecting task data. | This error occurs when GetTaskCursor() fails during activity data loading. To resolve this error, check the database connection and verify that activity field mappings are correct. |
| Error | DotNetPPMPrimaveraWebService.Init(): Failed to load Cobra.Model.dll. | This error occurs when wwDotNetBridge fails to load the Cobra.Model.dll assembly. To resolve this error, verify that Cobra.Model.dll exists in the application directory and confirm that the .NET version is compatible. |
| Warning | No dates specified for budget load - defaulting to early dates. | This warning occurs when the INTG_DATES_BASELINE_DATES setting is empty but budget loading is enabled. To resolve this warning, configure the baseline dates in the integration settings. |
| Warning | No dates specified for forecast load - defaulting to schedule dates. | This warning occurs when the INTG_DATES_FORECAST_DATES setting is empty but forecast loading is enabled. To resolve this warning, configure forecast dates in the integration settings. |
| Warning | Invalid Budget Class '{class}' for {CA1-CA2-CA3-WP}, ID {activity_id}. | This warning occurs when a resource assignment has a budget class that is not defined in the Cobra Classes table. To resolve this warning, add the class to the Cobra project’s Classes table or correct the class assignment in Primavera. |
| Warning | Invalid Forecast Class '{class}' for {CA1-CA2-CA3-WP}, ID {activity_id}. | This warning occurs when a resource assignment has a forecast class that is not defined in the Cobra Classes table. To resolve this warning, add the class to the Cobra project’s Classes table or correct the class assignment in Primavera. |