Article ID: 3090, created on Nov 22, 2007, last review on Apr 25, 2014

  • Applies to:
  • Operations Automation 5.4

Symptoms

The task 'Create Windows SiteBuilder site' fails with the following error message:

Axis call has failed, message is Server was unable to process request. --->
Exception of type 'SWsoft.SiteBuilder.BO.Facade.PlanLimitException' was thrown., code is 71

Cause

SiteBuilder Plan assigned to the customer does not allow to create more sites. Most probably, site limit in the POA Service Template do not match limit defined in the SiteBuilder Plan, so POA allows to create more sites than SiteBuilder does.

Resolution

Follow the steps below to synchronize POA Service Template sites limit with Sitebuilder Plan sites limit:

  1. Find the Resource Type limit in the corresponding POA Service Template:

    • Go to the POA Provider Control Panel > Operations Director > Domain Manager Domains > click on the problem domain > click on the customer account > Resources tab > Domains to get the subscription ID for the domain

    • Open the Subscriptions tab and click on the found subscription, then click on the Service Template name

    • Open the Resources tab and find the limit of the 'Windows SiteBuilder sites' Resource Type

  2. Find the limit in the corresponding Sitebuilder Plan:

    • Open the Parameters tab of the already selected POA Service Template and find the 'WSB Plan name' Activation Parameter

    • Login to Sitebuilder as a plan owner (Provider or reseller) and go to General > Users > Plans > select required plan > General

    • Set the 'Maximum number of regular sites' parameter to match the limit of the 'Windows SiteBuilder sites' in the POA Service Template

After synchronizing limits it should be possible to complete the task. If task cannot complete successfully, you can temporary increase SiteBuilder Plan limits in order to investigate this issue further.

Search Words

Create Parallels Plesk Sitebuilder site

SWsoft.SiteBuilder.BO.Facade.PlanLimitException

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF