Article ID: 127121, created on Oct 9, 2015, last review on Oct 9, 2015

  • Applies to:
  • Operations Automation

Symptoms

A set of O365 creation tasks with CustomerNotExistFault like below:

Last execution output   

Application configuration script reported errors: ' error id "validation-error", setting id "Configuration": Method edit_customer calling failed. Reason:CustomerDoesNotExistFault Method: ValidateOrder ({"ExtensionData":null,"CustomerId":"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",

It is also possible to locate ServiceUnavailableFault in the previous task's execution.

Cause

Microsoft Online Portal - the Office 365 backend endpoint located at Microsoft - is unable to locate the customer, likely due to internal error.

Resolution

  1. Obtain the list of such users by carefully examinining failed tasks, save the list of Customer IDs, in the example above it is aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee.

  2. Access MOSI via RDP, locate the directory with MOSI website,

  3. Go to \App_Data\XMLPayload inside MOSI directory,

    Then, for each customer found on step 1:

  4. Search for Customer-aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee - the XML exchange log between MOSI and Microsoft.

    Note: You have to use asterisks or full file name

  5. Contact Microsoft regarding the status of the customer, providing the file from step 4.
  6. Once Microsoft would fix/restore the user, please re-run the previously failing task.

In case the customer does not exist completely on Microsoft side - please contact Odin support.

Search Words

"additionalNonlocalizableMessage": "CustomerDoesNotExistFault",

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF