Can Windows Server 2003 run Apache web server and MS IIS at the same time?
Can Windows Server 2003 run Apache web server and MS IIS at the same time?
W2K-3 DC Server (abc2003) running Apache web server 2.0.50 (I think Apache was installed as part of WEBSENSE Internet content filtering software that also runs on this box)?
2 weeks ago I installed Windows Server Update Services (WSUS v3 Beta) on this same server but everyday abc2003's App Event Log has message "SELF UPDATE NOT WORKING" and network clients are not being updated (although WSUS has detected 77 of 83 computers on our network).
Per MS TechNet I check to make sure IIS is providing default web site access via port 80 to the SELFUPDATE virtual directory and see that the IIS Default Web site is (STOPPED) and attempts to start it yield the Error Message:
"THE PROCESS CANNOT ACCESS THE FILE BECAUSE IT IS BEING USED BY ANOTHER PROCESS."
Also when I enter the W2K-3 Server's default URL (http://abc2003:80) in my web browser it opens the default APACHE WEB SERVER page.
Am I possibly experiencing a limitation of the Windows 2003 Server's inability to run Apache & IIS web servers at the same time?
W2K-3 DC Server (abc2003) running Apache web server 2.0.50 (I think Apache was installed as part of WEBSENSE Internet content filtering software that also runs on this box)?
2 weeks ago I installed Windows Server Update Services (WSUS v3 Beta) on this same server but everyday abc2003's App Event Log has message "SELF UPDATE NOT WORKING" and network clients are not being updated (although WSUS has detected 77 of 83 computers on our network).
Per MS TechNet I check to make sure IIS is providing default web site access via port 80 to the SELFUPDATE virtual directory and see that the IIS Default Web site is (STOPPED) and attempts to start it yield the Error Message:
"THE PROCESS CANNOT ACCESS THE FILE BECAUSE IT IS BEING USED BY ANOTHER PROCESS."
Also when I enter the W2K-3 Server's default URL (http://abc2003:80) in my web browser it opens the default APACHE WEB SERVER page.
Am I possibly experiencing a limitation of the Windows 2003 Server's inability to run Apache & IIS web servers at the same time?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, they should be able to co-exist.
Try this:
Stop the Apache server and see if you can access the IIS based site.
Then do the opposite, stop IIS and hit the apache site.
What site are you wanting to host on that server? WSUS, or whatever Apache is serving?
Try this:
Stop the Apache server and see if you can access the IIS based site.
Then do the opposite, stop IIS and hit the apache site.
What site are you wanting to host on that server? WSUS, or whatever Apache is serving?
ASKER
WSUS is IIS dependent. Per Microsoft, your WSUS server must have the default web site running on Port 80 via IIS in order to make the SELFUPDATE virtual directory available to WSUS clients.
WEBSENSE needs Apache to work. (I think. I will double chek with Websense Tech Support on this).
I need both WSUS and WEBSENSE to run on this server since it is the only one at this site so, that is why I am asking if it is possible to have 2 different (software) web servers running on the same (hardware) server.
Should I try to get the WEBSENSE service to listen on a different port than 80?
WEBSENSE needs Apache to work. (I think. I will double chek with Websense Tech Support on this).
I need both WSUS and WEBSENSE to run on this server since it is the only one at this site so, that is why I am asking if it is possible to have 2 different (software) web servers running on the same (hardware) server.
Should I try to get the WEBSENSE service to listen on a different port than 80?
Yes, you could try to get Websense on a different port. Check with the vendor to be sure.
Is Websense acting as the proxy for the site?
Is Websense acting as the proxy for the site?
ASKER
I think the problem is resolved.
Websense Tech Support had me remove the 3 Websense application components dependent on web services and then un-install Apache Web Server.
Next we re-installed the 3 Websense application components dependent on web services but allowed them to default to IIS during setup & post install config selections.
Bottom line is YES, IIS & Apache were in conflict but the recommended resolution (which appears to have worked successfully after testing both WSUS & WEBSENSE) was to reconfigure WEBSENSE to use IIS [along with WSUS] (& ditch the Apache install alltogether).
Now I only have one web server (IIS) running on my W2K3 Server box but both applications are working normally.
Thanks trarthur for your help!
Websense Tech Support had me remove the 3 Websense application components dependent on web services and then un-install Apache Web Server.
Next we re-installed the 3 Websense application components dependent on web services but allowed them to default to IIS during setup & post install config selections.
Bottom line is YES, IIS & Apache were in conflict but the recommended resolution (which appears to have worked successfully after testing both WSUS & WEBSENSE) was to reconfigure WEBSENSE to use IIS [along with WSUS] (& ditch the Apache install alltogether).
Now I only have one web server (IIS) running on my W2K3 Server box but both applications are working normally.
Thanks trarthur for your help!
ASKER