Article ID: 116138, created on May 21, 2013, last review on Jun 17, 2016

  • Applies to:
  • Plesk 11.5 for Linux
  • Plesk 12.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 11.5 for Windows


The backup restoration process finishes with the following errors:

    Execution of "C:\Program Files (x86)\Parallels\Plesk\bin\user.exe" --create user@domain.test -owner customer1 -guid e00aa2c5-f47f-1fe5-4134-436c5595c7c5 -cname user@domain.test -passwd "" -passwd_type sym -status enabled -domain-admin false -role "Mail User" -for-all-subscriptions -ignore-nonexistent-options failed with return code 3.
    Stderr is
    Data error (cyclic redundancy check). (Error code 23) at BCryptDecrypt()

Also, in Plesk 12.5 the restoration may fail with the following error:

Erro: Unable to decrypt data: Data error (cyclic redundancy check). (Error code 23) at BCryptDecrypt()
at (AesCryptProvider::decrypt line 143)
at (zif_plesk_symmetric_decrypt line 2365) 


The restored backup was copied from another Plesk server's backup repository directly, without a proper export (usually by uploading to the FTP backup repository or downloading the backup file from the Plesk interface).

This results in presence of passwords encrypted with the original server's unique randomly generated key which cannot be decrypted by another Plesk server.


NOTE: The script works only in Plesk 12 and earlier.

If the source server is still available, it is recommended to download the backup from the Plesk interface or configure a Personal FTP repository and create a new backup to the repository. Both of these operations can be accomplished at the Tools & Settings > Backup Manager screen and, in both cases, the passwords will be properly decrypted in the backups.

If the source server is not available, the only choice is to replace all passwords in the XML files of the backup. Follow these instructions:

1) Download and unpack the attached script into the directory with the Plesk backup that is to be restored.

2) Open the administrator's command prompt and navigate to the same directory.

3) Once it is done, execute the following command:

for /r %x in (*.xml) do "%plesk_dir%\Additional\perl\bin\perl.exe" -p -i~ "%x"

The script will replace all encrypted passwords with randomly generated passwords, which will allow you to properly restore the backup.

NOTE: The script creates backup (*.xml~) of *.xml files. Move all *.xml~ files to another location because they can block a restoration process (software issue PPPM-3140).

After the backup is restored, the following user classes will have their passwords reset and need to be updated:

* Control panel users
* Mail users
* FTP users
* Protected directory users
* Database users

For a fast mass update of passwords, use the Plesk password mass-reset script from this article: #113391.

In case of Plesk 12.5 on Windows, you can apply this patch.

  1. First, back up the original file


    For example, rename it to "Encryptor.php_orig"

  2. Place the aforementioned patch to this location

This script will reset all the passwords during restoration. When the restoration finishes, the list of reset passwords will be provided in GUI. It will look like this:

    The password was generated for user ''. New password is '********'

For Plesk 12.5 and higher versions, the internal request PPPM-3752 has been submitted in order to improve such restoration procedures.

Search Words

Error code 23

do not see the error reason

domain service web

Failed deployment of domain

reseller account restore

data redundancy check

restore error

Unable to resolve all conflicts

Failed deployment of mail user

Data error (cyclic redundancy check). (Error code 23) at BCryptDecrypt()

backup restore

Data error (cyclic redundancy check)



bd7fc88cf1b01f097749ae6f87272128 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 46a8e394d6fa13134808921036a34da8 29d1e90fd304f01e6420fbe60f66f838 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 8b661cab116c79dbe6c4ac5bbdf1c8cb

Email subscription for changes to this article
Save as PDF