Share via

Azure Sync Server Manager failures

Anonymous
2024-07-26T14:51:23+00:00

In the process of relocating our offices our domain controllers as well as our Azure AD-Connect servers were offline for 7 days. Once servers were restored Azure Sync Manager syncs to <domain>.onmicrosoft.com were failing due to stopped-extension-dll-exception error. Researching this error points to a password issue for the Sync account.

Upon re-entering the account password in Azure Sync manager the application locks up for a time then returns error "request to endpoint timed out". I assumed the endpoint in question is in the O365 cloud?

Sync to our on-premises domain controllers are running and unaffected.

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-26T19:59:16+00:00

    Dear Jerry Toscano,

    Good day! Thank you for posting to Microsoft Community. We are happy to help you.

    The error message "stopped-extension-dll-exception" you're encountering in Azure AD Connect after your servers were offline indicates a potential issue with the synchronization process.

    1. Double-check that the password you entered for the sync account in Azure AD Connect Manager is correct and matches the password for the account in Azure AD. If you're unsure about the password, consider resetting it through the Azure Active Directory portal (https://azure.microsoft.com/en-us/get-started/azure-portal).
    2. Verify network connectivity between your on-premises environment and Azure AD. Ensure firewalls aren't blocking communication. Check if your DNS servers can properly resolve the Azure AD endpoints.
    3. Visit the Microsoft 365 Service Health portal (https://learn.microsoft.com/en-us/microsoft-365/enterprise/view-service-health?view=o365-worldwide) and check for any reported issues with Azure AD that might affect synchronization.
    4. Ensure you're running the latest version of Azure AD Connect. Updates often include bug fixes and performance improvements. Try restarting the Azure AD Connect service on your server. This might resolve temporary glitches.
    5. In extreme cases, you might need to reset the synchronization service. This will clear any existing data and perform a full initial synchronization, which can be time-consuming. Use this as a last resort after exhausting other options.

    By systematically working through these potential causes and solutions, you should be able to resolve the "stopped-extension-dll-exception" error and successfully re-establish synchronization between your on-premises environment and Azure AD.

    I hope this helps. Let me know if you have any further questions or concerns. Please understand that our initial response may not always resolve the issue right away. However, with your help and more detailed information, we can work together to find a solution. Thank you for your help.

    Was this answer helpful?

    0 comments