Article ID: 120946, created on Apr 8, 2014, last review on May 8, 2014

  • Applies to:
  • Plesk for Windows


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

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


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.)


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.

Search Words

Plesk for windows

backup restore


extract path is to long


a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 85a92ca67f2200d36506862eaa6ed6b8

Email subscription for changes to this article
Save as PDF