| 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安全性識別碼:%t%1%n%t帳戶名稱:%t%2%n%t網域名稱:%t%3%n%t登入識別碼:%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. |