| 1 | Extensible Authentication Protocol |
Extensible Authentication Protocol |
| 2 | 可延伸的驗證通訊協定 (EAP) 服務提供例如 802.1x 有線及無線、VPN 以及網路存取保護 (NAP) 環境中的網路驗證。 EAP 在驗證程序期間，也提供網路存取用戶端 (包括無線及 VPN 用戶端) 使用的應用程式開發介面 (API)。如果您停用此服務，此電腦將無法存取需要 EAP 驗證的網路。 |
The Extensible Authentication Protocol (EAP) service provides network authentication in such scenarios as 802.1x wired and wireless, VPN, and Network Access Protection (NAP). EAP also provides application programming interfaces (APIs) that are used by network access clients, including wireless and VPN clients, during the authentication process. If you disable this service, this computer is prevented from accessing networks that require EAP authentication. |
| 7 | EapHost Service |
EapHost Service |
| 0x3E9 | 未登錄方法或無法存取方法的登錄資料。LoadConfig: FriendlyName、ConfigCLSID 均空白 |
Method not registered or method's registry data could not be accessed. LoadConfig: FriendlyName, ConfigCLSID both are empty |
| 0x3EA | 無法剖析格式不正確的 EAP 封包 |
Unable to parse malformed EAP packet |
| 0x3EB | 未登錄方法或登錄值錯誤: 函數名稱=LoadConfig，ArgumentName=%1 |
Method not registered or registry value error: Function Name=LoadConfig, ArgumentName=%1 |
| 0x3EC | 交涉失敗。沒有可用的 EAP 方法 |
Negotiation failed. No available EAP methods |
| 0x3ED | 交涉失敗。對等建議的方法清單無效 |
Negotiation failed. Proposed methods list from peer is invalid |
| 0x3EE | 交涉失敗。要求的 EAP 方法無法使用 |
Negotiation failed. Requested EAP methods not available |
| 0x3EF | 已超過協力廠商 EapHost 處理程序的數目上限 (32)。正在捨棄目前的 eap 工作階段。 |
Exceeded the maximum number(32) of Third Party EapHost processes. Discarding the current eap session. |
| 0x7D1 | 無法確認 Eap 方法易記名稱，或無法存取 %1 路徑; 錯誤: 類型(%2)、authId(%3)、vendorId(%4)、vendorType(%5) |
Eap method friendly name can not be verified or %1 path could not be accessed; Error: type(%2), authId(%3), vendorId(%4), vendorType(%5) |
| 0x7D2 | 跳過: %1 驗證失敗。錯誤: typeId=%2、authorId=%3、vendorId=%4、vendorType=%5 |
Skipping: %1 validation failed. Error: typeId=%2, authorId=%3, vendorId=%4, vendorType=%5 |
| 0x7E9 | 超過協力廠商 EapHost 程序的最大數目 (32)。請以短時間 Eap3Host 程序執行目前的 eap 工作階段。 |
Exceeded the maximum number(32) of Third Party EapHost processes. Running the current eap session in short lived Eap3Host process. |
| 0xBB9 | 無法載入 EAPHost。LoadLibraryW(%1) 失敗 %2 |
EAPHost failed to load. LoadLibraryW(%1) failed %2 |
| 0xBBA | 找不到要求的 EapMethod: TypeId(%1)、 AuthorId(%2)、VendorId(%3)、VendorType(%4) |
Could not find the requested EapMethod: TypeId(%1), AuthorId(%2), VendorId(%3), VendorType(%4) |
| 0x10000001 | 登錄 |
Registry |
| 0x10000002 | COM |
COM |
| 0x50000002 | 錯誤 |
Error |
| 0x50000004 | 資訊 |
Information |
| 0x70000001 | 驗證器 |
Authenticator |
| 0x70000002 | 對等 |
Peer |
| 0x70000003 | 一般 |
Common |
| 0x90000001 | Microsoft-Windows-EapHost |
Microsoft-Windows-EapHost |
| 0x90000002 | Application |
Application |
| 0x90000003 | Microsoft-Windows-EapHost/Operational |
Microsoft-Windows-EapHost/Operational |
| 0x90000004 | Microsoft-Windows-EapHost/Analytic |
Microsoft-Windows-EapHost/Analytic |
| 0x90000005 | Microsoft-Windows-EapHost/Debug |
Microsoft-Windows-EapHost/Debug |
| 0xB00003FD | 方法未登錄或無法存取方法的登錄資料。無法開啟登錄機碼 %1，錯誤碼 %2 |
Method not registered or method's registry data could not be accessed. Unable to open registry key %1, error code %2 |
| 0xB00003FE | 方法未登錄或無法存取方法的登錄資料。查詢方法的登錄 (%1) 失敗: TypeId=%2、AuthorId=%3、VendorId=%4、VendorType=%5 |
Method not registered or method's registry data could not be accessed. Query registry (%1) failed for method: TypeId=%2, AuthorId=%3, VendorId=%4, VendorType=%5 |
| 0xB00003FF | 方法未登錄或無法存取方法的登錄資料。驗證機碼 (%1) 失敗，方法資訊: Type Id=%2、AuthorId=%3、vendorId=%4、vendorType=%5 |
Method not registered or method's registry data could not be accessed. Validation failed for key (%1), Method Info: Type Id=%2, AuthorId=%3, vendorId=%4, vendorType=%5 |
| 0xB0000411 | 無法初始化 COM 程式庫。EapHostAuthenticatorInvokeConfigUI() 的例項已經執行中。CoInitializeEx 傳回 S_FALSE。 |
Unable to Initialize COM library. An instance of EapHostAuthenticatorInvokeConfigUI() is already running. CoInitializeEx returned S_FALSE. |
| 0xB0000412 | 無法初始化 COM 程式庫。為 EapHostAuthenticatorInvokeConfigUI() 指定了錯誤的並行處理模型。COM 錯誤: RPC_E_CHANGED_MODE。 |
Unable to Initialize COM library. The wrong concurrency model was specified for EapHostAuthenticatorInvokeConfigUI(). COM Error: RPC_E_CHANGED_MODE. |
| 0xB0000413 | 無法初始化 EapHostAuthenticatorInitialize() 的 COM 程式庫。%n 錯誤描述: %1 |
Unable to Initialize COM library for EapHostAuthenticatorInitialize(). %n Error Description: %1 |
| 0xB0000414 | EAP 方法傳回無效的 eatInnerEapMethodType。屬性的格式不正確 (%1) |
Invalid eatInnerEapMethodType returned by the EAP method. Attribute has incorrect format (%1) |
| 0xB0000415 | 方法不支援 EapMethodAuthenticatorUpdateInnerMethodParams() API，但已呼叫 UpdateInnerMethodParams() |
Method does not support EapMethodAuthenticatorUpdateInnerMethodParams() API, but UpdateInnerMethodParams() called |
| 0xB0000416 | 用戶端的回應: NAK=%1、接受=%2 |
Client's response: NAK=%1, Accept=%2 |
| 0xB0000417 | 對等沒有提供慣用的方法清單 |
No preferred methods list provided by Peer |
| 0xB0000418 | 工作階段 (%1)、狀態 (%2)、接收封包識別碼 (%3)、長度 (%4) |
Session(%1), state(%2), receive packet id(%3), length(%4) |
| 0xB0000419 | 傳送封包識別碼 (%1)、長度(%2) |
send packet id(%1), length(%2) |
| 0xB000041A | 找到 SoH 回應 |
SoH response found |
| 0xB000041B | 需要 NAP 交換，從網路原則伺服器取得 SoH 回應 |
NAP exchange required, get SoH response from network policy server |
| 0xB000041C | 方法不支援獨立模式。跳過 EapMethod TypeId=%1、AuthorId=%2 |
Method does not support stand-alone mode. Skipping EapMethod TypeId=%1, AuthorId=%2 |
| 0xB000041D | 無法剖析格式不正確的 EAP 封包。傳回 ERROR_PPP_INVALID_PACKET |
Unable to parse malformed EAP packet. ERROR_PPP_INVALID_PACKET returned |
| 0xB000041E | NAK 回應: 方法 (VenId(%2)、VenType(%3)、類型 (%1)) 存在 |
NAK Response: Method (VenId(%2), VenType(%3), Type(%1)) present |
| 0xB000041F | 效能 |
Performance |
| 0xB00007D3 | SoH 的 CoTaskMemAlloc() 失敗。未儲存 SoH。 |
CoTaskMemAlloc() failed for SoH. SoH not saved. |
| 0xB00007D4 | 無法初始化服務控制管理員通知執行緒中的 COM 程式庫 |
Could not initialize COM library in service control manager notification thread |
| 0xB00007D5 | SoH 變更失敗。EapQec::NotifySoHChange 發現 %1 的例外狀況: 0x%2 |
SoH change failed. EapQec::NotifySoHChange caught exception for %1: 0x%2 |
| 0xB00007D6 | ConfigSchema 驗證失敗。錯誤 %1 |
ConfigSchema validation failed. Error %1 |
| 0xB00007D7 | EapQec 接聽執行緒控制代碼是 NULL |
EapQec Listening thread handle is NULL |
| 0xB00007D8 | 工作階段 (%1、%2) 使用中 |
Session(%1, %2) in use |
| 0xB00007D9 | EAP 方法不支援 %1。 |
EAP method does not support %1. |
| 0xB00007DA | XML 設定問題; 找不到根項目。 |
XML configuration problem; Failed to find root element. |
| 0xB00007DB | XML 設定問題; 傳送的參數無效。 |
XML configuration problem; Invalid parameter passed. |
| 0xB00007DC | 登錄機碼驗證成功。 |
Registry key validation successful. |
| 0xB00007DD | 用戶端未啟用 NAP。SoH 變更失敗。 |
Client not NAP enabled. SoH change failed. |
| 0xB00007DE | 沒有收到 %1 的 SoH 回應 |
No SoH response received for %1 |
| 0xB00007DF | 通知 SoH 變更成功。 |
Notify SoH change succeeded. |
| 0xB00007E0 | 通知 SoH 變更失敗，介面: %1。 |
Notify SoH change failed with interface: %1. |
| 0xB00007E1 | 工作階段 (%1): 身分識別交換後收到 EAP 失敗: 可能是驗證使用者的帳戶時發生問題。 |
Session(%1): Received EAP-Failure after Identity exchange: There is likely a problem with the authenticating user's account. |
| 0xB00007E2 | 工作階段 (%1): EAP-Nak 交涉後收到 EAP 失敗: 用戶端和伺服器未設定為支援相同的 EAP 方法。(伺服器提供的 EAP 類型 %2; 用戶端傳送 Nak 並要求 EAP 類型 %3。) |
Session(%1): Received EAP-Failure after EAP-Nak negotiation: The client & server are not configured to support the same EAP methods. (Server offered EAP type %2; Client sent a Nak, and requested EAP type %3.) |
| 0xB00007E3 | 方法未實作 %1 |
Method does not implement %1 |
| 0xB00007E4 | COM API %1 失敗。%n 錯誤描述: %2 |
COM API %1 Failed.%n Error Description : %2 |
| 0xB00007E6 | _beginthreadex 失敗。%n 錯誤描述: %1 |
_beginthreadex failed.%n Error Description : %1 |
| 0xB00007E7 | 無效的 XML 文件。無法 selectSingleNode。%n 錯誤描述: %1 |
Invalid XML document. Failed to selectSingleNode.%n Error Description : %1 |
| 0xB00007E8 | 無法開啟 %1 控制代碼。%n 錯誤描述: %2 |
Unable to open %1 handle.%n Error Description : %2 |
| 0xB0000826 | EapHostPeerGetResult 傳回失敗。%nEap 方法易記名稱: %2%n理由代碼: %1%n根本原因字串: %3%n修復字串: %4 |
EapHostPeerGetResult returned a failure.%nEap Method Friendly Name: %2%nReason code: %1%nRoot Cause String: %3%nRepair String: %4 |
| 0xB0000827 | 使用者已輸入認證。 |
User Entered Credentials. |
| 0xB0000828 | 使用者使用已儲存的認證。 |
User Uses Saved Credentials. |
| 0xB0000829 | EAP 工作階段正於驗證階段期間完成。 |
EAP session is completing during the authentication phase. |
| 0xB0000BCD | 未登錄 EAP 方法或無法存取登錄資料; 無法開啟登錄 %1，錯誤碼: %2 |
EAP methods not registered or registry data could not be accessed; Failed to open registry %1, Error Code: %2 |
| 0xB0000BCE | 未登錄 EAP 方法或無法存取登錄資料; 無法開啟方法登錄 %2\\\\%1。跳過此類型識別碼 |
EAP methods not registered or registry data could not be accessed; Failed to open method registry %2\\\\%1. Skip this type ID |
| 0xB0000BCF | 未登錄 EAP 方法或無法存取登錄資料; 無法開啟方法登錄 %1。跳過此作者識別碼 |
EAP methods not registered or registry data could not be accessed; Failed to open method registry %1. Skip this author ID |
| 0xB0000BD0 | 未登錄 EAP 方法或無法存取登錄資料; 無法開啟方法登錄 %1\\\\254\\\\%2\\\\%3。跳過此廠商類型 |
EAP methods not registered or registry data could not be accessed; Failed to open method registry %1\\\\254\\\\%2\\\\%3. Skip this vendor type |
| 0xB0000BD1 | 未登錄 EAP 方法或無法存取登錄資料; 無法開啟方法登錄 %1\\\\254\\\\%2。跳過此廠商識別碼 |
EAP methods not registered or registry data could not be accessed; Failed to open method registry %1\\\\254\\\\%2. Skip this vendor ID |
| 0xB0000BD2 | 跳過: 無法新增 EAP 方法。易記名稱不存在。TypeId(%1)、AuthorId(%2)、VendorId(%3)、VendorType(%4) |
Skipping: Unable to add EAP method. Friendly name not present. TypeId(%1), AuthorId(%2), VendorId(%3), VendorType(%4) |
| 0xB0000BD3 | XML 設定問題; 無法取得 EapMethodType 節點 %n。錯誤描述: %1 |
XML configuration problem; Failed to get EapMethodType node %n. Error Description: %1 |
| 0xB0000BD4 | XML 設定問題; %1 的資料類型不符 |
XML configuration problem; Data Type mismatch for %1 |
| 0xB0000BD5 | XML 設定問題; 錯誤的方法: TypeId(%1)、AuthorId(%2)、VendorId(%3)、VendorType(%4) |
XML configuration problem; Bad method: TypeId(%1), AuthorId(%2), VendorId(%3), VendorType(%4) |
| 0xB0000BE1 | 無法載入方法。記憶體不足 |
Could not load method. Out of memory |
| 0xB0000BE2 | 重新初使化後無法新增新方法 |
Unable to add new method after re-initialization |
| 0xB0000BE3 | 發生 EAP 例外: authorId(%1)、類型(%2)、vendorId(%3)、vendorType(%4)、錯誤(%5) |
EAP Exception caught: authorId(%1), type(%2), vendorId(%3), vendorType(%4), error(%5) |
| 0xB0000BE4 | 發生例外: authorId(%1)、類型(%2)、vendorId(%3)、vendorType(%4)、錯誤(%5) |
Exception caught: authorId(%1), type(%2), vendorId(%3), vendorType(%4), error(%5) |
| 0xB0000BE5 | 錯誤 %1，讀取 EAP 方法易記的名稱 (muiRead)。從登錄抓取易記名稱 |
Error %1, reading EAP method friendly name(muiRead). Friendly name retrieved from registry |
| 0xB0000BE6 | 找不到 EAP 方法，正重新初始化程式庫管理員的 EapMethodList 資料 |
EAP method not found, re-initializing the library manager's EapMethodList data |
| 0xB0000BE7 | 重新初始化 EapMethodList 資料後找到新的方法 |
New method found after re-initializing EapMethodList data |
| 0xB0000BE8 | 已新增新 EAP 方法至 EapMethodList: TypeId=%1、AuthorId=%2、VendorId=%3、VendorType=%4 |
New EAP method added to EapMethodList: TypeId=%1, AuthorId=%2, VendorId=%3, VendorType=%4 |
| 0xB0000FA1 | %1 |
%1 |