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.
Outbound RESTMessageV2 request via MID server fails for users with snc_read_only role - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Outbound RESTMessageV2 request via MID server fails for users with snc_read_only role
KB0754125

Outbound RESTMessageV2 request via MID server fails for users with snc_read_only role


1032 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

When an outbound REST request is executed using RESTMessageV2 via a MID server as a user with snc_read_only role, it fails with the below error:

Security restricted: access for table: ecc_queue, user: abel.tuter, operation: create -- from class: ReadOnlyRoleAccessHandler
REST Msg Outbound - ECCRESTResponse : Error while evaluating the XPATH Expression against response: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:297)
org.apache.axiom.om.impl.dom.DocumentImpl.getOMDocumentElement(DocumentImpl.java:446)
org.apache.axiom.om.impl.dom.DocumentImpl.getDocumentElement(DocumentImpl.java:458)
com.glide.rest.outbound.ecc.ECCRESTResponse.getNodeList(ECCRESTResponse.java:252)
com.glide.rest.outbound.ecc.ECCRESTResponse.extractHeaders(ECCRESTResponse.java:215)
com.glide.rest.outbound.ecc.ECCRESTResponse.processResponse(ECCRESTResponse.java:176)
com.glide.rest.outbound.ecc.ECCRESTResponse.fetchAndProcessEccResponse(ECCRESTResponse.java:246)
com.glide.rest.outbound.ecc.ECCRESTResponse.getBody(ECCRESTResponse.java:135)

Release

Applicable to all releases

Cause

Since the REST Message is via the MID server, a RESTProbe ecc_queue record is supposed to be created for the MID server to process this request. However, the creation of this record fails because the user has the snc_read_only role and doesn't have the permission for the 'create' operation on the ecc_queue table. 

Resolution

To be able to let users with snc_read_only execute RESTMessageV2 requests via the MID server, you need to create the following property:

Name: glide.security.snc_read_only_role.tables.exempt_create

Type: string

Value:

sys_user_session, sysevent, syslog, syslog_transaction, sys_user_preference, sys_ui_list, sys_ui_list_element, sys_db_cache, user_multifactor_auth, ecc_queue

This will allow the 'create' operation to be successful on the ecc_queue table even though the user has the snc_read_only role. 

Additional Information

Read-Only properties


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.