XAMPP 1.8.3-4 on Windows Server 2008 R2

[mbsarino]

I have installed XAMPP 1.8.3-4 on Windows 2008 R2. When I started Apache on the control panel, I got the following message:

11:24:23 PM [main] Initializing Control Panel
11:24:23 PM [main] Windows Version: Windows Server 2008 R2 SP1 64-bit
11:24:23 PM [main] XAMPP Version: 1.8.3
11:24:23 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
11:24:23 PM [main] Running with Administrator rights - good!
11:24:23 PM [main] XAMPP Installation Directory: "c:\xampp2\"
11:24:23 PM [main] Checking for prerequisites
11:24:24 PM [main] All prerequisites found
11:24:24 PM [main] Initializing Modules
11:24:24 PM [Apache] Problem detected!
11:24:24 PM [Apache] Port 80 in use by "Unable to open process" with PID 4!
11:24:24 PM [Apache] Apache WILL NOT start without the configured ports free!
11:24:24 PM [Apache] You need to uninstall/disable/reconfigure the blocking application
11:24:24 PM [Apache] or reconfigure Apache and the Control Panel to listen on a different port
11:24:24 PM [Apache] Problem detected!
11:24:24 PM [Apache] Port 443 in use by "Unable to open process" with PID 4!
11:24:24 PM [Apache] Apache WILL NOT start without the configured ports free!
11:24:24 PM [Apache] You need to uninstall/disable/reconfigure the blocking application
11:24:24 PM [Apache] or reconfigure Apache and the Control Panel to listen on a different port
11:24:24 PM [main] The MySQL module is disabled
11:24:24 PM [main] The FileZilla module is disabled
11:24:24 PM [main] The Mercury module is disabled
11:24:24 PM [Tomcat] Java is already running on port 8080!
11:24:24 PM [Tomcat] Is Tomcat already running?
11:24:24 PM [main] Starting Check-Timer
11:24:24 PM [main] Control Panel Ready

After running netstat, I found that both ports 80 and 443 that XAMPP needs is used by the Windows system and therefore probably not safe to "end process". What do I need to do to get Apache running on my server?

[Nobbie]

What do I need to do to get Apache running on my server?

Stopp the Microsoft IIS, that is the Webserver from Microsoft and this is running on your PC and blocking Apache. WIndows Server Versions have their own Webservers instead of Apache.

[ocdondev]

Why reconfiguring IIS your server. ( stopping is a temp work around, you would then need to assign other ports..)

I would opt to change the ports for apache (via the control panel and then adjust the httpd.conf and the httpd-ssl.conf)

for http use (i.e.) 81 , for SSL use (i.e.) 2334 This is arbitrary as long as the ports are available:

use telnet to check the ports on localhost (or actual server name or its IP-address )whether they are available or not (from a shell: telnet <servername> <port> should not give a connection, if it does then there is a service running on that port)

[pjbeee]

Click the config button on the xampp control panel as suggested above or edit those 2 files. Then stop and restart Apache - change the ports to anything you want except 80 and 443.

[mbsarino]

Thanks everyone! I finally got it running!

[Nobbie]

Why reconfiguring IIS your server. ( stopping is a temp work around, you would then need to assign other ports..)

I would opt to change the ports for apache (via the control panel and then adjust the httpd.conf and the httpd-ssl.conf)

for http use (i.e.) 81 , for SSL use (i.e.) 2334

This is the worst solution of all, as you have to pass the portnumber in each URL from now on (http://localhost:81/xampp for example or https://localhost:2334). This is not only ugly and annoying, some (also bad programmed scripts) do not even consider the option of having a portnumber in the URL and they simply dont work correctly.

It is simply a bad idea to run IIS and Apache both.

[mbsarino]

I have disabled IIS and am still running Apache

[ocdondev]

Why reconfiguring IIS your server. ( stopping is a temp work around, you would then need to assign other ports..)

I would opt to change the ports for apache (via the control panel and then adjust the httpd.conf and the httpd-ssl.conf)

for http use (i.e.) 81 , for SSL use (i.e.) 2334

This is the worst solution of all, as you have to pass the portnumber in each URL from now on (http://localhost:81/xampp for example or https://localhost:2334). This is not only ugly and annoying, some (also bad programmed scripts) do not even consider the option of having a portnumber in the URL and they simply dont work correctly.

It is simply a bad idea to run IIS and Apache both.

context matters: i read from the question that the OP has little to no knowledge of TCP IP .. that is the real issue.( everyone can stop a service and start another..)
i just opt ' as it is a development environment or sandbox' that the OP should have a play with options. A Production instance is a different story.
as for issues with scripts: XAMPP has quite some flaws ootb (in the php files), so i fix them instead of skipping a challenge due to deprecated or arbitrary code.. the latter should not be accepted but resolved..

and for yourself: work on your communication skills. whatever message you tried to deliver failed as you ruled out a subjective opinion and instead jump to an absolute statement which is incomplete and hard to interpret if one does not understand the subject matter
ta

[pjbeee]

Hey. Some of us may have good reasons for running IIS and Apache at the same time, and for whatever reason, don't mind port redirects, don't find them annoying, and have no operational problems with their chosen implementation. Just sayin'. One size doesn't necessarily fit all.

"Aren't standards wonderful? There are so many from which to choose."