Search Engine: Elastic

Article ID: 129326, created on Aug 26, 2016, last review on Jul 13, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3
  • Operations Automation 7.4
  • Operations Automation 6.0


Office365 Provisioning 'AsyncOperations' task fails with the following output:

Last execution output Operation pending. 
Provisioning: resource 3dc35c31-xxxx-xxxx-xxxx-d7a35d421b11 of type 'asyncOperations' ( for APS application 'Office 365-16.5-64': Provisioning is being executed by the application.
Additional info: Configuring subscriptions is in progress. Waiting for the completion of the BA Order #219434.

O365 Endpoint sitelog contains the following entries:

2018-06-28 16:55:52,161 [ 140] INFO PBA         : Open API method 'GetOrder_API' called.
2018-06-28 16:55:52,169 [ 140] INFO aps_endpoint: Check ChangePlan order #22321817...
2018-06-28 16:55:52,169 [ 140] INFO aps_endpoint: ChangePlan order #22321817 isn't yet completed. Waiting for the resource limits propagation.
2018-06-28 16:55:52,170 [ 140] INFO aps_endpoint: BM order cannot be completed yet.
2018-06-28 16:55:52,170 [ 140] INFO aps_endpoint: Subscription provisioning is in progress: BM order cannot be completed yet.


The current order completion status is not specified as valid in the Office365 Endpoint configurations file.


  1. Check the corresponding order current status in Order Status History. E.g. it could be 'CP' (Completed).
  2. Open C:\inetpub\wwwroot\<Office 365 Gateway Application Name>\settings.config file.
  3. Alter the line to include the target order status:

    • before:

      <add key="ORDER_COMPLETION_STATUSES" value="PC,PT,WZ,WI"/>
    • after:

      <add key="ORDER_COMPLETION_STATUSES" value="PC,PT,WZ,WI,CP"/>
  4. Recycle the Office 365 website application pool in IIS.

caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d 55fe109b4b4fe3fbb893f22dbb85a41a 0871c0b47b3b86ae3b1af4c2942cd0ce 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF