while configuring password write back for SSPR, I get error and it says check event viewer. Not able to enable SSPR.

Anonymous
2022-09-14T13:57:25.883+00:00

While enabling SSPR, I need to enable password writeback in AAD connect however, when doing so, I face below mentioned error which is not letting me enable the same. Can someone please suggest on this.

TLS1.2 is already running on server. And we are using adfs server for SSO.

The server encountered an unexpected error while performing an operation for the client.

"BAIL: MMS(8344): ..\server.cpp(9546): 0x80004005 (Unspecified error)
Azure AD Sync 2.1.16.0"

The password management extension encountered an error.
The stack trace is:

"Couldn't connect to any service bus endpoint(s)

at Microsoft.CredentialManagement.OnPremisesPasswordReset.PasswordResetServiceManager.LogAndThrowPasswordResetException(String message, String context, Int32 eventId, Exception ex)
at Microsoft.CredentialManagement.OnPremisesPasswordReset.PasswordResetServiceManager.StartPasswordResetService(String configXML, IPasswordReset passwordResetProvider, Boolean initiatedByAdmin)
at AADPasswordReset.AADPasswordResetExtension.StartPasswordResetService(AADPasswordResetExtension* , _GUID managementAgentGuid, Char* serviceConfiguration, IAADPasswordReset* passwordResetServerHandle, Int32 initiatedByAdmin)

InnerException=>
Exception of type 'Microsoft.CredentialManagement.OnPremisesPasswordReset.OnPremisesPasswordResetException' was thrown.

at Microsoft.CredentialManagement.OnPremisesPasswordReset.PasswordResetServiceManager.StartPasswordResetService(String configXML, IPasswordReset passwordResetProvider, Boolean initiatedByAdmin)

InnerException=>
none

TrackingId: ec5b096a-7266-4ffd-af27-f4a288d39c8a, Couldn't connect to any service bus endpoint(s), Details:

TrackingId: ec5b096a-7266-4ffd-af27-f4a288d39c8a, Password writeback service is not in a healthy state. No serviceHost for service bus endpoints are in running state. Please refer aka.ms/ssprtroubleshoot, Details: Version: 5.0.922.0

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

5 answers

Sort by: Most helpful
  1. JimmySalian-2011 41,916 Reputation points
    2022-09-14T14:12:46.93+00:00

    Hi Ujjwal,

    Please check the time is sync and you are using correct GA account check this link for troubleshooting same issue: unable-configure-pwd-writeback-error

    ==
    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Dynamic 0 Reputation points
    2023-03-21T15:43:37.9333333+00:00
    1. Open the Event Viewer on the server where the Azure AD Connect is installed.
    2. Look for any errors or warnings related to SSPR or password writeback.
    3. Check the event logs for any errors related to Azure AD Connect.
    4. Make sure that the Azure AD Connect server is running the latest version of the software.
    5. Verify that the password writeback feature is enabled in the Azure AD Connect configuration.
    0 comments No comments

  5. Tom Murphy 0 Reputation points
    2024-03-28T13:39:39.12+00:00

    To fix this you must enable TLS 1.0 and 1.1 thats the only way I could get password writeback to enable. I had recently disabled this across our server estate. This is an undocumented feature that it required. Google how to enable TLS 1.0 and 1.1 - this is not a secure cypher in this day and age, but it was the only way the server would connect to the Azure Service bus for SSPR, before it was enabled, the Azure side would terminate the connection.

    Microsoft need to fix this.

    0 comments No comments