Article ID: 113495, created on Mar 21, 2012, last review on Sep 29, 2014

  • Applies to:
  • Operations Automation

Symptoms


POA cannot execute a task related to Office 365 service provisioning; the task fails with a confusing error message from the Microsoft API servers, like in the example below:

 Task ID    2165563
Queue name    aps_application_instance1384
Task name    APS application 'Microsoft Office 365', id 295, instance 1384 -> service 'customer', instance 2055: executing configuration script
Task description    APS application 'Microsoft Office 365', id 295, instance 1384 -> service 'customer', instance 2055: executing configuration script
Queue status    Failed     
Start not earlier than    Mar-07-2012 14:29
Method name    taskExecuteApplicationInstanceScript on OBJREF:APSManagerTasks:0:getAPSExternalTasks:0
Last execution output    Application configuration script reported errors: '<?xml version="1.0"?>
<output xmlns="http://apstandard.com/ns/1/configure-output">
<errors>
<error id="validation-error" setting-id="Configuration">
<message>Method edit_customer calling failed. Reason:InternalFault Method: AddDomain ({'Domain':{'ExtensionData':null,'Name':'cloud.parallelscloud.com'},'ExtensionData':null,'CustomerId':'ea2da929-71c8-4bf9-bbcd-728466a72c63','SubscriptionId':'00000000-0000-0000-0000-000000000000'})</message>
</error>
</errors>
</output>


Office 365 APS application of version 2.1 or below is installed in POA.

The problem has to be investigated with the help of the Microsoft Support Team. The Microsoft Support Team needs the exact request and response XML packets which the MOSI Gateway Server (Microsoft Online Services Interface) uses to provision services in Microsoft Office 365.

The article describes how to extract the request and response XML packets to/from the Microsoft API servers on a POA-managed MOSI Gateway Server.

 

Resolution


Follow the steps below to find the request and response XML packets on the MOSI Gateway Server.

  1. Install Service Trace Viewer Tool on a Windows workstation. It is a part of Microsoft Windows SDK which may be downloaded from this link http://msdn.microsoft.com/en-us/windows/bb980924.aspx.

  2. Enable the debug log on the MOSI Gateway server, following the instructions in this KB article: Office 365: How to enable verbose log on MOSI Gateway Host

  3. Run the failed Office 365 task in Task Manager in the POA Provider Control Panel at Top > System, Director > Task Manager, and wait until it fails.

  4. Disable the debug log on the MOSI Gateway Server and reverse the changes you made in step #2.

  5. Download the file web_messages.svclog from the MOSI Gateway Server on the workstation where Service Trace Viewer Tool is installed.

  6. Run Service Trace Viewer Tool and open the web_messages.svclog file you downloaded from the MOSI Gateway Server.

  7. The Service Trace Viewer will display a view that is similar to the screenshot below:



  1. In the left part of the screen, you will see the Activity tab listing all requests from the MOSI Gateway Server to the Microsoft API servers.

  2. Find the necessary request on the Activity tab (e.g., it may be AddDomain, AddUser, VerifyDomain, SetUserSubscriptions, etc.). In the example below, the request AddDomain is shown.

  3. In the right part of the Service Trace Viewer screen, you will see:
    • A list of subtasks for the activity selected in the left panel, a request to the Microsoft API servers, and a response from them (the request usually is displayed at the top of the list).
    • Three tabs: Formatted, XML, and Message. You may find XML packets on the XML and Message tabs.
  4. Select the first subtask in the list at the top of the screen and switch to the Message tab.

  5. Find and save the request XML packet:
    • Select everything in the tags <s:Header> and </s:Body> inclusively, and save as request.xml file.
  6. Select the last subtask in the list at the top of the screen and switch to Message.

  7. Find and save the response XML packet:
    • Select everything in the tags <s:Header> and /s:Body> inclusively, and save as response.xml file.
  8. Send the files request.xml and response.xml to the Microsoft Support Team to investigate the problem.

Note: do not send the entire contents of the XML packet found on the XML tab; not all of this information is needed by the Microsoft Support Team for proper problem investigation. Send only the contents of the Header and Body tags.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF