Plesk migration has finished with warning: the extract path is too long

Refers to:

  • Plesk for Windows

Created:

2016-11-16 12:52:53 UTC

Modified:

2016-12-21 19:26:40 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk migration has finished with warning: the extract path is too long

Symptoms

Plesk migration on windows systems has finished with the following warning:

Warning:    hosting "DOMAIN.TLD"Can not deploy content of domain DOMAIN.TLDWarning:    Repository error: Archive could not be extracted because the extract path is too long

Cause

In Windows API (with some exceptions), the maximum length for a path is MAX_PATH defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is " D:\\some 256-character path string<NUL> " where " <NUL> " represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)

Resolution

On the source:

  1. Use " tree /F > tree.txt " utility to view tree of folders and locate largest path/filename.

  2. Use third-party archiver (for example 7-Zip) to aggregate the folder with problematic path/filename to archive.

  3. Migrate the domain again.


On the destination:

  1. Run the archiver as Administrator and set the temporary working folder for archiver as "Current" (options\folders). Restore problematic folder from archive.

BTW : As an alternative solution, use " subst " utility to associate a path " C:\\inetpub\\vhosts\\<DOMAIN_NAME>\\httpdocs\\ ' to a drive letter.

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