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.
"Page not found" error thrown in IE11 when accessing a module where filter condition has Non-English characters (i.e. Japanese or German) - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • "Page not found" error thrown in IE11 when accessing a module where filter condition has Non-English characters (i.e. Japanese or German)
KB0716342

"Page not found" error thrown in IE11 when accessing a module where filter condition has Non-English characters (i.e. Japanese or German)


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

Description

If you have any modules where the filter conditions contain Japanese, German, French, or other non-English characters, then if you access these modules using IE11, the browser throws the "Page not Found error - 404".

 

Steps to Reproduce

 

  1. Login as administrator.
    2. Go to Modules > Create New:
    Name = JPL Incident
    Application = Incident
    Table = Incident
    Condition = Short Description contains ネットワーク
    3. Access the Instance using IE11.
    4. Click on the created module "JPL Incident".

    Observe the "Page not found error" and no incidents with short description containing ネットワーク get displayed.



Workaround

This problem is under review and targeted to be fixed in a future release. No workaround or back-porting patches are available for the current versions. You can Subscribe to this article to receive notifications when more information will become available.


Related Problem: PRB1313474

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.