Troubleshoot Packages

1. This installation will be aborted as another instance of the same package is being installed.

Probable Cause: This error might occur when you try to install a package, which is being installed by another user.

Solution: It is recommended to wait till the package installation is complete, before installing the same package, if required.

2. When packaging artifacts, the scripts are not packaged.

Solution: Match the schema in the source and target environment match.

If the schema is invalid in the target environment, ensure that you edit the schema prior to installing the package.

3. When packaging artifacts, the physical files are not packaged.

Solution: Copy all the .aspx page, images files and all dependant files from the source environment to the package environment before installing package.

4. An artifact that was not installed by package gets when uninstalling Package.

Scenario:This behavior occurs, in case you install and uninstall an artifact through the package. After uninstalling the package create an artifact in target environment with the same name as the one uninstalled by the package. Later, when you uninstall this artifact which was manually created through package, the artifact gets uninstalled. Refer to the following illustration:

Illustration:

1. Create an artifact [Artifact-1] and add it to a package [Package-1].

2. Publish, generate, and export [Package-1], in the source environment.

3. Import the .awspkg file of [Package-1], in the target environment.

4. Install [Package-1]. The artifact [Artifact-1] will be installed successfully.

5. Uninstall [Package-1]. [Artifact-1] will be uninstalled.

6. Create a new artifact [Artifact-1] and give it the same name as the artifact that was uninstalled by [Package-1].

7. Verify the behavior of the newly created artifact and package, when you try to update or uninstall [Package-1].

8. Update [Package-1]. An alert appears, intimating you that the artifact [Artifact-1] cannot be updated.
   
   [Workflow-1] was not updated as it is not the one installed by package, but the one created in step f.
   
   Now, verify the behavior of the artifact and package when [Package-1] is uninstalled.

9. Uninstall [Package-1], [Artifact-1] gets uninstalled.

   Probable Cause

   This occurs as the Package was uninstalled earlier and a backup of the artifact was taken. From the next consecutive attempt to uninstall, the artifacts will be deleted.

5. Error Cannot delete the selected item. Error while loading the Assembly appears when deleting a Forms Control installed through package, even though the dll file was copied to the specified path.

Cause

This error occurs if the Forms Control was installed through a package and the assembly dll is not present in the specified path.

This error will reoccur even after you manually copy the required dll to the specified path in the target environment.

Solution

1. Copy the required dll from source environment to the target environment.

2. Perform an IIS reset.

3. Clear the temp folder and the cookies

4. Restart all AVEVA Work Tasks Services engine.

5. Uninstall the package to delete the forms control.