Article ID: 5493, created on May 8, 2009, last review on May 11, 2014

  • Applies to:
  • Plesk 8.3 for Linux/Unix
  • Plesk 8.2 for Linux/Unix
  • Plesk 8.1 for Linux/Unix

Síntomas

Cuando intento eliminar un dominio a través de Parallels Plesk Pabel, aparece el siguiente error:

DomainUser::getAccount failed: Unable to create Account object: Account: unable to select: no such row in the table
0: /usr/local/psa/admin/plib/class.PhDomain.php:424
    PhDomain->reset(integer '0', boolean true, boolean false)
1: /usr/local/psa/admin/plib/class.BsDomain.php:313
    BsDomain->reset(integer '0')
2: /usr/local/psa/admin/plib/class.BsDomain.php:307
    BsDomain->delete(integer '0')
3: /usr/local/psa/admin/plib/class.BsDomain.php:540
    mdeleteDomains(array)
4: /usr/local/psa/admin/plib/class.Manager.php:352
    Manager->removeDomains(array)
5: /usr/local/psa/admin/htdocs/domains/removeDomains.php3:50

Causa

Este error denota que en la base de datos Parallels Plesk Panel no se han encontrado las configuraciones de la cuenta adecuadas para el administrador del dominio y la tarjeta. Para verificarlo, ejecute los siguientes comandos:

mysql> select dlu.* from dom_level_usrs dlu, domains d where dlu.dom_id=d.id and d.name='DOMAIN-NAME';
+--------+------------+-------+---------+---------+
| dom_id | account_id | state | card_id | perm_id |
+--------+------------+-------+---------+---------+
|     29 |        106 | true  |       5 |      18 |
+--------+------------+-------+---------+---------+
1 row in set (0.00 sec)

mysql> select * from accounts where id=106;
Empty set (0.00 sec)

mysql> select * from Cards where id=5;
Empty set (0.00 sec)

mysql>

Resolución

Actualice la tabla psa.dom_level_usrs manualmente para eliminar la discrepancia:

mysql> update dom_level_usrs set account_id=NULL where dom_id=29;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> update dom_level_usrs set card_id=NULL where dom_id=29;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql>


5dd10e4b1e2dd7a2aa8a50c580dd41a2 583c136e45a1f548d12213fea9b7833d 9f8b3267dc294b8e42f097f7cddbc524 b8ef5052d936e902043e41759118114e 29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF