Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Cannot restart Website. The process cannot access the file because it is being used by another process Exception from HRESULT: 0x80070020

Cannot restart Website. The process cannot access the file because it is being used by another process Exception from HRESULT: 0x80070020

Created by Alexander Aguilar, last modified by Alexander Aguilar on Feb 08, 2017

Views: 3,039 Votes: 2 Revisions: 6

Overview

  • The following error message is received in the Web Console homepage:

There was an error retrieving data from SolarWinds Information Service
Error: A query to the SolarWinds Information Service failed.

Cannot restart Website. The process cannot access the file because it is being used by another process (Exception from HRESULT: 0x80070020)

 

  • The following error message is received at the end of your Configuration Wizard

Website configuration failed.

Can not start Website - The process cannot access the file  because is being used by another process. (Exception from HRESULTS:  0x80070020)

 

Environment

NPM ALL

 

Cause 

The process cannot access the file because it is being used by another process.

Resolution

  1. Run the following command from a command prompt to find the PID of the process which is using TCP port 80 and/or 443.
                   netstat -aon | find ":80"
                   netstat -aon | find ":443"
    You will see an output similar to the following. Remember the actual PID may vary from case to case.
                   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       3604
                   TCP    0.0.0.0:443           0.0.0.0:0              LISTENING       3320
  2. Using Task Manager, identify which process the above PID belongs and take appropriate action. End the process using the same port.

 

Last modified

Tags

Classifications

Public