Active Directory Synchronisation Error Report - Blank Error Description


  • Hi,

    I am using Directory Syncronisation with Office 365. I am getting an error report however the "Error Description" column is blank. They are all Contacts (I recently added a load of Contacts). Can anyone assist in troubleshooting?

    Kind regards

    Monday, July 01, 2013 2:53 PM


All replies

  • Hi,

    Thanks for your posting.

    Have you check this MS article?

    Troubleshoot directory synchronization

    Setting up Directory Synchronization with the NEW Office 365

    If the issue persists, i would suggest that you can ask for help from Office 365 forums:


    Vivian Wang
    TechNet Community Support

    Tuesday, July 02, 2013 10:14 AM
  • Hi Vivian,

    I can only assume that there was something wrong with those contacts. I imported about 800 using a CVS into AD. 40 of them kept causing this email to come through with the blank error description. I moved a re-created them but the email kept coming through (different AD object ID and everything!). So I checked how many items where in my AD which was about 800, well below the 50,000 limit.

    I deleted the contacts that were causing me grief and I haven't seen the problem the email since. Although I do feel like I have swept this problem under the carpet somewhat.

    Kind regards, 

    Wednesday, July 03, 2013 7:55 AM
  • Hi DominoDongle,

    Not sure if you've already resolved this issue and have moved on, but I thought I'd share my experience and fix for this!

    We are using Windows Azure Directory Sync and when the Blank error occured, I ran the miisclient.exe tool and found that it gave me more detail into the error.

    Although the error detail itself was just as cryptic, 'Required attribute 'cloudanchor' missing', what DID help me was the fields within the tool.

    The fields showed that although User A was being imported, User B's email address was listed.  I checked User B's AD account and found that it had the wrong email address listed in his properties.  Made the change and ran the synchronization with no further issue!

    Hope this helps you or anyone else experiencing this problem!

    • Proposed as answer by Alan Go Wednesday, August 07, 2013 6:41 PM
    Wednesday, August 07, 2013 6:38 PM