| 1 | Extensible Authentication Protocol |
Extensible Authentication Protocol |
| 2 | 可扩展的身份验证协议(EAP)服务在以下情况下提供网络身份验证: 802.1x 有线和无线、VPN 和网络访问保护(NAP)。EAP 在身份验证过程中也提供网络访问客户端使用的应用程序编程接口(API)，包括无线客户端和 VPN 客户端。如果禁用此服务，该计算机将无法访问需要 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 路径无法访问；错误: type(%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 | 方法未注册或方法的注册表数据无法访问。使用方法: TypeId=%2、AuthorId=%3、VendorId=%4、VendorType=%5 查询注册表(%1)失败 |
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)的验证失败，方法信息: 类型 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、Accept=%2 |
Client's response: NAK=%1, Accept=%2 |
| 0xB0000417 | 对等端没有提供首选的方法列表 |
No preferred methods list provided by Peer |
| 0xB0000418 | Session(%1)、state(%2)、接收数据包 ID(%3)、length(%4) |
Session(%1), state(%2), receive packet id(%3), length(%4) |
| 0xB0000419 | 发送数据包 ID(%1)、length(%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)、Type(%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 | Session(%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 | 使用接口 %1 通知 SoH 更改失败。 |
Notify SoH change failed with interface: %1. |
| 0xB00007E1 | Session(%1): 标识交换之后收到 EAP 故障: 可能是对用户的帐户进行身份验证有问题。 |
Session(%1): Received EAP-Failure after Identity exchange: There is likely a problem with the authenticating user's account. |
| 0xB00007E2 | Session(%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。跳过该类型 ID |
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。跳过该作者 ID |
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。跳过该供应商 ID |
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)、type(%2)、vendorId(%3)、vendorType(%4)、error(%5) |
EAP Exception caught: authorId(%1), type(%2), vendorId(%3), vendorType(%4), error(%5) |
| 0xB0000BE4 | 捕获异常: authorId(%1)、type(%2)、vendorId(%3)、vendorType(%4)、error(%5) |
Exception caught: authorId(%1), type(%2), vendorId(%3), vendorType(%4), error(%5) |
| 0xB0000BE5 | 读取 EAP 方法友好名称(muiRead)时发生错误 %1。从注册表检索到友好名称 |
Error %1, reading EAP method friendly name(muiRead). Friendly name retrieved from registry |
| 0xB0000BE6 | 重新初始化库管理器的 EapMethodList 数据时找不到 EAP 方法 |
EAP method not found, re-initializing the library manager's EapMethodList data |
| 0xB0000BE7 | 重新初始化 EapMethodList 数据之后，找到新方法 |
New method found after re-initializing EapMethodList data |
| 0xB0000BE8 | 向 EapMethodList 中添加了新 EAP 方法: 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 |