Solved

3 million user on Local AD to be synchronized with Office 365 FID issue

Posted on 2015-01-16
4
147 Views
Last Modified: 2016-01-02
Hello everyone,

I have a customer (University) Who has an issue with DirSync. They have 3 million users on Local AD they want to synchronize with Office 365 to enable these users for Exchange online.

Now they have users "Students" enabled for Exchange online and management and staff are enabled on the On-premises Exchange servers.

Dirsync during the day synchronize 2 times fine without any error and again 2 times doesn't synchronize and gives error with no details. the error is "Stopped Extension-dll exception"

More errors shown as below
Directory Synchronization:
An unknown error occurred with the Microsoft Online Services Sign-in Assistant. Contact Technical Support. SetCredential() failed. Contact Technical Support.  (0x8009000B)

I am attaching other errors as well

   at Microsoft.Online.Coexistence.ProvisionHelper.GetLiveCompactToken(String userName, String userPassword)
   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.Initialize()
   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.Import(Byte[] syncCookie, Boolean isFullImport)
   at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntriesCore()
   at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntries(GetImportEntriesRunStep getImportEntriesRunStep)
Forefront Identity Manager 4.1.3465.0"

FIMSynchronizationService:
The management agent "Windows Azure Active Directory Connector" failed on run profile "Delta Import Delta Sync" because the server encountered errors.

FIMSynchronizationService:
The management agent "Windows Azure Active Directory Connector" step execution completed on run profile "Delta Import Delta Sync" but the watermark was not saved.
 
 Additional Information
 Discovery Errors       : "0"
 Synchronization Errors : "0"
 Metaverse Retry Errors : "0"
 Export Errors          : "0"
 Warnings               : "0"
 
 User Action
 View the management agent run history for details.

Directory Synchronization:
The Management Agent Windows Azure Active Directory Connector failed on execution. Error returned is 'stopped-extension-dll-exception'.  If the problem persists, contact Technical Support.

Open in new window


Customer have tried to involve Microsoft with them through a third party technical support company but microsoft was not able to apply anything since they have tried to apply some scripts but those scripts would take 3 days without finishing.

The first time the Dirsync was applied it took 1 week without finishing until now they were not able to apply a full import and export sync.

What have really got me interested is that Microsoft did not suggest to the customer to upgrade his FIM (ForeFront Identity Manager)'s old version to the latest one.

Customer is using Full SQL deployment on a dedicated server and DirSync (FID) on a separate server too. The deployed servers are virtual and have 32 GB ram and 200 GB HDD size and 4 cores.


I have recommended to this customer that we do not touch this current deployment since Microsoft themselves couldn't do anything in regard, but what we could do is take a virtual snapshot and then apply the upgrade and see if this resolves the issue or not?

Note:

Microsoft talked to them about a limited number of synchronized items to their Azure site per week! I am not sure about this but what the customer said is that they change approximately about 25,000 user object per day.
Could this issue happens because of this limit?


Thanks
anadolu-ad.jpg
0
Comment
Question by:Mohammed Hamada
  • 3
4 Comments
 
LVL 38

Expert Comment

by:Vasil Michev (MVP)
ID: 40553472
I'm not aware about such limits, but I will ask around, see if I can confirm this. The obvious bit is of course the predefined 300k limit for normal SKUs, but I highly doubt they have missed that. The SIA error is also puzzling, doesnt make sense to happen only sometimes if it was profile/credentials related.

Ask them to check for any mails sent to the technical contact address for the O365 tenant, they might contain additional information.
0
 
LVL 23

Author Comment

by:Mohammed Hamada
ID: 40553514
They basically have no direct connection with Microsoft, they hired a firm which applied the installation and configuration along with Microsoft's help. but in the last 2 years (Project was started right after the Office 365 hybrid integration came out) and until this moment they still have cases open with Microsoft that haven't been closed yet.

They have asked us (different technical company) to involve directly with them (the university) and see if we can get our hands on it and fix it. When I checked their Dirsync and SQL servers! they seem to be used old version of Forefront Identity Manager 2010 R2 (build 4.1.3456.0)

I am not sure if this includes SP1 in it but when I checked the (About) it didn't show anywhere if SP1 is installed or not but the version seems to be not that old but not the latest.

I've seen there's a hotfix which fixes some issues and suggested that we install it but they were terrified to do anything so I suggested that we take a snapshot of the machines and try upgrading FFIM to the latest version and install all hotfixes included and see if that works.

The worse possibility would be to Deactivate DirSync, then restore the old snapshots and reactive it which might take a day or two.

HotFix
http://support.microsoft.com/kb/2980295
0
 
LVL 23

Accepted Solution

by:
Mohammed Hamada earned 0 total points
ID: 41387957
My colleague was able to solve the problem by taking a backup of the SQL server, deleted the DirSync server and took a backup of the SQL key.

Reinstalled SQL , Dirsync and the problem was gone.
0
 
LVL 23

Author Closing Comment

by:Mohammed Hamada
ID: 41393090
Self managed
0

Join & Write a Comment

If you don't know how to downgrade, my instructions below should be helpful.
This article explains how to prepare an HTML email signature template file containing dynamic placeholders for users' Azure AD data. Furthermore, it explains how to use this file to remotely set up a department-wide email signature policy in Office …
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now