Search Engine: Elastic

Article ID: 8994, created on Sep 16, 2010, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation


Hosted Exchange service provisioning is failing in POA with error like this:

Could not find for provide Exchange 2007 services: Exchange2007Mailstore (mailboxes), Exchange2007Mailstore (public folders), Exchange2007SMTP, Exchange2007SMTPAuth, Exchange2007OAB, Exchange2007POP3, Exchange2007IMAP4, Exchange2007Protocols, Exchange2007Autodiscover. Please check the following requirements: 1) all necessary services are installed in one AD domain; 2) all services satisfy given attributes ('Exchange'); 3) there exist mailbox stores on the mail-store services, which satisfy given store attributes ('Exchange'); 4) there exist ready to provide mailbox and (or) public folder stores; 5) branding is configured.


One of the possible reasons of the problem with Hosted Exchange services provisioning is that all mailbox servers registered in POA are out of capacity of Exchange organizations. As a result POA cannot find server to create subscription.


To solve the problem you need to go through all mailbox servers registered in POA and check their capacity on Exchange organizations:
  1. Log into POA Provider CP and go to Top > Deployment Director > Server Manager > Hardware Nodes
  2. Click on mailbox server
  3. Switch to the tab General
  4. Switch to the sub-tab Capacities
  5. Check if you have available units for the resource Number of Exchange Organizations
If you have provisioning attribute assigned to the resource Hosted Exchange in the service template which cannot be provisioned (it is 'Exchange' in the error message above) then you need to check only mailbox servers which have the same attribute assigned. You may go to Top > Service Director > Provisioning Manager > Attributes > Exchange, click on the needed attribute and switch to the tab Hosts, you will find all servers the attribute is assigned to, check number of available Exchange organizations on these servers.

Additional information

Refer to the article for another reason of problem with Hosted Exchange services provisioning caused by not configured branding.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF