Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Enable user account in AD orchestration is failing with *** ERROR *** The server is unwilling to process the request. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Enable user account in AD orchestration is failing with *** ERROR *** The server is unwilling to process the request.
KB0779036

Enable user account in AD orchestration is failing with *** ERROR *** The server is unwilling to process the request.


1481 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Workflow failed on Enabling AD User Account, We can see the error *** ERROR *** The server is unwilling to process the request.

Cause

This error happens when enabling a user account and usually is raised if the password for the user does not meet domain requirements, as discussed in the link below.

https://social.technet.microsoft.com/Forums/office/en-US/6fac68a4-6665-4809-a595-68dbbe2dc18f/powershell-enabling-an-account-the-server-is-unwilling-to-process-the-request?forum=ITCG

Resolution

1. We can do a quick test with a different user via the OOB "Enable AD User Account" Activity.

Navigate to -> Orchestration -> Activity Designer Activities -> Enable AD User Account -> Test Input

2. If the error is triggering only on a specific user, then most likely the issue due to a password requirement is not met. Perhaps password setting activity on prior step has failed.

3. Manually set the password that met the Domain requirement for the user. Re-run the activity on step 1. IF this pass, it will confirm that prior step setting the Password may have failed.

4. Troubleshoot further on the Prior Step for setting the password. Check to see if there is a Credential tag for the Activity and that Credential valid and available to the MID Server.

5. Adding "Tags" and "MID Server" column on the Credential table would help see the issue.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.