Cannot install WordPress: Internal error: serviceNotFound

Created:

2016-12-18 06:52:16 UTC

Modified:

2017-08-16 17:19:24 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot install WordPress: Internal error: serviceNotFound

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 11.x for Windows
  • Plesk 11.x for Linux

Symptoms

Cannot install Wordpress application. The following error occurs in Plesk:

    Internal error: [[serviceNotFound]]
Message [[serviceNotFound]]
File App.php
Line 52
Type CommonPanel_Aps_Exception

Cause

Inconsistency in psa database, orphaned record in smb_apsContexts table.

Resolution

Find and remove incorrect entry in database.

  1. Find out the latest version of Wordpress:

    [dev.apsstandard.org](https://dev.apsstandard.org/apps/?name=wordpress&vendor=&aps_version=&category=&package_type=&addon=&perpage=10)
  2. Find the ID of that version in the database. Let's say that latest version is 3.9.2:

    mysql> select * from smb_apsPackages where name='Wordpress' and version='3.9.2';
    +-----+-----------+---------+---------+---------------+-----------------------+------------------------+
    | id | name | version | release | vendor | vendorHomePage | packager |
    +-----+-----------+---------+---------+---------------+-----------------------+------------------------+
    | 135 | WordPress | 3.9.2 | 38 | WordPress.org | http://wordpress.org/ | Glowtouch Technologies |
    +-----+-----------+---------+---------+---------------+-----------------------+------------------------+
    1 row in set (0.00 sec)

    mysql> SELECT * FROM `smb_apsContexts` AS `smb_apsContexts` WHERE (contextType = 0) AND (`packageId` = 135);
    +-----+-------------+-----------+-------------------------+----------------------+
    | id | contextType | packageId | requirementContextClass | requirementContextId |
    +-----+-------------+-----------+-------------------------+----------------------+
    | 344 | 0 | 135 | NULL | NULL |
    | 611 | 0 | 135 | NULL | NULL |
    +-----+-------------+-----------+-------------------------+----------------------+
    2 rows in set (0.00 sec)

    At the same time, there is no such contextId:

        mysql>  SELECT * FROM smb_apsMetas AS smb_apsMetas WHERE contextId=344;
    Empty set (0.00 sec)

    There is only contextId=611:

    mysql>  SELECT `smb_apsMetas`.* FROM `smb_apsMetas` AS `smb_apsMetas` WHERE (`contextId` = 611);
    +-----+-----------+-----------+----------------------------------------------+-------+-----------+
    | id | name | serviceId | xpath | class | contextId |
    +-----+-----------+-----------+----------------------------------------------+-------+-----------+
    | 293 | Wordpress | wordpress | aps::aps12::http://wordpress.org/::wordpress | | 611 |
    +-----+-----------+-----------+----------------------------------------------+-------+-----------+
  3. So, the first record is orphaned. To correct it, delete it as below:

    mysql> delete from smb_apsContexts where id=344;
    Query OK, 1 row affected (0.00 sec)
Have more questions? Submit a request
Please sign in to leave a comment.