• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1163
  • Last Modified:

Cannot Start Website IIS 7

I have a machine running Server 2008 / IIS 7.0. The machine is equipped with two separate NIC's with two distinct IP addresses (10.1.1.179 and 10.1.1.180). I have a WebMail client program running on 10.1.1.180 and it is bound only to that address. When I try and start a website from within IIS7, I get the "Process cannot access the file because it is being used by another process 0x80070020 error" I have checked and the IIS site is bound to the other IP address (10.1.1.179:80). When I run a NETSTAT -an it shows the WebMail site listening on 10.1.1.180:80 and nothing listening on the other address the IIS site is bound to (10.1.1.179:80). If I stop the WebMail client, the IIS site starts no problem... If I change the IIS port from 80 to 8080 it runs fine with the WebMail client.... How else can I find out what program or application has locked up 10.1.1.179:80 (the IIS NIC)?
0
ThePhreakshow
Asked:
ThePhreakshow
  • 4
  • 3
1 Solution
 
mvgeertruyenCommented:
Which webmail client? does it have it's own webserver? (tomcat, apache,...). If you stop IIS and start the webclient does it function?
0
 
ThePhreakshowAuthor Commented:
The mailserver is mDaemon. It has its own internal webserver. Stopping IIS will allow the webclient to run fine...
0
 
mvgeertruyenCommented:
Sounds normal to me that IIS won't start if the internal webserver of mDeamon is already using that port on that IP address - I might be missing sonething here however...
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ThePhreakshowAuthor Commented:
mDaemon is running on 10.1.1.180:80 and when it is running, NETSTAT shows listening on port 80 of that IP address... The website(s) that I have running on IIS7 are all bound to a different IP address, 10.1.1.179 and will not start....  I would suspect a bug somewhere in IIS7 that even though I have bound the website to that one specific IP address, it is still attempting to bind to all unassigned or some other address....
0
 
mvgeertruyenCommented:
You may need to configure the mDeamon website to listen on a specific IP address (only 180). I don't think it is IIS that is trying to bind to all addresses; I think it is the web server of mDeamon (but it should show up on your netstat on 10.1.1.197:80). Do you know which webserver mDeamon uses?
0
 
ThePhreakshowAuthor Commented:
I am not sure what webserver they are using, but yes I have made sure mDaemon is bound only to the other IP address (10.1.1.180:80) and when mDaemon webserver is running, it is shown in NETSTAT as listening on its specific port (10.1.1.180:80) and nothing is listening on the other 10.1.1.179 NIC.
0
 
ThePhreakshowAuthor Commented:
The theory here is correct, and yes I have the option to bind mDaemon to only one address... Either IIS or mDaemon is not doing what it is supposed to... I am going to wait until a version of mDaemon that FULLY supports IIS7 and Server 2008 is released and stable to make my final judgement.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now