Re: Unable to create the log file for site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kristofer Gafvert (kgafvert_at_NEWSilopia.com)
Date: 02/13/05


Date: Sun, 13 Feb 2005 09:28:20 -0800

Hi,

How often do you see the errors in the event log (only when you move the
files?)?

When you move the log files, do you also (try to) move the log file IIS is
currently logging to? I can assume that if you move this file, while IIS
is using it, it can cause problems.

-- 
Regards,
Kristofer Gafvert
www.gafvert.info - My Articles and help
www.ilopia.com
Anony2 wrote:
> Thanks for the reply, Ben.
>
> Yes, the W3SVC13 directory exists and the app pool runs under an admin
> account.
>
> Monday, I changed the schedule of moving the IISlogs to run weekly vice
> daily.  Since then, the errors have disappeared.  But, they will reappear
> once the log files are moved in the weekly schedule.
>
> Regardless, the logfiles are still created and logging still occurs.  I 
just
> want to know why I get the http errors and how do I get rid of them and 
still
> be able to move the log files to another location.
>
>
> "Ben Strackany" wrote:
>
> > Does the W3SVC13 directory exist? Check the application pool for the
> > erroring site -- does the app pool run under some unusual account?
> >
> > --
> > Ben Strackany
> > www.developmentnow.com
> >
> >
> > "Anony2" <Anony2@discussions.microsoft.com> wrote in message
> > news:12B9B83C-4EB9-4D84-A523-0D9C2894780E@microsoft.com...
> > > Hello,
> > >
> > > I am seeing source HTTP event errors 15001 and 15000.  The 
descriptions
> > are:
> > >
> > > Event 15001: Unable to create the log file for site W3SVC1713575364. 
Make
> > > sure that the logging directory for the site is correct and this 
computer
> > has
> > > write access to that directory.
> > >
> > > Event 15000: Unable to create log file
> > > C:\WINDOWS\system32\LogFiles\W3SVC13\ex050206.log. Make sure that the
> > logging
> > > directory is correct and this computer has write access to that 
directory.
> > >
> > > I am running Windows 2003 Enterprise Server with IIS6.0.  I have 13 
sites
> > on
> > > the server, and not all sites get this error.
> > >
> > > Even though I get the above errors, the log files are created and 
website
> > > hits are logged.  The log files turnover every 24 hrs (daily).  I 
then run
> > a
> > > batch file that moves the IIS Logfiles from the server to another 
location
> > at
> > > 0100.
> > >
> > > Administrators and system have FC and the Inet anonymous account has 
read.
> > >
> > > Any help would be greatly appreciated.
> > >
> > > Thanks!!!
> >
> >
> >


Relevant Pages

  • Re: Requiring specific computer to log on
    ... > Monitoring through the RRAS VPN log files is simple though. ... Double click the logfile. ... >> if I can simply block his own machine from logging on - that does resolve ... >> able to monitor his logging on. ...
    (microsoft.public.windows.server.sbs)
  • Re: GP Software Install / Log File
    ... I enabled the MSI logging also. ... the Windows Group Policy Guide is out from Microsoft Press!!! ... can also enable software installation specific logging. ... out where the log files go for this push. ...
    (microsoft.public.windows.group_policy)
  • Re: Requiring specific computer to log on
    ... Monitoring through the RRAS VPN log files is simple though. ... Access logging. ... Double click the logfile. ... to monitor compliance may be enough to have everyone play by the rules. ...
    (microsoft.public.windows.server.sbs)
  • RE: event id 7034 from Service Control Manager
    ... By default the following crash log files will be created: ... - If logging is turned on, the service copies all of the log files into the ... Microsoft Online Partner Support ... If you are outside the United States, ...
    (microsoft.public.sms.admin)
  • WSS logging vs. IIS logging
    ... guess), when we turned on "Enable Logging" for our WSS sites, SharePoint ... a top-level-site by top-level-site basis. ... I turned on "Enable Logging" from WSS ... WSS thus creates log files of its own, ...
    (microsoft.public.sharepoint.windowsservices)