EventLog.WriteEntry Method (String, EventLogEntryType, Int32, Int16, Byte())
Writes an entry with the given message text, application-defined event identifier, and application-defined category to the event log, and appends binary data to the message.
Assembly: System (in System.dll)
'Declaration Public Sub WriteEntry ( _ message As String, _ type As EventLogEntryType, _ eventID As Integer, _ category As Short, _ rawData As Byte() _ )
- Type: System.String
The string to write to the event log.
- Type: System.Int32
The application-specific identifier for the event.
- Type: System.Int16
The application-specific subcategory associated with the message.
- Type: System.Byte()
An array of bytes that holds the binary data associated with the entry.
The method attempted to register a new event source, but the computer name in MachineName is not valid.
- or -
The source is already registered for a different event log.
- or -
eventID is less than zero or greater than UInt16.MaxValue.
- or -
The message string is longer than 31,839 bytes (32,766 bytes on Windows operating systems before Windows Vista).
- or -
The source name results in a registry key path longer than 254 characters.
The registry key for the event log could not be opened.
type is not a valid EventLogEntryType.
The operating system reported an error when writing the event entry to the event log. A Windows error code is not available.
Use this overload to write application-defined event-specific data to the event log. The Event Viewer does not interpret this data; it displays raw data only in a combined hexadecimal and text format. Use event-specific data sparingly, including it only if you are sure it will be useful to someone debugging the problem. You can also use event-specific data to store information the application can process independently of the Event Viewer. For example, you could write a viewer specifically for your events, or write a program that scans the logfile and creates reports that include information from the event-specific data.
In addition to the binary data, you can specify an application-defined category and an application-defined event identifier. The Event Viewer uses the category to filter events written by an event source. The Event Viewer can display the category as a numeric value, or it can use the category as a resource identifier to display a localized category string.
The message string cannot contain %n, where n is an integer value (for example, %1), because the event viewer treats it as an insertion string. Because an Internet Protocol, version 6 (IPv6) address can contain this character sequence, you cannot log an event message that contains an IPv6 address.
The category parameter should be a positive value. Negative category values appear as a complementary positive number in the Event Viewer. For example, a –10 appears as 65,526, a –1 as 65,535.
To display localized category strings in the Event Viewer, you must use an event source configured with a category resource file, and set the category to a resource identifier in the category resource file. If the event source does not have a configured category resource file, or the specified category does not index a string in the category resource file, then the Event Viewer displays the numeric category value for that entry. Configure the category resource file, along with the number of category strings in the resource file, using the EventLogInstaller or the EventSourceCreationData class.
Event identifiers, along with the event source, uniquely identify an event. Each application can define its own numbered events and the description strings to which they map. Event viewers display these string values to help the user understand what went wrong and suggest what actions to take.
Finally, you can specify an EventLogEntryType for the event being written to the event log. The type is indicated by an icon and text in the Type column in the Event Viewer for a log. This parameter indicates whether the event type is error, warning, information, success audit, or failure audit.
Create the new event source during the installation of your application. This allows time for the operating system to refresh its list of registered event sources and their configuration. If the operating system has not refreshed its list of event sources, and you attempt to write an event with the new source, the write operation will fail. You can configure a new source using an EventLogInstaller, or using the CreateEventSource method. You must have administrative rights on the computer to create a new event source.
If the source specified in the Source property of this EventLog instance is not registered on the computer that your component is writing to, WriteEntry calls CreateEventSource and registers the source.
Many exceptions listed above are generated by errors raised during the process of registering the Source.
The source must be configured either for writing localized entries or for writing direct strings. The WriteEntry method writes the given string directly to the event log; it does not use a localizable message resource file. Use the WriteEvent method to write events using a localized message resource file.
If your application writes entries using both resource identifiers and string values, you must register two separate sources. For example, configure one source with resource files, and then use that source in the WriteEvent method to write entries using resource identifiers to the event log. Then create a different source without resource files, and use that source in the WriteEntry method to write strings directly to the event log using that source.
If you write an entry to a remote computer, the value of the message (the text string) might not be what you expect if the remote computer is not running the .NET Framework.
If the message parameter contains a NUL character, the message in the event log is terminated at the NUL character.
' Create the source, if it does not already exist. dim myLogName as string = "myNewLog" If Not EventLog.SourceExists("MySource") Then EventLog.CreateEventSource("MySource", myLogName) Console.WriteLine("Creating EventSource") else myLogName = EventLog.LogNameFromSourceName("MySource",".") End If ' Create an EventLog and assign source. Dim myEventLog As New EventLog() myEventLog.Source = "MySource" myEventLog.Log = myLogName ' Set the 'description' for the event. Dim myMessage As String = "This is my event." Dim myEventLogEntryType As EventLogEntryType = EventLogEntryType.Warning Dim myApplicatinEventId As Integer = 1100 Dim myApplicatinCategoryId As Short = 1 ' Set the 'data' for the event. Dim myRawData(3) As Byte Dim i As Integer For i = 0 To 3 myRawData(i) = 1 Next i ' Write the entry in the event log. Console.WriteLine("Writing to EventLog.. ") myEventLog.WriteEntry(myMessage, myEventLogEntryType, myApplicatinEventId, _ myApplicatinCategoryId, myRawData)
Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.