Data transferring from Plesk 8.6: Unable to find the 'packagename' package neither on the source server nor in the APS catalog

Created:

2016-11-16 13:10:43 UTC

Modified:

2017-04-24 11:55:31 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Data transferring from Plesk 8.6: Unable to find the 'packagename' package neither on the source server nor in the APS catalog

Applicable to:

  • Plesk for Linux
  • Plesk 11.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 9.x and below for Windows

Symptoms

The migration: Plesk 8.6.0.5 on Windows Server 2003 to Plesk 11.5.30 on Windows Server 2012.

The following message is appeared in migration log:

Warning:     domain "domainname"
Unable to find the 'packagename' package neither on the source server nor in the APS catalog. Panel will not consider this app as installed. The data related to this app will be migrated, but the app is unlikely to work correctly. If you are going to provide this app for users, install the 'packagename' package manually on the destination server and then start the migration again.

Cause

The application on source server is outdated, it cannot be installed on the destination server.

Resolution

  1. Go to %plesk_dir%\\var\\cgitory directory on source server.
  2. Find required application folder
  3. Put the contents of the folder to the archive named ' foldername.app.zip '. The root of the archive must contain application content like below:

    htdocs
    images
    scripts
    APP-META.xml
  4. Download and run app-list-xml.php . The command example is

    "%plesk_bin%\\php.exe" app-list-xml.php 'path_to_package_archive'

    It will create required file inside the archive.5. Upload the package on the destination server via package management page.

The package will appear in the list of installed packages. Note: the package will not be available for new installation if newer version of the same application is installed.

After that you can migrate required domains again.

If package folder is missing, then may follow instructions provided in KB #213387769 to cleanup psa database.

Have more questions? Submit a request
Please sign in to leave a comment.