Search Engine: Elastic

Article ID: 124435, created on Feb 10, 2015, last review on Feb 10, 2015

  • Applies to:
  • H-Sphere 3.6.3


The account move is failing due to "Miva Empresa" enabled for the domains on the source server but no longer used.

/var/log/hsphere/hsphere.log log contains the following error:

2015-02-10 12:20:23,865 [TP-Processor6] DEBUG psoft.hsphere.CP - Miva Empressa physicalCreate
2015-02-10 12:20:23,868 [TP-Processor6] DEBUG psoft.hsphere.CP - PhysicalServer.exec /hsphere/shared/scripts/miva-empresa5-install
2015-02-10 12:20:23,868 [TP-Processor6] DEBUG psoft.hsphere.CP - ssh -o StrictHostKeyChecking=no -x -a root@ /hsphere/shared/scripts/miva-empresa5-install wwwuser wwwuser /hsphere/local/home/wwwuser/domain.tld
2015-02-10 12:20:23,899 [TP-Processor6] DEBUG psoft.hsphere.CP - TT#6026 from:null
2015-02-10 12:20:23,900 [TP-Processor6] DEBUG psoft.hsphere.CP - TT is:
Physical creation problem: Miva Empresa Engine
Account ID: 1020
Source server: web.server.tld
Target Server: web40.server.tld
Resource ID: 1323
Miva has not been correctly installed. Please contact your server administrator
        at psoft.hsphere.resource.miva.Miva5UnixOperator.installMivaEmpresa(
        at psoft.hsphere.resource.apache.MIVAEmpresaOnlyResource.physicalCreate(
        at psoft.hsphere.admin.HDResourceInMove.physicalCreate(


Miva Empresa not installed on destination server.


NOTE: "wwwuser" is just example, the solution is applicable for any users.

  1. Cancel migration
  2. Delete "wwwused" on target server (it was created within migration process)

    [root@target_server ~]# /hsphere/shared/scripts/userdel wwwuser
  3. Disable Miva for the affected domains
  4. Start migration anew.

6b908665c0d1eca5bdd0141a32fd712a 6311ae17c1ee52b36e68aaf4ad066387 f213b9fa8759d57bee5d547445806fe7 2e39a5e5b1423cc126cf735bac076008

Email subscription for changes to this article
Save as PDF