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.
MID Server validation fails when sys_user record with mid_server role is configured for Web service access only - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • MID Server validation fails when sys_user record with mid_server role is configured for Web service access only
KB0598957

MID Server validation fails when sys_user record with mid_server role is configured for Web service access only


2456 Views Last updated : May 23, 2024 public Copy Permalink
KB Summary by Now Assist

Description

When the web_service_access_only field in the sys_user table is set to true for a user with the mid_server role, MID Server validation fails, and the following error is displayed:

User mid_user is not allowed to access the given processor: no thrown error 

This issue is related to the error in KB0598956, in which the mid_server role configuration caused validation to fail.

Steps to Reproduce

  1. Navigate to User Administration >  Users.
  2. Open a record for a user that has the mid_server role.
  3. Select the Web service access only option.
  4. Save the record.
  5. Create a new MID Server.
  6. Try to validate the new MID Server. 
    Note the log message: User mid_user is not allowed to access the given processor: no thrown error

Workaround

  1. Clear the Web service access only option in the sys_user record.
  2. Re-validate the MID Server.

Note:

This issue is fixed in Madrid, meaning MID server user can be set to Web service access only from Madrid onward.


Related Problem: PRB717020

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.