Windows could not start apache error code 1

During the installation of Apache2 I got the following message into cmd window: Installing the Apache2.2 service The Apache2.2 service is successfully installed. Testing httpd.conf.... ...

There is some other program listening on port 80, usual suspects are

  1. Skype (Listens on port 80)
  2. NOD32 (Add Apache to the IMON exceptions’ list for it to allow apache to bind)
  3. Some other antivirus (Same as above)

Way to correct it is either shutting down the program that’s using the port 80 or configure it to use a different port or configure Apache to listen on a different port with the Listen directive in httpd.conf. In the case of antivirus configure the antivirus to allow Apache to bind on the port you have chosen.

Way to diagnose which app, if any, has bound to port 80 is run the netstat with those options, look for :80 next to the local IP address (second column) and find the PID (last column). Then, on the task manager you can find which process has the PID you got in the previous step. (You might need to add the PID column on the task manager)

C:Usersvinko>netstat -ao -p tcp

Conexiones activas

  Proto  Dirección local          Dirección remota        Estado           PID
  TCP    127.0.0.1:1110         127.0.0.1:51373        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51379        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51381        ESTABLISHED     388
  TCP    127.0.0.1:1110         127.0.0.1:51382        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51479        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51481        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51483        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51485        ESTABLISHED     388
  TCP    127.0.0.1:1110         127.0.0.1:51487        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51489        ESTABLISHED     388
  TCP    127.0.0.1:51381        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:51485        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:51489        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:59264        127.0.0.1:59265        ESTABLISHED     5168
  TCP    127.0.0.1:59265        127.0.0.1:59264        ESTABLISHED     5168
  TCP    127.0.0.1:59268        127.0.0.1:59269        ESTABLISHED     5168
  TCP    127.0.0.1:59269        127.0.0.1:59268        ESTABLISHED     5168
  TCP    192.168.1.34:51278     192.168.1.33:445       ESTABLISHED     4
  TCP    192.168.1.34:51383     67.199.15.132:80       ESTABLISHED     388
  TCP    192.168.1.34:51486     66.102.9.18:80         ESTABLISHED     388
  TCP    192.168.1.34:51490     74.125.4.20:80         ESTABLISHED     388

If you want to Disable Skype from listening on port 80 and 443, you can follow the link http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/

I installed Apache on Windows 7 (localhost) and it worked fine. Then I went to download some other stuff and later noticed that the Apache server stopped. I went to command prompt (as administrator) and typed

net start apache2

It says «The Apache2 service is starting.» But before it finishes, I get the error

A service specific error occurred: 1.

It says that you can type in «NET HELPMSG 3547» for more info, but that doesn’t help at all.

Things I have tried:

  1. Quit Google Drive Sync
  2. Quit any and all programs using port 80 (port my server is on)
  3. Tried changing the port of the server and got same error message, so I don’t think it has anything to do with something else being in the port

None of those things have worked. I am confused at why it worked earlier, but now it won’t work.

random's user avatar

random

14.4k9 gold badges53 silver badges58 bronze badges

asked Jun 10, 2014 at 21:48

user2297366's user avatar

2

You should check the Event Viewer for whatever shows up in the Windows Logs. Under the Application section there should be a list of errors with more details about what was exactly going wrong.

Recent example found:

The Apache service named reported the following error:
>>> Syntax error on line 523 of C:/Program Files/Apache Software Foundation/Apache2.2/conf/httpd.conf:

In the above example it was because a referenced drive was no longer on the system and Apache could not find it.

You can usually (at least in Windows Vista) find Event Viewer along the lines of:

Control Panel → Administrative Tools → Event Viewer

This should highlight any thing touching the system that you may have overlooked and provide further details and hints about what to tweak or change instead of just uninstalling everything.

answered Dec 19, 2015 at 18:06

random's user avatar

randomrandom

14.4k9 gold badges53 silver badges58 bronze badges

2

