200 | Windows Event Log |
Windows Event Log |
201 | 此服务管理事件和事件日志。它支持日志记录事件、查询事件、订阅事件、归档事件日志以及管理事件元数据。它可以用 XML 和纯文本两种格式显示事件。停止该服务可能危及系统的安全性和可靠性。 |
This service manages events and event logs. It supports logging events, querying events, subscribing to events, archiving event logs, and managing event metadata. It can display events in both XML and plain text format. Stopping this service may compromise security and reliability of the system. |
0x14 | 在获取或处理通道 %2 的配置时,事件日志记录服务遇到错误 %1。 |
The event logging service encountered an error %1 while obtaining or processing configuration for channel %2. |
0x15 | 事件日志记录服务遇到一个通道 %2 的与配置相关的错误(res=%1)。该错误在处理 %3 配置属性时发生。 |
The event logging service encountered a configuration-related error (res=%1) for channel %2. The error was encountered while processing the %3 configuration property. |
0x16 | 初始化通道 %2 的发布资源时,事件日志记录服务遇到错误。如果通道类型为“分析”或“调试”,则这可能意味着初始化日志记录资源时也存在错误。 |
The event logging service encountered an error while initializing publishing resources for channel %2. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well. |
0x17 | 初始化通道 %2 的日志记录资源时,事件日志记录服务遇到错误(res=%1)。 |
The event logging service encountered an error (res=%1) while initializing logging resources for channel %2. |
0x19 | 事件日志记录服务遇到通道 %1 的损坏的日志文件。已使用 .corrupt 扩展名重命名该日志。 |
The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension. |
0x1A | 事件日志记录服务遇到通道 %1 的一个日志文件,该文件的版本不受支持。已使用 .UnsupportedVer 扩展名重命名该日志。 |
The event logging service encountered a log file for channel %1 which is an unsupported version. The log was renamed with a .UnsupportedVer extension. |
0x1B | 打开通道 %2 的日志文件时,事件日志记录服务遇到错误(res=%1)。请使用默认的日志文件路径 %3 重试。 |
The event logging service encountered an error (res=%1) while opening log file for channel %2. Trying again using default log file path %3. |
0x1C | 分析通道 %2 的筛选器时,事件日志记录服务遇到错误(res=%1)。将在没有筛选器的情况下继续。 |
The event logging service encountered an error (res=%1) while parsing filter for channel %2. Will continue without filter. |
0x1D | 将设置应用到通道 %2 时,事件日志记录服务遇到错误(res=%1)。服务正在关闭,因为执行此服务必须使用此通道。 |
The event logging service encountered a fatal error (res=%1) when applying settings to the %2 channel. The service is shutting down since this channel is vital to its operation. |
0x1E | 在允许发布者 %3 使用通道 %2 时,事件日志记录服务遇到错误(%1)。这不会影响通道的操作,但会影响发布者将事件发出通道的能力。该错误的一个常见原因是提供程序正在使用 ETW 提供程序安全,却未向事件日志服务标识授予启用权限。 |
The event logging service encountered an error (%1) while enabling publisher %3 to channel %2. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity. |
0x1F | 打开主通道 %2 的配置时,事件日志记录服务遇到错误(res=%1)。请使用默认配置重试。如果注册表已损坏或明显配置不当,则通常会发生此问题。 |
The event logging service encountered an error (res=%1) while opening configuration for primary channel %2. Trying again using default configuration. This problem usually occurs if registry has been corrupted or explicitly misconfigured. |
0x28 | 事件日志记录服务在尝试应用一个或多个策略设置时遇到错误。 |
The event logging service encountered an error when attempting to apply one or more policy settings. |
0x68 | %3 日志文件已被清除。 |
The %3 log file was cleared. |
0x69 | 事件日志自动备份%n%t日志:%t%1%n%t文件:%t%2%n |
Event log automatic backup%n%tLog:%t%1%n%tFile:%t%2%n |
0x6A | 在 %1 通道的日志中检测到损坏,某些数据被擦除。 |
Corruption was detected in the log for the %1 channel and some data was erased. |
0x6C | 以前的系统意外关闭。 |
The previous system shutdown was unexpected. |
0x44C | 事件日志服务已关闭。 |
The event logging service has shut down. |
0x44D | 该传输已丢弃这些审核事件。%1 |
Audit events have been dropped by the transport. %1 |
0x44E | 审核日志已被清除。%n主题:%n%t安全 ID:%t%1%n%t帐户名称:%t%2%n%t域名:%t%3%n%t登录 ID:%t%4 |
The audit log was cleared.%nSubject:%n%tSecurity ID:%t%1%n%tAccount Name:%t%2%n%tDomain Name:%t%3%n%tLogon ID:%t%4 |
0x44F | 安全日志现在使用了 %1。 |
The security log is now %1 percent full. |
0x450 | 安全日志现在已满。 |
The security log is now full. |
0x452 | 该事件日志服务已丢弃这些事件。原因代码为 %1。 |
Events have been dropped by the event logging service. The reason code is %1. |
0x453 | 处理来自发布者 %3 的传入事件并尝试处理该事件的元数据时,事件日志记录服务遇到错误。 |
The event logging service encountered an error while processing an incoming event from publisher %3 and trying to process the metadata for it. |
0x454 | 处理从 %3 发布的传入事件时,事件日志记录服务遇到错误。 |
The event logging service encountered an error while processing an incoming event published from %3. |
0x1770 | %1 日志文件已满。 |
The %1 log file is full. |
0x10000012 | 服务可用性 |
Service availability |
0x10000013 | 服务配置 |
Service configuration |
0x10000014 | 系统可用性 |
System availability |
0x10000036 | 审核成功 |
Audit Success |
0x30000001 | 开始 |
Start |
0x30000002 | 停止 |
Stop |
0x50000001 | 关键 |
Critical |
0x50000002 | 错误 |
Error |
0x50000003 | 警告 |
Warning |
0x50000004 | 信息 |
Information |
0x50000005 | 详细 |
Verbose |
0x70000064 | 服务启动 |
Service startup |
0x70000065 | 事件处理 |
Event processing |
0x70000067 | 服务关闭 |
Service shutdown |
0x70000068 | 日志清除 |
Log clear |
0x70000069 | 日志自动备份 |
Log automatic backup |
0x7000006C | 系统异常关闭 |
System Abnormal Shutdown |
0x90000001 | Microsoft-Windows-Eventlog |
Microsoft-Windows-Eventlog |
0x90000002 | System |
System |
0x90000003 | Security |
Security |
0x90000004 | 设置 |
Setup |
0x90000005 | Debug |
Debug |
0x90000006 | Analytic |
Analytic |
0xB0000067 | 该传输已丢弃这些事件。会话名称为 %2,原因代码为 %1。 |
Events have been dropped by the transport. The session name is %2 and the reason code is %1. |
0xB000006B | 当进行发布者配置时,事件日志记录服务遇到错误 %1。发布者 %2 已经使用 GUID %3 安装。 |
The event logging service encountered an error %1 while going through publisher configuration. The publisher %2 is already installed with GUID %3. |
0xB000006E | 正在为发布者 %2 (%1)加载元数据,并尝试为其处理元数据。 |
Loading metadata for publisher %2 (%1) and trying to process the metadata for it. |
0xB000006F | 已为发布者 %2 (%1)加载完元数据,已处理 %3 事件元数据。 |
Finished loading metadata for publisher %2 (%1), with %3 event metadatas processed. |
0xB0000070 | 无法为发布者 %2 (%1)加载元数据。原因代码为 %3。 |
Failed to load metadata for publisher %2 (%1). The reason code is %3. |
0xD0000001 | 由于没有可用缓冲区,事件丢失。刷新磁盘无法随传入事件更新。 |
Events were lost because there were no free buffers. Flushing to disk could not catch up with incoming events. |
0xD0000002 | 由于实时消费程序无法更新,已放弃一个或多个缓冲区。 |
One or more buffers were dropped because a real time consumer could not catch up. |
0xD0000003 | 实时备份文件由于非正常关机损坏。 |
The real time backup file was corrupt due to improper shutdown. |