Page 1 of 1

PID 5956 (apache itself) blocks my port. What now?

PostPosted: 23. June 2015 10:23
by Castor
As it happens taskmanager with tells me, that service with PID 5956 is Apache itself: httpd.exe in apache/bin folder.

Code: Select all
11:10:33  [Apache]  Problem detected!
11:10:33  [Apache]  Port 80 in use by "Unable to open process" with PID 5956!
11:10:33  [Apache]  Apache WILL NOT start without the configured ports free!
11:10:33  [Apache]  You need to uninstall/disable/reconfigure the blocking application
11:10:33  [Apache]  or reconfigure Apache and the Control Panel to listen on a different port
11:10:33  [Apache]  Problem detected!
11:10:33  [Apache]  Port 443 in use by "Unable to open process" with PID 5956!
11:10:33  [Apache]  Apache WILL NOT start without the configured ports free!
11:10:33  [Apache]  You need to uninstall/disable/reconfigure the blocking application
11:10:33  [Apache]  or reconfigure Apache and the Control Panel to listen on a different port

Re: PID 5956 (apache itself) blocks my port. What now?

PostPosted: 23. June 2015 14:45
by mark.mcdonald
Is apache installed and running as a service? Do you have 2 xampp control panels running?
Have you tried restarting your machine, going straight to localhost to see if it works.
If localhost doesn't work have you tried starting the proper control panel to start apache and see if it runs? Does it run?
Let us know when you have tried rebooting your computer and following above ideas.

Re: PID 5956 (apache itself) blocks my port. What now?

PostPosted: 23. June 2015 15:19
by Altrea
If the control panel is not started with elevated administrator rights it does not have the priviledge to check the path to the file the blocking process is started from.
So the control panel is unable to detect if it is a xampp process or not which is blocking the needed ports.