Can't get a log started

[Andy]

I can not get a counter log file started for a performance log.

This is what Event Viewer is saying.

Thanks,
Andy

Event Type: Warning
Event Source: SysmonLog
Event Category: None
Event ID: 2004
Date: 7/6/2013
Time: 3:13:29 PM
User: N/A
Computer: 21-7
Description:
The service was unable to open the log file C:\masm32\SOURCE\System_000004.blg for log System and will be stopped. Check the log folder for existence,spelling, permissions, and ensure that no other logs or applications are writing to this log file. You can reenter the log file name using the configuration program. This log will not be started. The error returned is: Unable to create the specified log file.
..

 

[Dennis]

Subject: Can't get a log started

A cup of coffee in the morning usually does it for me!

[[ insert rim shot here ]]

Sorry ... I couldn't resist. Reminded me of the Dennis Miller "coffee
log joke" back when he had a show on CNBC. It was so funny he milked it
for several nights in a row. That was probably the only reason why I
remembered it.

I was probably the only person who watched that show.

 

[JJ]

I can not get a counter log file started for a performance log.

This is what Event Viewer is saying.

Thanks,
Andy

Event Type: Warning
Event Source: SysmonLog
Event Category: None
Event ID: 2004
Date: 7/6/2013
Time: 3:13:29 PM
User: N/A
Computer: 21-7
Description:
The service was unable to open the log file C:\masm32\SOURCE\System_000004.blg for log System and will be stopped. Check the log folder for existence, spelling, permissions, and ensure that no other logs or applications are writing to this log file. You can reenter the log file name using the configuration program. This log will not be started. The error returned is: Unable to create the specified log file.

The description is pretty clear. What have you checked?

 

[Andy]

I can not get a counter log file started for a performance log.



This is what Event Viewer is saying.



Thanks,

Andy



Event Type: Warning

Event Source: SysmonLog

Event Category: None

Event ID: 2004

Date: 7/6/2013

Time: 3:13:29 PM

User: N/A

Computer: 21-7

Description:

The service was unable to open the log file C:\masm32\SOURCE\System_000004.blg for log System and will be stopped. Check the log folder for existence, spelling, permissions, and ensure that no other logs or applications are writing to this log file. You can reenter the log file name using the configuration program. This log will not be started. The error returned is: Unable to create the specified log file.

.

It creates this file, but it isn't updated.

PerfWiz - 5 second interval_07061523.blg

 

[Andy]

It creates this file, but it isn't updated.



PerfWiz - 5 second interval_07061523.blg

I would like to use sfc to check if some file is corrupted.

Anyone know which file(s) are used in generating log files ?

sfc/scannow is too slow in checking every file.

Thanks

 

[Paul]

I would like to use sfc to check if some file is corrupted.

Anyone know which file(s) are used in generating log files ?

sfc/scannow is too slow in checking every file.

Thanks

If you copy your installer CD, to a separate disk partition,
then SFC would run faster. In my case at least, I needed to
edit the registry, as SFC would not run properly until it
was pointed to a reference information source (my D: partition).
It wouldn't use my WinXP SP3 CD, if it was placed in the drive.
The drive letter has to line up, for whatever reason. So even if
you present it with a CD, it might not use it until the registry
is corrected.

Some info here...

http://www.updatexp.com/scannow-sfc.html

Not that I think this is going to fix anything...

*******

You can find EventID references on the web.

http://technet.microsoft.com/en-us/library/cc727117(v=WS.10).aspx

This site occasionally has more varied suggestions as to what is wrong.
You would not be surprised to find a "full moon" caused the problem here

http://www.eventid.net/display.asp?eventid=2004&eventno=646&source=PerfNet&phase=1

Paul

 

[Andy]

If you copy your installer CD, to a separate disk partition,

then SFC would run faster. In my case at least, I needed to

edit the registry, as SFC would not run properly until it

was pointed to a reference information source (my D: partition).

It wouldn't use my WinXP SP3 CD, if it was placed in the drive.

The drive letter has to line up, for whatever reason. So even if

you present it with a CD, it might not use it until the registry

is corrected.



Some info here...



http://www.updatexp.com/scannow-sfc.html



Not that I think this is going to fix anything...



*******



You can find EventID references on the web.



http://technet.microsoft.com/en-us/library/cc727117(v=WS.10).aspx



This site occasionally has more varied suggestions as to what is wrong.

You would not be surprised to find a "full moon" caused the problem here



http://www.eventid.net/display.asp?eventid=2004&eventno=646&source=PerfNet&phase=1



Paul

I tried everything with no luck.

Andy

 

[Paul]

I tried everything with no luck.

Andy

OK, so what process is opening the log, and does it
have permission to work in that directory ?

If you want to watch, you can use Sysinternals ProcMon and set
the filter for file opens or write attempts. You may find it
trying to traverse the path, and getting stuck.

Paul