HA1.5a xampp Problems - LUPMISManual

Search
Go to content

Main menu:

Annexes 1-10 > A1. LUPMIS setup

HA1.5a Additional Advice for xampp Installation

- Check again, that Skype does not use port 80. See Annex 1.5.

- - - - -


- If Apache doesn't start: You can see this in the XAMPP control panel, if you have the message “Apache started [Port 80]“, but Apache would not really start. This also originally showed itself as an error during install, stating “Ports 80 or 443 (SSL) already in use! Installing Apache xxx service failed”). The root cause was that Port 80 was being used by another process, which you have to stop.  

Action: To get a list of “listening” processes, you can run the following at the cmd line:

netstat -oan


The important line (most likely the first line) in the output being:

  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4

This tells you that PID 4 (Process Identifier 4) - or similar number - was hogging up port 80, which was not allowing Apache to use it.  If it is PID 4, it is most likely the “NT Kernel & System” System process: Check the following 3 approaches:

Approach 1: Under the services panel, find the service that has the description of “world wide web publishing service” and stop the service.  If you found this service, you can check to see if port 80 is still being used by running the netstat command quoted above.  

Approach 2: Again, under services, search for “SQL server reporting services”, and if you find the service, stop it. Check to see if port 80 is still being used by running the netstat command quoted above.

Approach 3: Again, under services, search for “Web Deployment Agent Service”(MsDepSvc). If you find the service, stop it. Check to see if port 80 is still being used by running the netstat command quoted above.  If that doesn’t work, it might not be the NT Kernel & System Process (The PID is usually 4 for this)

- - - - -


- If it is not PID 4, find out which process runs on port 80: Open the Task Manager (e.g. cmd > Taskmgr) > Processes > View > Select Columns... > Tick PID > OK > Processes > Sort PID: Line with current PID on port 80 should read httpd.exe ... Apache HTTP Server. If not, you know who causes the problem and have to quit the mentioned process.

If not possible, go again to Services (as earlier) and look for 'Internet information service' in the beginning of services list. If listed, stop it.

- - - - -


- If you receive an error message like: 'Xampp Component Status Check failure [3]: Current directory: d:/xampp. Run this program only from your Xampp root directory.' or similar, a bug in Xampp has to be solved in the registry.

Action: Be sure that you installed it from C:then enter the registry: cmd > regedit and change the [HKEY_LOCAL_MACHINENode] -> Install_Dir registry setting from D:to C:

- - - - -


- Again check with Skype: The PID could be any variety of numbers if Skype is the issue. I would suggest that you disable Skype from starting when windows starts (in Skype: Tools > Options > General settings). You can kick Skype off of port 80 simply by “Quitting” the application.  Skype will still work and simply pick another port the next time you start it.  

- - - - -


- If this is still not working, look in Apache's error.log and Windows' system log files. One of them will contain a detailed message about what went wrong.

- - - - -


- A last (!!) option would be to change the port number of Apache: Make sure Apache is off, then go to the Apache installation directory (C:) to the conf folder, find httpd.conf and open it with Notepad or another editor. Find the line Listen 80 (around line 47) and change 80 to your desired port (often 8080, 8000 or 81 is used). Then, find ServerName localhost:80 and again, replace 80 with your desired port (must be the same as the one used before). Save and start Apache.











 
Back to content | Back to main menu