Windows XP event log Windows uses the Windows XP event log to keep track of a number of significant occurrences in the system and in programs. The Windows XP event log is an excellent starting point when troubleshooting your pc. There's always room for improvement. Use the event viewer to inspect the contents of the event log : Click the Start button Select "Run" Type "eventvwr" without the quotes in the "open" field Click ok Windows opens up the event viewer.
For example, when your virus scanner encounters a problem, it could bring this to your attention through the application log. The developers of the program are responsible for the type of events that are logged here. Things that can dramatically slow down your pc. The security log : is used to bring valid and invalid logon attempts to your attention.
Also file access, creation and deletion of files can be logged here. You need to have an account with administrative privileges to enable, use and specify which events are logged in the security log. The system log : where you will find events logged by Windows system components. Can also reveal some VERY interesting troubleshooting information about your system. Three types of events in the Windows XP event log There are basically three types of events : information, warning and error. Windows opens this properties dialog : Here you can track down the system file that holds the event log info.
By using Windows PowerShell, these traditional types of event logs are easy to read, easy to write to, easy to back up, and easy to clear. I use the New-EventLog cmdlet to create a new event log. To use this cmdlet, I need three things:. The following command creates a new traditional event log named ScriptingGuys with a source named scripts. To ensure the command actually created a new event log, I use the Get-EventLog cmdlet with the —List parameter.
Here is the command and the associated output. One of the things I notice when I check the ScriptingGuys event log is that it is set to KB, and it will retain entries for 7 days when it will begin deleting older events.
This is not the behavior I want. What I want is for the log to be 64 KB in size and to overwrite as needed. The cmdlet is named Limit-EventLog. Looking at the Help, it appears there is only one parameter set. I craft the following command, but as you can see, it fails.
The 0 argument is less than the minimum allowed range of 1. Supply an argument that is greater than or equal to 1 and then try the command again. LimitEventLogCommand Major bummer. Asked 12 years, 4 months ago. Active 7 years, 11 months ago. Viewed 13k times. I am using C -.
NET Framework 3. John M John M Add a comment. Active Oldest Votes. CreateEventSource source, logName ; Be aware that to create a new eventLog or eventLog Source requires a higher level of authority WIndows Access Control List ACL permissions , than does simply writing to the log, and normally, this access level is not available to most applications Charles Bretana Charles Bretana k 22 22 gold badges silver badges bronze badges. Vinay Sajip Vinay Sajip Syntax is: EventLog.
You need to specify the Log property of the EventLog object. David David 70k 16 16 gold badges silver badges bronze badges. Mark Kadlec Mark Kadlec 7, 15 15 gold badges 59 59 silver badges 94 94 bronze badges.
Sign up or log in Sign up using Google.
0コメント