RE: .NET 1.1 created event log has only "Not available" properties

I found part of the problem. Looking at the EventLog registry entries, there
are several missing registry values for the .NET created event logs. By
manually adding the HKLM\SYSTEM\CurrentControlSet\Services\EventLog\<event
log name>\File registry value with the path to the event log file the
attibutes are now populated.
--
Thanks,

Tim


"Tim" wrote:

I tried the example on two more machines today with the same result. I have
tried it on three different Windows 2000 domains with varying security
settings (minimal to very secure) and all three domains display "Not
Available" for the attributes within Computer Management.

--
Thanks,

Tim


"Steven Cheng[MSFT]" wrote:

Hi Tim,

Thank you for posting.

From your description, I understanding you're using the EventLog class to
write entries into custom eventlog in .net 1.1 application. However, after
wrting the log correctly, you found that you can not view the custom log's
properties(size, modified...) in computer management console, correct?

Based on my local test, the custom log created or write through the
EventLog class should populated the specific properties correctly. So I
think it is likely a machine specific issue. Have you tried the application
or a very simple evetlog writing code snippet as below on some other
machines:

=================
private void button1_Click(object sender, System.EventArgs e)
{
if(!EventLog.SourceExists("MySource"))
{
EventLog.CreateEventSource("MySource", "MyNewLog1");
Console.WriteLine("CreatingEventSource");
}

// Create an EventLog instance and assign its source.
EventLog myLog = new EventLog();
myLog.Source = "MySource";

// Write an informational entry to the event log.
myLog.WriteEntry("Writing to event log.");

}
============

Or does it work if first create the customlog externally and then use
eventlog class to write into it?

Please feel free to post here if there is anything I missed.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


.