On-premises writeback client synchronisation issues

VENCANAH Pravish 20 Reputation points
2025-01-14T10:14:13.0033333+00:00

For an unknown reason, our SSPR does not work anymore.

We have this following message in EntraID:

"Unfortunately, it looks like we can't connect to your on-premises writeback client right now. Troubleshoot Microsoft Entra Connect to restore the connection."

Entra Connect Sync is set up (no cloud sync),

Password Hash Sync is working,

Password writeback is configured.

Already followed all the steps mentioned in the link below until "Disable and re-enable the password writeback feature" :
https://learn.microsoft.com/en-us/entra/identity/authentication/troubleshoot-sspr-writeback#disable-and-re-enable-the-password-writeback-feature

So far, disabling and re-enabling password writeback feature on ADConnect works but only temporarily. The issue re-occurs after a few hours.

Kindly help.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,193 questions
{count} votes

Accepted answer
  1. Akhilesh Vallamkonda 11,680 Reputation points Microsoft Vendor
    2025-01-20T14:43:02.7566667+00:00

    Hi @VENCANAH Pravish

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue:

    On-premises writeback client synchronisation issues

    Solution:

    You have fixed this issue, by changing to staging mode in second Entra connect server. and you fimd the issue with having two Entra Connect services with the same settings causing this issue.

    If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.


1 additional answer

Sort by: Most helpful
  1. VENCANAH Pravish 20 Reputation points
    2025-01-20T08:02:38.1266667+00:00

    Actually after further checks i managed to find out that ADconnect was installed on another server and not configured in "Staging mode", which was supposed to be the case! I guess this was causing conflict when both writeback clients on each machine were trying to communicate with EntraID.

    After setting the second ADconnect to staging mode, i restarted the sync service on the main server and the issue was resolved.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.