Common Problems

General Problems

• Operation or Process can get Active or Prototype status after deployment even if it is not valid.

During the deployment Operation or Process can get status Active or Prototype even if it is not valid. This happens when the “TargetRevisionStatus” flag is set to Prototype or Active as these entities are not validated by Global Process Manger during deployment. To work around this issue perform one of the following actions:

• Re-release the Operation or Process after deploying it (To validate it, can be done for entities in Prototype status only);
• Include all the entity dependencies prior to its migration to assure its validity at the destination server.

Package Generation Problems

• “Could not find the configured directory for…” – There is a file in the Package that is created from a predefined directory and that directory does not exist on the destination server (it is not predefined on the server).

Package Deployment Problems

• Problems with moving Reports/Labels – Reports and Labels are based on the REPORT table and use the ReportName column as their Global Unique Key. That may cause problems when they are moved between servers, as there can be many different Reports with the same name -- even more, there can be Reports and Labels that boast the same name. In situations where there is a Label with the same name as a Report being deployed, then that Label will be overridden by the Report.
• “There is more than one entity (…) with the same Global Unique Key column values. Duplicated row: (…)”
  or
  “There is more than one row in table (…) with the same Global Unique Key column values. Duplicated row: (…)” – There are numerous database rows with the same GUK column values. The only way to deploy a Package in this case is to modify the values on the database to give them unique GUK columns.
• “Referenced system table (…) data does not exist on the destination database. The missing data is (…)”
  
  or
  
  “Referenced entity (…) does not exist on the destination database. The missing data is (…)”– The referenced entity or table data does not exist on the destination server. To resolve this issue, the referenced data should be deployed or added to the server.
• “Cannot import entity (…) because there is a cycle in the entity configuration between the referenced entities.” – An Entity is incorrectly configured. The only way to solve this problem is to modify the entity’s configuration so it did not create a cycle between referenced entities.
• “Could not find the configured directory for…” – There is a file in the Package that is created from a predefined directory and that directory does not exist on the destination server (it is not predefined on the server).
• “Access to file {0} or directory {1} is denied. Could not deploy the file…” – The Deployment Services Windows service does not have access to the file that is being deployed.
• “Failed to remove component from GAC…” – The component cannot be removed from GAC.
• “Failed to Add *.dll to GAC.” – The GAC component cannot be deployed.
• “Unable to save script file, File Name: {0}” – Problems are occurring while saving temporary files with SQL scripts to disk. Check if the Deployment Service has rights to the C:\Temp\AprisoSQLScripts directory.
• “Unable to Deploy SQL script…” – The SQL script file cannot be deployed. The exact reason can be found within the log files in the C:\Temp\AprisoSQLScripts directory on the server.
• “Cannot read package data as it is in an older format” – The file is of an incorrect format or does not contain DELMIA Apriso Global Process Manager Package data.
• “Could not read package data” – If that message is displayed during deployment/redeployment or while a package is being sent/saved from the Package Repository then it indicates that data for that package is missing (the file with the required data has been removed or renamed).