Article ID: 129243, created on Aug 11, 2016, last review on Aug 11, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

Order provisioning fails for particular reseller customers:

The order provisioning has failed.
The last error - "Service Creation Failed: Parallels Operations Automation error #extype_id #53, module_id #Exchange, Could not find the following Exchange 2013 services for provisioning: Exchange2013Mailstore (mailboxes), Exchange2013Mailstore (public folders), Exchange2013SMTP, Exchange2013SMTPAuth, Exchange2013OAB, Exchange2013POP3, Exchange2013IMAP4, Exchange2013Protocols, Exchange2013Autodiscover.

The following message appears in the poa.log:

Jun  4 14:15:49 poacore.fusyx.com : INF [openapi:10.20.101.1:1456 1:14319:af4eeb70 Exchange 697316619]: [ Exchange::Utils::ServiceFilter::resolveService] [Service selection] Skipping service (id=413) because it is not enabled for subscription
Jun  4 14:15:50 poacore.fusyx.com : INF [openapi:10.20.101.1:1456 1:14319:af4eeb70 Exchange 697316619]: [ Exchange::Utils::isBAPReadyForProvide] [Service selection] The branding is not ready for provide (service type: ExchPOP3, access point: 010.005.032.030)

Cause

Exchange service branding is misconfigured for reseller`s brand

Resolution

Open:

PCP > Settings > Brands > Brand Name > Service branding > Exchange branding

Branding should either be configured or turned off. Turning off branding will let reseller to use provider's brand. Configuring it will let reseller to use his own brand.

Additional details regarding brand configuration can be obtained in Provider`s guide:

Provider's Guides > Provider's Guide > Branding in Operations Automation > Configuring Brand > Branding Exchange > Branding Exchange 2007/2010

Search Words

provisioning Exchange 2013

provision failed hosted exchange subscription

Service Creation Failed: Parallels Operations Automation error #extype_id #53, module_id #Exchange, Could not find the following Exchange 2013 services for provisioning: Exchange2013Mailstore (mailboxes), Exchange2013Mailstore (public folders), Exchange2013SMTP, Exchange2013SMTPAuth, Exchange2013OAB, Exchange2013POP3, Exchange2013IMAP4, Exchange2013Protocols, Exchange2013Autodiscover. Please check the following requirements are met: 1) all necessary services are installed in one AD domain ('USERS.cloudnet.services'), 2) all services have the specified attributes ('exchange2013'), 3) there are some mailbox stores on mail-store services which have the specified attributes (''), 4) there are "ready to provide" mailbox stores and (or) public folder stores or public folder mailboxes, 5) branding is configured..

failed

The branding is not ready for provide

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF