« Previous Next »

• 01-18-2009, 12:29 AM

  In reply to

  qbernard Joined on 03-25-2003, 10:12 PM Malaysia Posts 3,252	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact Tried all suggestions? what are those? what's the output of netstat -ano ? Cheers, Bernard Cheah

• 08-11-2009, 12:05 PM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7

  Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact After using some of the suggestions here I have found that process 0 is the process that is tied to port 443 which i am trying to free up so that my iis part of my exchange server can run.  This process is part of the system idle processes and I really don't want to kill that process.  Not sure how to move forward from here.

• 08-11-2009, 12:29 PM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 2,343	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact What do the following commands (from an elevated command prompt) say? %windir%\system32\inetsrv\appcmd.exe list sites netsh http show servicestate Anil Ruia Senior Software Design Engineer IIS Core Server

• 08-11-2009, 12:42 PM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7

  Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact First Command: SITE "Default Web Site" (id:1,bindings:net.tcp/808:*,net.pipe/*,net.msmq/localhost,msmq.formatname/localhost,https/*:443:,state:Stopped) SITE "Redirect Site" (id:2,bindings:http/*:80:,state:Stopped)  Second Command is a bit longer: Snapshot of HTTP service state (Server Session View): ----------------------------------------------------- Server session ID: FD00000320000001     Version: 1.0     State: Active     Properties:         Max bandwidth: 4294967295         Timeouts:             Entity body timeout (secs): 120             Drain entity body timeout (secs): 120             Request queue timeout (secs): 120             Idle connection timeout (secs): 120             Header wait timeout (secs): 120             Minimum send rate (bytes/sec): 150     URL groups:     URL group ID: FC00000340000001         State: Active         Request queue name: Request queue is unnamed.         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited Server session ID: FF00000220000003     Version: 2.0     State: Active     Properties:         Max bandwidth: 4294967295         Timeouts:             Entity body timeout (secs): 120             Drain entity body timeout (secs): 120             Request queue timeout (secs): 65535             Idle connection timeout (secs): 120             Header wait timeout (secs): 120             Minimum send rate (bytes/sec): 240     URL groups:     URL group ID: FE00000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: FD00000240000001         State: Active         Request queue name: MSExchangeServicesAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: FC00000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: 4294967295             Timeouts:                 Entity body timeout (secs): 120                 Drain entity body timeout (secs): 120                 Request queue timeout (secs): 65535                 Idle connection timeout (secs): 120                 Header wait timeout (secs): 0                 Minimum send rate (bytes/sec): 0             Logging information:                 Log directory: C:\inetpub\logs\LogFiles\W3SVC1                 Log format: 0     URL group ID: FB00000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: FA00000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited             Authentication Configuration:                 Authentication schemes enabled:                     NTLM                     Negotiate                 Authentication settings:                     Receive context handle     URL group ID: F900000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F800000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F700000240000001         State: Active         Request queue name: MSExchangeUMAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F600000240000001         State: Active         Request queue name: MSExchangeSyncAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F500000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F400000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F300000240000001         State: Active         Request queue name: MSExchangeAutodiscoverAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F200000240000001         State: Active         Request queue name: MSExchangeServicesAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F100000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: F000000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: EF00000240000001         State: Active         Request queue name: MSExchangeAutodiscoverAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: EE00000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: 4294967295             Timeouts:                 Entity body timeout (secs): 120                 Drain entity body timeout (secs): 120                 Request queue timeout (secs): 65535                 Idle connection timeout (secs): 120                 Header wait timeout (secs): 0                 Minimum send rate (bytes/sec): 0             Logging information:                 Log directory: C:\inetpub\logs\LogFiles\W3SVC2                 Log format: 0     URL group ID: ED00000240000001         State: Active         Request queue name: MSExchangeUMAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: EC00000240000001         State: Inactive         Request queue name: RemotingAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: EB00000240000001         State: Active         Request queue name: DefaultAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: EA00000240000001         State: Active         Request queue name: MSExchangeOWAAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited     URL group ID: E900000240000001         State: Active         Request queue name: MSExchangeAutodiscoverAppPool         Properties:             Max bandwidth: inherited             Max connections: inherited             Timeouts:                 Timeout values inherited Request queues:     Request queue name: MSExchangeAutodiscoverAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: MSExchangeOWAAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 1         Controller process ID: 4044         Process IDs:             4476     Request queue name: DefaultAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: RemotingAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: MSExchangeUMAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: MSExchangeServicesAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: MSExchangeSyncAppPool         Version: 2.0         State: Active         Request queue 503 verbosity level: Limited         Max requests: 1000         Number of active processes attached: 0         Controller process ID: 4044         Process IDs:     Request queue name: Request queue is unnamed.         Version: 1.0         State: Active         Request queue 503 verbosity level: Basic         Max requests: 1000         Number of active processes attached: 1         Process IDs:             1080

• 08-11-2009, 1:07 PM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact First command: SITE "Default Web Site" (id:1,bindings:net.tcp/808:*,net.pipe/*,net.msmq/localhost,msmq.formatname/localhost,https/*:443:,state:Stopped) SITE "Redirect Site" (id:2,bindings:http/*:80:,state:Started) Second Command:

• 08-11-2009, 1:28 PM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact The redirect site listed above works fine.  I can connect to that just fine but the first site does not.

• 08-14-2009, 2:38 PM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 2,343	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact What exactly is running in process-id 1080? Anil Ruia Senior Software Design Engineer IIS Core Server

• 08-14-2009, 5:06 PM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7

  Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact I apologize, usually I double and triple check the answers given by the experts but I guess this time I asked an extra question to soon.  With the tools provided in the previous posts I was able to come across a PCHelpware process that was grabbing control of port 443 before IIS.  Thanks for your reply anilr.  And rest of forum.

• 09-29-2009, 12:25 AM

  In reply to

  goody_buddy Joined on 09-29-2009, 4:24 AM Posts 1	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact Very helpful post. cheers! Guru

• 10-28-2009, 2:01 PM

  In reply to

  pavan0384 Joined on 10-28-2009, 5:58 PM Posts 1

  Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact  Can you people help me out in this one...  I can't see any thing on my IIS manager. There is no default website, just i want to know how to store websites in iis manger. And i am using the WINDOWS VISTA Home premium.  I enabled everything in iis manger, is located in windows feature.

• 10-28-2009, 8:42 PM

  In reply to

  qbernard Joined on 03-25-2003, 10:12 PM Malaysia Posts 3,252	Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact Any error msgs during turn on/off the IIS component? And when you fire up IIS Manager, you got nothing? no app pool, default website /etc. Cheers, Bernard Cheah

• 10-29-2009, 8:36 AM

  In reply to

  hedrinjt Joined on 08-11-2009, 3:54 PM Wisconsin Posts 7

  Re: IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) Reply Contact qbernard: Any error msgs during turn on/off the IIS component? And when you fire up IIS Manager, you got nothing? no app pool, default website /etc.  You may want to uninstall iis and reinstall it, doesn't sound like its default settings are correct.