Search Engine: Elastic

Article ID: 132195, created on Feb 6, 2018, last review on Feb 6, 2018

  • Applies to:
  • Operations Automation 7.2

Symptoms

Installation of Exchange PPM-package (Protocols/IMAP/POP3/SMTP) fails. Event registered in PCP > Operations > Tasks > Events:

Installation of package Exchange2013Protocols 1.11 (id=ID) to host EXCAS01.DOMAIN.LOCAL (id=ID) was failed. Reason: Failed to process finalizeInstallUpdate for pkgId: ID, ex message is: IDL:Plesk/ExSystem:1.0

Error in /var/log/pa/core.log on OA Management Node:

Jan 16 22:56:03.215 : DBG [SysDbHeartbeat p:-default-threadpool;-w:-Idle:738 pau]: c.p.p.s.b.e.BrandedServiceBean addBrandableService acc.point NNN.NNN.NNN.NNN service ExchIMAP4 hostname PREFIX.DOMAIN.TLD
Jan 16 22:56:03.218 : DBG [SysDbHeartbeat p:-default-threadpool;-w:-Idle:738 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.branding.ejb.BrandedServiceBean.addBrandableServicePlesk.ErrorHandling.BrandingManagement.PrefixAlreadyRegistered: IDL:Plesk/ExSystem:1.0

Prerequisite:

Provider has same Exchange package installed with the same prefix but different domain and different IP

Cause

This is a result of bug POA-113517.

Expected behavior: in case if prefix is occupied by another service OA constructs unique value by adding "-1", "-2".. at the end of the prefix. Package installation completes successfully. It does not work because of the bug.

Actual behavior: package installation fails with error PrefixAlreadyRegistered

Resolution

Please upgrade your OA-installation to version 7.3 where bug POA-113517 is fixed.

Workaround: Use unique value of the prefix, i.e exchange-1, autodiscover-redirect-1.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 31987597efff5a3a9ce779cc203bbe5e 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF