Primavera Schedule Integration Error and Warning Messages
Learn about the error and warning messages related to the Primavera Schedule Integration process, as displayed in the process log, along with their resolutions.
| Type | Message | Cause and Resolution |
|---|---|---|
| Error | SQL error executing query to determine Primavera version - version assumed to be 5 | This error occurs when the SQL query to determine the Primavera P3e version fails. To resolve this error, ensure the database connection is valid, confirm that the database schema is correct, and check that you have appropriate permissions to query database metadata. |
| Error | Project name must be set before continuing | This error occurs when Cobra attempts to proceed with operations without first setting the INTG_PROJECT_SCHEDULE_PROJECT setting. To resolve this error, ensure that the project schedule setting is configured before calling any methods that require project context. |
| Error | SQL error selecting project details for project {project_name}. | This error occurs when the SQL query to retrieve project details from the PROJECT table fails. To resolve this error, verify the database connection, ensure that the PROJECT table exists and is accessible, and confirm that the SQL syntax is correct for the database version being used. |
| Error | Unable to find details for project {project_name}. | This error occurs when the SQL query to retrieve project details executes successfully but returns no records. To resolve this error, verify that the project name is correct and exists in the Primavera database. |
| Error | SQL Error selecting Primavera codes. | This error occurs when the SQL query to retrieve Primavera code definitions fails. To resolve this error, verify the database connection and ensure that code-related tables are accessible. |
| Error | SQL Error getting list of users defined fields. | This error occurs when the SQL queries to retrieve user-defined field definitions from the UDFTYPE or UDFVALUE tables fail. To resolve this error, verify that the UDFTYPE and UDFVALUE tables exist and are accessible and ensure that the user has permissions to query these tables. |
| Error | SQL Error getting list of user defined fields on resource assignments. | This error occurs when the SQL queries to retrieve user-defined field definitions for resource assignments (TASKRSRC table) fail. To resolve this error, verify that the UDFTYPE and UDFVALUE tables exist and include entries that support the TASKRSRC table name. |
| Error | SQL error getting list of projects. | This error occurs when the SQL query to retrieve the list of available Primavera projects fails. To resolve this error, verify that the PROJECT table is accessible and that the database connection is valid. |
| Error | Couldn’t extract the Tphase spread data from the Primavera Integration API. | This error occurs when the extraction of time-phased spread data from the Primavera API fails. To resolve this error, verify that the Primavera API connection is valid and ensure that time-phased data exists in the project. |
| Error | Primavera API User ID is blank. | This error occurs when you do not provide a Primavera API username in the connection credentials. To resolve this error, enter a valid Primavera API username in the connection settings. |
| Error | Primavera API Password is blank. | This error occurs when you do not provide a Primavera API password in the connection credentials. To resolve this error, enter a valid Primavera API password in the connection settings. |
| Error | Primavera API Location is blank. | This error occurs when you do not specify the directory location where Primavera API files are stored. To resolve this error, enter a valid directory path for the Primavera API files. |
| Error | Directory is not accessible from the server. | This error occurs when the specified Primavera API directory location cannot be accessed from the Cobra server (n-tier deployment scenario). To resolve this error, ensure that the P3eAPILocation path is accessible from the Cobra server by using a network path or a server-accessible directory. |
| Error | Directory is not accessible. | This error occurs when the specified Primavera API directory location does not exist or cannot be accessed (stand-alone deployment scenario). To resolve this error, verify that the P3eAPILocation path exists and is accessible and check the file system permissions. |
| Error | Couldn’t read the Java Runtime home directory. | This error occurs when the ReadJavaHomePath() method returns an empty string, which indicates that neither the JDK nor JRE registry entries could be found. To resolve this error, ensure that the Java JDK or JRE is properly installed in the directory and that the registry keys are created. |
| Error | The Cobra P3e API files do not exist. | This error occurs when the P3eAPI directory does not exist in the current working directory. To resolve this error, ensure that the P3eAPI directory exists in the Cobra installation and contains the required *.class files. |
| Error | Connection failed. | This error occurs when the Java P3e API process fails to connect to the Primavera database. To resolve this error, verify that the Primavera database credentials are correct, ensure that the database server is accessible, and check the network connectivity. |
| Warning | SQL Error getting project description from WBS table | This warning occurs when the SQL query to retrieve the project description from the PROJWBS table fails. To resolve this warning, verify that the PROJWBS table exists and is accessible. This is non-fatal—Cobra will use “Undefined” as the description. |
| Warning | Unable to locate project description in WBS table | This warning occurs when the SQL query to retrieve the project description executes successfully but returns no records. To resolve this warning, verify that the Primavera project has a properly configured WBS that includes a project node. |
| Warning | No dates specified for budget load - defaulting to early dates | This warning occurs when budget loading is enabled but no date type has been specified. To resolve this warning, specify which date type to use for budget loading or accept the default early date. |
| Warning | No dates specified for forecast load - defaulting to schedule dates | This warning occurs when forecast loading is enabled but no date type has been specified. To resolve this warning, specify which date type to use for forecast loading or accept the default scheduled date. |
| Warning | Invalid Budget Class '{class}' for {CA-WP keys}, ID {resource_id} | This warning occurs when a resource assignment has a class value that is not configured as a valid budget class in Cobra. To resolve this warning, configure the class in Cobra as a valid budget class or ensure that resource assignments use only valid budget classes. |
| Warning | Invalid Forecast Class '{class}' for {CA-WP keys}, ID {resource_id} | This warning occurs when a resource assignment has a class value that is not configured as a valid forecast class in Cobra. To resolve this warning, configure the class in Cobra as a valid forecast class or ensure that resource assignments use only valid forecast classes. |