Windows 2019, AD Connect - How to resolve Unable to display Connector run summary?

Wade Stolz 1 Reputation point

I've not been able to resolve this message. Today I also received 3 new Event ID's related. I had completed a in place AD Connect upgrade to, one because it was outdated and 2 because of another popup message " Synchronization Server Manager - Unable to display Connector run summary. I've run the troubleshooting wizard, everything came back good. I've spent all day trying to locate possible solutions and have not been able to .

  • Directory Synchronization Event ID 665 - Unable to store password hash sync... Details System.Data.SqlClient.SqlException (0x80131904)
  • ADSync Event ID 6056 The management agent "" failed on run profile "Delta Synchronization" because of server error.
  • ADSync Event ID 6401 "ERR_: MMS(188): ..\memutils.cpp(8086): Unusual error code reported 0x80231362 Azure AD Sync"

Any suggestions would be extremally helpful and appreciated.


Thank you


Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,602 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Marilee Turscak-MSFT 36,411 Reputation points Microsoft Employee

    Hi @Wade Stolz ,

    The exception details say "The timeout period elapsed prior to completion of the operation or the server is not responding."

    This error indicates that there is a query that is taking too long. In SSMS, you can update the timeout by right-clicking on the query > Query Options. You can also set a query timeout under Tools > Query Execution > SQL Server > General > Execution time-out and set it to 0.

    If that doesn't work, you may also need to check the values in the server connection strings under Connect > Database Engine > Options > Execution time-out.

    Note that you might also run into this issue using older versions of SQL server. Azure AD Connect supports all versions of SQL Server from 2012 (with the latest service pack) to SQL Server 2019 and needs to run on those.

    It would also help if you could share more event logs. If the suggested fixes don't work, I would recommend doing a server reboot or even a reinstall to see if the issue persists.

    Let me know if this helps. I'll be happy to continue the discussion or open a support case for you if the suggestions do not resolve the issue.

    If the information helped you, please Accept the answer. This will help us as well as others in the community who might be researching similar issues.

    0 comments No comments