Clever Geek Handbook

What access does Apache 2.0 require on Windows Server 2003 to run as a service?

Until this morning, I had Apache 2.0 running as a service using a local account that was configured with the appropriate permissions. Sometime yesterday, someone must have changed something, and now Apache 2.0 does not start as a service on that account.

I temporarily made the account an administrator and Apache 2.0 started working fine.

I've tried using the access given in the official documentation but it seems to require more access. Does anyone know what kind of Apache 2.0 access should run as a service?

I am running Apache 2.0.63 with SVN 1.4.6 and mod_auth_sspi for windows authentication.

I also checked the syntax of the config file from the command line using the -t option , but I got the Syntax OK message .

Here is the error I get when running as a service from the command line:

X: \> net start apache2
The Apache2 service is starting.
The Apache2 service could not be started.

A service specific error occurred: 1.

More help is available by typing NET HELPMSG 3547.
0


source to share


2 answers


Make sure your service still has the Log On user right. If your computer is part of a domain, it is possible that account permissions or user rights have been reset by group policy.



Can you run "Run As" using the Apache account and start Apache from the command line? This will tell you if there are other permission issues.

+1


source


Set the "LogLevel" directive for "debugging" in the apache config file.

Execute Apache from the command line and use the "-X" argument to prevent Apache from handling fork processes.



Apache should output a little more information to help debug your problem.

+1


source






More articles:


All Articles