Unable to rename a domain: Site old.example.com does not exist

Symptoms

• When renaming a domain from old-example.com to example.com, the following error appears in Plesk:

  PLESK_ERROR: Error: Site old.example.com does not exist
          at (WebServerManager::renameHosting line 3083)
          at renameHosting(old.example.com, example.com)(WebServerManager::renameHosting line 3122)
          at execute console command --rename-vhost(vconsoleapp::start line 122)
          at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin64\websrvmng" --rename-vhost "--vhost-config=tmp2811.tmp" "--old-name=old-example.com"(vconsoleapp::run line 139) (Error code 1)

  OR

  PLESK_ERROR: Error: websrvmng failed: Site old-example.com doesn't exist
          at (WebServerMap::get line 189)
          at startHosting(old-example.com)(WebServerAdapter::startHosting line 772)
          at execute console command --start-vhost(vconsoleapp::start line 122)
          at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin64\websrvmng" --start-vhost "--vhost-name=old-example.com"(vconsoleapp::run line 139)
  (Error code 1)

• The "plesk repair web" utility fails with the error message below:

  C:\> plesk repair web old-example.com
  
  Repairing web server configuration
  Repairing web server configuration for the domain
  old-example.com ............................................... [FAILED]
  - Filename:
  \?\C:\Inetpub\vhosts\old-example.com\httpdocs\web.config
  Line number: 14
  Error: Configuration file is not well-formed XML
  
  In module
  Exception type: System.Runtime.InteropServices.COMException
  <...>

• There is no old-example.com site in IIS Manager > SERVERNAME > Sites.

• In some cases, the folder of the domain old-example.com is already renamed to example.com in %plesk_vhosts%.

Cause

• Incorrect website configuration in IIS.

• The web-config file of the domain old-example.com contains invalid-records.

Resolution

1. Connect to a Plesk server via RDP.

2. If the folder example.com already exists in %plesk_vhosts%, rename it to old-example.com.

3. Rename the file web.config to web-config.orig of the domain old-example.com at %plesk_vhosts%.

4. Start Internet Information Services (IIS) Manager at Windows Start > All Programs > Administrative Tools.

5. In IIS Manager, expand SERVERNAME > Sites > right-click on example.com > click Remove.

6. Start a command prompt as an Administrator and repair the website old-example.com:

   C:\> plesk repair web old-example.com

   In some cases, the repair process may fail with one of the following error messages:

   • Error 1:

     C:\> Repairing web server configuration for the domain example.com [FAILED]
     - A specified logon session does not exist. It may already have
     been terminated. (Exception from HRESULT: 0x80070520)

     In this case, go to Plesk > Domains > example.com > Hosting Settings > select Default Certificate from the drop-down list and click OK. Retry repair.

   • Error 2:

     C:\> Repairing web server configuration for the domain
     example.com ............................................... [FAILED]
     - Filename:
     \?\D:\INETPUB\VHOSTS\example.com\httpdocs\web.config
     Line number: 14
     Error: Configuration file is not well-formed XML

     In this case, rename the file web.config to web-config.orig of the domain old-example.com in %plesk_vhosts%.

7. Repair password-protected directories:

   C:\> "%plesk_cli%\repair.exe" --synchronize-protected-directories-storage

8. Log in to Plesk and rename the domain.

Related Articles

• How to enable/disable debug logging in Plesk 11.5 and higher for Windows

• Cannot modify subscriptions settings: Update Protected Directory user failed: User doesn't exist