Self Service Password Reset in AADConnect not working

For those google searching the eventlog azure ad connect sync errors I just had, which I couldn’t google an answer to:

  1. start the AADConnect wizard and disable Password Writeback
  2. do a delta sync
  3. start the AADConnect wizard and enable Password Writeback
  4. good 2 go 🙂

Errors for indexing:

TrackingId: e28140af-054b-4ea3-848b-23ff5bfabe14, Writeback Service for Namespace: ssprdedicatedsbprodncu, Endpoint: c42c6655-bda0-4175-90ba-b6e48cacd561_8b979142-2995-4eba-b993-9c14befea09a could not be started, Details: Version: 5.0.0.1541

TrackingId: e28140af-054b-4ea3-848b-23ff5bfabe15, ServiceHost for Namespace: ssprdedicatedsbprodncu, Endpoint: c42c6655-bda0-4175-90ba-b6e48cacd561_8b979142-2995-4eba-b893-9c14befea09a is not running, Details: Version: 5.0.0.1541

TrackingId: e28140af-054b-4ea3-848b-23ff5bfabe14, Listener for Namespace: ssprdedicatedsbprodscu, Endpoint: c42c6655-bda0-4175-90ba-b6e48cacd561_034af243-8b70-4a13-95fe-678a824f6943 offline Event. Last error encountered Microsoft.ServiceBus.RelayNotFoundException: Relay must be created at this address before using the binding with IsDynamic set to false. TrackingId:82abab71-87ed-4e40-a0a6-396b614a22bb_G14, SystemTracker:ssprdedicatedsbprodscu.servicebus.windows.net:c42c6655-bda0-4175-90ba-b6448cacd561_034af293-8b70-4a13-95fe-678a824f6944, Timestamp:1/8/2018 8:58:54 AM —> Microsoft.ServiceBus.Messaging.Amqp.AmqpException: Relay must be created at this address before using the binding with IsDynamic set to false. TrackingId:82abab71-87ed-4e40-a0a6-396b614a22bb_G14, SystemTracker:ssprdedicatedsbprodscu.servicebus.windows.net:c42c6655-bda0-4175-90ba-b6e48cacd561_034af293-8b70-4a13-95fe-678a824f6944, Timestamp:1/8/2018 8:58:54 AM
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Amqp.AmqpObject.OpenAsyncResult.End(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Amqp.AmqpObject.EndOpen(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Amqp.DuplexAmqpLink.OnOperationComplete(AmqpObject link, IAsyncResult result, Boolean isOpen)
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Amqp.AmqpObject.OpenAsyncResult.End(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Amqp.AmqpObject.EndOpen(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceBus.AmqpRelay.ConnectTask.<Start>d__5.MoveNext()
— End of inner exception stack trace —
at Microsoft.ServiceBus.RelayedOnewayListener.RelayedOnewayAmqpListenerClient.AmqpRelayedConnection.Open(TimeSpan timeout)
at Microsoft.ServiceBus.RelayedOnewayListener.RelayedOnewayAmqpListenerClient.GetOrCreateConnection(Uri via, TimeSpan timeout)
at Microsoft.ServiceBus.RelayedOnewayListener.RelayedOnewayAmqpListenerClient.Connect(TimeSpan timeout)
at Microsoft.ServiceBus.RelayedOnewayTcpClient.EnsureConnected(TimeSpan timeout, Boolean isRetry), Details: Version: 5.0.0.1541

Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

6 Comments
Most Voted
Newest Oldest
Inline Feedbacks
View all comments
Lewis
Lewis
7 years ago

Brilliant – resolved it for me! thanks 🙂

Arnaud
Arnaud
9 months ago

Great, still valid in 2025. Got the same error and you saved my day. Huge thanks 🙂

Carlos
Carlos
6 years ago

thank You! works pretty well 🙂

Simon
Simon
6 years ago

Thank you for the post, worked, though does have me scratching my head what is the trigger.

David
David
3 years ago

Resolved it for us as well!
Good resource. Thank you.

ekow
ekow
6 months ago

Unfortunately, this really isn’t a fix, it works for a while, but the problem just returns the next day or couple of hours later, Microsoft doesn’t have any proper solution either because even after applying all their troubleshooting steps, the error still persists.