This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 69%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
I did a swing migration of AD Connect and export/import from a DC to a doman-joined Windows 2022. However, when I try SSPR I get the following error (image). However, I verified together with an MS Engineer that there are no connectivity issues from the new server. I've disabled and re-enabled writeback, but still no success. However, I see this error when the AD Sync service restarts.
TrackingId: 3c04d636-7c80-4c06-a9b7-380c997692ee, Listener for Namespace: ssprdedicatedsbprodweu, Endpoint: 6b4d1213-177e-4265-8d11-66892fc886c5_c99d45ac-47f4-476c-b38f-ed151dd3b1e5 offline Event. Last error encountered System.ServiceModel.CommunicationException: The connection to the connect service was lost. ---> Microsoft.ServiceBus.ConnectionLostException: The connection to the connect service was lost.
--- End of inner exception stack trace ---, Details: Version: 5.0.922.0
Any additional insights from the community will be appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 20%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Just checking in to see if the below answer helped. If this answers your query, please don’t forget to click "Accept Answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
I was able to resolve the issue. This is just super weird. On the only DC I had installed the cloud provisioning agent (cloud sync) and also installed in on the new one. However, I uninstalled from the DC but this error was shown which is expected but it was green for the new server. I then decided to remove the yellow checkbox and guess what started to work...SSPR!
We also had the similar issue. We had both Entra ID connect sync and Clud sync(for separate domains but using same tenant ). Write back was forced to go via cloud sync however we were not using cloud sync for that particular domain for ID and pwd sync. Just need to uncheck the write back password with MS Entra connect cloud sync option and now pwd write back will go via Entra ID connect sync only.
Moreover Microsoft gives you message also to update/change the write-back if we read the screen carefully.
I also ensured the following:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Hi @ISE •
Did you try to restart the Entra connect server ?
Some links should help you for troubleshooting :
Troubleshoot self-service password reset in Microsoft Entra ID
How does self-service password reset writeback work in Microsoft Entra ID?
Please don't forget to accept helpful answer
Yes, I restarted the server many times. I also went through all of the troubleshooting links you sent and nothing works. Based on the error OnPremisesConnectivityError = 30, but I'm able to resolve everything from this server. So I'm not sure what other connectivity issue.
Hi @ISE
Happy to hear that your problem is fixed and thank you for sharing your feedback.
I will ad your answeras a comment to let you accept it and close this thread.