Office 365:- An error occurred executing configure aad sync task element ‘ma-run-data’ was not found

So this week I have been performing an Office 365 migration and part way through federating my domains and getting ADFS up and running I came across this error below

First thing I did was go have a quick look at what was going on within the Event log and there was a rather odd error. This can be down to your service account losing its groups or the DCOM components losing their permissions too but mine seemed to be ok

Scheduler::SchedulerThreadMain : An error occured and scheduler run failed to perform all operation.

System.Management.Automation.CmdletInvocationException: Run profile ‘Full Import’ does not have run steps. —> System.InvalidOperationException: Run profile ‘Full Import’ does not have run steps.

at Microsoft.DirectoryServices.MetadirectoryServices.UI.WebServices.MMSWebService.InvokeRunProfile(String connectorName, String runProfileName)

Firstly do try a repair of the install and ensure you are at the latest version, as I said before this may be permissions related but if not after much head scratching for some very very odd reason all my rules had been dropped in the Synchronization Service Manager. To be honest I never got to the bottom of quite why they vanished during switching over the federation but to get things working again launch the application and goto the connectors tab

You should see you main AD and any others you wanted to sync in your forest. select your local AD Domain Services and then select configure run profiles on the right hand side

Within this window it will probably now look rather bare and this is what the cryptic error is going on about. It basically doesn’t know what to do!

Repopulate all the option including the export which is pretty much simply select the matching type to the profile and ensuring your base DN/partition is correct

Do make sure your Export one is populated as I found my password sync stopped working and had to do this and then use the Wizard to remove ADFS and flip back to password hash and then re-integrate. If you don’t do this you will see errors in the 365 Portal stating Password sync hasn’t occurred and get this error in your event log despite things now looking like they are syncing

Scheduler::SchedulerThreadMain : An error occured and scheduler run failed to perform all operation.

System.Management.Automation.CmdletInvocationException: Run profile ‘Export’ does not have run steps. —> System.InvalidOperationException: Run profile ‘Export’ does not have run steps.

at Microsoft.DirectoryServices.MetadirectoryServices.UI.WebServices.MMSWebService.InvokeRunProfile(String connectorName, String runProfileName)

at Microsoft.IdentityManagement.PowerShell.Cmdlet.InvokeADSyncRunProfileCmdlet.ProcessRecord()

— End of inner exception stack trace —

at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)

at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)

The final thing to do now is run the sync by right clicking the AD connector, selecting run and then the relevant task. I did select full first just to make things are working.

Hopefully you will now see nice informal messages in your event log like below and your 365 portal should update within the hour to say its all back in sync