Article ID: 128812, created on May 10, 2016, last review on May 10, 2016

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


Office365 executing configuration script task fails with the following output:

<StatusDescription>Internal Server Error</StatusDescription>
<s:Text xml:lang="en-US">ServiceUnavailableFault</s:Text>


APSC request was not able to reach MOP.


First of all, check that gateway IIS site (and corresponding application pool) on MOSI GW server is up and running. Otherwise, restart it manually.

If it does not help, please contact Microsoft Support, providing the following log files:

  1. Sitelog: C:\inetpub\wwwroot\mosi\App_Data\sitelog
  2. XMLPayload related to the customer in question: C:\inetpub\wwwroot\mosi\App_Data\XMLpayload\customer1234.log
  3. log with increased verbosity, it can be done using the article How to enable verbose log on MOSI Gateway Host
  4. XML requests C:\inetpub\wwwroot\mosi\App_Data\web_messages.svclog and C:\inetpub\wwwroot\mosi\App_Data\web_tracelog.svclog

Search Words

O365 task ServiceUnavailableFault

Office365 ServiceUnavailableFault

Office365 task fails:Reason:ServiceUnavailableFault Method: CreateCustomerAccount.

Reason:ServiceUnavailableFault Method: CreateCustomerAccount

O365: Reason:ServiceUnavailableFault Method: CreateCustomerAccount.

O365 task fails: Reason:ServiceUnavailableFault Method: CreateCustomerAccount.

Office365: Reason:ServiceUnavailableFault Method: CreateCustomerAccount.


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

Email subscription for changes to this article
Save as PDF