Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
From: "Iain Cunningham" <iain.cunningham@architecta.co.uk>
To: <users@httpd.apache.org>
Date: Wed, 14 Jan 2004 12:19:08 -0000
Message-ID: <000101c3da98$9c4a8740$7b00000a@architecx44llh>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <Pine.WNT.4.58.0401131603580.1056@Poste3947.hec.ca>
Subject: RE: [users@httpd] Apache 2.0.48 + Windows 2000 Server SP4 + Adaptec
 RAID array = "DocumentRoot must be a directory"

> -----Original Message-----
> From: Joshua Slive [mailto:joshua@slive.ca] 
> Sent: 13 January 2004 21:06
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Apache 2.0.48 + Windows 2000 
> Server SP4 + Adaptec RAID array = "DocumentRoot must be a directory"
> Importance: High
> 
> 
> 
> On Tue, 13 Jan 2004 iain.cunningham@architecta.co.uk wrote:
> > DocumentRoot "E:/intranet/test"
> >
> > and made the appropriate change in the <Directory "..."> section.
> >
> > I tested the httpd.conf file with "apache -t" and it 
> checked out ok, 
> > so I restarted the service, went to http://127.0.0.1 and 
> promptly got 
> > a "File not found error".  I then noticed that Apache was 
> not running 
> > as a service any more.  Checking the system error log 
> showed an error 
> > stating that "DocumentRoot must be a directory" (but 
> > "E:/intranet/test" IS a directory!).
> 
> I'm not a win32 apache expert, but I believe the most common 
> cause of this problem is that the user under which the apache 
> service is running doesn't have access to the network drives. 
>  In particular, the default LocalSystem user cannot access 
> the network.  You can change this from the win32 services 
> configuration screen.
> 
> (You can verify if this is the problem by shutting down the 
> service and launching apache manually from the command line.)
> 
> Joshua.

OK, I tried from the command prompt and that just caused the same
"DocumentRoot..." message in the system error log (nothing in the Apache
log or the command prompt window though), so I then went back to Google
with some different search criteria and found this (apologies if you're
a *nix user, if OpenOffice/StarOffice can't open this, but it's probably
not of much interest to you anyway):

http://das.ite.iowa.gov/security/doc/Windows_Apache_2.doc

Having looked through it I have set up the server with an "apache"
account that has appropriate levels of access to the various parts of
the filesystem and it now appears to be running just fine.

Thanks for your help,

Iain


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org