Symptoms
-
Plesk shows the following error after login:
external error: Domain Service Web not exists: domain=sub.example.com, id=41
Domain Service Web not exists: domain=sub.example.com, id=41
File DSWeb.php
Line 76
Type PleskFatalException -
The following errors may be shown in the
/var/log/plesk/panel.logfile:[2015-11-23 22:23:48] ERR [panel] Failed to search for WordPress instances on subscription example.com: Domain with id=270 was not found
[2015-11-23 22:23:52] ERR [panel] Attempt to change status of non-configured mail service. [domain_id = 270]
[2015-11-23 22:23:52] ERR [panel] Unable to load object of type PhDomain with id=270: Turn off domain failed: Unable to find service node for web service on domain with id=270
[2015-11-23 22:23:52] ERR [panel] Some of the subscriptions selected were not suspended.<br>Unable to load object of type PhDomain with id=270: Turn off domain failed: Unable to find service node for web service on domain with id=270
[2015-11-23 22:23:59] ERR [panel] No data.
[2015-11-23 22:24:09] ERR [panel] Failed to search for WordPress instances on subscription example.com: Resource with UID 'bd314c87-865a-46e6-b694-342e71899445' not found.
Cause
The domain mentioned in the error messages has been deleted, but PSA database still contains an entry for this domain.
Plesk database was not properly upgraded. The ' psa.DomainServices ' table has no records of the "web" type.
Resolution
Note: This article may require additional administrative knowledge to apply. If any help required, contact server’s administrator or hosting support.
Warning: Please check that the domain physically exists before making changes. If it does, back up all the domain content from the corresponding directories /var/www/vhosts/<domain> and /var/qmail/mailnames/<domain> (in case of Linux) or from C:Inetpubvhosts and %plesk_dirMailEnablepostoffices% (in case of Windows).
There are several possible scenarios:
Scenario 1. Domain physically exists in Plesk
-
Connect to the server via SSH (Plesk for Linux) or RDP (Plesk for Windows)
-
Remove the domain with ID in
psa.domainsmentioned in the first error message from the PSA database:# plesk db "DELETE FROM domains WHERE id='41'"
-
Find orphaned records in the databases as follows:
For Plesk on Linux:
-
Create
psaandapscdatabase backups:# plesk db dump psa > /root/psa_dump_$(date +'%Y-%m-%d').sql
# plesk db dump apsc > /root/apsc_dump_$(date +'%Y-%m-%d').sql
-
Find orphaned records in table
psa.domainsusing the values mentioned in the error messages:# grep 'bd314c87-865a-46e6-b694-342e71899445' /root/apsc_dump_$(date +'%Y-%m-%d').sql
# grep 'bd314c87-865a-46e6-b694-342e71899445' /root/psa_dump_$(date +'%Y-%m-%d').sql
# grep 'example' /root/apsc_dump_$(date +'%Y-%m-%d').sql
# grep 'example' /root/psa_dump_$(date +'%Y-%m-%d').sql | grep -v -E 'log_components|exp_event'
INSERT INTO Configurations (id, name, serviceNodeId, file, version, objectType, objectId, status, active, description, errorFile) VALUES (115,'nginxDomainWebmail',1,'/etc…
-