Apache server wouldn’t start after I downloaded coldfusion and added it to the server. I just uninstalled apache and coldfusion and reinstalled apache and it works fine now. The official error was that I added an extension(coldfusion) to apache and for some reason apache didn’t recognize it.

answered Jun 12, 2014 at 18:39

user2297366's user avatar

user2297366user2297366

1793 gold badges4 silver badges9 bronze badges

1

Цитата
Сообщение от svsw
Посмотреть сообщение

lawliet93, посмотрите что пишется в error.log и в виндовый журнал

да я смотрел, но это не помогло
вот error.log

Кликните здесь для просмотра всего текста

Starting the Apache2.2 service
The Apache2.2 service is running.
rmine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
[Mon Mar 18 14:26:16 2013] [notice] Apache/2.2.22 (Win32) configured — resuming normal operations
[Mon Mar 18 14:26:16 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 14:26:16 2013] [notice] Parent: Created child process 3576
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Child process is running
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Acquired the start mutex.
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Starting 64 worker threads.
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Starting thread to listen on port 80.
[Mon Mar 18 14:26:27 2013] [error] [client 127.0.0.1] File does not exist: C:/server/apache/htdocs/favicon.ico
[Mon Mar 18 15:40:20 2013] [warn] pid file C:/server/apache/logs/httpd.pid overwritten — Unclean shutdown of previous Apache run?
[Mon Mar 18 15:40:20 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 18 15:40:20 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 15:40:20 2013] [notice] Parent: Created child process 1892
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Child process is running
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Acquired the start mutex.
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Starting 64 worker threads.
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Starting thread to listen on port 80.
[Mon Mar 18 15:43:36 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 15:44:41 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 22:24:05 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 22:31:29 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Mon Mar 18 22:31:29 2013] [notice] Child 1892: Exit event signaled. Child process is ending.
[Mon Mar 18 22:31:30 2013] [notice] Child 1892: Released the start mutex
[Mon Mar 18 22:31:31 2013] [notice] Child 1892: All worker threads have exited.
[Mon Mar 18 22:31:36 2013] [notice] Child 1892: Child process is exiting
[Mon Mar 18 22:31:36 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
[Mon Mar 18 22:35:13 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 18 22:35:13 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 22:35:13 2013] [notice] Parent: Created child process 2700
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Child process is running
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Acquired the start mutex.
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Starting 64 worker threads.
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Starting thread to listen on port 80.
[Mon Mar 18 23:08:34 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/Client
[Mon Mar 18 23:09:03 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/Client
[Mon Mar 18 23:09:06 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Mon Mar 18 23:09:06 2013] [notice] Child 2700: Exit event signaled. Child process is ending.
[Mon Mar 18 23:09:07 2013] [notice] Child 2700: Released the start mutex
[Mon Mar 18 23:09:11 2013] [notice] Child 2700: All worker threads have exited.
[Mon Mar 18 23:09:11 2013] [notice] Child 2700: Child process is exiting
[Mon Mar 18 23:09:11 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
[Tue Mar 19 13:45:22 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Tue Mar 19 13:45:22 2013] [notice] Server built: Jan 28 2012 11:16:39
[Tue Mar 19 13:45:22 2013] [notice] Parent: Created child process 3616
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Child process is running
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Acquired the start mutex.
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Starting 64 worker threads.
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Starting thread to listen on port 80.
[Tue Mar 19 13:53:09 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Tue Mar 19 13:53:09 2013] [notice] Child 3616: Exit event signaled. Child process is ending.
[Tue Mar 19 13:53:10 2013] [notice] Child 3616: Released the start mutex
[Tue Mar 19 13:53:11 2013] [notice] Child 3616: All worker threads have exited.
[Tue Mar 19 13:53:16 2013] [notice] Child 3616: Child process is exiting
[Tue Mar 19 13:53:16 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
[Wed Mar 20 12:21:09 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Wed Mar 20 12:21:09 2013] [notice] Server built: Jan 28 2012 11:16:39
[Wed Mar 20 12:21:09 2013] [notice] Parent: Created child process 4452
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Child process is running
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Acquired the start mutex.
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Starting 64 worker threads.
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Starting thread to listen on port 80.
[Wed Mar 20 13:31:14 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Wed Mar 20 13:37:36 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Wed Mar 20 13:37:36 2013] [notice] Child 4452: Exit event signaled. Child process is ending.
[Wed Mar 20 13:37:37 2013] [notice] Child 4452: Released the start mutex
[Wed Mar 20 13:37:38 2013] [notice] Child 4452: All worker threads have exited.
[Wed Mar 20 13:37:43 2013] [notice] Child 4452: Child process is exiting
[Wed Mar 20 13:37:43 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
[Wed Mar 20 16:33:48 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Wed Mar 20 16:33:48 2013] [notice] Server built: Jan 28 2012 11:16:39
[Wed Mar 20 16:33:48 2013] [notice] Parent: Created child process 4164
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Child process is running
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Acquired the start mutex.
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Starting 64 worker threads.
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Starting thread to listen on port 80.
[Wed Mar 20 17:09:07 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Wed Mar 20 17:09:07 2013] [notice] Child 4164: Exit event signaled. Child process is ending.
[Wed Mar 20 17:09:08 2013] [notice] Child 4164: Released the start mutex
[Wed Mar 20 17:09:16 2013] [notice] Child 4164: All worker threads have exited.
[Wed Mar 20 17:09:21 2013] [notice] Child 4164: Child process is exiting
[Wed Mar 20 17:09:21 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
[Mon Mar 25 16:25:57 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 25 16:25:57 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 25 16:25:57 2013] [notice] Parent: Created child process 5052
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Child process is running
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Acquired the start mutex.
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Starting 64 worker threads.
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Starting thread to listen on port 80.

а вот что в журнале виндовса

Кликните здесь для просмотра всего текста

The Apache service named reported the following error:
>>> (OS 10013)Сделана попытка доступа к сокету методом, запрещенным правами доступа. : make_sock: could not bind to address 0.0.0.0:80 .
The Apache service named reported the following error:
>>> no listening sockets available, shutting down .
The Apache service named reported the following error:
>>> Unable to open logs .
Служба «Apache2.2» завершена из-за внутренней ошибки Неверная функция..

Perform the steps below to resolve this issue.

To refresh the Webtrends Apache HTTP configuration:
1. Ensure the Webtrends — MySQL (or MS SQL system database) and the Webtrends — User interface service are running. If the User interface has not started, you will be unable to proceed until they do.

2. Open the following file in a text editor:

Webtrendscommonapacheconfhttpd.conf

3. Find the line that reads similar to the following:

#Listen 12.34.56.78:80.

4. On the line below, paste the following:

Listen 7099

5. Find the a line similar to «ServerName pdxfasteenn02:» (pdxfasteenn02 should be the name of the Webtrends server).

6. Replace it with the following:

ServerName pdxfasteenn02:7099

Ensure both the Listen line and the ServerName line do not contain a ‘#’.

7. Save the httpd.conf file.

8. Open a command prompt and navigate to the following folder:

Webtrendscommonapachebin

9. Type the following, and then press enter:

apache.exe

The command window may appear as if it has hung or locked up but this is the expected behavior.

10. Open the Windows Services snap-in and verify that Apache is started.

11. If necessary, start the Tomcat service.

Do not stop and then start Webtrends — User interface service. If you do, it will overwrite the changes made to the httpd.conf file with faulty data.

12. Log into Webtrends and click Administration > System Management > Hosts > UI Server.

13. If the box for «Enable HTTP» is not checked, check it. If it is checked, uncheck and then recheck it, also check or uncheck the box for Enable Tomcat logging (making this change will force a write to the configuration file; you can go back and undo the Tomcat logging change later).

14. In the «Apache Port» box, type 7099, and then click Save.

15. If you are prompted to restart the Webtrends services, click Restart Services.

The Apache service should now start normally. If you made a change to the Tomcat logging settings in step 13, go back and undo that change now.

Windows could not start the Apache Tomcat 8 on Local Computer. Error code 1

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER

CA Service Desk Manager — Unified Self Service

CA Service Desk Manager

CA Service Management — Asset Portfolio Management

CA Service Management — Service Desk Manager

Issue/Introduction

Unable to start Tomcat service for JasperSoft and receive the following popup error message:

<Please see attached file for image>

When checking Apache Tomcat logs (Apache Software FoundationTomcat 8.0logs), the following error is seen:

[info]  [ 3388] Running ‘Tomcat8’ Service…
[info]  [ 3712] Starting service…
[error] [ 3712] Failed creating java C:Program FilesJavajre1.8.0_112binserverjvm.dll
[error] [ 3712] The system cannot find the path specified.
[error] [ 3712] ServiceStart returned 1
[error] [ 3712] The system cannot find the path specified.
[info]  [ 3388] Run service finished.

Environment

Service Desk Manager 14.1 or 17.0
JasperSoft 6.2 or 6.3
Apache Tomcat 8.x
All Supported Windows Operating Systems

Cause

Main causes for the error are:

1.  Apache Tomcat cannot find the JVM.DLL file in the specific location because it does not exist

2.  Incorrect read and write permissions for the JAVA install folder or JVM.DLL file

3.  Incorrect JAVA_HOME path specified in the Apache Tomcat configuration

Resolution

1.  Confirm that the JVM.DLL file does indeed exist in the specified directory (i.e. C:Program FilesJavajre1.8.0_112binserver)

2.  Make sure that the JVM.DLL file has read and write permissions

3.  Confirm that the Apache Tomcat JAVA_HOME configuration is correct

The following instructions apply if Tomcat is installed as a Service:

  • Locate the Java install path folder on the JasperSoft server
  • Run Tomcat8w.exe to launch the Tomcat Service Manager Program and access the «Java» tab
  • Update the Java Virtual Machine path to the current JRE installation folder (i.e. C:Program FilesJavajre1.8.0_73binserverjvm.dll
  • Restart Apache Tomcat service

If Tomcat is not installed as a Service, or Tomcat8w.exe is non-existent, one will need to modify the JAVA_HOME and JRE_HOME environment variables directly.

If only the JAVA_HOME environment variable is set, Tomcat will run under the JRE as part of the JDK specified by the JAVA_HOME variable. Therefore, we change JRE for Tomcat by updating this variable.

JAVA_HOME=C:Program FilesJavajre7

If both the JAVA_HOME and JRE_HOME environment variables are set, the JRE_HOME is preferred. Here’s an example of a valid value for the JRE_HOME variable (path on Windows):

JRE_HOME=C:Program FilesJavajre7

Attachments

1558690755229000006805_sktwi1f5rjvs16gdv.jpeg

get_app

1558617951265000006805_sktwi9tkjvsehwqw.jpeg

get_app

Feedback

thumb_up
Yes

thumb_down
No

  •  
  • windows

  • windows-xp

  • apache2

  •  10-07-2019
  •  | 

  •  

Question

During the installation of Apache2 I got the following message into cmd window:

Installing the Apache2.2 service The
Apache2.2 service is successfully
installed. Testing httpd.conf….

Errors reported here must be corrected
before the service can be started.
httpd.exe: Could not reliably
determine the server’s fully qualified
domain name , using 192.168.1.3 for
ServerName (OS 10048)Only one usage of
each socket address (protocol/network
address/port) is normally permitted.
: make_sock: could not bind to address
0.0.0.0:80 no listening sockets available, shutting down Unable to
open logs Note the errors or messages
above, and press the key to
exit. 24…

and after installing everything look fine, but it isn’t. If I try to start service I got the following message:

Windows could not start the Apache2 on
Local Computer. For more information,
review the System Event Log. If this
is a non-Micorsoft service, contact
the service vendor, and refer to
service-specific error code 1.

Apach2 version is 2.2.9

Does anyone have the same problem, or could help me.

Solution

There is some other program listening on port 80, usual suspects are

  1. Skype (Listens on port 80)
  2. NOD32 (Add Apache to the IMON exceptions’ list for it to allow apache to bind)
  3. Some other antivirus (Same as above)

Way to correct it is either shutting down the program that’s using the port 80 or configure it to use a different port or configure Apache to listen on a different port with the Listen directive in httpd.conf. In the case of antivirus configure the antivirus to allow Apache to bind on the port you have chosen.

Way to diagnose which app, if any, has bound to port 80 is run the netstat with those options, look for :80 next to the local IP address (second column) and find the PID (last column). Then, on the task manager you can find which process has the PID you got in the previous step. (You might need to add the PID column on the task manager)

C:Usersvinko>netstat -ao -p tcp

Conexiones activas

  Proto  Dirección local          Dirección remota        Estado           PID
  TCP    127.0.0.1:1110         127.0.0.1:51373        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51379        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51381        ESTABLISHED     388
  TCP    127.0.0.1:1110         127.0.0.1:51382        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51479        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51481        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51483        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51485        ESTABLISHED     388
  TCP    127.0.0.1:1110         127.0.0.1:51487        TIME_WAIT       0
  TCP    127.0.0.1:1110         127.0.0.1:51489        ESTABLISHED     388
  TCP    127.0.0.1:51381        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:51485        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:51489        127.0.0.1:1110         ESTABLISHED     5168
  TCP    127.0.0.1:59264        127.0.0.1:59265        ESTABLISHED     5168
  TCP    127.0.0.1:59265        127.0.0.1:59264        ESTABLISHED     5168
  TCP    127.0.0.1:59268        127.0.0.1:59269        ESTABLISHED     5168
  TCP    127.0.0.1:59269        127.0.0.1:59268        ESTABLISHED     5168
  TCP    192.168.1.34:51278     192.168.1.33:445       ESTABLISHED     4
  TCP    192.168.1.34:51383     67.199.15.132:80       ESTABLISHED     388
  TCP    192.168.1.34:51486     66.102.9.18:80         ESTABLISHED     388
  TCP    192.168.1.34:51490     74.125.4.20:80         ESTABLISHED     388

If you want to Disable Skype from listening on port 80 and 443, you can follow the link http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/

OTHER TIPS

I hope this helps others with this error.

Run the httpd.exe from the command line to get an accurate description of the problem.

I had the same error message and it turned out to be a miss configured ServerRoot path. Even after running setup_xampp.bat the httpd.conf had the wrong path.

My error.log was empty and starting the service does not give an informative error message.

the better way to resolve the issue is change the port number in Apache2confhttpd.conf . Change the port number as fallows::: Listen 8888 and ServerName machinename:8888 .Restart the Apache server after changing the port number.

I had the same problem. I checked netstat, other processes running, firewall and changed httpd.conf, stopped antivirus, But all my efforts were in vain. :(

So finally the solution was to stop the IIS. And it worked :)

I guess IIS and apache cant work together. If anybody know any work around let us know.

Run the httpd.exe from the command line, as Tim mentioned. The path to PostgreSQL changed, nothing else was running on Port 80 and I didn’t see anything in the error.log file.

I clone my boot drive/partition once the base is setup so I don’t have to spend three days installing and retweaking everything. Turns I had reinstalled my WAPP stack and used very specific names/versions for PostgreSQL. Windows will not return a specific error message unless you run the command from the command line.

Follow this step it will works fine.
Go to Control panel—>Programs and features—>click Turn Windows features on and off—> see IIS is Checked Or Not If checked please unckeck IIS and restart the computer.After that Open services see Web Deployement Agent Service status if its started please stop.And also see WampAppache and WampSqlID if its not started please start manually. it will works for me.

Hi i also meet this problem today.
And the log error in the Event viewer is as following
The Apache service named reported the following error:

1.Wrapper php-cgi.exe cannot be accessed: (720005)Access is denied.

2.apache service monitor:the requested operation has failed

It is actual the access problem.So the solution as flowing is help me
change the php-cgi.exe security properties

  • not inheit from parent the permission…

  • please add the everyone user

if appache and IIS both are running at a time then there is a posibility to hang the apache service,,,,

when i stopped all IIS websites once and then restarted apache service and it works for me….Jai…

Windows Vista Home Premium operating system issue: The easiest way to resolve the issue is to change the port number in Apache2confhttpd.conf.

Change the port number at the following lines. ‘Listen’ from 80 to 8888 and ‘ServerName’ machinename (ex:localhost) from 80 to 8888. Save then close. Open up Apache Service Monitor and restart service or go to Computer Management > Services and locate Apache 2.2 and start or restart.

Remove apache from Control Panel and delete the apache folder from Program Files and restart the machine, then install apache again. This will solve the problem; if not do the following: Install IIS if not installed, then start IIS and stop it … Using services start apache service… enjoy apache.

I’ve had this problem twice. The first problem was fixed using the marked answer on this page (thank you for that). However, the second time proved a bit more difficult.

I found that in my httpd-vhosts.conf file that I made a mistake when assigning the document root to a domain name. Fixing this solved my problem. It is well worth checking (or even reverting to a blank copy) your httpd-vhosts.conf file for any errors and typo’s.

if you are using windows os and believe that skype is not the suspect, then you might want to check the task manager and check the «Show processes from all users» and make sure that there is NO entry for httpd.exe. Otherwise, end its process. That solves my problem.

Yes , i had to change the port :80 to :90 as port :80 was busy by some other system resource.

You can see the logs in the folder of Apache2.2logs

Thanks,

Always double check httpd.conf to see if document root is correctly pointing to an existing folder

#if you have c:your-main-folderwww
DocumentRoot "c:/your-main-folder/www/" 

#if you have c:your-main-folderwwwsub-folder
DocumentRoot "c:/your-main-folder/www/sub-folder/" 

DocumentRoot points to a folder that must exist in your drive.

I had the same issue. when i restarted my wamp it turns to Yellow color icon but not green.
In services i stop all sql server services. after that it works for me..

  • Two thinks that should must be take care.
    1 ) port should be different
    2 ) stop those services which can be on port 80

Thanks for the help guys. I found another culprit. Recently SimplifyMedia added a photo sharing option. Apparently it too uses port 80 and prevented Apache from starting up. I hope this helps someone out.

Me also coming the same problem. The solution is goto add or remove programes then click the turn windows features on or off. Turn off the IIS. That is turn off the ‘Internet information services’ and ‘Internet information service removable web core’. I chosed the remaining features are on. Computer will ask to restart the system. Restart ur computer and then install the apache http server. I got it. Server succesfully working…

For me, this was the result of having set the document root (in httpd.conf) to a directory that did not exist (I had just emptied htdocs of a previous project).

Windows 10 — administrator account

I needed to switch the account to an admin type account, in windows services

httpd.exe -k install

fails to add setup with enough user rights.

Страницы 1

Чтобы отправить ответ, вы должны войти или зарегистрироваться

1 2012-06-10 06:24:59

  • Hase
  • Активный
  • Неактивен
  • Откуда: Москва
  • Зарегистрирован: 2012-01-04
  • Сообщений: 132

Тема: Apache2.2 не запускается. Специфическая ошибка 1.

Здравствуйте! И снова я к вам) При запуске start.bat выскакивает ошибка не возможности запустить apache. В error.log в каталоге apache пишется следующее: (OS 5)Отказано в доступе.  : httpd.exe: could not open error log file E:/WebServer/apache/hpstudio.ru/error.log.
Unable to open logs.

ОСЬ — windows 7. Подскажите, пожалуйста, как надо настроить права, или дело может быт даже не в этом? П.с. бтаник запускаю от администратора.
Сразу прикрепляю httpd.conf и vhost

# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "c:/Apache2" will be interpreted by the
# server as "c:/Apache2/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "e:/webserver/Apache2"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "E:/WebServer/php/php5apache2_2.dll"
PHPIniDir "E:/WebServer/php"

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin admin@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName hpstudio.ru:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "E:/Webserver/Apache2/htdocs"
DocumentRoot "E:/WebServer/apache"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
Options Includes Indexes FollowSymLinks
AllowOverride All
Allow from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html index.htm index.shtml index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "E:/WebServer/apache/error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i"" combined
    LogFormat "%h %l %u %t "%r" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "E:/WebServer/apache/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    Alias /pma "E:/WebServer/apache/hpstudio.ru/www/phpmyadmin"
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "e:/WebServer/Apache2/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "c:/Apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "e:/WebServer/Apache2/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
    AddType application/x-httpd-php .php
    AddType application/x-httpd-php-source .phps
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at 
# <URL:http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
NameVirtualHost *:80

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#

<VirtualHost *:80>
# Папка, в которой будет корень вашего хоста.
DocumentRoot "E:/WebServer/apache/hpstudio.ru/www"
# Домен по которому вы сможете обращаться к виртуальному хосту.
ServerName hpstudio.ru
# Алиас (добавочное имя) домена.
ServerAlias www.hpstudio.ru
# Файл, в который будут записываться ошибки.
ErrorLog журнала доступа к хосту.
CustomLog "E:/WebServer/apache/hpstudio.ru/access.log" common
</VirtualHost>

"E:/WebServer/apache/hpstudio.ru/error.log"
# Файл 

2 Ответ от Hanut 2012-06-10 14:34:43

  • Hanut
  • Hanut
  • Модератор
  • Неактивен
  • Откуда: Рига, Латвия
  • Зарегистрирован: 2006-07-02
  • Сообщений: 9,723

Re: Apache2.2 не запускается. Специфическая ошибка 1.

Проверьте, чтобы был создан каталог E:/WebServer/apache/hpstudio.ru/

Если данный каталог создан — значит проблема в правах. Попробуйте зайти под администратором в Windows 7.

3 Ответ от Hase 2012-06-10 15:00:48

  • Hase
  • Активный
  • Неактивен
  • Откуда: Москва
  • Зарегистрирован: 2012-01-04
  • Сообщений: 132

Re: Apache2.2 не запускается. Специфическая ошибка 1.

Так я и так сижу через администратора… Каталог есть. Может Вы в курсе, как права настроить?

4 Ответ от Hase 2012-06-10 15:07:06

  • Hase
  • Активный
  • Неактивен
  • Откуда: Москва
  • Зарегистрирован: 2012-01-04
  • Сообщений: 132

Re: Apache2.2 не запускается. Специфическая ошибка 1.

Так, я исправил эту ошибку, просто удалил error.log. Он создался автоматически и апач запустился. Но теперь проблема с mysql…  Вот что пишет сервер:
Warning: mysql_connect() [function.mysql-connect]: [2002] Подключение не установлено, т.к. конечный компьютер отверг запро (trying to connect via tcp://hpstudio.ru:3306) in E:WebServerapachehpstudio.ruwwwphp_scriptsfunctions.php on line 5

Warning: mysql_connect() [function.mysql-connect]: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. in E:WebServerapachehpstudio.ruwwwphp_scriptsfunctions.php on line 5
Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение

5 Ответ от Hanut 2012-06-10 15:09:50

  • Hanut
  • Hanut
  • Модератор
  • Неактивен
  • Откуда: Рига, Латвия
  • Зарегистрирован: 2006-07-02
  • Сообщений: 9,723

Re: Apache2.2 не запускается. Специфическая ошибка 1.

Хост MySQL должен быть localhost.

Страницы 1

Чтобы отправить ответ, вы должны войти или зарегистрироваться

Понравилась статья? Поделить с друзьями:
  • Windows could not determine the language to use for setup error code 0x80004005 что делать
  • Windows could not determine the language to use for setup error code 0x80004005 при установке
  • Windows could not determine the language to use for setup 0x80004005 как исправить
  • Windows com stopcode код остановки как исправить
  • Windows com stopcode whea uncorrectable error