Search

Language:  
Search for:

Available article translations:

[FIX] Unable to rename a domain in Plesk.

Symptoms

Domain cannot be renamed in Plesk. The following error is displayed:

Unable to rename domain - Cannot find domain by name '1'

Error: Unable to rename the domain: Execute websrvmng --start-vhost
"--vhost-name=d1.vw2003a.qa.plesk.ru" failed: Site d1.vw2003a.qa.plesk.rudoesn't exist
at (WebServerMap::get line 3034)
at startHosting(d1.vw2003a.qa.plesk.ru)(WebServerAdapter::startHosting line600)
at execute console command --start-vhost(vconsoleapp::start line 128)
at execute "E:\P S A\admin\bin\websrvmng" --start-vhost"--vhost-name=d1.vw2003a.qa.plesk.ru"(vconsoleapp::run line 138)
at (execUtil line 122)
at Execute E:\P S A\admin\bin\websrvmng --start-vhost"--vhost-name=d1.vw2003a.qa.plesk.ru"(execUtil line 142)
at Turn on web service for domain d1.vw2003a.qa.plesk.ru(domainmng::web_on_offline 422)
at (domainmng::web_on_off line 423)
at Turn on domain d1.vw2003a.qa.plesk.ru (state=5)(domainmng::turnDomain line141)
Execute websrvmng --rename-vhost "--old-name=d1.vw2003a.qa.plesk.ru""--new-name=newd1.vw2003a.qa.plesk.ru" failed: Cannot find domain by name '1'
at (PSADatabase::getDomain line 361)
at renameHosting(d1.vw2003a.qa.plesk.ru)(WebServerManager::renameHosting line2549)
at execute console command --rename-vhost(vconsoleapp::start line 128)
at execute "E:\P S A\admin\bin\websrvmng" --rename-vhost" --old-name=d1.vw2003a.qa.plesk.ru""--new-name=newd1.vw2003a.qa.plesk.ru"(vconsoleapp::run line 138)
at (execUtil line 122)
at Execute E:\P S A\admin\bin\websrvmng --rename-vhost"--old-name=d1.vw2003a.qa.plesk.ru""--new-name=newd1.vw2003a.qa.plesk.ru"(execUtil line 142)
at rename domain d1.vw2003a.qa.plesk.ru tonewd1.vw2003a.qa.plesk.ru(domainmng::renameDomain line 108)
at execute console command --rename-domain(vconsoleapp::start line 128)
at execute "E:\P S A\admin\bin\domainmng.exe" --rename-domain"--old-domain-name=d1.vw2003a.qa.plesk.ru""--new-domain-name=newd1.vw2003a.qa.plesk.ru"(vconsoleapp::run line 138)

Resolution

This problem has been solved in Plesk version 8.2. Consider upgrading Plesk to the latest version



FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No