When the ERR_CACHE_MISS error occurs, it displays a message “Confirm Form Resubmission” which means that the website you are visiting requires data resubmission. However, when the error keeps repeating, it can mean there are problems with the web browser because cache issues or incorrect configurations may trigger the resubmission problem.

Possible causes

  1. Browser cache corruption

  2. Incompatible browser settings

  3. Web browser extensions

  4. Browser version

  5. Issues with the network connection

What could be causing this type of problem?

The ERR_CACHE_MISS is a Google Chrome-specific error and can occur due to poor settings and configurations, the browser’s cache, inappropriate extensions, or something similar. As the error is tied to the browser more than the operating system, it can occur on all versions of Windows and macOS, as well as other platforms. The version of the browser being used should also be factored in.

In most cases, it is an isolated incident concerning an individual device that happens to be accessing Internet (or intranet) locations that have, for some reason, changed since the last visit. In this case, individual fixes can be applied as outlined below.

If this is a widespread incident, consider the following questions:

  • Has your browser been recently updated?

  • Has there been a change to the network resulting in a different route or path needed to be taken to the website’s destination?

  • Are the devices using a predefined proxy server to get to their destination?

  • Has the destination, usually a website, been altered or changed?

Read the suggestions below to find out how Nexthink can help solve these problems.

How to Scope this issue

The first step is to scope the issue to understand how serious or widespread the problem is.

Scoping with Applications

Using Applications Reliability dashboards, look at the various breakdowns and filter them to find correlations. For instance, specific errors could be present on:

Specific applications only

In this instance, try to understand what has changed concerning a particular web application.

Specific OS, browser version

Has the OS or browser version changed? Has the browser been updated recently? Using Nexthink, investigate the performance of various browser versions to understand if a specific version is experiencing the problem.

Specific hierarchy nodes

If an infrastructure component such as a network change, a proxy server, or something similar is causing the problem, then it is likely to be shown by a specific area in the hierarchy containing a high quantity of errors.

Specific key pages or URLs

Most likely, a change was made at the web app level. Contact the appropriate application support team and inform them of the problem.

Specific time frames only

Examine if it is a one-time event that must be investigated, or whether this is a recurring event where something on the network, e.g., corporate backup, may be altering the availability of the network.

Scoping with Nexthink Finder (classic)

If a proxy server is in question, then Nexthink Finder can help better understand if this is the root cause. Create an investigation targeted at the domain name of the application in question and note whether most of the device traffic is going through a particular proxy. It is also possible to make the proxy server the actual target of the investigation itself and then use it to show various analytics such as the number of failed requests or response times from the proxy. This approach will reveal any unexpected behaviors.

Possible Solutions

Fixing Employee Devices 

NOTICE: Consider the scoping procedures first, see the steps above.

Be aware of the scope of impact when running corrective actions using Nexthink. If you are dealing with a single device or just a few devices, the Remote Actions can be run in the background while providing help to the affected employees or they can even be performed silently.

Should the scoping reveal that the incident is widespread, the issue will require more attention. We recommend employing Engage Campaigns to ensure that affected employees will get a visual notification of any changes being performed through remote actions at scale because employees may not be aware of the Remote Action taking place.

Refresh the page

Refreshing the page can be a quick way to fix the problem because usually, the error is a temporary one. Press CTRL+F5, which works on most browsers, or refer to your documentation if needed.

Clear cache

If the cache hasn’t been cleared for a while, some of the files within it may be corrupt. Clearing the cache can help. Select the Basic data clearing option if the user does not want to lose saved passwords and other personalized data.

Use the remote actions to clear the browser cache on Edge or Chrome (‘Clear Edge / Chrome Settings’). Clearing of the cache can be carried out remotely to assist the user.

It may also help to clear the DNS cache on the client-side in case it is trying to retrieve the page from a site that has moved. Use the Clear DNS Cache Remote Action for this test.

Update browser to the latest version

  • Browser breakdown in the Applications reliability dashboard allows you to quickly check if the browser version is the root cause of the problem.

  • If it is a browser version issue, Chrome is updated regularly, so the latest version should always be installed at the earliest opportunity.

  • Nexthink can perform such actions with Remote Actions to install or uninstall an application as long as the source binaries for Chrome are supplied.

  • Additionally, if SCCM is in use at your organization and if you have a task sequence for removing and installing your browser, then the Start Application or Task Sequence Remote Action can be used.

Uninstalling the Toolbar and Spam/Adware Programs

Sometimes the error occurs after the installation of inferior, malware-oriented toolbars in the web browser. Removing them may fix the issue.

Manage plugins and reset settings

The library pack in Google Chrome can retrieve the installed plugins and control them using Google Chrome Policies. It can also be used to clear the settings and test whether the browser version is current or set to a particular version.

In addition, this pack contains Remote Actions to confirm the Compliance of Chrome plugins to a particular level or version, which can help pinpoint if a particular version of the plugin is causing the problem.

Confirm Network Settings 

Use the Remote action Get Network Configuration to confirm that the DNS settings on the devices are correct. If they are not, ensure the correct DNS settings are used (see the step above), either by renewing the DHCP lease (ipconfig /renew) if on a DHCP enabled network or by simply entering the correct DNS server settings into the IP configuration settings of the client, if they are managed locally.

Reset Google Chrome

Resetting Chrome to its default settings may help with the issue. This is done within the Advanced settings of the browser.

IMPORTANT: by resetting the web browser, all saved configurations, bookmarks, passwords, autofill forms and similar information will be lost.

This activity can be automated using the Google Chrome Remote Action for Clear Chrome Settings.

Last updated