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" or "An error occurred communicating with the server" when using Perceptive Experience in Google Chrome web browser.

[Doc 8386 content is unavailable at this time.]

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, locate the instructions for your browser and operating system here Clearing Browser Cache and Cookies AND beware you will lose cookies currently stored by Chrome.

If it does not appear to address the issue, please verify that you cleared cache and cookies "For all time."


Keywords:
imagenow image now perceptive content enterprise management service ECM ECMS document digital experience google chrome resource not found wiser wisdm bad request An error occurred communicating with the server 
Doc ID:
85101
Owned by:
Craig S. in ECMS
Created:
2018-08-22
Updated:
2024-12-13
Sites:
DoIT Help Desk, ECMS