I get the error below on my web server on a regular basis. It occurs for
different sites, apparently at random. The storage location is on the local
disk and the disk has at least 20GB of free space.
An helpful suggestions will be appreciated.
Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
full. If this is a network path, make sure that network connectivity is not
broken.
Ron,
Can you verify that your log files are pointing to a folder on the local
drive and not on a network drive somewhere?
Walid
MCSE NT/2000/2003
"Ron" wrote:
> I get the error below on my web server on a regular basis. It occurs for
> different sites, apparently at random. The storage location is on the local
> disk and the disk has at least 20GB of free space.
>
> An helpful suggestions will be appreciated.
>
> Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> full. If this is a network path, make sure that network connectivity is not
> broken.
>
The files are definately on the local drive. The drive has 20GB of space.
"Walid" wrote:
> Ron,
>
> Can you verify that your log files are pointing to a folder on the local
> drive and not on a network drive somewhere?
>
> Walid
> MCSE NT/2000/2003
>
> "Ron" wrote:
>
> > I get the error below on my web server on a regular basis. It occurs for
> > different sites, apparently at random. The storage location is on the local
> > disk and the disk has at least 20GB of free space.
> >
> > An helpful suggestions will be appreciated.
> >
> > Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> > full. If this is a network path, make sure that network connectivity is not
> > broken.
> >
Do you know which website W3SVC1 refers to? Find that website, go to the
website's properties by righ-clicking. Under the "enable logging", go the
properties tab and verify where the log file directory is pointing.
"Ron" wrote:
> The files are definately on the local drive. The drive has 20GB of space.
>
> "Walid" wrote:
>
> > Ron,
> >
> > Can you verify that your log files are pointing to a folder on the local
> > drive and not on a network drive somewhere?
> >
> > Walid
> > MCSE NT/2000/2003
> >
> > "Ron" wrote:
> >
> > > I get the error below on my web server on a regular basis. It occurs for
> > > different sites, apparently at random. The storage location is on the local
> > > disk and the disk has at least 20GB of free space.
> > >
> > > An helpful suggestions will be appreciated.
> > >
> > > Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> > > full. If this is a network path, make sure that network connectivity is not
> > > broken.
> > >
This server hosts several related web sites. All of these web sites have
received this error, and I do not detect any pattern.
These logs are getting entries written to them. The logs do not appear to
loose any entries, even though the error shows up. The log mentioned in the
error below has entries both before and after the error appears in the event
log. The same error appeared in the event log for another site a few minutes
after the error below appeared.
"Walid" wrote:
> Do you know which website W3SVC1 refers to? Find that website, go to the
> website's properties by righ-clicking. Under the "enable logging", go the
> properties tab and verify where the log file directory is pointing.
>
>
> "Ron" wrote:
>
> > The files are definately on the local drive. The drive has 20GB of space.
> >
> > "Walid" wrote:
> >
> > > Ron,
> > >
> > > Can you verify that your log files are pointing to a folder on the local
> > > drive and not on a network drive somewhere?
> > >
> > > Walid
> > > MCSE NT/2000/2003
> > >
> > > "Ron" wrote:
> > >
> > > > I get the error below on my web server on a regular basis. It occurs for
> > > > different sites, apparently at random. The storage location is on the local
> > > > disk and the disk has at least 20GB of free space.
> > > >
> > > > An helpful suggestions will be appreciated.
> > > >
> > > > Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> > > > full. If this is a network path, make sure that network connectivity is not
> > > > broken.
> > > >
Ok. But did you verify the log file location for each site within IIS?
"Ron" wrote:
> This server hosts several related web sites. All of these web sites have
> received this error, and I do not detect any pattern.
>
> These logs are getting entries written to them. The logs do not appear to
> loose any entries, even though the error shows up. The log mentioned in the
> error below has entries both before and after the error appears in the event
> log. The same error appeared in the event log for another site a few minutes
> after the error below appeared.
>
>
> "Walid" wrote:
>
> > Do you know which website W3SVC1 refers to? Find that website, go to the
> > website's properties by righ-clicking. Under the "enable logging", go the
> > properties tab and verify where the log file directory is pointing.
> >
> >
> > "Ron" wrote:
> >
> > > The files are definately on the local drive. The drive has 20GB of space.
> > >
> > > "Walid" wrote:
> > >
> > > > Ron,
> > > >
> > > > Can you verify that your log files are pointing to a folder on the local
> > > > drive and not on a network drive somewhere?
> > > >
> > > > Walid
> > > > MCSE NT/2000/2003
> > > >
> > > > "Ron" wrote:
> > > >
> > > > > I get the error below on my web server on a regular basis. It occurs for
> > > > > different sites, apparently at random. The storage location is on the local
> > > > > disk and the disk has at least 20GB of free space.
> > > > >
> > > > > An helpful suggestions will be appreciated.
> > > > >
> > > > > Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> > > > > full. If this is a network path, make sure that network connectivity is not
> > > > > broken.
> > > > >
This sounds like a folder permissions error. You can use Filemon from
Sysinternals to determine which folder / files are getting denied. If you
enable auditing so access denied messages are logged in the Security event
log. IIS perf will suffer from log files not being able to be created.
http://www.microsoft.com/technet/sysinternals/utilities/file mon.mspx
--
Best regards,
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
"Ron"
news:08294BDD-BACC-4F79-94E6-160633E5EB4B@microsoft.com...
>I get the error below on my web server on a regular basis. It occurs for
> different sites, apparently at random. The storage location is on the
> local
> disk and the disk has at least 20GB of free space.
>
> An helpful suggestions will be appreciated.
>
> Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> full. If this is a network path, make sure that network connectivity is
> not
> broken.
>
Do you have other messages in the event log related to disk errors? One
thing that comes to my mind since this is happening randomly (and it fixes
itself since it logs future requests) is that the disk is about to fail.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Ron wrote:
>I get the error below on my web server on a regular basis. It occurs for
>different sites, apparently at random. The storage location is on the local
>disk and the disk has at least 20GB of free space.
>
>An helpful suggestions will be appreciated.
>
>Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
>full. If this is a network path, make sure that network connectivity is not
>broken.
Thanks to everyone for the help.
Kristofer, I will run a check on the disk. I have not seen any other disk
errors, but that is a possibility.
Note that all of the web sites are writing to the logs on a continuous basis
without any apparent problem. I monitor the logs for attack. The only
indication of a problem is the entry in the system error log. It looks like
some transient event is occurring that stops the write process for a short
period of time. When I look at the logs at the time the error was posted, I
just see a list of log entries. Of course, if a few entries were missing, I
would not notice.
I will enable logging. That is a very good suggestion.
"Steve Schofield" wrote:
> This sounds like a folder permissions error. You can use Filemon from
> Sysinternals to determine which folder / files are getting denied. If you
> enable auditing so access denied messages are logged in the Security event
> log. IIS perf will suffer from log files not being able to be created.
>
> http://www.microsoft.com/technet/sysinternals/utilities/file mon.mspx
>
> --
>
> Best regards,
>
> Steve Schofield
> Windows Server MVP - IIS
> http://weblogs.asp.net/steveschofield
>
>
> "Ron"
> news:08294BDD-BACC-4F79-94E6-160633E5EB4B@microsoft.com...
> >I get the error below on my web server on a regular basis. It occurs for
> > different sites, apparently at random. The storage location is on the
> > local
> > disk and the disk has at least 20GB of free space.
> >
> > An helpful suggestions will be appreciated.
> >
> > Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> > full. If this is a network path, make sure that network connectivity is
> > not
> > broken.
> >
>
>
"Ron"
news:7775CE56-93DB-4102-83E9-FA8676E81812@microsoft.com...
> Thanks to everyone for the help.
>
> Kristofer, I will run a check on the disk. I have not seen any other disk
> errors, but that is a possibility.
>
> Note that all of the web sites are writing to the logs on a continuous
> basis
> without any apparent problem.
Yes, we get that.
I monitor the logs for attack. The only
> indication of a problem is the entry in the system error log. It looks
> like
> some transient event is occurring that stops the write process for a short
> period of time. When I look at the logs at the time the error was posted,
> I
> just see a list of log entries. Of course, if a few entries were missing,
> I
> would not notice.
Without other leads to go on, I would suspect a disk system problem;
- monitor read writes for a bit
- stand in front of it and listen
- shut off anti-virus, auto-defrag, backup sequences, etc to aleviate
potential disk timeout issues
- get a disk tool from your drive manufacturer and run diagnostics, you
could be losing an array or the drive it is single
- run scandisk, checkdisk, or spinrite (requires reboot or down time for
these)
Or, you could just ignore it, if it doesnt actually hurt anything.
If you are not aware of it, log files tend to get extremely fragmented, so
cycling the logs before they get too big (start a new file) and defragging
regularly might help.
Thanks again to everyone....
We are going to move the sites on that server to a different machine and run
chkdsk / diagnostics and run a consistency check on the raid array.
The disk does have some very fragmented files, but the active log files are
not listed in the fragmented files.
I also double checked the disk load. The disk is not heavily used.
"Kristofer Gafvert" wrote:
> Do you have other messages in the event log related to disk errors? One
> thing that comes to my mind since this is happening randomly (and it fixes
> itself since it logs future requests) is that the disk is about to fail.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Ron wrote:
>
> >I get the error below on my web server on a regular basis. It occurs for
> >different sites, apparently at random. The storage location is on the local
> >disk and the disk has at least 20GB of free space.
> >
> >An helpful suggestions will be appreciated.
> >
> >Unable to write to the log file ex060126.log for site W3SVC1. Disk may be
> >full. If this is a network path, make sure that network connectivity is not
> >broken.
>