Search Engine: Elastic

Article ID: 115904, created on Apr 4, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.4
  • Business Automation 5.5
  • Business Automation 5.4


The Provider cannot create a subscription for a customer in OA Control Panel; the error message There is no valid resources dependency combination found. Attributes: "Apache". is displayed in the Control Panel, like in the example below:

The error message may be slightly different:

There are no apache services that satisfy given set of attributes and located on 'Ready to provide' host; attrlist='Apache'.

The name of the particular attribute and service may be different in different cases.

The same error message is displayed in BA when provisioning the customer's sales order on a OA-based Service Plan. The error may be seen on the Provisioning Items tab in the failed order properties or on the Service Status History tab in the corresponding subscription that cannot be provisioned, like in the example below:


Resources in the OA Service Template used to create subscriptions are configured improperly. Some resource in a Service Template requires a host that satisfies the following requirements:

  • Required service is installed on some OA-managed host, e.g., Apache, MySQL, IIS, or Exchange

  • Provisioning attribute mentioned in the error message is assigned to the host with the required service installed

  • Host is marked as Ready to Provide in OA

However, OA cannot find a managed host that satisfies all of the above-mentioned requirements.


The ultimate goal is to assign the Provisioning Attribute mentioned in the error message to the host (or hosts) that satisfies all the requirements listed above.

  1. In OA Provider Control Panel, go to Service Director > Provisioning Manager > Attributes.

  2. Find the attribute mentioned in the error message (Apache in the example provided above).

  3. Switch to the Hosts tab.

  4. If this tab does not contain any hosts, it means the attribute was not assigned to any host yet. Follow the steps below. Otherwise, go to step 10.

  5. To fix this, open the Service Template for the subscription that could not be created.

  6. On the Resources tab in the Service Template, find the resource that has the problem attribute assigned.

  7. Then, depending on the resource, locate the host that you would like to use to provision this resource: Select hosts that have the required service (application) installed, e.g., Apache service for the Physical Hosting (Apache) resource:

    • If the host is a Parallels Virtuozzo container, open Service Director > Virtuozzo Manager > VPSs.

    • If the host is a physical server or a virtual machine other than a Virtuozzo container, open Deployment Director > Server Manager > Hardware Nodes.
  8. Click on the host you would like to use for provisioning of the resource and open the General tab.

  9. On the General tab, click on Attributes and then on "Assign" to assign the required attribute:

  10. Make sure that the host the attribute is assigned to has the required service on the Applications tab in the host properties (it depends on the resource) and is marked as Ready to provide; it means OA may provision customers' services on the host. Open the Summary tab in the host properties, and if Ready to provide is set to No, click the Mark as ready to provide button:

    In case services are not installed on node, you should install correct packages in OA Provider Control Panel > Service Nodes > <EXPECTED NODE> > Packages > PPM > Install Package.

    If everything is correct, new application will be added to the Application list on the node.

    Otherwise you have to explore Notification Log, find latest notification with subject 'Package installation failed' and resolve issues with installation (e.g. existing package conflicts with PPM package, then you have to remove existing package from node).

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 198398b282069eaf2d94a6af87dcb3ff 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 801221f8cd76fba7300d1e6817c8e08b e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF