Article ID: 113135, created on Jan 13, 2012, last review on Oct 6, 2015

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

Symptoms

Office 365 provisioning tasks fail with the error message

An unsecured or incorrectly secured fault was received from the other party.

Cause

  1. The time setting is incorrect on the MOSI gateway server. MOSI requests contain a digitally signed time stamp, and Microsoft will only tolerate a maximum time difference of five minutes. This issue is described in the MOSI SDK guide in the section WS-Security Header.

  2. SSL certificate installed on MOSI Gateway server expired. Use IIS Manager to check SSL certificate installed on the MOSI Gateway web site.

Resolution

  1. Correct the time and configure a reliable time source on the MOSI Gateway server. If the MOSI gateway is joined into Active Directory domain and the time is synced from there, configure a time source on a domain controller that holds the PDC Emulator role.

  2. Install correct SSL certificate on MOSI Gateway server following procedure described in the Odin Automation Office 365 Integration Provider's Guide.

Once the problem with incorrect time or SSL certificate is solved on the MOSI gateway, resubmit all failed OA background tasks related to Office 365 services provisioning.

Search Words

Unable to provision an Office 365 account

An unsecured or incorrectly secured fault was received from the other party

Method edit_customer calling failed. Reason:An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. Method: CreateCustomerAccount

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 ac82ce33439a9c1feec4ff4f2f638899

Email subscription for changes to this article
Save as PDF