Reviewing the Package Generation Log

If you receive a status of Failed or Partially Successful after attempting to generate a package, you can review the Package Generation Log to identify the cause and resolution of failures that occurred during package generation.

On this page

Review the package generation log

  1. Go to the Manage Packages page.
    1. From the menu, click Admin menu.
    2. Under Application Builder, click Packages.
  2. Locate the package that did not successfully generate.
  3. In the Status column, click the status of the package to open the Package Generation Log page.
  4. Review the error message and make any necessary updates to the package components.

Warning messages

The following table describes warning messages.
Message Description

The scheduler field {0} is missing module(s) {1} from the package, this may cause errors during install.

When packaging an application that contains a scheduler field, you must also package any applications related to the field. If the referenced application does not exist in the target environment, the system generates an error during package installation.

The {0}, {1}, references a file, {2}, that cannot be found. Please make sure this file exists in your configured repository files directory, or remove and re-add the attachment. This reference has been excluded from the package.

A repository file that is attached to either an application, questionnaire, sub-form, global values list, workspace, or dashboard cannot be found in the file repository. The file will not be installed during package installation.

 

A {0} with the name {1} contains a filter that references content. This may cause issues on package install.

Filters that reference specific content are unlikely to translate to another environment. It is recommended that you evaluate these filters prior to package generation to reduce the cleanup effort after installation.

 

The Advanced Workflow for level {0} with process ID {1} has an empty configuration.

The application referenced in the error message has an advanced workflow configuration that is empty. Inactivate the advanced workflow and generate the package again.

 

The CAST field {0} has a reference that is not included in the package. This may cause an issue on installation.

When packaging an application that contains a CAST field, it is recommended that you also package any applications related to the field. If the referenced application does not exist on the target environment, the system generates a warning when the package is installed.

{0} references only specific users.

You cannot package specific users. Notifications, DDEs, and other items listed may not install in the target environment if they reference only specific users. Verify that specific users are not referenced in the package file.

Failure messages

The following table describes failure messages.

Message

Resolution

The Workflow Service is currently unavailable.

Verify that the Advanced Workflow service is running. If it is not running, start the service.

A {0} that ties to {1} contains an invalid value.

The referenced field contains an invalid value. Delete the field and generate the package again.

The {0}, {1}, that ties to {2} is invalid.

The values list value is invalid. Delete the value from the values list.

Unable to retrieve Level Layout information for the given Level {0}.

The layout for the reference application is invalid. Delete the layout from the application.

The report {0} was unable to be packaged. The following error has been thrown {1}.

The report listed has an error. Fix the report and generate the package again.

Levels could not be found.

Listed levels could not be included in the package.