Search Engine: Elastic

Article ID: 129689, created on Oct 26, 2016, last review on Jul 19, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 6.0
  • Business Automation 7.1
  • Business Automation 7.2

Symptoms

The task Provisioning "Subscription" for APS application Office 365 fails with the output as below:

500 Internal Server Error
[ApplicationUnknownError] Provisioning: resource 969388d3-8882-4e1b-aa02-0e7febf70fd8 of type 'subscriptions' (http://www.parallels.com/Office365/Subscription/1.2) for APS application 'Office 365-17.1.3': Object reference not set to an instance of an object..

Body: {
"code": 500,
"message": "Object reference not set to an instance of an object.",
"additionalNonlocalizableMessage": "",
"error": "ApplicationUnknownError",
"http_request": "POST /O365App/aps/subscriptions to '10.0.0.1'"
}

The sitelog on the endpoint server contains entries indicating that it is unable to set up a password for the admin user:

2016-03-23 12:21:49,259 [ 212] DEBUG aps_endpoint: Going to set the password policy ForceChangePasswordNextLogin for the admin to FALSE
2016-03-23 12:21:49,259 [ 212] DEBUG flow        : CSP: Reset admin password policy of customer 'John Doe'
2016-03-23 12:21:49,259 [ 212] DEBUG flow        : CSP: Change admin password of customer 'John Doe'
2016-03-23 12:21:49,384 [ 212] ERROR aps_endpoint: SubscriptionsController.Post finished by exception System.AggregateException: One or more errors occurred.
2016-03-23 12:21:49,384 [ 212] ERROR aps_endpoint: System.NullReferenceException: Object reference not set to an instance of an object.

Cause

In case Office365/Tenant APS resource has bind_to_domain property filled - this is software-related issue #APSA-18590.

Otherwise: the reason is Global Admin user was removed or renamed on the MOP side. Issue also happens when Global Administrator permissions are revoked from the user on the MOP side.

Resolution

Software-related issue #APSA-18590 is fixed in Office 365 17.2 package version. To workaround the issue it is enough to create user admin@subdomain.onmicrosoft.com (where subdomain.onmicrosoft.com is the domain name specified on the order placement) with Global Admin role for customer in the Microsoft Online Portal.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 7c0b495571a6c1bec50e4f324a20ec14 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 8c199f0ee4305da1a577740620df4a51 ef171e3fccb12bd8e09076a7b49212c0

Email subscription for changes to this article
Save as PDF