ECMS - Perceptive Experience error "The requested resource was not found" or "Bad Request" in Google Chrome

This document provides steps to trouble-shoot the error "The requested resource was not found" or "Bad Request" when using Perceptive Experience in Google Chrome web browser.

If a user receives an error message "The requested resource was not found" or "Bad Request" when trying to access a document in the Imaging system via the Chrome web browser, or or is unable to access previously accessible documents, the solution is often to clear Chrome’s cache. First, verify the issue is with Chrome by confirming that you can access the document in another web browser (e.g., FireFox, Edge, etc...).

To clear the cache in Chrome, please perform the following steps BUT beware you will lose cookies currently stored by Chrome:

  1. On your computer, open Chrome.
  2. At the top right, click the row of three vertical dots (also known as “More”).
  3. Click More tools Clear browsing data.
  4. At the top, choose a time range. To delete everything, select All time.
  5. Next to "Cookies and other site data" and "Cached images and files," check the boxes.
  6. Click Clear data.
  7. Exit Chrome, then try accessing the resource again. If the same error is received try clearing all the values in the browsing data.




Keywords:imagenow image now perceptive content enterprise management service ECM ECMS document digital experience google chrome resource not found wisdm bad request   Doc ID:85101
Owner:Craig S.Group:ECMS
Created:2018-08-22 08:19 CSTUpdated:2022-10-24 15:21 CST
Sites:DoIT Help Desk, ECMS
Feedback:  0   0