Article ID: 130798, created on May 11, 2017, last review on May 11, 2017

  • Applies to:
  • Operations Automation

Symptoms

An Exchange 2007 DAG cluster is being deployed in OA. Installation of the OA Agent on the active cluster node fails with the following message:

POA Error: HRESULT = -2147016656; There is no such object on the server.
--- Extended ADs error description ---
Provider: LDAP Provider
Error description: 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:
        'CN=System,DC=hosting,DC=local'
        CustomAction registerPleskDAsClusterResource returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 0:12:34: InstallFinalize. Return value 3.

WPE is used on the installation, MPS is not deployed.

The "CN=PEM Configuration,CN=System,DC=hosting,DC=local" entity exists in corresponding Active Directory domain.

Cause

The OA Agent installation process tries to store the data about the cluster in the "adminDescription" field of the "PEM Configuration" AD object. This can't be done if this field's value is longer than 1024 symbols (AD limitation), in this case we try to store the same data in MPS.

In case WPE is used on the installation instead of MPS it is not properly checked whether MPS is installed, which is why the installation fails.

This issue is reported to the development team as POA-111284: "Agent installation failed on windows node in clustered configuration."

Resolution

Please contact your Account Manager or Pooled Technical Associates team (pta@odin.com) to trace the status of POA-111284.

As a workaround the following can be performed:

  1. Run ADSI Edit (adsiedit.msc) on an AD-connected server.
  2. Locate the "CN=PEM Configuration,CN=System,DC=hosting,DC=local" object and open its properties.
  3. Edit the "adminDescription" attribute, remove all the <cluster> tags from the config, so only the following is left:

    <config><clusters></clusters><hostingOUName>Hosting</hostingOUName></config>
    
  4. Save properties and install the OA Agent.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF