(2016-12-19) Azure AD Connect Delta Import Run Profile Throws “Stopped-Server-Down”

You may notice that the “Delta Import” Run Profile for the AAD connector in Azure AD Connect throws a “Stopped-Server-Down” after running for about 20 or so minutes. Other connectors and other profiles execute without any problem!

In the application event log, you may see the following information and error events.

Figure 1: Informational Event In The Application Event Log

–

The underlying connection was closed: The connection was closed unexpectedly.

–

Figure 2: Informational Event In The Application Event Log

–

ProvisioningServiceAdapter::ExecuteWithRetry: Action: Import, Attempt: 0.

Live token has expired and it will be renewed automatically.

–

Figure 3: Error Event In The Application Event Log

–

Failure while prefetching import data.

–

Figure 4: Error Event In The Application Event Log

–

Failure while importing entries from Windows Azure Active Directory. Exception: Microsoft.MetadirectoryServices.ServerDownException: Failed even after 5 retries. Action: Import, Network error occurrences = 5. Exception: Unable to communicate with the Windows Azure Active Directory service. Tracking ID: b1796718-1719-4014-aa4a-80e73c5f8087 See the event log for more details.. —> Microsoft.Online.Coexistence.ProvisionRetryException: Unable to communicate with the Windows Azure Active Directory service. Tracking ID: b1796718-1719-4014-aa4a-80e73c5f8087 See the event log for more details. —> System.ServiceModel.CommunicationException: The underlying connection was closed: The connection was closed unexpectedly. —> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.

   at System.Net.HttpWebRequest.GetResponse()

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   — End of inner exception stack trace —

Server stack trace:

   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Microsoft.Online.Coexistence.Schema.IProvisioningWebService.ReadBackAzureADSyncObjects(Byte[] inputCookie, Boolean isFullSync)

   at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel)

   — End of inner exception stack trace —

   at Microsoft.Online.Coexistence.ProvisionHelper.CommunicationExceptionHandler(CommunicationException ex)

   at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel)

   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.<>c__DisplayClass7.<Import>b__6()

   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.ExecuteWithRetry(String actionName, Action action)

   — End of inner exception stack trace —

   at Microsoft.Azure.ActiveDirectory.Connector.GetImportEntriesTask.GetNextBatch()

   at Microsoft.Azure.ActiveDirectory.Connector.AADConnector.GetImportEntriesCore()

   at Microsoft.Azure.ActiveDirectory.Connector.AADConnector.GetImportEntries(GetImportEntriesRunStep getImportEntriesRunStep).

–

Figure 5: Error Event In The Application Event Log

–

The management agent "XXXXXXXXXXXXXXXX.onmicrosoft.com – AAD" failed on run profile "Delta Import" because the server encountered errors.

–

The solution? Believe it or not, but it worked for me!

Set-ADSyncScheduler -SyncCycleEnabled $FALSE

Start-ADSyncSyncCycle -PolicyType Initial

Start-ADSyncSyncCycle -PolicyType Delta

Set-ADSyncScheduler -SyncCycleEnabled $TRUE

–

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: https://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————