I also installed SQL Server 2008 Standard R2
Sharley wrote:There was no need to change ports and may I suggest you return the httpd.conf file back to it's default settings.
Are there any clues in the \xampp\apache\logs\error.log file?
What are you typing in your browser?
I assume that Apache and MySQL are both running?
Exit the older 2.5 Control Panel and use the new xampp-control-3-beta.exe found in the xampp folder, it has better error reporting and creates a log file also in the xampp folder.
The log file still has Apache listening on port 8080 - did you restart Apache after editing the conf file back to port 80?Synthologic wrote:I changed the ports back to 80.
Sharley wrote:The log file still has Apache listening on port 8080 - did you restart Apache after editing the conf file back to port 80?Synthologic wrote:I changed the ports back to 80.
The log file has no record of a file not found 404 error which it should have.
Where exactly did you store your php files on the server...
...and what are you now typing in your browser when you get the 404 error?
What did the log file of the new CP3 contain when you tried to start Apache and MySQL?
Sharley wrote:The 'system' using port 80 can be one of 2 things - as suggested earlier the installation of the SQL server has an agent using port 80 and so if possible temporarily disable this or have the SQL server agent listen on a different port than port 80 (Microsoft seems to prefer that you use their $$$ products rather than a free Apache server and so seems to like hogging port 80 when ever it can)
The other could be that you are have installed the service module for Apache and MySQL (a green tick in the CP3 service module column).
If possible try and remove the ticks and answer the question when asked.
If it is not possible to remove the ticks then in CP3 there is a Win-service button and when pressed will go to the Service Controller where you can Start or Stop Apache2.2 then when you return to the CP3 you may be able to start Apache.
Also in the Service Controller you may be able to find the SQL server entry listed and perhaps be able to disable it for now.
There is a conflict with port 80 and if possible it is best to disable what ever is using the web server default port 80 as if you change the Listen port then this can lead to possible issues down the track.
Without a 404 log file entry it will be hard to solve your 404 issue but after we get Apache using port 80 then it may be that there will be a log file entry.
Sharley wrote:The 404 error when you had the Listen port on 8080 may have been caused by not appending the port number to the address like so:
A good reason to have Apache listen on port 80 if possible as you can see now that this 8080 port number has to be appended to every URL that you use and could be a real issue in future.
Users browsing this forum: Altrea and 55 guests