How To Check Event Log In Windows Server 2003

The Result Viewer or the Event Logs are generally the starting time identify anyone using Server 2003 should begin their troubleshooting. Depending on how you have them set up, they are a quite comprehensive record of what happens on your server. Especially useful when troubleshooting, the Result Viewer logs also give a good thought of organization and awarding functioning.

The standard setup volition record application, security, directory services, file replication, and DNS issues.

Issue Viewer has been around since the Windows NT days, but has had regular tweaks and enhancements as later versions of the operating system have been released. It is substantially a passive log collecting program that records events during normal performance also every bit during faults or error conditions.

To open Event Viewer y'all can either right click on My Reckoner and choose Manage, or use Administrator Tools from the Starting time menu. The Administration Panel will open and yous can select from a group of options from the menu on the left. We desire Event viewer here.

Either double click or click the "+" beside the option to drop the menu and expose the log types. If you are just having an explore, and so feel gratuitous to cull whatever of them and aggrandize the carte further. You should see something similar this.

This is the list view which provides an overview of what's going on within DNS on this server. The Information types are just that, data on DNS events that aren't cause for concern. Errors on the other hand volition need checking out. The next two columns are the date and time the effect occurred. This is very useful if y'all have enough information to know when a system rebooted or misbehaved in some fashion. You can trace what happened around that fourth dimension, which should atomic number 82 you to the crusade. Each column can be sorted past clicking on the description to make investigation easier.

At that place is a third event type chosen Warning. This is denoted by a yellowish alert triangle with an exclamation marking in it. These are things that should be checked out, only won't cause besides serious problems in the meantime.

Double clicking on an entry will bring up another dialog box with data specific to the event.

EventView2

In this case a DNS error, which are common in networked servers. Here in that location is more data from which to investigate the fault. The Description oft provides enough information to tell you exactly what happened, like in this example. However it tin can likewise be frustratingly cryptic, and even worse, just incorporate hex lawmaking.

There was a lot of negative feedback from server administrators virtually this, and so from Server 2003 onwards a new information repository was made available directly from Microsoft.

The link at the bottom of the clarification window contains a link to Microsoft's Technet resource which may have more than data. This site is maintained by Microsoft only is updated with information provided by users, so often has a amend clarification, or more information than Event Viewer alone.

In that location will be times when Upshot Viewer simply doesn't have the data for you. This isn't always Microsoft's fault, especially when 3rd party applications are causing the issues. The system depends on the information it receives from each plan, which is sometimes sadly lacking.

At that place is enough information bachelor through Result Viewer for most people to be able to effectively monitor and troubleshoot their systems. At present yous, likewise, know how to utilise Event Viewer and obtain information on how to monitor system and application performance.

Technet