Partilhar via


Error messages generated by the Semantic Logging Application Block

patterns & practices Developer Center

The Semantic Logging Application Block uses the events listed in the following table to notify you of any problems it encounters at runtime.

Event Id

Level

Keywords

Description

1

Error

Sink

Trace event for logging any unhandled exception that occurs in a custom sink.

2

Error

Formatter

Trace event for logging any unhandled exception that occurs in a custom formatter.

100

Error

Sink

The SQL Database sink could not open the configured database.

101

Error

Sink

The SQL Database sink could not write to the configured database.

102

Warning

Sink

The SQL Database sink could not publish messages and discarded them.

103

Warning

Sink

The SQL Database sink could not publish an individual message and discarded it.

200

Critical

Sink

The Console sink could not write to the console.

300

Critical

Sink

The Flat File sink could not write to the configured file.

400

Critical

Sink

The Rolling Flat File sink could not write to the configured file.

500

Critical

Sink

The Azure Table Storage sink could not publish to the configured Azure storage table.

501

Critical

Sink

The Azure Table Storage sink could not create the configured Azure storage table.

502

Warning

Sink

The Azure Table Storage sink encountered a transient error.

503

Critical

Sink

The Azure Table Storage sink could not create the entity.

504

Error

Sink

The Azure Table Storage sink could not publish messages and discarded them.

700

Warning

Formatting

The block failed to serialize a trace message to JSON.

701

Warning

Formatting

The block failed to write a JSON trace message.

702

Warning

Formatting

The block failed to write an XML trace message.

703

Warning

Formatting

The block failed to write a text trace message.

800

Critical

TraceEvent

The block encountered an unobserved task exception when processing trace messages.

801

Error

TraceEvent

The block encountered an error during the serial processing of trace messages.

802

Informational

TraceEvent

The block removed the ETW session

803

Error

TraceEvent

The block encountered an error when it attempted to reconfigure the ETW session.

804

Informational

TraceEvent

The block successfully reconfigured the ETW session.

805

Warning

TraceEvent

The new configuration was partially successful. Check logs for further error details.

806

Warning

TraceEvent

Some trace messages will be lost because the buffer in the ETW session is full.

807

Warning

TraceEvent

Reports the number of messages the trace event service lost.

808

Error

TraceEvent

A fault occurred shutting down the trace event service.

809

Error

TraceEvent

A fault occurred loading the trace event service configuration file.

810

Critical

Sink

An improperly generated manifest was received.

811

[Depends on the event source]

[Depends on the event source]

An out-of-band event notification was received from an event source not defined in the block. For example, the sampling parameters were invalid.

900

Warning

Sink

The capacity of the block’s internal buffer is exceeded.

901

Informational

Sink

The capacity of the block’s internal buffer is restored.

902

Warning

Sink

Some events could not be sent to the event sink and will be lost. Reports the number of lost events.

903

Critical

Sink

The block detected an unobserved exception and restarted the event publisher task.

1000

Error

Sink

Failed to parse the source manifest from ETW.

1100

Critical

Sink

Failed to format an entry as a string in a formatter.

1101

Warning

Sink

Failed to perform the color mapping in a formatter.

If you are running the Out-of-Process Host application as a Windows service, it writes these error messages to the Windows Application Event Log from the source “Enterprise Library Semantic Logging Service.”

If you are running the Out-of-Process Host application as a console application, it displays these messages in the console window.

If you are using the Semantic Logging Application Block in-process, you should create and enable an event listener for the SemanticLoggingEventSource class as shown in the following code:

myEventListener.EnableEvents(
  SemanticLoggingEventSource.Log, EventLevel.LogAlways, Keywords.All);

For more information about creating and configuring event listeners, see the topic Key scenarios for the Semantic Logging Application Block.

Next Topic | Previous Topic | Home | Community