Search Engine: Elastic

Article ID: 131137, created on Jul 12, 2017, last review on Sep 22, 2017

  • Applies to:
  • Operations Automation 7.1

Symptoms

Office 365 synchronization fails with the following error message:

"Username (login) can't be null"

Cause

The cause is a software-related issue #APSA-18908: "[O365] The new users created in MOP are not synced to the OSA".

Resolution

The issue has been fixed in the Office 365 package version 17.1.2.

Please contact your Technical Account Manager or Pooled Team Associates(pta@odin.com) to schedule Office 365 upgrade.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF