| 1 | WSMan Quota Statistics |
WSMan Quota Statistics |
| 3 | 显示 WS-Management 进程的配额使用率和冲突信息。 |
Displays quota usage and violation information for WS-Management processes. |
| 5 | Total Requests/Second |
Total Requests/Second |
| 7 | 显示每秒来自授权用户的批准请求和拒绝请求的数目。 |
Displays the number of approved and rejected requests per second from authorized users. |
| 9 | User Quota Violations/Second |
User Quota Violations/Second |
| 11 | 显示用户配额冲突的数量。 |
Displays the number of user quota violations. |
| 13 | System Quota Violations/Second |
System Quota Violations/Second |
| 15 | 显示受系统限制的请求数目。 |
Displays the number of requests subject to system throttling. |
| 17 | Active Shells |
Active Shells |
| 19 | 显示所有用户的活动外壳程序的当前数目。 |
Displays the current number of active shells for all users. |
| 21 | Active Operations |
Active Operations |
| 23 | 显示所有用户的活动操作的当前数目。 |
Displays the current number of active operations for all users. |
| 25 | Active Users |
Active Users |
| 27 | 显示处于活动状态的授权用户的当前数目。 |
Displays the current number of active, authorized users. |
| 29 | Process ID |
Process ID |
| 31 | 显示当前进程 ID (PID) |
Displays the current process ID (PID) |
| 0x00072775 | WinRM 服务未在侦听请求，因为它至少在一个地址和端口上无法进行侦听。%n%n 使用 WinRM 的远程管理将失败。%n%n 用户操作 %n 通过对侦听程序的“自动配置”启用 GPO 策略或使用 WinRM 命令行工具手动创建侦听程序来配置侦听程序。 |
The WinRM service is not listening for requests since it failed to listen on at least one address and port. %n%n Remote management using WinRM will fail. %n%n User Action %n Configure listeners by enabling GPO policy for Auto Configuration of listeners or manually create a listener using WinRM command line tool. |
| 0x00072776 | WinRM 服务未在侦听 %1 请求，因为 HTTP.SYS 中存在绑定到 URL (%2)的故障。%n%n 已注册另一个进程来侦听 WinRM 服务的 URL 前缀。%n%n 用户操作 %n 通过停止另一个进程，更改其 URL 前缀或更改 WS-Management 侦听地址的配置来解决此问题。 |
The WinRM service is not listening for %1 requests because there was a failure binding to the URL (%2) in HTTP.SYS. %n%n Another process is registered to listen on the WinRM service URL prefix. %n%n User Action %n Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address. |
| 0x00072777 | WS-Management 客户端未在侦听推的事件，因为 HTTP.SYS 中存在绑定到 URL (%1)的故障。%n%n已注册另一个进程来侦听 WinRM 客户端的 URL 前缀。%n%n 用户操作 %n 通过停止另一个进程，更改其 URL 前缀或更改 WS-Management 侦听地址的配置来解决此问题。 |
The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n Another process is registered to listen on the WinRM client URL prefix. %n%n User Action %n Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address. |
| 0x00072778 | WinRM 服务未在侦听 HTTPS 请求，因为 HTTP.SYS 中存在绑定到 URL (%1)的故障。%n%n不会在该 URL 上为任何远程请求提供服务。%n%n 用户操作 %n 请使用 \"netsh http\" 检查是否已经将 \"URL ACL\" (%1)设置为“网络服务”。%n%n 其他数据 %n 从 HTTP.sys 收到的错误代码为 %2: %%%2 |
The WinRM service is not listening for HTTPS requests because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n No remote requests will be serviced on that URL. %n%n User Action %n Please use \"netsh http\" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys is %2: %%%2 |
| 0x00072779 | WS-Management 客户端未在侦听推的事件，因为 HTTP.SYS 中存在绑定到 URL (%1)的故障。%n%n 用户操作 %n 请使用 \"netsh http\" 检查是否已经将 URL(%1) 的 ACL 设置为网络服务。%n%n 其他数据 %n 从 HTTP.sys 收到的错误代码为 %2: %%%2 |
The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n User Action %n Please use \"netsh http\" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys was %2: %%%2 |
| 0x0007277E | WinRM 服务无法验证客户端证书，因为证书链中的证书状态或证书之一脱机或已经过时。%n%n 用户操作 %n 请确保证书吊销列表可以访问并且保持最新。 |
The WinRM service cannot validate the client certificate because the revocation status of the certificate or one of the certificates in the certificate chain is either offline or stale. %n%n User Action %n Please ensure that the Certificate Revocation List is accessible and up-to-date. |
| 0x0007277F | 使用基本身份验证方案的用户身份验证失败。%n%n 其他数据 %n 从 LogonUser %1 收到的错误: %%%1。 |
User authentication using Basic authentication scheme failed. %n%n Additional Data %n Unexpected error received from LogonUser %1: %%%1. |
| 0x00072780 | 客户端证书超出 WinRM 服务允许的最大大小。%n%n 用户操作 %n 请使用不同的客户端证书或不同的身份验证机制。 |
The client certificate exceeded the maximum size allowed by the WinRM service.%n%n User Action %n Please use a different client certificate or a different authentication mechanism. |
| 0x00072781 | 请求处理失败，因为 WinRM 服务无法加载数据或事件源: DLL=\"%1\"%n%n 用户操作 %n 请检查“%1”是否存在。%n%n 其他数据 %n 加载 %1 失败，错误=\"%2\"(%%%2)。 |
Request processing failed because the WinRM service cannot load data or event source: DLL=\"%1\" %n%n User Action %n Please check if \"%1\" exists. %n%n Additional Data %n Loading %1 failed with error=\"%2\" (%%%2). |
| 0x00072782 | IP %1 和端口 %2 的 SSL 配置与其他服务共享，如 Internet 信息服务(IIS)。 |
The SSL configuration for IP %1 and port %2 is shared with another service, such as Internet Information Services (IIS). |
| 0x00072787 | WinRM 服务无法启动，因为在初始化过程中出现故障。%n%n 其他数据 %n 错误代码为 %1。 |
The WinRM service is unable to start because of a failure during initialization. %n%n Additional Data %n The error code is %1. |
| 0x00072788 | WinRM 服务收到来自 %1 的不安全 HTTP 连接。%n%n 这是不安全的配置。%n%n 用户操作 %n 在 WinRM 配置中将 AllowUnencrypted 设置为 False，以确保在线上加密数据包。 |
The WinRM service has received an unsecure HTTP connection from %1. %n%n This is not a secure configuration. %n%n User Action %n Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire. |
| 0x00072789 | 已经将 WinRM 服务配置为接受不安全 HTTP 连接的基本身份验证。%n%n 这是不安全的配置。%n%n 用户操作 %n 在 WinRM 中将 AllowUnencrypted 设置为 False，以确保在线上加密数据包。 |
The WinRM service has been configured to accept basic authentication for unsecure HTTP connections. %n%n This is not a secure configuration. %n%n User Action %n Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire. |
| 0x00072790 | WinRM 服务未在侦听 HTTP 请求，因为 HTTP.SYS 中存在绑定到 URL (%1)的故障。%n%n 不会在该 URL 上为任何远程请求提供服务。%n%n 用户操作 %n 请使用 \"netsh http\" 检查是否已经将 URL(%1) 的 ACL 设置为网络服务。%n%n 其他数据 %n 从 HTTP.sys 收到的错误代码为 %2: %%%2 |
The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n No remote requests will be serviced on that URL. %n%n User Action %n Please use \"netsh http\" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys is %2: %%%2 |
| 0x00072792 | 在侦听程序“自动配置”的 GPO 策略中指定的 IP 筛选器 %1 无效，因此将被忽略。因为此问题，WinRM 服务无法使用自动配置的侦听程序。%n%n \"*\" 用于指明服务应该侦听计算机上所有可用的 IP。在使用 \"*\" 时，不能在筛选器中指定其他范围。%n%n 用户操作 %n 如果需要在 IP 筛选器中包括 \"*\"，则请删除其他 IP 范围。 |
IP Filter %1 specified in the GPO policy for Auto Configuration of listeners is invalid and it will be ignored. Due to this issue, the WinRM service cannot use the autoconfigured listener. %n%n \"*\" is used to indicate that the service should listen on all available IPs on the machine. When \"*\" is used, other ranges cannot be specified in the filter. %n%n User Action %n Remove other IP ranges if \"*\" needs to be included in the IP Filter. |
| 0x00072793 | IP 范围 %1 无效，因此将被忽略。%n%n 使用语法 IP1-IP2 指定范围。使用 \",\" 作为分隔符将多个范围分隔。%n 示例 IPv4 范围: 2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22 %n示例 IPv6 范围: 3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 %n%n 用户操作 %n 使用上述语法更正 IP 筛选器 %1。 |
The IP Range %1 is invalid and it will be ignored. %n%n Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using \",\" as delimiter. %n Example IPv4 ranges: 2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22 %nExample IPv6 ranges: 3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 %n%n User Action %n Correct the IP filter %1 using the syntax described above. |
| 0x00072794 | WinRM 服务未在侦听策略更改，因为注册 WS-Management 策略密钥内容的更改时出现故障。%n%n 不会处理任何组策略更改。%n%n 用户操作 %n 停止并重新启动 WinRM 服务。%n%n 其他数据 %n 错误代码为 %1。 |
The WinRM service is not listening for policy changes because there was a failure registering for changes to the contents of the WS-Management policy key. %n%n No group policy change will be serviced. %n%n User Action %n Stop and restart the WinRM service. %n%n Additional Data %n The error code was %1. |
| 0x00072798 | WinRM 服务遇到灾难性的安全故障。服务无法继续在其安全上下文下运行。%n%n 用户操作 %n 停止并重新启动 WinRM 服务。%n%n 其他数据 %n 错误代码为 %1。 |
The WinRM service encountered a catastrophic security failure. The service can no longer run under its security context. %n%n User Action %n Stop and restart the WinRM service. %n%n Additional Data %n The error code is %1. |
| 0x00072799 | WinRM 服务无法迁移具有 IP 地址 %1 和端口 %2 的侦听程序，因为在目标计算机上不存在该 IP 地址。在迁移过程中已忽略此侦听程序。%n%n 用户操作 %n 请使用正确的 IP 地址重新创建侦听程序。 |
The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the IP address does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct IP address. |
| 0x0007279A | WinRM 服务无法迁移具有地址 %1 和传输 %2 的侦听程序，因为在目标计算机上不存在 IP 地址 %3。在迁移过程中已忽略此侦听程序。%n%n 用户操作 %n 请使用正确的 IP 地址重新创建侦听程序。 |
The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the IP address %3 does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct IP address. |
| 0x0007279B | WinRM 服务无法迁移具有 IP 地址 %1 和端口 %2 的侦听程序，因为在目标计算机上不存在 MAC 地址 %3。在迁移过程中已忽略此侦听程序。%n%n 用户操作 %n 请使用正确的 MAC 地址重新创建侦听程序。 |
The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the MAC address %3 does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct MAC address. |
| 0x0007279C | WinRM 服务无法迁移具有地址 %1 和传输 %2 的侦听程序，因为在目标计算机上不存在 MAC 地址 %3。在迁移过程中已忽略此侦听程序。%n%n 用户操作 %n 请使用正确的 MAC 地址重新创建侦听程序。 |
The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the MAC address %3 does not exist on the destination machine. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct MAC address. |
| 0x0007279D | WinRM 服务无法迁移具有 IP 地址 %1、端口 %2 和传输 %3 的侦听程序。已存在具有地址=%4 且传输=%5 配置的侦听程序。 |
The WinRM service cannot migrate the listener with IP address %1, Port %2 and Transport %3. A listener that has Address=%4 and Transport=%5 configuration already exists. |
| 0x0007279E | WinRM 服务无法迁移具有地址 %1 和传输 %2 的侦听程序。已存在具有相同地址和传输配置的侦听程序。 |
The WinRM service cannot migrate the listener with Address %1 and Transport %2. A listener that has the same Address and Transport configuration already exists. |
| 0x0007279F | WinRM 服务在迁移期间出现故障。%n%n用户操作%n 使用 WinRM 命令行工具再次创建配置。%n%n其他数据%n 错误代码为: %1 %%%1 |
The WinRM service had a failure during migration. %n%n User Action %n Create the configuration again using the WinRM command line tool. %n%n Additional Data %n The error code is: %1 %%%1 |
| 0x000727A0 | WinRM 服务在读取当前配置时出现故障，正在停止。%n%n用户操作%n使用下列命令还原默认值: %n%n winrm invoke Restore winrm/config @{} %n%n 然后添加任意自定义配置设置并重新启动该服务。%n%n其他数据%n错误代码为: %1 %%%1 |
The WinRM service had a failure reading the current configuration and is stopping. %n%n User Action %n Use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} %n%n Then add any custom configuration settings and restart the service. %n%n Additional Data %n The error code is: %1 %%%1 |
| 0x000727A1 | WinRM 服务在应用当前配置时出现故障，正在停止。%n%n用户操作%n检查前一个事件日志消息并重新启动该服务。 |
The WinRM service had a failure applying the current configuration and is stopping. %n%n User Action %n Check for previous event log messages and restart the service. |
| 0x000727A3 | 主机名称模式“%1”无效，将被忽略。主机名称模式不能为空，最多可以包含一个通配符(“*”)。“*”模式可用于表明所有主机；如果使用该模式，列表中不会显示其他模式。特殊字符串“”可用于表示所有不包含“.”的主机名称%n%n用户操作%n使用以上说明的语法纠正主机名称模式。 |
The host name pattern \"%1\" is invalid and it will be ignored. Host name patterns must not be empty and they can contain at most one wildcard (\"*\"). \"*\" pattern can be used to indicate all hosts; if this pattern is used, no other pattern can show up in the list. Special string \"\" can be used to indicate all host names that do not have a '.'%n%n User Action %n Correct the host name pattern using the syntax described above. |
| 0x000727A4 | WinRM 服务正在侦听 WS-Management 请求。%n%n用户操作%n使用下列命令查看 WinRM 正在侦听的特定 IP: %n%n winrm enumerate winrm/config/listener |
The WinRM service is listening for WS-Management requests. %n%n User Action %n Use the following command to see the specific IPs on which WinRM is listening: %n%n winrm enumerate winrm/config/listener |
| 0x000727A5 | WinRM 服务未在侦听 WS-Management 请求。%n%n用户操作%n如果你并非有意停止该服务，请使用下列命令查看 WinRM 配置:%n%n winrm enumerate winrm/config/listener |
The WinRM service is not listening for WS-Management requests. %n%n User Action %n If you did not intentionally stop the service, use the following command to see the WinRM configuration: %n%n winrm enumerate winrm/config/listener |
| 0x000727A6 | WinRM 服务无法使用下列侦听程序接收 WS-Management 请求。侦听程序已启用，但它没有配置 IP 地址。%n%n用户操作%n检查基础网络配置确定该侦听程序是否至少有一个有效 IP。如果该 IP 有效，请使用下列命令确保 WinRM 配置没有将该 IP 地址排除在外:%n%n winrm get winrm/config/service %n%n 其他数据 %n 侦听程序传输: %1 %n 侦听程序地址: %2 |
The WinRM service could not use the following listener to receive WS-Management requests. The listener is enabled but the listener does not have an IP address configured. %n%n User Action %n Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: %n%n winrm get winrm/config/service %n%n Additional Data %n Listener transport: %1 %n Listener address: %2 |
| 0x000727A7 | WinRM 服务在通知 IP 地址更改期间读取配置失败(%1)。%n%n 服务将继续使用旧配置运行。%n%n 用户操作 %n 如果需要立即更改，可手动重新启动该服务 |
The WinRM service had a failure (%1) reading configuration during ip address change notification. %n%n Service will continue running with old configuration.%n%n User Action %n If immediae changes are required manually restart the service |
| 0x000727A8 | WinRM 服务已成功处理地址更改通知。 |
The WinRM service successfully processed an address change notification. |
| 0x000727A9 | WSMan IIS 模块无法读取配置。收到的错误为 %1: %%%1 %n %2。%n%n 用户操作 %n 请确保架构和验证文件存在且有效。 |
The WSMan IIS module failed to read configuration. The error received was %1: %%%1 %n %2.%n%n User Action %n Make sure both the schema and validation files are present and valid. |
| 0x000727AA | WinRM 服务无法创建以下 SPN: %1; %2。%n%n 附加数据 %n 收到的错误为 %3: %%%3。%n%n 用户操作 %n SPN 可以由管理员使用 setspn.exe 实用工具创建。 |
The WinRM service failed to create the following SPNs: %1; %2. %n%n Additional Data %n The error received was %3: %%%3.%n%n User Action %n The SPNs can be created by an administrator using setspn.exe utility. |
| 0x000727AB | WSMan 服务无法读取下列插件的配置: %n%1。%n%n收到的错误为 %2: %%%2 %n %3。%n%n 用户操作 %n 请确保此插件配置有效。 |
The WSMan service failed to read configuration of the following plugin: %n %1. %n%nThe error received was %2: %%%2 %n %3.%n%n User Action %n Make sure this plugin configuration is valid. |
| 0x000727AC | WinRM 服务无法初始化 CredSSP。%n%n 附加数据 %n 收到的错误为 %1。%n%n 用户操作 %n 在 WinRM 配置下为服务配置 CertificateThumbprint 设置。使用有效证书的指纹，并确保网络服务有访问该证书的私钥的权限。 |
The WinRM service failed to initialize CredSSP. %n%n Additional Data %n The error received was %1.%n%n User Action %n Configure CertificateThumbprint setting under the WinRM configuration for the service. Use the thumbprint of a valid certificate and make sure that Network Service has access to the private key of the certificate. |
| 0x000727AD | 尝试卸载数据或事件源时 WinRM 服务收到错误: DLL=“%1”%n%n 用户操作 %n 请检查是否有以下文件的已更新版本可用:“%1”。%n%n 附加数据 %n 关闭 %1 失败，错误为=“%2”(%%%2)。 |
The WinRM service received an error while trying to unloading a data or event source: DLL=\"%1\" %n%n User Action %n Please check if there is an updated version of this file available: \"%1\". %n%n Additional Data %n Shutting down %1 failed with error=\"%2\" (%%%2). |
| 0x000727AE | WinRM 服务正在默认 %1 端口 %2 和 %1 (兼容性) 端口 %3 上侦听 WS-Management 请求。%1 端口 %3 不再是 WinRM 服务的默认端口。%n%n 如果要禁用(兼容性)端口 %3 上的侦听程序，请运行以下命令:%n%n Winrm set winrm/config/service @{%4=\"False\"} |
The WinRM service is listening on the default %1 port %2 and on %1 (Compatibility) port %3 for WS-Management requests. %1 port %3 is no longer the default port for the WinRM service.%n%n If you want to disable the listener on the (Compatibility) port %3, run the following command:%n%n Winrm set winrm/config/service @{%4=\"False\"} |
| 0x000727AF | WinRM 服务在过去 %2 分钟内终止了 %1 个未经身份验证的连接，以保持良好的系统状态。如果该服务超载或受到基于身份验证的攻击，则可能会出现这种情况。%n%n 操作: %n启用并查看 Windows 远程管理分析日志以查找 ID 1843 警告事件。这包括有关突然终止的客户端的其他信息。 |
The WinRM service has terminated %1 unauthenticated connections over the past %2 minutes to maintain healthy system state. This will likely happen if the service is overloaded or if the service is under an authentication based attack. %n%n Action: %nEnable and observe Windows Remote Management Analytic log and look for warning events with Id 1843. These include additional information about the clients that got abruptly terminated. |
| 0x10000001 | Soap 跟踪 |
Soap Trace |
| 0x10000002 | 客户端 |
Client |
| 0x10000003 | 服务器 |
Server |
| 0x10000004 | 安全性 |
Security |
| 0x10000005 | QuotaViolation |
QuotaViolation |
| 0x10000006 | 活动传送 |
Activity Transfer |
| 0x10000007 | 错误 |
Error |
| 0x10000038 | 经典 |
Classic |
| 0x30000001 | 开始 |
Start |
| 0x30000002 | 停止 |
Stop |
| 0x4033C351 | WS-Management 服务无法处理该请求，因为 URI 包含一个 \"?\"，但没有关键字。 |
The WS-Management service cannot process the request because the URI contains a '?' but no key was present. |
| 0x4033C352 | WS-Management 服务无法处理该请求。URI 包含一个关键字: (%1)。但是 WS-Management找不到值，因为找不到 \"=\"。 |
The WS-Management service cannot process the request. The URI contains a key: (%1). But WS-Managementcannot find a value because no '=' was found. |
| 0x4033C353 | WS-Management 服务无法处理该请求，原因是 URI 包含在括号中的值后接“%1!c!”。此 URI 应结束或应在 \"+\" 后开始新的关键字。 |
The WS-Management service cannot process the request because the URI contains a value in parentheses followed by '%1!c!'.The URI should either end or a new key should start following a '+'. |
| 0x4033C354 | WS-Management 服务无法处理该请求。资源 URI (%1!d! 个字符)超过支持的最大长度(%2!d! 个字符)。 |
The WS-Management service cannot process the request. The resource URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters). |
| 0x4033C355 | WS-Management 服务无法处理该请求。筛选器方言 URI (%1!d! 个字符)超过支持的最大长度(%2!d! 个字符)。 |
The WS-Management service cannot process the request. The filter dialect URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters). |
| 0x4033C356 | WS-Management 无法处理该请求。SOAP 数据包包含的 WS-Addressing Action 元素(%1!d! 个字符)超过支持的最大长度(%2!d! 个字符)。 |
The WS-Management service cannot process the request. The SOAP packet contained a WS-Addressing Action element that was longer (%1!d! characters) that the maximum length that is supported (%2!d! characters). |
| 0x4033C357 | WS-Management 服务无法处理该请求。URI 包含的关键字数目超过 WS-Management 支持的最大数目(%1!d!)。 |
The WS-Management service cannot process the request.The URI contains more keys than maximum number that WS-Management supports (%1!d!). |
| 0x4033C358 | WS-Management 服务无法处理该请求。URI 包含重复关键字(%1)。 |
The WS-Management service cannot process the request. The URI contains a duplicate key (%1). |
| 0x4033C359 | WS-Management 服务无法处理该请求。URI 缺少右括号或左括号。 |
The WS-Management service cannot process the request. The URI lacks a closing or an opening parenthesis. |
| 0x4033C35A | WS-Management 服务不支持对枚举执行同时拉操作。 |
The WS-Management service does not support concurrent pull operations for enumerations. |
| 0x4033C35B | WS-Management 服务无法处理该请求。在 WS-Management 编录中找不到资源 URI (%1)。该编录包含描述资源或逻辑终结点的元数据。 |
The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Managementcatalog. The catalog contains the metadata that describes resources, or logical endpoints. |
| 0x4033C35C | 未使用。将被删除。 |
Not used. To be removed. |
| 0x4033C35D | WS-Management 服务无法处理该请求。资源 URI 不支持 %1 操作。 |
The WS-Management service cannot process the request. The resource URI does not support the %1 operation. |
| 0x4033C35E | WS-Management 服务无法处理该请求。操作 ID %1 大于期望值。 |
The WS-Management service cannot process the request. The operation id %1 is larger than expected. |
| 0x4033C35F | ProvSysException，ErrorCode=%1!d!， Message=%2。 |
ProvSysException, ErrorCode=%1!d!, Message=%2. |
| 0x4033C360 | 函数“%1”意外失败。错误=%2!d!。 |
The function: \"%1\" failed unexpectedly. Error=%2!d!. |
| 0x4033C361 | 函数“%1”意外失败。错误=%2!d!，GetLastError=%3!d!。 |
The function \"%1\" failed unexpectedly. Error=%2!d!, GetLastError=%3!d!. |
| 0x4033C362 | 函数“%1”意外失败。Hresult=%2!X!。 |
The function \"%1\" failed unexpectedly. Hresult=%2!X!. |
| 0x4033C363 | 无法从 %1 访问 WS-Management 编录。该编录包含描述资源或逻辑终结点的元数据。 |
Could not access the WS-Management catalog from %1. The catalog contains the metadata that describesresources, or logical endpoints. |
| 0x4033C364 | 函数“%1”意外失败。GetLastError=%2!d!。 |
The function: \"%1\" failed unexpectedly. GetLastError=%2!d!. |
| 0x4033C365 | 来自内部函数“%1”的意外结果。%nGetLastError: %2!d!。%n文件: %3:%4!d! %n |
Unexpected result from internal function: \"%1\".%nGetLastError: %2!d!.%nFile: %3:%4!d! %n |
| 0x4033C366 | 调用函数“%1”时提供了无效参数。 |
A call to the function \"%1\" supplied an invalid parameter. |
| 0x4033C367 | 调用函数“%1”时提供了无效参数。无效参数= %2。 |
A call to the function \"%1\" supplied an invalid parameter. The invalid parameter = %2. |
| 0x4033C368 | WS-Management 服务不支持该请求。 |
The WS-Management service does not support the request. |
| 0x4033C369 | WS-Management 找不到具有指定 ID (%1)的数据源。 |
The WS-Management cannot locate the data source with the specified id (%1). |
| 0x4033C36A | WS-Management 服务无法处理该请求。未决请求数已超出允许的最大数目。 |
The WS-Management service cannot process the request. The number of outstanding requests exceeds themaximum number allowed. |
| 0x4033C36B | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-ManagementResourceURI 元素无效、重复或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains a WS-ManagementResourceURI element that is either invalid, duplicated, or too long. |
| 0x4033C36C | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-AddressingMessageID 元素无效、重复或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains a WS-AddressingMessageID element that was either invalid, duplicated, or too long. |
| 0x4033C36D | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-AddressingTo 元素无效、重复或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains a WS-AddressingTo element that was either invalid, duplicated, or too long. |
| 0x4033C36E | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-Addressing Action元素无效、重复或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing Actionelement that is either invalid, duplicated, or too long. |
| 0x4033C36F | WS-Management 服务无法处理该请求。SOAP 数据包没有有效的 WS-Addressing ReplyTo 元素。该元素重复或不是 WS-Addressing 匿名 URI。http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous。 |
The WS-Management service cannot process the request. The SOAP packet does not contain a validWS-Addressing ReplyTo element. The element is duplicated or is not the WS-Addressing anonymous URI.http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous. |
| 0x4033C370 | WS-Management 服务无法处理该请求。SOAP 数据包没有有效的 WS-AddressingFaultTo 元素。该元素重复或不是 WS-Addressing 匿名 URI。http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous。 |
The WS-Management service cannot process the request. The SOAP packet does not contain a valid WS-AddressingFaultTo element. The element is duplicated or is not the WS-Addressing anonymous URI.http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous. |
| 0x4033C371 | WS-Management 服务无法处理该请求。SOAP 数据包没有有效的 WS-ManagementLocale 元素。该元素重复或与系统的区域设置不匹配。 |
The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-ManagementLocale element. The element is duplicated or does not match the system locale. |
| 0x4033C372 | WS-Management 服务无法处理该请求。SOAP 数据包没有有效的枚举上下文 ID 元素。传入的 Pull 或 Release 数据包应该有包含 WS-Enumeration EnumerationContext 的主体项。 |
The WS-Management service cannot process the request. The SOAP packet does not contain a validenumeration context ID element. The incoming Pull or Release packet should contain a body entry containingan WS-Enumeration EnumerationContext. |
| 0x4033C373 | WS-Management 服务无法处理该请求。WS-Management 无法识别 SOAP 数据包中的枚举上下文 ID。该数据包可能已无效，或操作已超时。 |
The WS-Management service cannot process the request. WS-Management cannot identify the enumeration context IDin the SOAP packet. The packet may have been invalid, or the operation may have timed out. |
| 0x4033C374 | WS-Management 服务无法识别收到的 SOAP 数据包中的订阅上下文 ID。该数据包可能已无效，或操作已超时。 |
The WS-Management service could not identify the subscription context ID in the SOAP packet that was received.The packet may have been invalid, or the operation may have timed out. |
| 0x4033C375 | WS-Management 服务收到的 SOAP 数据包包含执行 %1 操作的请求。该操作要求主体中只有一个元素。在 SOAP 主体中发现的元素数为 %2!d!。 |
The WS-Management service received a SOAP packet that contained a request to do a %1 operation.This operation requires a single element in the body.Number of elements found in the soap body was %2!d!. |
| 0x4033C376 | WS-Management 服务无法处理该请求。SOAP 数据包包含执行 %1 操作的请求。该操作要求主体中只有一个元素。 |
The WS-Management service cannot process the request. The SOAP packet contains the request to do a %1 operation.This operation requires a single element in the body. |
| 0x4033C377 | WS-Management 服务无法处理该请求。SOAP 数据包不具有要求的所有字段。 |
The WS-Management service cannot process the request. The SOAP packet does not have all the fields that are required. |
| 0x4033C378 | WS-Management 服务无法处理该请求。输入 XML 包含无法识别的 XML 元素:“%1”。请确保该元素名的拼写正确。 |
The WS-Management service cannot process the request. The input XML contains an unrecognized XML element: \"%1\".Ensure that the spelling of the element name is correct. |
| 0x4033C379 | WS-Management 服务无法处理该配置请求。XML 元素 %1 必须包含子元素，但是不存在任何子元素。 |
The WS-Management service cannot process the configuration request. XML element %1 must contain sub-elementsand none are present. |
| 0x4033C37A | WS-Management 服务无法处理该请求。XML 包含的布尔值“%1”无效。有效布尔值为 \"true\"、\"false\"、\"1\" 或 \"0\"。 |
The WS-Management service cannot process the request. The XML contains an invalid booleanvalue: \"%1\". Valid boolean values are \"true\", \"false\", \"1\", or \"0\". |
| 0x4033C37B | WS-Management 服务无法处理该请求。XML 包含的整数值“%1”无效。有效整数值由 \"0\" 到 \"9\" 之间的字符组成并且长度不超过 10 位。 |
The WS-Management service cannot process the request. The XML contains an invalid integer value \"%1\".Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length. |
| 0x4033C37C | WS-Management 服务无法处理该请求。XML 包含的安全描述符“%1”无效；从 ConvertStringSecurityDescriptorToSecurityDescriptor 收到错误(%2!d!)。 |
The WS-Management service cannot process the request. The XML contains an invalid securitydescriptor \"%1\";received error (%2!d!) from ConvertStringSecurityDescriptorToSecurityDescriptor. |
| 0x4033C37D | WS-Management 服务无法处理该配置请求。XML 包含的安全描述符“%1”无效。该安全描述符缺少所有者。 |
The WS-Management service cannot process the configuration request. The XML contains an invalidsecurity descriptor: \"%1\". The security descriptor is missing an owner. |
| 0x4033C37E | WS-Management 服务无法处理该配置请求。XML 包含的安全描述符“%1”无效。该安全描述符缺少组。 |
The WS-Management service cannot process the configuration request. The XML contains an invalidsecurity descriptor: \"%1\". The security descriptor is missing a group. |
| 0x4033C37F | WS-Management 服务无法处理该配置请求。XML 包含的安全描述符“%1”无效。该安全描述符缺少随机访问控制列表(DACL)。 |
The WS-Management service cannot process the configuration request. The XML contains an invalidsecurity descriptor: \"%1\". The security descriptor is missing a discretionary access control list (DACL). |
| 0x4033C380 | WS-Management 服务无法处理该配置请求。XML 包含的安全描述符“%1”无效。WS-Management 不支持访问控制项(ACE)类型: %2!d!。 |
The WS-Management service cannot process the configuration request. The XML contains an invalidsecurity descriptor: \"%1\". WS-Management does not support the access control entry (ACE) type: %2!d!. |
| 0x4033C381 | 安全描述符“%1”无效；访问权限必须是GR (generic read = WSManGet, WSManEnumerate, WSManSubscribe)、GW (generic write = WSManPut, WSManCreate, WSManDelete)或GX (generic execute = WSManInvoke)GA (generic all)的组合 |
Invalid security descriptor \"%1\"; access rightmust be a combination ofGR (generic read = WSManGet, WSManEnumerate, WSManSubscribe),GW (generic write = WSManPut, WSManCreate, WSManDelete), orGX (generic execute = WSManInvoke)GA (generic all) |
| 0x4033C382 | WS-Management 服务无法处理该配置请求。请求的设置为空。%1 不能为 \"\"(空白或空字符)或 NULL。 |
The WS-Management service cannot process the configuration request.The request has a blank setting. %1 cannot be \"\" (blank or empty string) or NULL. |
| 0x4033C383 | WS-Management 服务无法处理该配置请求。WS-Management 配置收到无效的 URL。URL 前缀不能以“/”开头或结尾。 |
The WS-Management service cannot process the configuration request. WS-Management configuration receivedan invalid URL. The URL prefix cannot start or end with a '/'. |
| 0x4033C384 | WS-Management 服务无法处理该配置请求。XML 包含具有无效字符的 URL。URL 前缀不能包含 %1!c!。 |
The WS-Management service cannot process the configuration request. The XML contains a URL with an invalidcharacter. The URL prefix cannot contain %1!c!. |
| 0x4033C385 | WS-Management 服务无法处理该配置请求。XML 包含无效整数设置 %1，其值 %2!lu! 太小。该值不能小于 %3!lu!。 |
The WS-Management service cannot process the configuration request. The XML contains an invalid integersetting: %1 that is too small: %2!lu!. The value must be %3!lu! or more. |
| 0x4033C386 | WS-Management 服务无法处理该配置请求。XML 包含无效整数设置 %1，其值 %2!lu! 太大。该值不能大于 %3!lu!。 |
The WS-Management service cannot process the configuration request. The XML contains an invalid integer setting: %1that is too large: %2!lu!. The value must be %3!lu! or less. |
| 0x4033C387 | WS-Management 服务无法处理该请求。XML 包含无效端口号 %1!lu!。该值不能小于 %2!lu!。 |
The WS-Management service cannot process the request. The XML contains an invalid port number: %1!lu! Thevalue must be %2!lu! or more. |
| 0x4033C388 | WS-Management 服务无法处理该请求。XML 包含无效端口号，其值 %1!lu! 太大。该值不能大于 %2!lu!。 |
The WS-Management service cannot process the request. The XML contains an invalid port number that istoo large: %1!lu! The value must be %2!lu! or less. |
| 0x4033C389 | WS-Management 服务无法处理该配置请求。XML 包含的设置类型 %1!d! 无效。 |
The WS-Management service cannot process the configuration request. The XML contains an invalid setting type: %1!d!. |
| 0x4033C38A | WS-Management 服务无法处理该配置请求。XML 包含的设置 %1!d! 无效。 |
The WS-Management service cannot process the configuration request. The XML contains an invalid setting: %1!d!. |
| 0x4033C38B | WS-Management 服务无法处理该配置请求。XML 包含无效设置 %1。该值大于最大长度 %2!d! |
The WS-Management service cannot process the configuration request. The XML contains an invalid setting %1. Thevalue is longer than the maximum length of %2!d! |
| 0x4033C38C | WS-Management 服务无法处理该配置请求，因为它无法启用 %1 特权。对注册表项设置安全级别需要该特权。错误代码为 %2!d!。 |
The WS-Management service cannot process the configuration request because it cannot enable the %1 privilege.This privilege is required to set security on registry keys. The error code is %2!d!. |
| 0x4033C38D | WS-Management 服务无法处理该配置请求，因为它无法打开注册表项。错误代码为 %1!d!。 |
The WS-Management service cannot process the configuration request because it cannot open a registry key.The error code is %1!d!. |
| 0x4033C38E | WS-Management 服务无法处理该配置请求。XML 包含未知的 URI: %1。 |
The WS-Management service cannot process the configuration request. The XML contains an unknown URI: %1. |
| 0x4033C38F | WS-Management 服务无法处理该配置请求。XML 包含重复的元素: %1。 |
The WS-Management service cannot process the configuration request. The XML contains a repeated element: %1. |
| 0x4033C390 | WS-Management 服务无法处理该配置请求。XML 包含的元素 %1 很复杂。WS-Management 配置需要简单的元素。 |
The WS-Management service cannot process the configuration request. The XML contains a complexelement: %1. WS-Management configuration requires a simple element. |
| 0x4033C391 | WS-Management 服务无法处理该配置请求。XML 包含的元素 %1 很简单。WS-Management 配置需要复杂的元素。 |
The WS-Management service cannot process the configuration request. The XML contains a simple element: %1.WS-Management configuration requires a complex element. |
| 0x4033C392 | WS-Management 服务无法处理该配置请求。WS-Addressing Action URI (%1)与资源 URI (%2)不匹配。%3 操作只能用于资源 %4。 |
The WS-Management service cannot process the configuration request. The WS-Addressing Action URI (%1) andresource URI (%2) do not match. The %3 action can only be used on the %4 resource. |
| 0x4033C393 | WS-Management 服务无法处理该配置请求。此操作要求输入 XML 的元素名为 %1 并且没有参数。 |
The WS-Management service cannot process the configuration request. This action requires input XML with an element name of %1 and no parameters. |
| 0x4033C395 | WS 管理服务无法处理该请求。用户不具有在 %2 资源上执行 %1 操作的权限。 |
The WS-Management service cannot process the request. The user does not have permission for the %1 operationon the %2 resource. |
| 0x4033C396 | WS-Management 服务无法处理该请求。XML 的 SOAP 标头 %1 中包含无效超时字段。 |
The WS-Management service cannot process the request. The XML contains an invalid timeout field in the SOAP header: %1. |
| 0x4033C397 | WS-Management 服务无法处理该请求。URI 不包含关键字，但是该类不是 Singleton 类。 |
The WS-Management service cannot process the request. The URI does not contain keys, but the class is not a singleton. |
| 0x4033C398 | WS-Management 服务无法处理该请求。XML 包含的超时值 %1!lu! 太小。该超时值必须大于 %2!lu!。 |
The WS-Management service cannot process the request. The XML contains a timeout value thatis too small: %1!lu!. The timeout value must be larger than %2!lu!. |
| 0x4033C399 | WS-Management 服务无法处理该请求。SOAP 标头 %1 包含 mustUnderstand 属性，但是它对于此 WS-Management 实现是一个未知标头。这可能是由于使用了不受支持的协议版本而造成的，或者可能是客户端和服务器实现之间不兼容。 |
The WS-Management service cannot process the request. The SOAP header %1 contains the mustUnderstand attribute, but it is not a known header by this WS-Management implementation. This could be caused by the use of a version of the protocol which is not supported, or may be an incompatibility between the client and server implementations. |
| 0x4033C39A | WS-Management 服务无法处理该请求。SOAP 批参数 %1 无效。 |
The WS-Management service cannot process the request. The SOAP batch parameter %1 is invalid. |
| 0x4033C39B | WS-Management 服务无法处理该请求。SOAP 数据包没有有效的 Timeout 元素、重复或持续时间不是有效的 xs:Duration。例如，超时 PT30S 为 30 秒。 |
The WS-Management service cannot process the request. The SOAP packet did not contain a valid Timeoutelement, was duplicated or the duration was not a valid xs:Duration. For example, the timeout PT30S is 30 seconds. |
| 0x4033C39C | |
|
| 0x4033C39D | WS-Management 服务无法处理该请求。数据源未能返回结果。 |
The WS-Management service cannot process the request. The data source failed to return the result. |
| 0x4033C39E | WS-Management 服务无法处理该请求。数据源未能从操作返回结果 URI 以创建新的实例。 |
The WS-Management service cannot process the request. The data source failed to return the result URI from anoperation to create a new instance. |
| 0x4033C39F | WS-Management 无法连接到指定的目标: (%1:%2!d!)。 |
WS-Management could not connect to the specified destination: (%1:%2!d!). |
| 0x4033C3A0 | 操作已中止。 |
The operation was aborted. |
| 0x4033C3A1 | WS-Management 无法处理该请求。操作由于 HTTP 错误而失败。HTTP 错误(%1!lu!)为: %2。 |
WS-Management cannot process the request. The operation failed because of an HTTP error.The HTTP error (%1!lu!) is: %2. |
| 0x4033C3A2 | 目标计算机(%1:%2!d!)上的服务器证书包含以下错误: %3 %4 %5 %6 %7 %8 %9 %10 |
The server certificate on the destination computer (%1:%2!d!) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10 |
| 0x4033C3A3 | WS-Management 无法处理该请求。目标计算机(%1:%2!d!)返回“拒绝访问”错误。 |
WS-Management cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error. |
| 0x4033C3A4 | WS-Management 无法处理该请求。从目标计算机得到的 HTTP 响应的格式与请求的格式不同。已发送的可能是 Unicode 请求数据包，而收到的是 ANSI 数据包。 |
WS-Management cannot process the request. The HTTP response from the destinationcomputer was not in the same format as the request. A Unicode request packet may have been sent and anANSI packet received. |
| 0x4033C3A5 | 客户端在发送到目标计算机的请求中指定了用户名和密码。但是目标计算机请求的是客户端证书。 |
The client specified username and password in the request to the destination computer. But the destinationcomputer requested a client certificate. |
| 0x4033C3A6 | WS-Management 无法处理该请求。从目标计算机接收的响应包含元素 %1。但是此元素与期望的元素不匹配。 |
WS-Management cannot process the request. The response received from the destination computerincludes element %1. But this element does not match what is expected. |
| 0x4033C3A7 | WS-Management 无法处理该请求。目标计算机发送的响应中缺少元素 %1。 |
WS-Management cannot process the request. The element %1 is missing from the responsesent by the destination computer. |
| 0x4033C3A8 | WS-Management 遇到无效的内部参数。 |
WS-Management encountered an invalid internal parameter. |
| 0x4033C3A9 | WS-Management 服务无法处理该配置请求，因为请求中的证书指纹不是有效的十六进制字符串: %1。 |
The WS-Management service cannot process the configuration request because the certificatethumbprint in the request is not a valid hex string: %1. |
| 0x4033C3AA | WS-Management 服务不支持同时传递多个事件操作。 |
The WS-Management service does not support concurrent event delivery operations. |
| 0x4033C3AB | WS-Management 服务遇到内部错误。 |
The WS-Management service encountered an internal error. |
| 0x4033C3AC | WS-Management 服务无法处理该请求。从目标计算机得到的响应无效。 |
The WS-Management service cannot process the request. The response from the destination computer is invalid. |
| 0x4033C3AD | WS-Management 服务无法处理该请求，因为它找不到请求的系统。 |
The WS-Management service cannot process the request because it cannot find the requested System. |
| 0x4033C3AE | WS-Management 服务无法处理该请求，因为 URI 包含WS-Management 无法处理的错误关键字。 |
The WS-Management service cannot process the request because the URI contains incorrect keys that WS-Managementcannot process. |
| 0x4033C3AF | WS-Management 服务无法处理该请求，因为端口 %1 无效。 |
The WS-Management service cannot process the request because port %1 is invalid. |
| 0x4033C3B0 | WS-Management 服务无法处理该请求，因为 IP 地址 %1 无效。 |
The WS-Management service cannot process the request because IP address %1 is invalid. |
| 0x4033C3B1 | WS-Management 服务无法处理该配置请求，因为该服务不支持传输: %1。该值应为可接受的值之一: %2。 |
The WS-Management service cannot process the configuration request because the transport is not supportedby the service: %1. The value should be one of the accepted values: %2. |
| 0x4033C3B2 | WS-Management 服务无法处理该配置请求，因为配置静态侦听地址要求 MAC 地址设置为空。 |
The WS-Management service cannot process the configuration request because the configurationfor a static listening address requires an empty MAC address setting. |
| 0x4033C3B3 | WS-Management 服务无法处理该请求，因为 SOAP 数据包包含无效或重复的 WS-Management SelectorSet 元素。 |
The WS-Management service cannot process the request because the SOAP packet contained an invalidor duplicate WS-Management SelectorSet element. |
| 0x4033C3B4 | 数据源遇到错误: %1。 |
The data source encountered the error: %1. |
| 0x4033C3B5 | WS-Management 服务无法处理该配置请求。在配置侦听程序之后，不能更改 IP 地址或端口号的值。 |
The WS-Management service cannot process the configuration request. After a listener is configured,you cannot change the value of the IP address or of the port number. |
| 0x4033C3B6 | WS-Management 服务收到无效的 SOAP 数据包。该数据包包含无效的 WS-Management Delivery 模式或缺少 WS-Management Delivery 模式。 |
The WS-Management service received an invalid SOAP packet. The packet contains an invalid or missing WS-Management Delivery mode. |
| 0x4033C3B7 | WS-Management 服务无法处理该配置请求。配置动态 IP 地址需要 MAC 地址设置。 |
The WS-Management service cannot process the configuration request. The configuration of a dynamic ipaddress requires a MAC address setting. |
| 0x4033C3B8 | WS-Management 服务无法处理该配置请求。IP %1 和端口 %2 的 SSL 配置属于其他服务，无法共享。 |
The WS-Management service cannot process the configuration request. The SSL configuration for IP %1 andport %2 is owned by another service and cannot be shared. |
| 0x4033C3B9 | WS-Management 服务无法处理该请求。选择器 %1 的值无效。 |
The WS-Management service cannot process the request. The value for the selector %1 is invalid. |
| 0x4033C3BA | WS-Management 服务无法处理该请求，因为信封大小上限标头无效或重复。 |
The WS-Management service cannot process the request because the maximum envelope size header was invalid or duplicated. |
| 0x4033C3BB | WS-Management 服务无法处理该请求，因为请求的信封大小上限(%1!lu!)太小。大小不能小于 %2!lu!。 |
The WS-Management service cannot process the request because the maximum envelope size requestedis (%1!lu!) too small. The size must be %2!lu! or larger. |
| 0x4033C3BC | WS-Management 服务无法处理该请求，因为请求的信封大小上限(%1!lu!)太大。大小不能大于 %2!lu!。 |
The WS-Management service cannot process the request because the maximum envelope size requestedis (%1!lu!) too large. The size must be %2!lu! or smaller. |
| 0x4033C3BD | WS-Management 服务无法处理该请求，因为超时值 %1!lu! 太大。超时值必须小于 %2!lu!。 |
The WS-Management service cannot process the request because the timeout value is too large: %1!lu! Thetimeout value must be less than %2!lu!. |
| 0x4033C3BE | WS-Management 服务无法处理该请求。计算出的响应数据包大小(%1!lu!)超过允许的信封大小上限(%2!lu!)。 |
The WS-Management service cannot process the request. The computed response packet size (%1!lu!)exceeds the maximum envelope size that is allowed (%2!lu!). |
| 0x4033C3BF | 函数“%1”中的算术运算失败。错误代码为 %2!d!。 |
An arithmetic operation failed in function \"%1\". The error code is %2!d!. |
| 0x4033C3C0 | WS-Management 服务无法处理该请求。网络适配器的 MAC 地址没有动态 IP 地址。 |
The WS-Management service cannot process the request. The MAC address for the networkadapter does not have the dynamic IP address. |
| 0x4033C3C1 | WS-Management 服务无法处理该枚举请求。服务器已经在执行最大数目的枚举。请稍后重试。 |
The WS-Management service cannot process the enumeration request. The server is already executingthe maximum number of enumerations. Retry later. |
| 0x4033C3C2 | WS-Management 服务无法处理该请求，因为终结点引用未包含 WS-Addressing Address 元素。 |
The WS-Management service cannot process the request because the Endpoint Reference doesnot contain a WS-Addressing Address element. |
| 0x4033C3C3 | WS-Management 服务无法处理该请求，因为终结点引用(EPR)中的 WS-Addressing Address 包含一个或多个意外的子元素。 |
WS-Management service cannot process the request because the WS-Addressing Address in theEndpoint Reference (EPR) contains one or more unexpected child elements. |
| 0x4033C3C4 | WS-Management 服务无法处理该请求，因为 WS-Addressing EndPointReference (EPR)包含意外的 XML 元素。 |
The WS-Management service cannot process the request because the WS-Addressing EndPointReference (EPR)contained an unexpected XML element. |
| 0x4033C3C6 | WS-Management 服务无法处理该请求，因为 WS-Addressing EndPointReference包含重复的子元素: %1。 |
The WS-Management service cannot process the request because the WS-Addressing EndPointReferencecontains a repeated child element: %1. |
| 0x4033C3C7 | 未使用。 |
Not used. |
| 0x4033C3C8 | WS-Management 服务无法处理该请求，因为该服务不支持操作 %1。 |
The WS-Management service cannot process the request because the service does not support the action: %1. |
| 0x4033C3C9 | WS-Management 服务无法处理该请求，因为筛选器或方言中包含语法错误，或者包含 WS-Enumeration 和 WS-Management 版本的过滤器、其他语义问题，或者过于复杂。 |
The WS-Management service cannot process the request because the filter or dialect has syntax errors,contains both a WS-Enumeration and WS-Management version of the filter, other semantic problems, or istoo complex. |
| 0x4033C3CA | 数据源无法将其他项目添加到 WS-Management 消息信封，原因是批中的单个元素超过了信封大小。 |
The data source cannot add another item to a WS-Management message envelope because a singleelement in the batch exceeded the envelope size. |
| 0x4033C3CB | WS-Management 服务无法处理该请求。WS-Management 收到的 SOAP 数据包没有有效的 %1 元素。 |
The WS-Management service cannot process the request. The SOAP packet that WS-Management receiveddid not contain a valid %1 element. |
| 0x4033C3CC | WS-Management 服务无法处理该请求，因为 SOAP 数据包中的 XML 无效。 |
The WS-Management service cannot process the request because the XML in the SOAP packet is invalid. |
| 0x4033C3CD | WS-Management 服务无法处理该请求。从 CIM 路径生成的 URI 太长。支持的最大长度为 %1!d! 个字符。 |
The WS-Management service cannot process the request. The URI generated from the CIM path is too long.The maximum supported length is %1!d! characters. |
| 0x4033C3CE | WS-Management 服务无法处理该请求。类 %3 的实例中的关键字 %2 具有意外 CIM 类型。 |
The WS-Management service cannot process the request. The key %2 in an instance of class %3 has an unexpected CIM type. |
| 0x4033C3CF | WS-Management 服务无法处理该请求，原因是该请求包含嵌入式对象或嵌入式对象数组。WS-Management 不支持检索或更新包含嵌入式对象或嵌入式对象数组的实例。 |
The WS-Management service cannot process the request because the request contains an embedded object orarray of embedded objects. WS-Management does not support retrieving or updating instances containingembedded objects or arrays of embedded objects. |
| 0x4033C3D0 | WS-Management 服务无法处理该请求，原因是 WMI 实例包含无效的 char16 值 %1。 |
The WS-Management service cannot process the request because a WMI instance contains an invalid char16 value: %1. |
| 0x4033C3D1 | WS-Management 服务无法处理该请求，原因是 XML 包含属性 %1 的未知 CIM 类型。 |
The WS-Management service cannot process the request because the XML contains an unknown CIM type for the property: %1. |
| 0x4033C3D2 | WS-Management 服务无法处理该请求，原因是 XML 的 WMI 实例中包含无效的日期时间值(%1)。 |
The WS-Management service cannot process the request because the XML contains an invalid datetime value (%1) ina WMI instance. |
| 0x4033C3D3 | WS-Management 服务无法处理该请求。该请求包含不代表字符串属性的 XML 元素(%1)。只有字符串属性可以为空。若要指定空值，请将 xsi:nil属性添加到该元素中。 |
The WS-Management service cannot process the request. The request contains an XML element (%1) that does notrepresent a string property. Only string properties can be empty. To specify a null value, add the xsi:nilattribute to the element. |
| 0x4033C3D4 | WS-Management 服务无法处理该请求。如果将数组属性设置为 null，则输入 XML 中只能有一个具有该名称的元素。属性: %1。 |
The WS-Management service cannot process the request. When setting an array property to null, onlyone element with that name can be present in the input XML. Property: %1. |
| 0x4033C3D5 | WS-Management 服务无法处理该请求，原因是对于不是数组的属性，它包含多个同名的 XML 元素。属性: %1。 |
The WS-Management service cannot process the request because it contains several XML elements withthe same name for a property that is not an array. Property: %1. |
| 0x4033C3D6 | WS-Management 服务无法处理该请求，原因是它的实例或类上属性限定符的类型无效。属性: %2 限定符: %1。 |
The WS-Management service cannot process the request because it contains an invalid type for aproperty qualifier on an instance or on the class. Property: %2 Qualifier: %1. |
| 0x4033C3D7 | WS-Management 服务无法处理该请求，原因是它包含的用于代表数字的空字符串无效。 |
The WS-Management service cannot process the request because it contains an invalid empty stringfor representing a number. |
| 0x4033C3D8 | WS-Management 服务无法处理该请求，因为它包含无效字符。WS-Management 无法将字符串转换为数字。字符串: %1。确保该字符串代表正确的数据类型。 |
The WS-Management service cannot process the request because it contains an invalid character.WS-Management cannot convert the string to a number. String: %1. Ensure that the string represents the correct datatype. |
| 0x4033C3D9 | WS-Management 服务无法处理该请求。WS-Management 无法将字符串转换为无符号数。该请求包含不应有的减号。字符串: %1。确保该字符串代表正确的数据类型。 |
The WS-Management service cannot process the request. WS-Management cannot convert a string to an unsignednumber. The request contains an unexpected minus sign. String: %1. Ensure that the string represents the correct datatype. |
| 0x4033C3DA | WS-Management 服务无法处理该请求，因为该服务无法将字符串 %1 转换为包含 %2!d! 位的数。该字符串代表的数字不在允许的范围内。确保该字符串代表正确的数据类型。 |
The WS-Management service cannot process the request because the service cannot convert string %1 to anumber with %2!d! bits. The string does not represent a number in the allowed range. Ensure that the stringrepresents the correct datatype. |
| 0x4033C3DB | WS-Management 服务无法处理该请求，因为该请求中的元素 %2 的布尔值(%1)无效。值必须是 \"true\"、\"false\"、\"1\" 或 \"0\"。 |
The WS-Management service cannot process the request because the request contains an invalid booleanvalue (%1) for element %2. The value must contain \"true\", \"false\", \"1\", or \"0\". |
| 0x4033C3DC | WS-Management 服务无法处理该请求。名为 %1 的数组的元素包含 xsi:nil 属性。该数组不能具有 NULL 元素。 |
The WS-Management service cannot process the request. An element of the array named %1 containsthe xsi:nil attribute. The array cannot have a NULL element. |
| 0x4033C3DD | WS-Management 服务无法处理该请求。XML 包含无效的 xs:Duration 字符串: %1。 确保该字符串代表正确的数据类型。 |
The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1.Ensure that the string represents the correct datatype. |
| 0x4033C3DE | WS-Management 服务无法处理该请求。XML 包含无效的 xs:duration 字符串: %1。CIM 日期时间类型不允许超过 99999999 天。 |
The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1.CIM datetime type does not accept more than 99999999 days. |
| 0x4033C3DF | WS-Management 服务无法处理该请求。该请求包含无效的日期时间。字符串 %1 不代表下列任何类型: xs:dateTime、xs:date 或 xs:time。 |
The WS-Management service cannot process the request. The request contains an invalid datetime.The string %1 does not represent any of these types: xs:dateTime, xs:date, or xs:time. |
| 0x4033C3E0 | WS-Management 服务无法处理该请求，因为它的系统属性 %1 的值无效。该值不是字符串或是空字符串。 |
The WS-Management service cannot process the request because it contains an invalid value for asystem property: %1. The value is not a string or it is an empty string. |
| 0x4033C3E1 | WS-Management 服务无法处理该请求，因为 XML 简单内容无效: %1。 |
The WS-Management service cannot process the request because the XML simple content is invalid: %1. |
| 0x4033C3E2 | WS-Management 服务无法处理该请求，因为类具有无效的 Singleton 限定符。 该类是 %1。类型不是布尔型，或者值不是 \"TRUE\"。 |
The WS-Management service cannot process the request because a class has an invalid Singleton qualifier.The class is %1. The type is not boolean or the value is not 'TRUE'. |
| 0x4033C3E3 | WS-Management 服务无法处理该请求。日期时间值的元素必须正好包含一个子元素，不能有混合的内容。 |
The WS-Management service cannot process the request. The element for adatetime value must have exactly one child and no mixed content. |
| 0x4033C3E4 | WS-Management 服务无法处理该请求。日期时间属性中的元素的名称 %1 不正确。 |
The WS-Management service cannot process the request. An element in a datetime property has an incorrect name: %1. |
| 0x4033C3E5 | WS-Management 服务无法处理该请求，因为它无法将字符串(%1)转换为双精度类型值。请确保该字符串代表的类型正确。 |
The WS-Management service cannot process the request because it cannot convert the string (%1) to a double value.Ensure that the type that the string represents is correct. |
| 0x4033C3E6 | WS-Management 服务无法处理该请求，因为它无法将字符串(%1)转换为浮点型值。该值太大。请确保该字符串代表的类型正确。 |
The WS-Management service cannot process the request because it cannot convert the string (%1) to a floatingpoint value. The value is too large. Ensure that the type that the string represents is correct. |
| 0x4033C3E7 | 终结点引用值的元素必须包含并且只能包含一个子元素。 |
The element for a endpoint reference value must have one and only one child. |
| 0x4033C3E8 | WS-Management 服务无法处理该请求。操作 URI (%1)无效。在类 %3 中不存在方法 %2。 |
The WS-Management service cannot process the request. The action URI (%1) is invalid. Method %2 does not exist in class %3. |
| 0x4033C3E9 | WS-Management 服务无法处理该请求。数组属性(%1)元素的顺序必须是连续的。 |
The WS-Management service cannot process the request. The elements for an array property (%1) must be in consecutive order. |
| 0x4033C3EA | WS-Management 服务无法处理该配置请求。IP %1 和端口 %2 的 SSL 配置与其他服务共享。相互配置的客户端证书必须映射至用户帐户。其他服务没有此 http 配置。 |
The WS-Management service cannot process the configuration request. The SSL configurationfor IP %1 and port %2 is shared with another service. Client certificates for Mutual configurationmust map to a user account. The other service does not have this http configuration. |
| 0x4033C3EB | WS-Management 服务未能设置用于用户身份验证的用户证书。 |
The WS-Management service failed to set the user certificate for user authentication. |
| 0x4033C3EC | WS-Management 服务无法保证返回请求的区域设置中的所有数据，因为某些数据源可能不符合要求。使用区域设置作为提示重新发送远程请求(SOAP 标头应包含mustUnderstand=\"false\")。 |
The WS-Management service cannot guarantee that all data is returned in the requested locale as some data sourcesmay not be able to comply. Resend the remote request with locale as a hint (the SOAP header should havemustUnderstand=\"false\"). |
| 0x4033C3ED | WS-Management 服务无法执行该配置操作。已存在具有 Address=%1 和 Transport=%2 配置的侦听程序。必须先删除现有的侦听程序才能使用相同的 Address和 Transport 值创建侦听程序。 |
The WS-Management service cannot perform the configuration operation. A listener with Address=%1 and Transport=%2configuration already exists. You have to delete the existing listener first in order to be able to create it with the same Addressand Transport values. |
| 0x4033C3EE | WS-Management 服务无法处理该请求，因为终结点引用未包含 WS-Management ResourceURI 元素。 |
The WS-Management service cannot process the request because the Endpoint Reference doesnot contain a WS-Management ResourceURI element. |
| 0x4033C3EF | 元素(%1)中缺少 xsi:type 属性。嵌入式对象需要该属性。 |
The xsi:type attribute is missing from element (%1). This attribute is required for embedded objects. |
| 0x4033C3F0 | WS-Management FragmentTransfer 元素没有文本内容。 |
The WS-Management FragmentTransfer element has no text content. |
| 0x4033C3F1 | WS-Management FragmentTransfer 元素包含一个或多个子元素。 |
The WS-Management FragmentTransfer element contains one or more child elements. |
| 0x4033C3F2 | 收到的 SOAP 数据包没有有效的 WS-Management FragmentTransfer 元素或该元素重复。 |
The SOAP packet that was received did not contain a valid WS-Management FragmentTransfer element, or was duplicated. |
| 0x4033C3F3 | 从目标机器收到的响应包含意外元素 %1。 |
The response received from the destination machine includes unexpected element %1. |
| 0x4033C3F4 | 没有为给定方言指定筛选器。 |
There is no filter specified for the given dialect. |
| 0x4033C3F5 | 给定命名空间中没有指定类。 |
The specified class does not exist in the given namespace. |
| 0x4033C3F6 | 没有找到具有给定属性值的实例。 |
No instance found with given property values. |
| 0x4033C3F7 | WS-Management 服务无法处理该请求。WQL 查询无效。 |
The WS-Management service cannot process the request.The WQL query is invalid. |
| 0x4033C3F8 | 策略设置 %1 无效；指定的值 %2!lu! 低于所需的最小值 %3!lu!。 |
Invalid policy setting %1;The specified value %2!lu! is below the minimum required value of %3!lu!. |
| 0x4033C3F9 | 策略设置 %1 无效；值必须小于 %3!lu!，但给出的是 %2!lu! |
Invalid policy setting %1;value must be no larger than %3!lu!, but given %2!lu! |
| 0x4033C3FA | 策略设置 %1 无效；策略类型错误。 |
Invalid policy setting %1; the policy has the wrong type. |
| 0x4033C3FB | 策略设置 %1 无效； |
Invalid policy setting %1; |
| 0x4033C3FC | 侦听程序地址 %1 无效。 |
Invalid listener address %1. |
| 0x4033C3FD | 解析下列路径片断时发生异常(%1!d!): %2。 |
An exception was thrown (%1!d!) while parsing the following fragment path : %2. |
| 0x4033C3FE | 下列路径片断的位置 %1!d! 出现语法错误: %2。 |
Syntax error at position %1!d! for the following fragment path : %2. |
| 0x4033C3FF | 下列路径片断的位置 %1!d! 出现词法错误: %2。 |
Lexical error at position %1!d! for the following fragment path : %2. |
| 0x4033C400 | 下列路径片断的位置 %2!d! 出现解析错误(%1!d!): %3。 |
Parsing error (%1!d!) at position %2!d! for the following fragment path : %3. |
| 0x4033C401 | 绝对路径片断必须以资源 URI 中存在的类名称开头。 |
An absolute fragment path must start with the class name present in the resource URI. |
| 0x4033C402 | 节点 %1 无效: 前一个节点必须对应于 WMI 对象而此节点必须是该对象的一个属性，或者前一个节点必须对应于 datetime 属性而此节点必须具有下列值之一(Datetime、Date、Time、Interval 或 CIM_DateTime)。 |
Node %1 is invalid : the previous node must correspond to a WMI object and this node must a property of that objector the previous node must correspond to a datetime property and this node must have one of these values(Datetime, Date, Time, Interval or CIM_DateTime). |
| 0x4033C403 | 无法将 text() 函数应用到数组、对象、日期时间或引用属性。 |
Cannot apply text() function to array, object, datetime or reference properties. |
| 0x4033C404 | 碎片路径已选择未知属性。仅可使用 'type' 和 'nil'。 |
The fragment path selected an unknown attribute. Only 'type' and 'nil' can be used. |
| 0x4033C405 | 元素的位置必须是非零正整数。给定了值 %1!lu!。 |
The position of the element must be a non-zero positive integer. Value %1!lu! was given. |
| 0x4033C406 | 节点 %1 没有对应于数组属性；不能将位置上下文用于该节点。 |
Node %1 does not correspond to an array property; position context cannot be used for it. |
| 0x4033C407 | 路径片断选择了一个属性，但更新的属性不受支持。 |
An attribute was selected by the fragment path, but updating attributes is not supported. |
| 0x4033C408 | 输入 XML 对此碎片级别的 Put 操作无效: 它只能包含一个元素(WS-Management XmlFragment 元素)，该元素必须具有简单内容或为空；简单内容只允许用于字符串属性。 |
The input XML is not valid for this fragment-level Put operation : it must contain a single element(the WS-Management XmlFragment element), which must have a simple content or be empty; empty contentis allowed only for string properties. |
| 0x4033C409 | 节点 %1 选择了 key 属性，但关键字无法更新。 |
Node %1 selects a key property, but keys cannot be updated. |
| 0x4033C40A | 输入 XML 对此碎片级别的 Put 操作无效: 它只能包含一个元素(WS-Management XmlFragment 元素)，该元素只能具有一个名称与要更新的属性匹配的子项；仅当该操作更新字符串属性时，该子项才能具有空内容。 |
The input XML is not valid for this fragment-level Put operation : it must contain a single element(the WS-Management XmlFragment element), which must have a single child with name matching the property to be updated; the child can have empty content only if the operation updates a string property. |
| 0x4033C40B | 路径片断无法选择深于 %1!d! 级的属性。 |
The fragment path cannot select a property more than %1!d! levels deep. |
| 0x4033C40C | WS-Management 服务无法处理该请求。请求包含的选项超过了支持的最大项数(%1!d!)。 |
The WS-Management service cannot process the request. The request contains more options than maximum supported(%1!d!). |
| 0x4033C40D | WS-Management 服务无法处理该请求，因为收到的 SOAP 数据包包含的 WS-Management OptionSet元素无效或重复。 |
The WS-Management service cannot process the request because the SOAP packet that was received contained a invalid WS-Management OptionSetelement, or it was duplicated. |
| 0x4033C40E | WS-Management 服务 Wmi 插件不支持指定的 OptionSet，因为其中一个选项设置了 MustComply。 |
The WS-Management service Wmi plugin does not support the specified OptionSet because MustComply for one of the options is set. |
| 0x4033C40F | 资源 URI 不支持选项。 |
The resource URI does not support options. |
| 0x4033C410 | WS-Management 服务不支持指定的压缩方案(%1)。 |
The WS-Management service does not support the specified compression scheme (%1). |
| 0x4033C411 | 无法更改配置设置 %1，因为受策略控制。策略需要设置为“未配置”才能更改配置设置。 |
The config setting %1 cannot be changed because is controlled by policies.The policy would need to be set to \"Not Configured\" in order to change the config setting. |
| 0x4033C412 | 指定数组中没有与索引 %1!d! 对应的属性。 |
There exists no property corresponding to index %1!d! in the specified array. |
| 0x4033C413 | WS-Management 不允许更改由组策略自动创建的侦听程序。策略“允许自动配置针对 WinRm 服务的侦听程序”需要设置为“未配置”才能创建Address 和 Transport 相同的新的侦听程序或修改现有的侦听程序。 |
WS-Management does not allow changes to a listener created automatically by the group policy.The policy \"Allow Auto Configuration of listeners on WinRm service\" would need to be set to \"Not Configured\" in order to createa new listener for same Address and Transport or to modify an already existing listener. |
| 0x4033C414 | 不允许更改已配置的侦听程序的地址值或传输值。 |
It is not allowed to change the value of the address or of the transport for a configured listener. |
| 0x4033C415 | WS-Management 服务无法处理该请求，因为无法将端口号附加到服务主体名称上。要将端口号附加到远程服务器的服务主体名称上，需要实现 WINHTTP_OPTION_SPN 选项标记的 WinHTTP.dll 版本。 |
The WS-Management service cannot process the request because appending port number to service principal name cannot be executed.Appending port number to the service principal name of the remote server requires a version of WinHTTP.dll that implementsWINHTTP_OPTION_SPN option flag. |
| 0x4033C416 | 无法执行所请求的操作。使用 HTTPS 时，没有可用的默认授权方案。必须指定用户名和密码。 |
The requested operation cannot be performed. No default authorization schemes are availablewhen using HTTPS. Username and password must be specified. |
| 0x4033C417 | 路径片断包含的令牌不得超过 1023 个字符。 |
The fragment path must not contain tokens longer than 1023 characters. |
| 0x4033C418 | Windows 远程管理的单元测试插件 |
Unit test plugin for Windows Remote Management |
| 0x4033C419 | Windows 远程管理的 WMIv1 插件 |
WMIv1 plugin for Windows Remote Management |
| 0x4033C41A | Windows 远程管理的 SEL 插件 |
SEL plugin for Windows Remote Management |
| 0x4033C41B | Windows 远程管理的测试插件 |
Test plugin for Windows Remote Management |
| 0x4033C41C | Windows 命令行解释器的测试插件 |
Test plugin for Windows Command Shell |
| 0x4033C41D | Windows 远程管理的事件收集器插件 |
Event collector plugin for Windows Remote Management |
| 0x4033C41E | Windows 远程管理的内置编录插件 |
Built-in catalog plugin for Windows Remote Management |
| 0x4033C41F | WinRM 加载 %1 的插件 DLL 失败。加载路径 %2 的 DLL 时失败，错误代码为 %3!d!。插件可能不可用或 DLL 没有正确安装。 |
WinRM failed to load the plugin DLL for %1. Loading the DLL failed for thepath %2 with error code %3!d!. The plugin may be unavailable or the DLL maynot be properly installed. |
| 0x4033C420 | WinRM 无法处理该请求，因为请求丢失了标题为“%1”的元素。 |
WinRM cannot process the request because the request is missing theelement titled '%1'. |
| 0x4033C421 | WinRM 无法处理该请求，因为选择器集包含文本。选择器集只能包含“%1”元素。 |
WinRM cannot process the request because a selector set contains text.Selector sets must contain only '%1' elements. |
| 0x4033C422 | WinRM 无法处理该请求，因为选择器集包含无法识别的元素。选择器集只能包含“%1”元素。 |
WinRM cannot process the request because a selector set contains anunrecognized element. Selector sets must contain only '%1' elements. |
| 0x4033C423 | WinRM 无法处理该请求，因为“%1”元素丢失了“%2”属性。 |
WinRM cannot process the request because a '%1' element is missing a '%2'attribute. |
| 0x4033C424 | WinRM 无法处理该请求，因为选择器包含多个子元素。 |
WinRM cannot process the request because a selector contains multiple childelements. |
| 0x4033C425 | WinRM 无法处理该请求，因为选择器同时包含文本和子元素。删除文本。 |
WinRM cannot process the request because a selector contains both text and achild element. Remove the text. |
| 0x4033C426 | WinRM 无法处理该请求，因为选项集包含文本。选项集只能包含“%1”元素。 |
WinRM cannot process the request because an option set contains text. Optionsets must contain only '%1' elements. |
| 0x4033C427 | WinRM 无法处理该请求，因为选项集包含无法识别的元素。选项集只能包含“%1”元素。 |
WinRM cannot process the request because an option set contains anunrecognized element. Option sets must contain only '%1' elements. |
| 0x4033C428 | WinRM 无法处理该请求，因为选项包含多个子元素或复杂内容。 |
WinRM cannot process the request because an option contains multiple childelements or complex content. |
| 0x4033C429 | WinRM 无法处理该请求，因为关键字为“”(空白或空字符串)或 NULL。 |
WinRM cannot process the request because a key is either \"\" (blank or empty string) or NULL. |
| 0x4033C42A | WinRM 无法处理该请求，因为选项包含的名称属性为“”(空白或空字符串)或 NULL。 |
WinRM cannot process the request because an option contains a name attribute which is either \"\" (blank or empty string) or NULL. |
| 0x4033C42B | WinRM 无法处理该请求，因为 WMI 选项值为 NULL。 |
WinRM cannot process the request because a WMI option value is NULL. |
| 0x4033C42C | WinRM 无法处理该请求，因为非数组 WMI 选项出现多次。WMI 数组选项必须使用前缀 \"wmiarray:\"。 |
WinRM cannot process the request because a non-array WMI option occurred morethan once. WMI array options must use the prefix 'wmiarray:'. |
| 0x4033C42D | WinRM 无法处理该请求，因为 WMI 选项同时定义为数组选项和非数组选项。WMI 使用前缀 \"wmi:\" 只能出现一次或使用前缀 \"wmiarray:\" 至少出现一次。 |
WinRM cannot process the request because a WMI option was defined both as anarray option and as a non-array option. WMI options must occur exactly oncewith the prefix 'wmi:' or at least once with the prefix 'wmiarray:'. |
| 0x4033C42E | xsi:type 属性(%1)未标识现有类。 |
The xsi:type attribute (%1) does not identify an existing class. |
| 0x4033C42F | XML 命名空间 URI (%1)无效。有关建立 CIM 类的命名空间 URI 的信息，请查阅文档。 |
The XML namespace URI (%1) is invalid. Check the documentation for constructing the namespace URI for a CIM class. |
| 0x4033C430 | %n无法检查 SSL 证书吊销。用于检查吊销的服务器可能不可访问。 |
%nThe SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable. |
| 0x4033C431 | %nSSL 证书无效。 |
%nThe SSL certificate is invalid. |
| 0x4033C432 | %nSSL 证书已吊销。 |
%nThe SSL certificate was revoked. |
| 0x4033C433 | %nSSL 证书由未知的证书颁发机构签名。 |
%nThe SSL certificate is signed by an unknown certificate authority. |
| 0x4033C434 | %nSSL 证书包含与主机名不匹配的公用名(CN)。 |
%nThe SSL certificate contains a common name (CN) that does not match the hostname. |
| 0x4033C435 | %nSSL 证书已过期。 |
%nThe SSL certificate is expired. |
| 0x4033C436 | %nSSL 证书不适用于服务器身份验证。 |
%nThe SSL certificate is not appropriate for server authentication. |
| 0x4033C437 | %nSSL 库中出现内部错误。 |
%nEncountered an internal error in the SSL library. |
| 0x4033C438 | WS-Management 服务无法处理该请求。WS-Management 编录中找不到资源 URI (%1)。要获取 Windows 远程管理配置，请使用下列资源 URI: %2。 |
The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Management catalog.For getting Windows Remote Management configuration, use the following resource URI: %2. |
| 0x4033C439 | 无法使用类 %2 的实例表示更新类 %1 的实例；请提供类 %1 的实例表示。 |
Cannot update an instance of class %1 using a representation of an instance for class %2; please provide a representation of an instance for class %1. |
| 0x4033C43B | Windows 命令解释器的内置编录插件 |
Built-in catalog plugin for Windows Command Shell |
| 0x4033C43C | WS-Management 服务无法处理该请求，因为嵌入式对象或引用元素包含混合的内容。 |
The WS-Management service cannot process the request because an embedded objector reference element contains mixed content. |
| 0x4033C43D | WS-Management 服务无法处理该请求，因为日期时间元素或简单属性包含子元素。 |
The WS-Management service cannot process the request because a date-timeelement or simple property contains child elements. |
| 0x4033C43E | WS-Management 服务无法处理该请求，因为输入 XML 中缺少元素(“%1”)。输入 XML 中不能缺少非数组属性。 |
The WS-Management service cannot process the request because an element (\"%1\") is missing from the input XML. Non-array properties cannot be missing from the input XML. |
| 0x4033C43F | WinRM 无法处理该请求，因为 XML 分析程序意外到达了输入的结尾。 |
WinRM cannot process the request because the XML parser unexpectedly reachedthe end of input. |
| 0x4033C445 | WinRM 无法处理该请求，因为输入 XML 使用了未定义的 XML 命名空间。 |
WinRM cannot process the request because the input XML uses an undefined XMLnamespace. |
| 0x4033C449 | WinRM 从 R2 迁移的配置已损坏。侦听程序配置无效。 |
The WinRM migrated configuration from R2 is corrupted. The listener configuration is not valid. |
| 0x4033C44A | WinRM 配置已损坏。请使用以下命令还原默认值:%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}%n%n然后添加所有自定义配置设置。 |
The WinRM configuration is corrupted. Use the following command to restore defaults:%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}%n%nThen add any custom configuration settings. |
| 0x4033C44B | WS-Management 服务无法处理该请求。SOAP 数据包未包含有效订阅 ID 元素。传入的“取消订阅”请求应该包含标头项，其中带有从“订阅”响应获得的引用属性元素。 |
The WS-Management service cannot process the request. The SOAP packet does not contain a validsubscription ID element. The incoming Unsubscribe request should contain a header entry with the referenceproperty element obtained from the Subscribe response. |
| 0x4033C44C | WinRM 无法处理该配置请求。主机名模式无效: “%1”主机名模式必须包含一个或多个模式。一个模式最多可包含一个通配符(\"*\")。特殊模式 \"\" 可用来指定所有没有 \".\" 的主机名。若要信任所有主机，将 \"*\" 用作唯一的模式。 |
WinRM cannot process the configuration request.The hostname pattern is invalid: \"%1\"Hostname patterns must contain one or more patterns.A pattern can contain at most one wildcard (\"*\").The special pattern \"\" can be used to indicate all hostnames that do not have a '.'.To trust all hosts use \"*\" as the only pattern. |
| 0x4033C44D | WinRM 客户端无法处理该请求。WinRM 客户端收到来自服务器的“拒绝访问”错误，它尝试重新发送消息，但配置已更改，新设置不允许重新发送消息。使用更新的配置允许的身份验证机制重新尝试处理该请求。 |
The WinRM client cannot process the request. The WinRM client received an 'access denied' error from the serverand it tried to send again the message, but the configuration changed and the new settings did not allow the message to be re-sent.Try the request again with an authentication mechanism that is allowed by the updated configuration. |
| 0x4033C44E | WinRM 客户端无法处理该请求。服务器不支持客户端请求的身份验证机制或服务配置中禁用未加密流量。请验证服务配置中的未加密流量设置或指定服务器支持的身份验证机制之一。若要使用 Kerberos，请指定计算机名作为远程目标。同时验证客户端计算机和目标计算机均已加入域。若要使用基本身份验证，请指定计算机名作为远程目标，指定基本身份验证并提供用户名和密码。服务器报告的可能身份验证机制: %1 %2 %3 %4 %5 |
The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration.Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain.To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password.Possible authentication mechanisms reported by server: %1 %2 %3 %4 %5 |
| 0x4033C44F | WinRM 客户端无法处理该请求。目标计算机(%1:%2!d!)返回“拒绝访问”错误。请指定服务器支持的身份验证机制之一。如果使用 Kerberos 机制，请确保客户端计算机和目标计算机加入域。服务器报告的可能身份验证机制: %3 %4 %5 %6 %7 |
The WinRM client cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error.Specify one of the authentication mechanisms supported by the server. If Kerberos mechanism is used,verify that the client computer and the destination computer are joined to a domain.Possible authentication mechanisms reported by server: %3 %4 %5 %6 %7 |
| 0x4033C450 | WinRM 客户端无法处理该请求。WinRM 客户端尝试使用 %1 身份验证机制，但目标计算机(%2:%3!d!)返回“拒绝访问”错误。请更改配置以允许使用 %1 身份验证机制或指定服务器支持的身份验证机制之一。若要使用 Kerberos，请指定本地计算机名作为远程目标。同时验证客户端计算机和目标计算机均已加入域。若要使用基本身份验证，请指本地定计算机名作为远程目标，指定基本身份验证并提供用户名和密码。服务器报告的可能身份验证机制: %4 %5 %6 %7 %8 |
The WinRM client cannot process the request. The WinRM client tried to use %1 authentication mechanism, but the destination computer (%2:%3!d!) returned an 'access denied' error.Change the configuration to allow %1 authentication mechanism to be used or specify one of the authentication mechanisms supported by the server.To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain.To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password.Possible authentication mechanisms reported by server: %4 %5 %6 %7 %8 |
| 0x4033C451 | WS-Management 服务无法处理该请求。WS-Eventing Delivery 部分可能缺少 WS-Eventing NotifyTo 元素，或者该元素可能无效。它可能超过允许的最大长度。 |
The WS-Management service cannot process the request.The WS-Eventing NotifyTo element might be missing from the WS-Eventing Delivery section or it might be invalid.It might be longer than the maximum length allowed. |
| 0x4033C452 | WS-Management 服务无法处理该请求。WS-Eventing NotifyTo 部分缺少 WS-Addressing Address 元素。 |
The WS-Management service cannot process the request.The WS-Addressing Address element is missing from the WS-Eventing NotifyTo section. |
| 0x4033C453 | WS-Management 服务无法处理该请求。SOAP 数据包的 WS-Eventing NotifyTo 部分包含的 WS-Addressing Address 元素无效、重复或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains an WS-Addressing Address element in the WS-Eventing NotifyTo sectionthat is either invalid, duplicated, or too long. |
| 0x4033C454 | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-Eventing 过期元素无效、重复、不受支持或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing expiration element that is either invalid, duplicated, not supported, or too long. |
| 0x4033C455 | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-Eventing 区域设置元素无效、重复、不受支持或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing locale element that is either invalid, duplicated, not supported, or too long. |
| 0x4033C456 | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-Management 检测信号元素无效。 |
The WS-Management service cannot process the request. The SOAP packet contains an WS-Management heartbeat element that is invalid. |
| 0x4033C457 | WS-Management 服务无法处理该请求。此请求仅在指定了 -remote 选项时有效。 |
The WS-Management service cannot process the request. This request is valid only when the -remote option is specified. |
| 0x4033C458 | WinRM 客户端无法处理该请求。没有会话调用 API。 |
The WinRM client cannot process the request. API was called with no session. |
| 0x4033C45B | WS-Management 服务无法处理该配置请求。XML 包含的值超过最大长度 %1!d! |
The WS-Management service cannot process the configuration request. The XML contains avalue longer than the maximum length of %1!d! |
| 0x4033C45C | WinRM 无法处理该请求。请求的区域设置“%1”包含无效语言代码。 |
WinRM cannot process the request. The requested locale '%1' contains an invalidlanguage code. |
| 0x4033C45D | WinRM 无法处理该请求。请求的区域设置“%1”包含无效国家或地区代码。 |
WinRM cannot process the request. The requested locale '%1' contains an invalidcountry code. |
| 0x4033C45E | WS-Management 服务无法处理该请求。批处理(%1!d! 字节)小于受支持的最小字节数(%2!d! 字节)。 |
The WS-Management service cannot process the request. The batch is smaller (%1!d! bytes) than theminimum size that is supported (%2!d! bytes). |
| 0x4033C45F | WS-Management 服务无法处理该请求。WS-Eventing Delivery 部分缺少 WS-Eventing EndTo 元素，或该元素无效。 |
The WS-Management service cannot process the request. The WS-Eventing EndTo element is missing from the WS-Eventing Delivery section, or is invalid. |
| 0x4033C460 | WinRM 无法处理该配置请求。服务资源 URI (%1)只支持下列操作: %2 和 %3。 |
WinRM cannot process the configuration request. The service resource URI (%1) only supports the following actions: %2 and %3. |
| 0x4033C461 | WinRM 无法处理该配置请求。该操作要求输入 XML 的元素名称为 %1。 |
WinRM cannot process the configuration request. This action requires input XML with an element name of %1. |
| 0x4033C463 | 在 %1://%2 上创建 WinRM 侦听程序接受 WS-Man 对此机器上任意 IP 的请求。 |
Create a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine. |
| 0x4033C465 | 无法在 %1://%2 上创建 WinRM 侦听程序。 |
Could not create a WinRM listener on %1://%2. |
| 0x4033C466 | 在 %1://%2 上启用 WinRM 侦听程序。 |
Enable the WinRM listener on %1://%2. |
| 0x4033C468 | 无法在 %1://%2 上启用 WinRM 侦听程序。 |
Could not enable the WinRM listener on %1://%2. |
| 0x4033C469 | 该资源需要下列选择器: %1 %2 |
This resource requires the following selectors: %1 %2 |
| 0x4033C46A | 该资源不需要选择器。 |
This resource requires no selectors. |
| 0x4033C46B | 启动 WinRM 服务。 |
Start the WinRM service. |
| 0x4033C46C | 将 WinRM 服务类型设置为延迟的自动启动。 |
Set the WinRM service type to delayed auto start. |
| 0x4033C46D | 将 WinRM 服务设置为自动启动。 |
Set the WinRM service type to auto start. |
| 0x4033C46E | 已启动 WinRM 服务。 |
WinRM service started. |
| 0x4033C46F | 无法启动 WinRM 服务: %1 |
Could not start the WinRM service: %1 |
| 0x4033C470 | 成功更改 WinRM 服务类型。 |
WinRM service type changed successfully. |
| 0x4033C471 | 无法更改 WinRM 服务类型: %1 |
Could not change the WinRM service type: %1 |
| 0x4033C472 | WinRM 服务无法处理该请求。配置设置或组策略设置拒绝对资源 URI (%1)的访问。 |
The WinRM service cannot process the request. A configuration setting or group policy setting denies access to the resource URI (%1). |
| 0x4033C473 | 操作 URI (%1) 无效。 |
The action URI (%1) is invalid. |
| 0x4033C474 | 请求中指定了下列身份验证机制: %1 %2 %3 %4 %5 %6 |
The following authentication mechanisms were specified in the request: %1 %2 %3 %4 %5 %6 |
| 0x4033C476 | WS-Management 服务无法处理该请求。URI 包含无效字符(%1)。 |
The WS-Management service cannot process the request. The URI contains a invalid character (%1). |
| 0x4033C477 | WinRM 无法处理该请求。使用 %2 身份验证时发生错误代码为 0x%1!x! 的以下错误: %3 %n可能的原因为:%n -指定的用户名或密码无效。%n -未指定身份验证方法和用户名时，使用了 Kerberos。%n -Kerberos 接受域用户名，但不接受本地用户名。%n -远程计算机名和端口的服务主体名称(SPN)不存在。%n -客户端和远程计算机位于不同的域中，并且两个域之间没有信任关系。%n检查上述问题之后，尝试以下操作:%n -检查事件查看器中与身份验证有关的事件。%n -更改身份验证方法；将目标计算机添加到 WinRM TrustedHosts 配置设置中或使用 HTTPS 传输。%n请注意，TrustedHosts 列表中的计算机可能未经过身份验证。%n -有关 WinRM 配置的详细信息，请运行以下命令: winrm help config。 |
WinRM cannot process the request. The following error with errorcode 0x%1!x! occurred while using %2 authentication: %3 %nPossible causes are:%n -The user name or password specified are invalid.%n -Kerberos is used when no authentication method and no user name are specified.%n -Kerberos accepts domain user names, but not local user names.%n -The Service Principal Name (SPN) for the remote computer name and port does not exist.%n -The client and remote computers are in different domains and there is no trust between the two domains.%nAfter checking for the above issues, try the following:%n -Check the Event Viewer for events related to authentication.%n -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.%nNote that computers in the TrustedHosts list might not be authenticated.%n -For more information about WinRM configuration, run the following command: winrm help config. |
| 0x4033C478 | 无法检查 WinRM 服务的状态。 |
Unable to check the status of the WinRM service. |
| 0x4033C479 | 无法检查防火墙的状态。 |
Unable to check the status of the firewall. |
| 0x4033C47A | 启用 WinRM 防火墙异常。 |
Enable the WinRM firewall exception. |
| 0x4033C47C | 无法启用 WinRM 的防火墙。 |
Unable to enable the firewall for WinRM. |
| 0x4033C47D | 警告: 无法为所有活动的配置文件启用 WinRM 防火墙例外。 |
Warning: The WinRM firewall exception could not be enabled for all active profiles. |
| 0x4033C47E | WinRM 防火墙异常已启用。 |
WinRM firewall exception enabled. |
| 0x4033C47F | WinRM 客户端从远程 WS-Management 服务收到一个 %1!d! 的 HTTP 状态代码。 |
The WinRM client received an HTTP status code of %1!d! from the remote WS-Management service. |
| 0x4033C480 | 订阅数据包的 Locale 元素缺少语言属性。Locale 元素需要语言属性。 |
The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element. |
| 0x4033C481 | WinRM 无法处理该配置请求。该操作要求输入包含带有值为 \"http\" 或 \"https\" 的 %1 的元素名称的 XML。 |
WinRM cannot process the configuration request. This action requires input XML containing an element name of %1 with value \"http\" or \"https\". |
| 0x4033C482 | Windows 远程解释器无法处理该请求。服务器已经在执行用户可以远程打开同一系统上最大数目的并发解释器。稍后重试。 |
The Windows Remote Shell cannot process the request. The server is already executingthe maximum number of concurrent shells an user can remotely open on the same system. Retry later. |
| 0x4033C483 | Windows 远程解释器无法处理该请求。服务器超过了 在同一系统上并发执行远程操作的最大用户数。稍后重试。 |
The Windows Remote Shell cannot process the request. The server exceeded the maximum number of users concurrently performing remote operations on the same system. Retry later. |
| 0x4033C484 | Windows 远程解释器无法处理该请求。服务器已试图应用该远程解释器对象的配额限制，但是系统确定这些限制无效。请修改配置设置，这些设置可利用下列命令 \"winrm get winrm/config/winrs\" 进行查看。 |
The Windows Remote Shell cannot process the request. The server attempted to apply the quota limits for the Remote Shell object, however the system determined that the limits were invalid. Please correct the configuration settings, the settings can be viewed using the following command \"winrm get winrm/config/winrs\". |
| 0x4033C485 | Windows 远程解释器收到一个依赖某个命令标识符执行某项操作的请求，而该命令标识符不存在。该命令已经执行完毕或者客户端指定了一个无效的命令标识符。 |
The Windows Remote Shell received a request to perform an operation on a command identifier that does not exist. Either the command has completed execution or the client specified an invalid command identifier. |
| 0x4033C486 | Windows 远程解释器无法处理该请求，因为它需要下列选择器: %1。请使用正确的选择器重试。 |
The Windows Remote Shell cannot process the request because it requires the following selector: %1. Retry with the correct selector. |
| 0x4033C487 | ShellId 为 %1 的 Windows 远程 Shell 的请求失败，因为在服务器上找不到该 Shell。可能的原因是: 指定的 ShellId 不正确，或该 Shell 不在该服务器上。请提供正确的 ShellId 或创建新的 Shell，然后重试该操作。 |
The request for the Windows Remote Shell with ShellId %1 failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation. |
| 0x4033C488 | 解释器或命令的每个实例只能有一个 rsp:Send。请在收到 rsp:SendResponse 之后再重新发送 rsp:Send 请求。 |
Only one rsp:Send can be outstanding per instance of the shell or command. Resend the rsp:Send request after a rsp:SendResponse is received. |
| 0x4033C489 | 解释器或命令的每个实例只能有一个 rsp:Receive。请在收到 rsp:ReceiveResponse 之后再重新发送 rsp:Receive 请求。 |
Only one rsp:Receive can be outstanding per instance of the shell or command. Resend the rsp:Receive request after a rsp:ReceiveResponse is received. |
| 0x4033C48A | 解释器或命令的每个实例只能有一个 rsp:Signal。请在收到 rsp:SignalResponse 之后重新发送 rsp:Signal 请求。 |
Only one rsp:Signal can be outstanding per instance of the shell or command. Resend the rsp:Signal request after a rsp:SignalResponse is received. |
| 0x4033C48B | WS-Management 服务无法处理有 wsman:Locale 的请求，wsman:Locale 与正在初始化的 wxf:Create 请求中的使用不同。请重新发送没有区域设置的远程请求，或重新发送带有与最初由 wxf:Create 所使用的相同区域设置的远程请求。 |
The WS-Management service cannot process the request with a wsman:Locale different from that used in the initiating wxf:Create request.Resend the remote request without locale or with the same locale initially used by wxf:Create. |
| 0x4033C48C | Windows 远程解释器无法处理该请求。不允许除最初创建者之外的其他用户使用正在运行的解释器实例，即使他们拥有自己创建解释器的相同甚至更高的权限。管理员可以枚举所有正在运行的解释器实例，还可获得并删除正在运行的解释器实例。 |
The Windows Remote Shell cannot process the request. It is not permitted for other users then the initial creator to make use of a running shell instance, even if they have permissions to create shells themselves with the same or even greater privileges.The administrator can enumerate all running shell instances, also get and delete a running shell instance. |
| 0x4033C48D | Windows 远程外壳程序无法处理该请求。资源 URI 无效或服务无法找到由资源URI 和选择器标识的资源。wsman:ResourceURI 值应为 %1 或在 CustomRemoteShell 表中定义该值。检查文档或使用以下命令获取有关如何填充 CustomRemoteShell 表\"winrm help customremoteshell\" 的信息。选择器与资源 URI 相关。使用正确的资源 URI 或选择器重试该请求。 |
The Windows Remote Shell cannot process the request. The resource URI is not valid or the service cannot find the resource identified by the resource URI and selectors.The wsman:ResourceURI value should be %1 or be defined in the CustomRemoteShell table. Check the documentation or use the following command for information on how to populate CustomRemoteShell table: \"winrm help customremoteshell\".The selectors are relative to the resource URI.Retry the request with the correct resource URI or selectors. |
| 0x4033C48E | Windows 远程解释器无法处理该请求。从解释器插件返回的命令 ID 为空。 |
The Windows Remote Shell cannot process the request. The command id returned from the shell plugin is empty. |
| 0x4033C48F | Windows 远程解释器无法处理该请求。WS-Addressing Action URI 无效。有效操作是 Command、Receive、Send 和 Signal。检查 Windows 远程解释器文档，获取如何构建 Action URI 的信息。 |
The Windows Remote Shell cannot process the request. The WS-Addressing action URI is invalid. The valid actions are Command, Receive, Send and Signal.Check the Windows Remote Shell documentation for information on how to construct an action URI. |
| 0x4033C490 | Windows Remote Shell 无法处理该请求。SequenceId 元素为空的或无效。 |
The Windows Remote Shell cannot process the request. The SequenceId element is empty or invalid. |
| 0x4033C491 | Windows Remote Shell 无法处理该请求。计算出的响应数据包大小超过允许的信封大小上限。 |
The Windows Remote Shell cannot process the request. The computed response packet size exceeds the maximum envelope size that is allowed. |
| 0x4033C492 | WS-Management 服务无法处理碎片过滤器，因为不支持指定的 XPath 过滤器。尝试简化路径并重试。 |
The WS-Management service cannot process the fragment filter because the specified XPath filter is not supported.Try simplifying the path and try again. |
| 0x4033C493 | Windows Remote Shell 无法处理该请求。SOAP 数据包包含无效的元素 %1。使用正确的 XML 元素重试该请求。 |
The Windows Remote Shell cannot process the request. The SOAP packet contains an element %1 that is invalid.Retry the request with the correct XML element. |
| 0x4033C494 | WinRM 客户端无法处理该请求。以下设置是只读的，无法修改: %1。请从命令中删除此设置，然后再试一次。 |
The WinRM client cannot process the request. The following setting is read-only and cannot be modified: %1.Remove this setting from the command and try again. |
| 0x4033C495 | 用于 Windows 远程管理的订阅管理器插件 |
Subscription Manager plugin for Windows Remote Management |
| 0x4033C496 | WS-Management 服务无法处理该请求。SOAP 包包含的 MachineID 元素无效、重复或太长。 |
The WS-Management service cannot process the request.The SOAP packet contains a MachineID element that was either invalid, duplicated, or too long. |
| 0x4033C497 | WS-Management 服务配置包含 URI 安全表中不确定的条目: 多个模式匹配下列资源 URI: %1。授权过程无法继续。请修改 URI 安全表中的条目，然后再次尝试。 |
The WS-Management service configuration contains ambiguous entries in the URI security table: more than one pattern matches the following resource URI: %1.Authorization process cannot continue. Fix the entries in the URI security table and try the request again. |
| 0x4033C498 | Windows 远程管理 |
Windows Remote Management |
| 0x4033C499 | 完全控制(All Operations) |
Full Control(All Operations) |
| 0x4033C49A | 读取(Get,Enumerate,Subscribe) |
Read(Get,Enumerate,Subscribe) |
| 0x4033C49B | 写入(Put,Delete,Create) |
Write(Put,Delete,Create) |
| 0x4033C49C | 执行(Invoke) |
Execute(Invoke) |
| 0x4033C49D | 外壳程序的每个实例只能有一个没有完成的命令。无论命令提前终止或运行至完成，在所有情况下，都必须使用信号作为最后消息终止该命令。在收到 SignalResponse 以后重新发送命令请求。 |
Only one Command can be outstanding per instance of the shell. You must terminate the command using Signal as the last message in all cases, whether the command is terminated early or run to completion. Resend the Command request after a SignalResponse is received. |
| 0x4033C49E | 筛选器包含类中不存在的属性(%1)。 |
The filter contains a property (%1) that does not exist in the class. |
| 0x4033C49F | 筛选器包含不受支持类型的属性(%1)。以下类型的属性不支持筛选: 日期、引用、对象和数组。 |
The filter contains a property (%1) that is of an unsupported type.Filtering is not supported on properties with the following types: datetime, reference, object, and array. |
| 0x4033C4A0 | 资源 URI (%1)不支持未筛选的枚举。需要下列筛选器方言之一: %2。 |
The resource URI (%1) does not support unfiltered enumeration. One of the following filter dialects is required: %2. |
| 0x4033C4A1 | 不允许更改颁发者、使用者的值或已配置证书映射条目的 URI。 |
It is not allowed to change the value of the Issuer,Subject or the URI for a configured certmapping entry. |
| 0x4033C4A2 | 此资源需要下列选择器: %1 %2 %3 |
This resource requires the following selectors: %1 %2 %3 |
| 0x4033C4A3 | 此资源需要下列选择器: %1 |
This resource requires the following selector: %1 |
| 0x4033C4A4 | 下列选择器不是已访问资源的键属性: %1。使用是要访问的资源的键属性的选择器。 |
The following selector is not a key property of the resource accessed : %1. Use selectors that are key properties for the resource that you want to access. |
| 0x4033C4A5 | WinRM 无法处理该请求，因为输入 XML 包含无效 XML 标头。 |
WinRM cannot process the request because the input XML contains an invalid XML header. |
| 0x4033C4A6 | WinRM 无法处理该请求，因为输入 XML 包含不匹配的元素。终止名称与起始名称不匹配。 |
WinRM cannot process the request because the input XML contains a mismatchedelement. The ending name does not match the starting name. |
| 0x4033C4A7 | WinRM 无法处理该请求，因为输入 XML 包含无效属性或元素名称。 |
WinRM cannot process the request because the input XML contains an invalidattribute or element name. |
| 0x4033C4A8 | WinRM 无法处理该请求，因为输入 XML 包含无效属性。 |
WinRM cannot process the request because the input XML contains an invalidattribute. |
| 0x4033C4A9 | WinRM 无法处理该请求，因为输入 XML 包含语法错误。 |
WinRM cannot process the request because the input XML contains a syntax error. |
| 0x4033C4AA | WinRM 无法处理该请求，因为输入 XML 包含太多嵌套层次的元素。 |
WinRM cannot process the request because the input XML contains too many nestedlevels of elements. |
| 0x4033C4AB | WinRM 无法处理该请求，因为 XML 元素的内容或子元素的 xsi:nil 属性标记为 NULL。 |
WinRM cannot process the request because an XML element has content or child elements but is marked as NULL with the xsi:nil attribute. |
| 0x4033C4AC | WinRM 无法处理该请求，因为布尔属性包含无效的布尔值。 |
WinRM cannot process the request because a boolean attribute contains aninvalid boolean value. |
| 0x4033C4AD | WinRM 客户端无法处理该请求。批处理项目必须至少为: %1!d! |
The WinRM client cannot process the request. The batch items must be at least: %1!d! |
| 0x4033C4AE | WinRM 客户端无法处理该请求。最大字符数必须至少为: %1!d! |
The WinRM client cannot process the request. The max characters must be at least: %1!d! |
| 0x4033C4AF | 资源 URI (%1)支持未筛选的枚举以及下列筛选器方言: %2。 |
The resource URI (%1) supports unfiltered enumeration and the following filter dialects: %2. |
| 0x4033C4B0 | 会话选项 %1 无效；指定的值 %2!lu! 低于所需的最小值 %3!lu!。 |
Invalid session option %1;The specified value %2!lu! is below the minimum required value of %3!lu!. |
| 0x4033C4B1 | 会话选项 %1 无效；值太大: %2!lu!。值必须小于等于 %3!lu!。 |
Invalid session option %1;the value is too large: %2!lu!. The value must be %3!lu! or less. |
| 0x4033C4B2 | 会话选项 %1 无效；此选项的类型无效。 |
Invalid session option %1;the type of the option is not valid. |
| 0x4033C4B4 | 配置 XML 无效。配置 XML 包含意外的 XML 元素: 当元素处于以下条件下时“%1”:“%2%”应在此点上。请确保元素的顺序正确，并且元素名称的拼写正确。 |
The configuration XML is not valid. The configuration XML contains an unexpected XML element: \"%1\" while element: \"%2%\" is expected at this point. Ensure that the elements are in correct sequence and that the spelling of the element name is correct. |
| 0x4033C4B5 | 配置 XML 无效。配置 XML 包括无效的 XML 元素:“%1”。请确保元素的顺序正确，并且元素名称的拼写正确。 |
The configuration XML is not valid. The configuration XML contains an invalid XML element: \"%1\". Ensure that the elements are in correct sequence and that the spelling of the element name is correct. |
| 0x4033C4B6 | 配置 XML 无效。XML 元素的命名空间“%1”不正确。 |
The configuration XML is not valid. The namespace for XML element: \"%1\" is not correct. |
| 0x4033C4B7 | 配置 XML 无效。找到太多的 XML 元素“%1”的实例。 |
The configuration XML is not valid. Too many instances of XML element: \"%1\" found. |
| 0x4033C4B8 | 配置 XML 无效。期望 XML 元素“%1”但是未找到。 |
The configuration XML is not valid. The XML element: \"%1\" is expected but not found. |
| 0x4033C4B9 | 配置 XML 无效。不期望 XML 元素“%1”的文本。 |
The configuration XML is not valid. Text for XML element: \"%1\" is not expected. |
| 0x4033C4BA | 配置 XML 无效。属性“%1”不是元素“%2”的预期属性，或其命名空间无效。 |
The configuration XML is not valid. Either attribute: \"%1\" is not expected for element: \"%2\" or its namespace is invalid. |
| 0x4033C4BB | 配置 XML 无效。重复元素“%2”的属性“%1”。 |
The configuration XML is not valid. Attribute: \"%1\" is repeated for element: \"%2\". |
| 0x4033C4BC | 配置 XML 无效。元素“%2”需要属性“%1”。 |
The configuration XML is not valid. Attribute: \"%1\" is required for element: \"%2\". |
| 0x4033C4BD | 配置 XML 无效。属性“%1”的配置值长度超过最大限制(10240 个字符)。 |
The configuration XML is not valid. The configuration value length for attribute %1 exceeded the maximum limit of 10240 characters. |
| 0x4033C4BE | 配置 XML 无效。属性值“%1”不是有效整数。有效的整数值由字符“0”到“9”组成，且长度不能超过 10 位数。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid integer.Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length. |
| 0x4033C4BF | 配置 XML 无效。属性值“%1”不是有效的布尔值。有效布尔值为 true 和 false。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid boolean.Valid boolean values are \"true\" and \"false\". |
| 0x4033C4C0 | 配置 XML 无效。属性值“%1”不是有效的功能类型。有效的功能类型为 \"Identify\"、\"Get\"、\"Put\"、\"Create\"、\"Delete\"、\"Invoke\"、\"Enumerate\"、\"Subscribe\" 和 \"Shell\"。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid capability type.Valid capability types are \"Identify\", \"Get\", \"Put\", \"Create\", \"Delete\", \"Invoke\", \"Enumerate\", \"Subscribe\" and \"Shell\". |
| 0x4033C4C1 | 配置 XML 无效。属性值“%1”不是有效的插件名称。插件名称不能为空，并且不能超过 255 个字符。插件名称前面不应包含任何空格或制表符。插件名称不应包含反斜杠字符和双引号字符。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid plugin name.Plugin name cannot be empty and cannot exceeded 255 characters. Plugin name should not have any preceding space or tab characters.The plugin name should not contain backslash and double quote characters. |
| 0x4033C4C2 | 配置 XML 无效。当前不支持 SDK 版本“%1”。 |
The configuration XML is not valid. SDK Version: \"%1\" is currently not supported. |
| 0x4033C4C3 | 配置 XML 无效。属性值“%1”不是有效的 xml 呈现类型。有效的 xml 呈现类型为 \"text\" 和 \"XmlReader\"。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid xml rendering type.Valid xml rendering types are \"text\" and \"XmlReader\". |
| 0x4033C4C4 | 配置 XML 无效。资源 URI“%1”已在插件配置中多次注册。 |
The configuration XML is not valid. Resource Uri: \"%1\" is registered more than once in theplugin configuration. |
| 0x4033C4C5 | 配置 XML 无效。资源 URI“%1”无效。插件资源 URI 不能以 WSMan 配置根 URI 作为前缀。 |
The configuration XML is not valid. Resource Uri: \"%1\" is not valid. Plugin resource Uris cannothave WSMan configuration root uri as a prefix. |
| 0x4033C4C6 | 配置 XML 无效。资源 URI“%1”不能被多个插件公开。 |
The configuration XML is not valid. Resource Uri: \"%1\" cannot be exposed by more than one plugin. |
| 0x4033C4C7 | 配置 XML 无效。 已为资源 URI“%2”多次定义功能“%1”。 |
The configuration XML is not valid. Capability: \"%1\" is defined multiple times for resource uri: \"%2\". |
| 0x4033C4C8 | 配置 XML 无效。功能“%1”不支持片段。 |
The configuration XML is not valid. Fragments are not supported for capability: \"%1\". |
| 0x4033C4C9 | 配置 XML 无效。功能“%1”不支持筛选器。 |
The configuration XML is not valid. Filters are not supported for capability: \"%1\". |
| 0x4033C4CA | 配置 XML 无效。资源 URI %1 不能同时支持外壳程序功能和其他功能。 |
The configuration XML is not valid. Resource uri: %1 cannot simultaneously support shell capability with other capabilities. |
| 0x4033C4CB | 配置 XML 无效。属性 name 的值与给定的选择器不匹配。 |
The configuration XML is not valid. Value of attribute \"name\" does not match the given selector. |
| 0x4033C4CC | 配置 XML 无效。属性值“%1”不是有效的文件路径。有效的文件路径应是绝对的，位于 system32 目录中且应指向现有的文件。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid file path. Valid file path should be absolute, reside in the system32 directory and should point to an existing file. |
| 0x4033C4CD | WS-Management 服务无法处理该请求。插件“%1”的配置已损坏。此插件需要重新配置，或将其删除。请使用以下命令删除插件配置%n%nwinrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz%n%n或使用以下命令还原默认插件配置。注意，在此还原操作期间将注销所有外部插件。%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{} |
The WS-Management service cannot process the request. Configuration for plugin: \"%1\" is corrupted.This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration%n%nwinrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz%n%nOr use the following command to restore default plugin configuration. Note that all external plugins will be unregistered during this restore operation.%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{} |
| 0x4033C4CE | WS-Management 服务无法处理该请求。插件配置的选择器不能超过 255 个字符。 |
The WS-Management service cannot process the request. The selector for plugin configuration cannot exceed 255 characters. |
| 0x4033C4CF | WS-Management 服务无法执行此配置操作。插件名称=%1 的插件配置已经存在。你必须先删除现有的插件配置才能创建具有相同插件名称的插件配置。 |
The WS-Management service cannot perform the configuration operation. A plugin configuration with plugin name=%1 already exists.You have to delete the existing plugin configuration first in order to be able to create it with the same plugin name. |
| 0x4033C4D0 | 读取 IIS 配置时出错。%n文件: %1 %n行: %2 %n问题: %3 |
An error occurred while reading the IIS configuration. %nFile: %1 %nLine: %2 %nIssue: %3 |
| 0x4033C4D1 | WSMan 客户端无法处理该请求。该客户端不支持代理请求的身份验证机制。唯一支持的代理身份验证机制为协商、基本或摘要式身份验证。代理报告的可能身份验证机制: %1 %2 %3 %4 %5 |
The WSMan client cannot process the request. The authentication mechanism requested by the proxy is not supported by the client.The only proxy authentication mechanisms supported are Negotiate, Basic or Digest.Possible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5 |
| 0x4033C4D2 | WSMan 客户端从服务器接收到了重定向状态，但服务器未给定要使用的实际重定向位置。 |
The WSMan client received a redirect status from the server, but the server did not givethe actual redirect location to use. |
| 0x4033C4D3 | 为服务配置 CertificateThumbprint 设置，该设置将用于 CredSSP 身份验证。 |
Configure CertificateThumbprint setting for the service, to be used for CredSSP authentication. |
| 0x4033C4D4 | 已为该服务配置 CertificateThumbprint 设置。 |
Configured CertificateThumbprint setting for the service. |
| 0x4033C4D5 | 无法为此服务配置 CertificateThumbprint 设置。 |
Could not configure CertificateThumbprint setting for the service. |
| 0x4033C4D6 | WS-Management 服务无法处理该请求。允许此用户的并发外壳程序的最大数目为 %1!d!，已超过该最大数目。请关闭现有外壳程序或提高此用户的配额。 |
The WS-Management service cannot process the request.This user is allowed a maximum number of %1!d! concurrent shells, which has been exceeded.Close existing shells or raise the quota for this user. |
| 0x4033C4D7 | WS-Management 服务无法处理该请求。允许此用户的并发操作的最大数目为 %1!d!，已超过该最大数目。请结束此用户现有的操作，或提高此用户的配额。 |
The WS-Management service cannot process the request.This user is allowed a maximum number of %1!d! concurrent operations, which has been exceeded.Close existing operations for this user, or raise the quota for this user. |
| 0x4033C4D8 | WS-Management 服务无法处理该请求。已超过每 %2!d! 秒 %1!d! 个请求的用户负载配额。以较慢速率发送将来的请求或提高此用户的配额。来自此用户的下一请求将被拒绝至少 %3!d! 毫秒。 |
The WS-Management service cannot process the request.The user load quota of %1!d! requests per %2!d! seconds has been exceeded.Send future requests at a slower rate or raise the quota for this user.The next request from this user will not be approved for at least %3!d! milliseconds. |
| 0x4033C4D9 | WS-Management 服务无法处理该请求。已超过每 %2!d! 秒 %1!d! 个请求的系统负载配额。以较慢速率发送将来的请求或提高系统配额。来自此用户的下一请求将被拒绝至少 %3!d! 毫秒。 |
The WS-Management service cannot process the request.The system load quota of %1!d! requests per %2!d! seconds has been exceeded.Send future requests at a slower rate or raise the system quota.The next request from this user will not be approved for at least %3!d! milliseconds. |
| 0x4033C4DA | WSMan 服务无法启动主机进程以处理给定的请求。请确保正确注册了 WSMan 提供程序的主机服务器和代理。 |
The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. |
| 0x4033C4DB | WSMan 提供程序主机进程未能返回适当的响应。主机进程中的提供程序的行为不正确。 |
The WSMan provider host process did not return a proper response. A provider in the host process may have behaved improperly. |
| 0x4033C4DC | 配置 XML 无效。Name 和 Value 的初始化 xml 属性值不能为空。 |
The configuration XML is not valid. Initialization xml attribute values for \"Name\" and \"Value\" cannot be empty. |
| 0x4033C4DD | 配置 LocalAccountTokenFilterPolicy 以远程向本地用户授予管理权限。 |
Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users. |
| 0x4033C4DE | 已配置 LocalAccountTokenFilterPolicy 以远程向本地用户授予管理权限。 |
Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users. |
| 0x4033C4DF | 无法配置 LocalAccountTokenFilterPolicy 以远程向本地用户授予管理权限。 |
Could not configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users. |
| 0x4033C4E0 | 授权插件返回了以下错误: %1。 |
The authorization plugin returned the following error: %1. |
| 0x4033C4E1 | WS-Management 服务无法处理该请求。此服务已配置为允许并发外壳程序用户的最大数目为 %1!d!，已超过该最大数目。请稍后重试请求或提高并发外壳程序用户的配额。 |
The WS-Management service cannot process the request.This service is configured to allow a maximum of %1!d! concurrent shell users, which has been exceeded.Retry your request after sometime or raise the quota for concurrent shell users. |
| 0x4033C4E2 | WS-Management 服务无法处理该请求。SOAP 数据包包含无效的 WS-Management ActivityId 元素。该元素重复或采用的格式不正确。ActivityId 应为以指定为字符串的 UUID 格式的 128 位值。 |
The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-Management ActivityId element. The element is duplicated or is not in the correct format. The ActivityId should be a 128 bit value in the UUID format specified as a string. |
| 0x4033C4E3 | WS-Management 服务不能保证将使用 ActivityId，因为默认情况下会禁用跟踪。使用 ActivityId 作为提示重新发送远程请求(SOAP 标头应使 mustUnderstand=false)。 |
The WS-Management service cannot guarantee that the ActivityId will be used as the tracing is turned OFF by default. Resend the remote request with ActivityId as a hint (the SOAP header should have mustUnderstand=\"false\"). |
| 0x4033C4E4 | WS-Management 服务无法处理该请求。配置设置“%1”已被否决且无法更改。请删除此设置，然后再试一次。 |
The WS-Management service cannot process the request.The configuration setting \"%1\" is deprecated and cannot be changed. Remove this setting and try again. |
| 0x4033C4E5 | 配置 XML 无效。属性值“%1”不是有效的体系结构类型。32 位系统上有效的体系结构类型为 32；在 64 位系统上为 32 和 64。 |
The configuration XML is not valid. Attribute value: \"%1\" is not a valid architecture type.Valid architecture types are \"32\" on a 32-bit system; \"32\" and \"64\" on a 64-bit system. |
| 0x4033C4E6 | WSMan 客户端无法处理该请求。在 HTTP 传输下不支持代理。请将传输更改为 HTTPS 并指定有效代理信息，然后再试一次。 |
The WSMan client cannot process the request. Proxy is not supported under HTTP transport. Change the transport to HTTPS and specify valid proxy information and try again. |
| 0x4033C4E7 | WSMan 客户端无法处理该请求。针对服务器的身份验证机制为 Kerberos 或 CredSSP 时，不支持代理。请将身份验证机制更改为协商、摘要式或基本身份验证，然后再试一次。 |
The WSMan client cannot process the request. Proxy is not supported when the authentication mechanism with the server is Kerberos or CredSSP. Change the authentication mechanism to Negotiate or Digest or Basic and try again. |
| 0x4033C4E8 | 配置 XML 无效。资源 URI:“%1”无效。资源 URI 不符合 RFC 3986。请更改配置 XML 中的资源 URI 并重试。 |
The configuration XML is not valid.Resource Uri: \"%1\" is not valid.The Resource URI does not conform to RFC 3986.Change the Resource URI in the configuration XML and try again. |
| 0x4033C4E9 | WS-Management 服务无法处理该请求。SOAP 数据包未包含有效的远程外壳 CompressionType 元素。该元素已重复、未标记为必须理解或者格式不正确。唯一支持的压缩类型为 \"xpress\"。 |
The WS-Management service cannot process the request. The SOAP packet did not contain a valid remote shell CompressionType element. The element is duplicated, is not marked as must understand or is not in the correct format.The only supported compression type is \"xpress\". |
| 0x4033C4EA | 配置 XML 无效。资源 URI:“%1”是 WSMan 外壳管理器的保留项。 |
The configuration XML is not valid. Resource Uri: \"%1\" is reserved for the WSMan shell manager. |
| 0x4033C4EB | XML 的配置无效。提供程序“%1”支持 %2 方法，但却无法加载该方法。请验证提供程序能正确导出 %2 方法。 |
The configuration XML is not valid.The provider \"%1\" supports the %2 method but it could not be loaded.Verify that the provider exports the %2 method properly. |
| 0x4033C4EC | Windows 远程管理 - 兼容模式(HTTP-In) |
Windows Remote Management - Compatibility Mode (HTTP-In) |
| 0x4033C4ED | 配置“网络访问: 本地帐户的共享和安全模型”策略，以允许本地用户使用其本来的身份在网络上进行身份验证。 |
Configure \"Network access: Sharing and security model for local accounts\" policy to allow local users to authenticate as themselves over network. |
| 0x4033C4EE | 已配置“网络访问: 本地帐户的共享和安全模型”策略，以允许本地用户使用其本来的身份在网络上进行身份验证。 |
Configured \"Network access: Sharing and security model for local accounts\" policy to allow local users to authenticate as themselves over network. |
| 0x4033C4EF | 无法将“网络访问: 本地帐户的共享和安全模型”策略配置为允许本地用户使用其本来的身份在网络上进行身份验证。 |
Could not configure \"Network access: Sharing and security model for local accounts\" policy to allow local users to authenticate as themselves over network. |
| 0x4033C4F0 | WS-Management 服务无法处理该操作，因为 SOAP 数据包不包含有效的 SessionID 元素。请验证 SessionID 元素不是重复元素或 GUID，然后重试该操作。 |
The WS-Management service cannot process the request because the SOAP packet does not contain a valid SessionID element. Verify that the SessionID element is not a duplicate or GUID and retry the operation. |
| 0x4033C4F1 | WinRM 服务无法处理该请求，因为 WinRS Shell 实例已在处理连接操作。 |
The WinRM service cannot process the request because the WinRS shell instance is already processing a connect operation. |
| 0x4033C4F2 | 配置 XML 无效。属性“%1”的值必须介于 %2 和 %3 之间。 |
The configuration XML is not valid. The value for the attribute \"%1\" must be between %2 and %3. |
| 0x4033C4F3 | 配置 XML 无效。只有在同时指定了属性“%2”时，才能指定属性“%1”。 |
The configuration XML is not valid. The attribute \"%1\" can be specified only if the attribute \"%2\" is also specified. |
| 0x4033C4F4 | 配置 XML 无效。只有在属性“%2”设置为 true 时，属性“%1”才能为非零值。 |
The configuration XML is not valid. The attribute \"%1\" can be non-zero only if the attribute \"%2\" is set to true. |
| 0x4033C4F5 | 配置 XML 无效。只有在将属性“%2”设置为 true，指定属性“%3”并且属性“%4”至少为 %5 时，才能指定属性“%1”。 |
The configuration XML is not valid. The attribute \"%1\" can be specified only if the attribute \"%2\" is set to true, the attribute \"%3\" is specified, and the attribute \"%4\" is at least %5. |
| 0x4033C4F6 | 配置 XML 无效。必须指定属性“%1”以更改属性“%2”。 |
The configuration XML is not valid. The attribute \"%1\" must be specified to change the attribute \"%2\". |
| 0x4033C4F7 | 此配置 XML 无效。插件“%1”为默认插件，因此不能修改其属性。 |
The configuration XML is not valid. The plugin \"%1\" is a default plugin and its attributes cannot be modified. |
| 0x4033C4F8 | 订阅组策略更改通知时，遇到错误 %1!d!。 |
An error %1!d! was encountered while subscribing to a Group Policy change notification. |
| 0x4033C4F9 | 配置 XML 无效。插件无法同时支持 Shell 功能和其他功能。 |
The configuration XML is not valid. A plugin cannot simultaneously support the shell capability with other capabilities. |
| 0x4033C4FA | 配置 XML 无效。配额 %1 对于此插件无效。 |
The configuration XML is not valid. The quota %1 is not valid for this plugin. |
| 0x4033C4FB | 配置 XML 无效。属性值“%1”必须更改为有效的服务器缓冲模式值“%2”或“%3”。 |
The configuration XML is not valid. The attribute value \"%1\" must be changed to a valid Server Buffering Mode value of either \"%2\"or \"%3\". |
| 0x4033C4FC | WS-Management 服务无法处理该请求。此用户已超过插件“%2”的最大并发 Shell 数 %1!d!。请关闭现有 Shell，或提高此用户的插件配额。 |
The WS-Management service cannot process the request. This user has exceeded the maximum number of %1!d! concurrent shells for plugin \"%2\".Close the existing shells or raise the plugin quota for this user. |
| 0x4033C4FD | WS-Management 服务无法处理该请求。此服务已超过插件“%2”允许的最大并发用户数 %1!d!。请稍后重试该请求，或提高并发用户配额。 |
The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent users allowed for plugin \"%2\".Retry the request later or raise the quota for concurrent users. |
| 0x4033C4FE | WS-Management 服务无法处理该请求。此服务已超过插件“%2”允许的最大并发 Shell 数 %1!d!。请稍后重试该请求，或提高每个插件的最大 Shell 配额。 |
The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent shells allowed for plugin \"%2\".Retry the request later or raise the Maximum Shells per Plugin quota. |
| 0x4033C4FF | WS-Management 服务无法处理该请求。此服务已超过插件“%2”允许的最大并发操作数 %1!d!。请稍后重试该请求，或提高每个插件的最大操作配额。 |
The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations allowed for plugin \"%2\".Retry the request later or raise the Maximum Shells per Plugin quota. |
| 0x4033C500 | WS-Management 服务无法处理该请求。此服务已超过插件“%2”允许的每个用户的最大并发操作数 %1!d!。请稍后重试该请求，或提高每个用户的最大操作配额。 |
The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations per user allowed for plugin \"%2\".Retry the request later or raise the Maximum Operations per User quota. |
| 0x4033C501 | WS-Management 服务无法处理该命令。此服务已超过插件“%2”允许的每个 Shell 的最大并发命令数 %1!d!。请稍后重试该请求，或提高每个 Shell 的最大命令配额。 |
The WS-Management service cannot process the command. This service has exceeded its maximum of %1!d! concurrent commands per shell allowed for plugin \"%2\".Retry the request later or raise the Maximum Commands per Shell quota. |
| 0x4033C502 | WS-Management 服务无法处理该命令。该服务没有为插件“%1”启动新操作所需的最低资源。请稍后尝试该请求，或降低该插件的最低要求。 |
The WS-Management service cannot process the command.The service does not have minimum required resources to start a new operation for the plugin \"%1\".Try the request later or lower the minimum requirement for the plugin. |
| 0x4033C503 | WS-Management 服务无法处理该请求。如果指定了筛选器或方言，WS-Management 服务无法接受指示类订阅。请删除筛选器，然后重试。 |
The WS-Management service cannot process the request.The WS-Management service cannot accept subscriptions to an indication class, when either the filter or the dialect is specified.Retry with filter removed. |
| 0x4033C504 | 验证 runAs 用户凭据失败，错误为 %1!d!。 |
The verification of the runAs user credentials failed with the error %1!d!. |
| 0x4033C505 | WS-Management 服务无法处理此请求。CIM 命名空间 %1 无效。 |
The WS-Management service cannot process the request.The CIM namespace %1 is invalid. |
| 0x4033C506 | WS-Management 服务无法处理此请求。%2 命名空间中不存在类 %1。 |
The WS-Management service cannot process the request.The class %1 does not exist in the %2 namespace. |
| 0x4033C507 | 将服务配置为允许远程请求。 |
Configure service to allow remote requests. |
| 0x4033C508 | 将服务配置为允许使用 Kerberos 协议对请求进行身份验证。 |
Configure service to allow authenticating requests using Kerberos protocol. |
| 0x4033C509 | 将服务配置为允许使用协商协议对请求进行身份验证。 |
Configure service to allow authenticating requests using Negotiate protocol. |
| 0x4033C50A | 无法为服务配置一个或多个配置设置。 |
Could not configure one or more configuration settings for the service. |
| 0x4033C50B | 已为服务配置所需的设置。 |
Configured required settings for the service. |
| 0x4033C50C | 将 GP 设置“允许通过 WinRM 进行远程服务器管理”修改为“未配置”或“已启用”。 |
Modify the GP setting \"Allow remote server management through WinRM\" to either \"Not Configured\" or \"Enabled\". |
| 0x4033C50D | 将 GP 设置“不允许 Kerberos 身份验证”修改为“未配置”或“已禁用”。 |
Modify the GP setting \"Disallow Kerberos authentication\" to either \"Not Configured\" or \"Disabled\". |
| 0x4033C50E | 将 GP 设置“不允许协商身份验证”修改为“未配置”或“已禁用”。 |
Modify the GP setting \"Disallow Negotiate authentication\" to either \"Not Configured\" or \"Disabled\". |
| 0x4033C50F | 将 GP 设置“允许通过 WinRM 进行远程服务器管理”修改为“未配置”或“已禁用”。 |
Modify the GP setting \"Allow remote server management through WinRM\" to either \"Not Configured\" or \"Disabled\". |
| 0x4033C510 | WinRM 客户端无法处理此请求，因为此 XML 包含不受支持的类型(%1)。 |
The WinRM client cannot process the request because the XML contains an unsupported type (%1). |
| 0x4033C511 | WS-Management 服务无法处理此请求，因为未指定任何 CIM 命名空间。请选择一个有效的 CIM 命名空间并重试。 |
The WS-Management service cannot process the request because no CIM namespace was specified.Choose a valid CIM namespace and try again. |
| 0x4033C512 | 已启用远程访问。 |
Enabled remote access. |
| 0x4033C513 | 无法启用远程访问。 |
Unable to enable remote access. |
| 0x4033C514 | 已禁用远程访问。 |
Disabled remote access. |
| 0x4033C515 | 无法禁用远程访问。 |
Unable to disable remote access. |
| 0x4033C516 | WinRM 客户端无法处理此请求。\"AllowRemoteAccess\" 设置为只读，因此无法修改。请使用以下命令更改远程访问行为:%n%nwinrm invoke EnableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service%n%nwinrm invoke DisableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service |
The WinRM client cannot process the request. \"AllowRemoteAccess\" setting is read-only and cannot be modified.Use the following commands instead to change the remote access behavior:%n%nwinrm invoke EnableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service%n%nwinrm invoke DisableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service |
| 0x4033C517 | WS-Management 服务无法处理此配置请求。服务资源 URI %1 仅支持以下操作: %2、%3 和 %4。 |
The WS-Management service cannot process the configuration request. The service resource URI %1 only supports the following actions: %2, %3 and %4. |
| 0x4033C518 | WS-Management 服务无法处理此配置请求。配置资源 URI %1 仅支持以下操作: %2。 |
The WS-Management service cannot process the configuration request. The configuration resource URI %1 only supports the following action: %2. |
| 0x4033C519 | WinRM 无法处理此请求。使用 %1 身份验证时发生以下错误: 找不到计算机 %2。请验证网络上是否存在此计算机，以及提供的名称是否拼写正确。 |
WinRM cannot process the request. The following error occurred while using %1 authentication: Cannot find the computer %2. Verify that the computer exists on the network and that the name provided is spelled correctly. |
| 0x4033C51A | WS-Management 服务无法处理该请求。找不到请求的资源 URI 的匹配证书映射。 |
The WS-Management service cannot process the request. There was no matching certificate mapping found for the requested resource URI. |
| 0x4033C51B | WS-Management 服务无法处理该请求。不支持重试请求。 |
The WS-Management service cannot process the request. Retry requests are not supported. |
| 0x4033C51C | WS-Management 服务无法处理该请求。不支持涉及来自客户端的多条消息的操作。 |
The WS-Management service cannot process the request. Operations involving multiple messages from the client are not supported. |
| 0x4033C51D | WS-Management 服务无法处理该请求。配置 XML 无效。配额 %1 的值不能小于 %2 的值。 |
The WS-Management service cannot process the request. The configuration XML is not valid. The value for Quota %1 cannot be less than value for %2. |
| 0x4033C51E | WinRM 无法处理请求。使用协商身份验证时，出现以下错误，错误代码为 0x%1!x!: %2 %n如果提供的凭据在目标服务器上无效，或者无法验证服务器身份，则可能会出现这种情况。如果服务器身份可信，请将服务器名称添加到 TrustedHosts 列表中，然后重试该请求。可以使用 winrm.cmd 查看或编辑 TrustedHosts 列表。请注意，可能无法验证 TrustedHosts 列表中的计算机。有关如何编辑 TrustedHosts 列表的详细信息，请运行以下命令: winrm help config。 |
WinRM cannot process the request. The following error with error code 0x%1!x! occurred while using Negotiate authentication: %2 %nThis can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified. If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request.Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated.For more information about how to edit the TrustedHosts list, run the following command: winrm help config. |
| 0x4033C51F | 由于以下原因，无法启用远程访问: %1。 |
Unable to enable remote access because of the following reason: %1. |
| 0x4033C520 | WS-Management 服务无法处理该请求。请求的 IdleTimeout %1!d! 超出允许的范围。请指定介于 %2!d! 到 %3!d! 之间的 IdleTimeout 值，然后重试该操作。 |
The WS-Management service cannot process the request. The requested IdleTimeout of %1!d! is outside the allowed range. Specify an IdleTimeout value between %2!d! and %3!d!, and retry the operation. |
| 0x4033C521 | WinRM 无法处理请求。在使用 Kerberos 身份验证时，出现以下错误: 计算机 %1 对 Kerberos 未知。请验证该计算机在网络上是否存在，提供的名称是否拼写正确，以及用于访问该计算机的 Kerberos 配置是否正确。最常见的 Kerberos 配置问题是，没有为目标配置具有 HTTP/%1 格式的 SPN。如果不需要使用 Kerberos，请指定协商身份验证机制并重新提交操作。 |
WinRM cannot process the request. The following error occurred while using Kerberos authentication: The computer %1 is unknown to Kerberos. Verify that the computer exists on the network, that the name provided is spelled correctly, and that the Kerberos configuration for accessing the computer is correct. The most common Kerberos configuration issue is that an SPN with the format HTTP/%1 is not configured for the target. If Kerberos is not required, specify the Negotiate authentication mechanism and resubmit the operation. |
| 0x4033C522 | WinRM 客户端无法处理该请求。具有 MI 类型 %2 的属性“%1”与架构中的预期类型不匹配: %3。请指定正确的类型，然后重试该操作。 |
The WinRM client cannot process the request.Property \"%1\" with MI type %2 does not match the expected type from the schema: %3.Specify the correct type and retry the operation. |
| 0x4033C523 | 由于以下错误，无法从服务器中检索元数据: %1 |
The metadata failed to be retrieved from the server, due to the following error: %1 |
| 0x4033C524 | WS-Management 服务无法处理该请求。WMI 服务或 WMI 提供程序返回未知错误: HRESULT 0x%1!x! |
The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x%1!x! |
| 0x4033C525 | WS-Management 服务无法处理该请求。SOAP 数据包包含的 WS-Eventing 编码元素无效、重复、不受支持或太长。 |
The WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing Encoding element that is either not valid, duplicated, not supported, or too long. |
| 0x4033C526 | WS-Management 服务无法处理该请求。对象包含无法识别的属性:“%1”。请验证该属性名称的拼写正确无误。 |
The WS-Management service cannot process the request.The object contains an unrecognized property: \"%1\".Verify that the spelling of the property name is correct. |
| 0x4033C527 | WinRM 客户端无法处理该请求。对象包含无法识别的属性:“%1”。请验证该属性名称的拼写正确无误。 |
The WinRM client cannot process the request.The object contains an unrecognized property: \"%1\".Verify that the spelling of the property name is correct. |
| 0x4033C528 | WS-Management 服务无法处理该请求。对象包含无法识别的参数:“%1”。请验证参数名称的拼写正确无误。 |
The WS-Management service cannot process the request.The object contains an unrecognized argument: \"%1\".Verify that the spelling of the argument name is correct. |
| 0x4033C529 | WinRM 客户端无法处理该请求。对象包含无法识别的参数:“%1”。请验证参数名称的拼写正确无误。 |
The WinRM client cannot process the request.The object contains an unrecognized argument: \"%1\".Verify that the spelling of the argument name is correct. |
| 0x4033C52A | WS-Management 服务无法处理该请求。方法名“%1”无效。请验证该方法名的拼写正确无误。 |
The WS-Management service cannot process the request.The method name \"%1\" is not valid.Verify that the spelling of the method name is correct. |
| 0x4033C52B | WinRM 客户端无法处理该请求。方法名“%1”无效。请验证该方法名的拼写正确无误。 |
The WinRM client cannot process the request.The method name \"%1\" is not valid.Verify that the spelling of the method name is correct. |
| 0x4033C52C | %1 到 %2 的网络连接已中断。正在尝试重新连接，最多可持续 %3!d! 分钟... |
%1 The network connection to %2 has been interrupted. Attempting to reconnect for up to %3!d! minutes... |
| 0x4033C52D | %1 正在尝试重新连接到 %2 ... |
%1 Attempting to reconnect to %2 ... |
| 0x4033C52E | %1 到 %2 的网络连接已恢复。 |
%1 The network connection to %2 has been restored. |
| 0x4033C52F | %1 尝试重新连接到 %2 失败。 |
%1 The reconnection attempt to %2 failed. |
| 0x4033C530 | %1 在尝试检索操作所需的 CIM 架构时尝试重新连接到 %2 失败。 |
%1 The reconnection attempt to %2 failed while trying to retrieve the CIM schema needed for the operation. |
| 0x4033C531 | WS-Management 服务无法处理该请求。只有管理员才可访问 WinRS shell 实例。 |
The WS-Management service cannot process the request. You must be an administrator in order to access the WinRS shell instance. |
| 0x4033C532 | WS-Management 服务无法处理该请求。不能通过远程连接访问 WinRS shell 实例。 |
The WS-Management service cannot process the request. The WinRS shell instance is not accessible over a remote connection. |
| 0x4033C533 | 无法查找组的 SID:“%1”。请确保该组有效。 |
Unable to look up SID of group: \"%1\". Ensure that the group is valid. |
| 0x4033C534 | 指定的用户名似乎是一个托管服务帐户。此类帐户的密码是托管的，不应指定。 |
Username specified looks like a Manged Service Account. Passwords to such accounts are managed and should not be specified. |
| 0x4033C535 | 验证托管服务帐户失败，错误为 %1!d!。请确保帐户有效。 |
The verification of the Managed Service Account failed with error %1!d!. Ensure that the account is valid. |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 信息 |
Information |
| 0x70000001 | WSMan API 初始化 |
WSMan API Initialize |
| 0x70000002 | WSMan API 取消初始化 |
WSMan API Deinitialize |
| 0x70000003 | WSMan 会话初始化 |
WSMan Session initialize |
| 0x70000004 | WSMan 会话取消初始化 |
WSMan Session deinitialize |
| 0x70000005 | WSMan API 调用 |
WSMan API call |
| 0x70000006 | 正在自动检测代理设置 |
Auto-detecting proxy settings |
| 0x70000007 | 用户身份验证 |
User authentication |
| 0x70000008 | 用户授权 |
User authorization |
| 0x70000009 | 请求处理 |
Request handling |
| 0x7000000A | 响应处理 |
Response handling |
| 0x7000000B | Winrm 服务启动/停止 |
Winrm service start/stop |
| 0x7000000C | Winrm 配置 |
Winrm configuration |
| 0x7000000D | Winrm 操作 |
Winrm Operation |
| 0x7000000E | WinRM MI 协议处理程序 |
WinRM MI Protocol Handler |
| 0x7000000F | WinRM MI 会话 |
WinRM MI Session |
| 0x70000010 | WinRM MI 操作 |
WinRM MI Operation |
| 0x70000011 | Winrm 详细消息 |
Winrm Verbose Message |
| 0x80338000 | WS-Management 服务无法处理该请求。该服务找不到资源 URI 和选择器标识的资源。 |
The WS-Management service cannot process the request. The service cannot find the resource identified by the resource URI and selectors. |
| 0x80338001 | WS-Management 服务无法处理该请求。WS-Addressing action URI 无效。请检查文档以获取有关如何创建 action URI 的信息。 |
The WS-Management service cannot process the request. The WS-Addressing action URI is invalid. Check the documentation for information on how to construct an action URI. |
| 0x80338002 | WS-Management 服务无法处理该请求。缺少资源 URI 或其格式不正确。请检查文档或使用以下命令获取有关如何创建资源 URI 的信息: \"winrm help uris\"。 |
The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format.Check the documentation or use the following command for information on how to construct a resource URI: \"winrm help uris\". |
| 0x80338003 | 在插件中遇到错误。 |
An error was encountered inside the plugin. |
| 0x80338004 | WS-Management 服务无法完成该请求。WSManEnumerator 对象已满，不能再添加其他项。 |
The WS-Management service cannot complete the request. The WSManEnumerator object is full and no more items can be added. |
| 0x80338005 | WS-Management 配置已损坏。请使用以下命令还原默认值:%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}%n%n然后添加任何自定义的配置设置。 |
The WS-Management configuration is corrupted. Use the following command to restore defaults:%n%nwinrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}%n%nThen add any custom configuration settings. |
| 0x80338006 | WS-Management 服务无法处理拉请求，因为已经在进行拉操作。 |
The WS-Management service cannot process a pull request because a pull operation is already in progress. |
| 0x80338007 | WS-Management 枚举会话已完成或已取消并无法使用。启动一个新的枚举。 |
The WS-Management enumeration session is finished or cancelled and cannot be used. Start a new enumeration. |
| 0x80338008 | 事件订阅已关闭并无法使用。启动一个新的订阅。 |
The event subscription is already closed and cannot be used. Start a new subscription. |
| 0x80338009 | 事件订阅会话正在关闭并无法使用。启动一个新的订阅。 |
The event subscription session is closing and cannot be used. Start a new subscription. |
| 0x8033800A | 具有事件订阅的应用程序或脚本未请求检测信号间隔内的拉操作。订阅会话已关闭。启动一个新的订阅。 |
The application or script that has an event subscription did not request a pull operation within the heartbeat interval.The subscription session was closed. Start a new subscription. |
| 0x8033800B | 事件源未在检测信号间隔内返回事件。订阅会话已关闭。启动一个新的订阅。 |
The event source did not return events within the heartbeat interval.The subscription session was closed. Start a new subscription. |
| 0x8033800C | WS-Management 服务不支持指定的超时。指定的值小于该设置允许的最小值。更改超时并重试请求。 |
The WS-Management service does not support the specified timeout.The value specified is smaller than the minimum allowed value for this setting.Change the timeout value and try the request again. |
| 0x8033800D | WS-Management 服务不支持请求中指定的 SOAP 版本。 |
The WS-Management service does not support the SOAP version specified in the request. |
| 0x8033800E | WS-Management 服务不支持请求中指定的编码。 |
The WS-Management service does not support the encoding specified in the request. |
| 0x8033800F | WS-Management 服务无法处理该请求。该请求包含一个或多个无效的 SOAP 标头。 |
The WS-Management service cannot process the request. The request contains one or more invalid SOAP headers. |
| 0x80338010 | WS-Management 服务无法处理由客户端标记为 mustUnderstand 的请求中的 SOAP 标头。这可能是由于使用了不受支持的协议版本而造成的，或者可能是客户端和服务器实现之间不兼容。 |
The WS-Management service cannot process a SOAP header in the request that is marked as mustUnderstand by the client. This could be caused by the use of a version of the protocol which is not supported, or may be an incompatibility between the client and server implementations. |
| 0x80338011 | WS-Management 服务无法处理该请求。该请求没有所有期望的 SOAP 标头。 |
The WS-Management service cannot process the request. The request does not have all the expected SOAP headers. |
| 0x80338012 | 客户端无法连接到请求中指定的目标。请验证该目标上的服务是否正在运行以及是否正在接受请求。有关目标(通常是 IIS 或 WinRM)上运行的 WS 管理服务，请查阅日志和文档。如果目标是 WinRM 服务，则在目标上运行以下命令来分析和配置 WinRM 服务: \"winrm quickconfig\"。 |
The client cannot connect to the destination specified in the request.Verify that the service on the destination is running and is accepting requests.Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: \"winrm quickconfig\". |
| 0x80338013 | WS-Management 服务不支持请求中指定的操作。 |
The WS-Management service does not support the action specified in the request. |
| 0x80338014 | WS-Management 服务无法处理该请求，因为资源已脱机。请稍后在资源联机时重试该请求。 |
The WS-Management service cannot process the request because the resource is offline. Retry the requestlater when the resource is online. |
| 0x80338015 | WS-Management 服务无法识别传递到 Put 或 Create 方法的对象的格式。输入 XML 可能不适合于资源或为资源使用的架构不正确。请更改请求中的输入 XML。 |
The WS-Management service cannot identify the format of the object passed to a Put or Create method.The input XML may not be appropriate for the resource or uses the wrong schema for the resource.Change the input XML in the request. |
| 0x80338016 | 传递到 WS-Management Enumerate 方法的过期时间无效。该时间值可能为零，或引用的是过去的某个时间。更改过期时间并重试请求。 |
The expiration time passed to the WS-Management Enumerate method is not valid. The time value may be zeroor refer to a time in the past. Change the expiration time and try the request again. |
| 0x80338017 | 数据源不支持过期时间。从请求中删除过期时间，并重试请求。 |
The data source does not support expiration time. Remove the expiration time from the request and try the request again. |
| 0x80338018 | 数据源不支持筛选。从请求中删除筛选器，并重试请求。 |
The data source does not support filtering. Remove the filter from the request and try the request again. |
| 0x80338019 | 此资源不支持筛选器方言(与筛选器关联的类型)。更改筛选器方言或从请求中将其删除，然后重试请求。 |
The filter dialect (the type associated with the filter) was not supported for this resource.Change the filter dialect or remove it from the request and try the request again. |
| 0x8033801A | 数据源无法处理筛选器。该筛选器可能丢失或无效。更改筛选器，然后重试请求。 |
The data source could not process the filter. The filter might be missing or it might be invalid.Change the filter and try the request again. |
| 0x8033801B | 枚举中的 WS-Enumeration 上下文无效。枚举可能已完成或已取消。无法再使用该枚举上下文。启动一个新的枚举。 |
The WS-Enumeration context in the enumeration is not valid. Enumeration may have been completed or canceled.You cannot use this enumeration context anymore. Start a new enumeration. |
| 0x8033801C | 拉操作在 MaxTime 期间没有获取任何数据。但枚举仍有效。客户端可以尝试发出另一个拉请求以检索数据。 |
The pull operation did not get any data in the MaxTime duration. But the enumeration is still valid.The client can attempt to do another pull request to retrieve data. |
| 0x8033801D | WS-Management 服务无法续订枚举。启动一个新的枚举。 |
The WS-Management service cannot renew the enumeration. Start a new enumeration. |
| 0x8033801E | WS-Management 服务不支持指定资源的传递模式。客户端应更改订阅以使用受支持的传递模式之一。 |
The WS-Management service does not support the delivery mode for the specified resource. The client should change thesubscription to use one of the supported delivery modes. |
| 0x8033801F | 订阅的过期时间无效。该时间不受支持，为零或者为过去的某个时间。更改过期时间并重试请求。 |
The expiration time of the subscription is invalid. The time is either not supported, zero or a time that happened in the past.Change the expiration time and try the request again. |
| 0x80338020 | 为订阅指定的过期时间无效。将过期时间指定为一段持续时间。 |
The expiration time specified for subscription was invalid. Specify the expiration time as a duration. |
| 0x80338021 | 事件源不支持筛选。从请求中删除筛选器，然后重试请求。 |
The event source does not support filtering. Remove the filter from the request and try the request again. |
| 0x80338022 | 事件源无法处理指定的筛选器。更改筛选器或从请求中将其删除，然后重试请求。 |
The event source cannot process the specified filter.Change the filter or remove it from the request and try the request again. |
| 0x80338023 | 事件源无法处理订阅。 |
The event source cannot process the subscription. |
| 0x80338024 | WS-Management 服务无法续订事件订阅。创建一个新的订阅。 |
The WS-Management service cannot renew the event subscription. Create a new subscription. |
| 0x80338025 | WS-Management 服务无法完成 WS-Eventing 请求，因为该请求具有一些未知的或无效的内容并且无法对其进行处理。 |
The WS-Management service cannot complete the WS-Eventing request because the request had some unknown or invalid content and couldnot be processed. |
| 0x80338026 | WS-Management 服务无法处理响应，因为该响应大于允许的最大大小。 |
The WS-Management service cannot process the response because it is larger than the maximum size allowed. |
| 0x80338027 | WS-Management 服务无法处理该请求，因为请求数据包没有有效的 SOAP 主体。 |
The WS-Management service cannot process the request because the request packet does not have a valid SOAP body. |
| 0x80338028 | 在订阅中指定的恢复上下文无效。可能已过期，或格式不正确。 |
The resumption context specified in the subscription is invalid. It may have expired, or be in the wrong format. |
| 0x80338029 | WS-Management 服务无法在 OperationTimeout 中指定的时间内完成操作。 |
The WS-Management service cannot complete the operation within the time specified in OperationTimeout. |
| 0x8033802A | 事件源不支持可恢复的订阅。 |
The event source does not support subscriptions that can be resumed. |
| 0x8033802B | WS-Management 服务不支持订阅请求的恢复类型。 |
The WS-Management service does not support the type of resumption requested by the subscription. |
| 0x8033802C | 请求中包含不支持的字符编码。WS-Management 仅支持以 UTF-8 或 UTF-16 编码的请求。更改请求中的字符编码并重试请求。 |
The request contains character encoding that is unsupported. WS-Management only supports requests that areencoded in UTF-8 or UTF-16. Change the character encoding in the request and try the request again. |
| 0x8033802D | URI 的长度大于允许的最大长度。 |
The URI is longer than the maximum length allowed. |
| 0x8033802E | WS-Management 服务无法处理该请求，因为订阅 ID 无效。 |
The WS-Management service cannot process the request because the subscription ID is invalid. |
| 0x8033802F | WS-Management 服务无法处理批请求。请求必须指定 MaxItems、MaxCharacters 或 MaxTime。 |
The WS-Management service cannot process the batch request. The request must specify either MaxItems, MaxCharacters,or MaxTime. |
| 0x80338030 | 事件的收件人未确认事件送达。再次提交订阅，无需确认选项。 |
The receiver of the event did not acknowledge the event delivery.Submit the subscription again without the acknowledgement option. |
| 0x80338031 | WS-Management 服务无法处理该请求，因为请求中的 WS-Addressing Action URI 与该资源不兼容。 |
The WS-Management service cannot process the request because the WS-Addressing Action URI in the request is notcompatible with the resource. |
| 0x80338032 | WS-Management 服务无法完成请求中的 WS-Addressing Action URI，因为该资源已在使用。 |
The WS-Management service cannot complete the WS-Addressing Action URI in the request because the resourcewas already in use. |
| 0x80338033 | WS-Management 服务无法创建该资源，因为它已存在。 |
The WS-Management service cannot create the resource because it already exists. |
| 0x80338034 | WS-Management 服务无法完成该请求，因为收件人不接受事件的送达。收件人请求取消订阅。事件收件人返回此消息以强制取消订阅。 |
The WS-Management service cannot complete the request because the receiver does not accept the delivery of events.The receiver requests that the subscription be cancelled. Event receivers return this message to force thecancellation of a subscription. |
| 0x80338035 | WS-Management 服务无法处理该请求，因为请求的编码超出内部编码限制。请重新配置客户端，以发送符合服务编码限制的消息。 |
The WS-Management service cannot process the request because the encoding of the request exceeds an internalencoding limit. Reconfigure the client to send messages which fit the encoding limits of the service. |
| 0x80338036 | WS-Management 服务无法验证发件人的身份。 |
The WS-Management service cannot authenticate the sender. |
| 0x80338037 | WS-Management 服务不支持 WS-Addressing 终结点引用的格式。 |
The WS-Management service does not support the format of the WS-Addressing Endpoint Reference. |
| 0x80338038 | 订阅中的书签无效。该书签可能已过期或已损坏。发布一个不带任何书签的新订阅，或查找正确的书签。 |
The bookmark in the subscription is invalid. The bookmark may be expired or corrupted. Issue a new subscriptionwithout any bookmarks or locate the correct bookmark. |
| 0x80338039 | WS-Management 服务无法处理该请求，因为一个或多个选项无效。选项名或值可能无效或用法组合不正确。检索资源的编录项并确定如何更正无效的选项值。 |
The WS-Management service cannot process the request because one or more options are not valid. The option names orvalues may not be valid or they are used in incorrect combinations. Retrieve the catalog entry for the resource anddetermine how to correct the invalid option values. |
| 0x8033803A | WS-Management 服务无法处理该请求，因为操作的参数无效。 |
The WS-Management service cannot process the request because a parameter for the operation is not valid. |
| 0x8033803B | WS-Management 服务无法处理该请求。缺少资源 URI 或其格式不正确。请检查文档或使用以下命令以获取有关如何创建资源 URI 的信息: \"winrm help uris\"。 |
The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format.Check the documentation or use the following command for information on how to construct a resource URI: \"winrm help uris\". |
| 0x8033803C | WS-Management 服务需要有效的 System URI 才能处理该请求。 |
The WS-Management service requires a valid System URI to process the request. |
| 0x8033803D | WS-Management 服务无法处理该请求，因为资源的选择器无效。 |
The WS-Management service cannot process the request because the selectors for the resource are not valid. |
| 0x8033803E | 当前地址中没有可用的请求元数据。请使用新地址重试该请求。 |
The requested metadata is not available at the current address. Retry the request with a new address. |
| 0x8033803F | WS-Management 服务忙于处理其他请求。请稍后重试。 |
The WS-Management service is busy servicing other requests. Retry later. |
| 0x80338040 | WS-Management 服务无法重命名资源。资源的选择器不正确。该资源可能已存在、地址可能不正确或资源 URI 可能无效。请更改请求并重试。 |
The WS-Management service cannot rename the resource. The selectors for the resource are not correct. Theresource may exist already, the address may be incorrect, or the resource URI may be invalid. Change therequest and retry. |
| 0x80338041 | 消息中的 SOAP XML 与相应的 XML 架构定义不匹配。请更改 XML 并重试。 |
The SOAP XML in the message does not match the corresponding XML schema definition. Change the XML and retry. |
| 0x80338042 | WS-Management 服务不支持指定的功能。删除请求中不支持的功能并重试。 |
The WS-Management service does not support the specified feature. Remove the unsupported feature from the request and retry. |
| 0x80338043 | WS-Management 服务无法处理该请求，因为 XML 无效。 |
The WS-Management service cannot process the request because the XML is invalid. |
| 0x80338044 | WS-Management 服务无法处理该请求，因为 URI 包含意外的选择器。 |
The WS-Management service cannot process the request because the URI contains an unexpected selector. |
| 0x80338045 | 事件源试图传递一个事件，而此时某个传递过程已在进行。 |
The event source is attempting to deliver an event when a delivery is in progress already. |
| 0x80338046 | WS-Management 服务找不到系统。 |
The WS-Management service cannot locate the system. |
| 0x80338047 | 请求中的信封大小上限太大。更改信封大小上限，然后重试请求。 |
The maximum envelope size in the request is too large.Change the maximum envelope size and try the request again. |
| 0x80338048 | WS-Management 服务计算出的响应超出请求中的信封大小上限。 |
The response that the WS-Management service computed exceeds the maximum envelope size in the request. |
| 0x80338049 | WS-Management 服务计算出的响应超出信封大小的内部限制。 |
The response that the WS-Management service computed exceed the internal limit for envelope size. |
| 0x8033804A | WS-Management 服务无法处理该请求，因为 URI 包含的选择器太多。 |
The WS-Management service cannot process the request because the URI contains too many selectors. |
| 0x8033804B | WS-Management 服务无法处理该请求，因为它包含的选项太多。 |
The WS-Management service cannot process the request because it contains too many options. |
| 0x8033804C | WS-Management 服务不支持请求中使用的字符集。将请求更改为使用 UTF-8 或 UTF-16。 |
The WS-Management service does not support the character set used in the request. Change the request to use UTF-8 or UTF-16. |
| 0x8033804D | 操作已成功并且无法反转，但是结果太大，无法发送。 |
The operation succeeded and cannot be reversed but the result is too large to send. |
| 0x8033804E | WS-Management 服务不支持请求 XML 中的空白。 |
The WS-Management service does not support white space in the request XML. |
| 0x8033804F | WS-Management 服务不支持请求中的筛选器方言。筛选器方言是筛选器的类型，例如 XPath 或 WQL。 |
The WS-Management service does not support the filter dialect in the request. The filter dialect is the type of filter, suchas XPath or WQL. |
| 0x80338050 | WS-Management 服务无法处理该请求，因为它包含已过期的书签。 |
The WS-Management service cannot process the request because it contains a bookmark that is expired. |
| 0x80338051 | WS-Management 提供程序不支持指定的选项集，因为其中的一个选项的 mustComply 设置为 true。请将该选项的 mustComply 更改为 false。 |
The WS-Management provider does not support the specified option set because mustComply for one of the options is set to true.Change mustComply for one of the options to false. |
| 0x80338052 | WS-Management 服务无法处理该请求，因为一个或多个选项的名称无效。 |
The WS-Management service cannot process the request because one or more of the options has an invalid name. |
| 0x80338053 | WS-Management 服务无法处理该请求，因为一个或多个选项的值无效。 |
The WS-Management service cannot process the request because one or more of the options has an invalid value. |
| 0x80338054 | WS-Management 服务无法处理该请求。操作所需的参数的类型不正确。 |
The WS-Management service cannot process the request. A parameter that is required for the operation is not thecorrect type. |
| 0x80338055 | WS-Management 服务无法处理该请求。参数名无效。 |
The WS-Management service cannot process the request. A parameter name is invalid. |
| 0x80338056 | WS-Management 服务无法处理该请求，因为 XML 内容包含无效的值。 |
The WS-Management service cannot process the request because the XML content has invalid values. |
| 0x80338057 | WS-Management 服务无法处理该请求，因为 XML 内容缺少值。 |
The WS-Management service cannot process the request because the XML content has missing values. |
| 0x80338058 | WS-Management 服务无法识别传递到 Put 或 Create 方法的对象的格式。输入 XML 的 XML 命名空间无效。在请求中更改输入 XML 的 XML 命名空间。 |
The WS-Management service cannot identify the format of the object passed to a Put or Create method.The XML namespace for the input XML is invalid. Change the XML namespace for the input XML in the request. |
| 0x80338059 | WS-Management 服务无法处理该请求，因为 URI 中的 XML 片断无效。 |
The WS-Management service cannot process the request because an XML fragment in the URI is invalid. |
| 0x8033805A | WS-Management 服务无法处理该请求，因为请求中没有所需的所有选择器。 |
The WS-Management service cannot process the request because the request did not contain all required selectors. |
| 0x8033805B | WS-Management 服务无法处理该请求，因为请求包含对资源无效的选择器。 |
The WS-Management service cannot process the request because the request contained invalid selectors for the resource. |
| 0x8033805C | WS-Management 服务无法处理该请求，因为某个选择器的一个值的类型不正确。 |
The WS-Management service cannot process the request because a value for a selector is of the wrong type. |
| 0x8033805D | WS-Management 服务无法处理该请求，因为选择器的值无效。 |
The WS-Management service cannot process the request because a value for the selector is invalid. |
| 0x8033805E | WS-Management 服务无法处理该请求，因为资源的选择器不确定。 |
The WS-Management service cannot process the request because the selectors for the resource are ambiguous. |
| 0x8033805F | WS-Management 服务无法处理该请求，因为该请求包含重复的选择器。 |
The WS-Management service cannot process the request because the request contains duplicate selectors. |
| 0x80338060 | WS-Management 服务无法处理该请求，因为该请求包含对目标资源无效的选择器。 |
The WS-Management service cannot process the request because the request contains invalid selectors for the target resource. |
| 0x80338061 | WS-Management 服务无法处理该请求，因为该请求包含对目标资源无效的 URI。 |
The WS-Management service cannot process the request because the request contains an invalid URI for the target resource. |
| 0x80338062 | WS-Management 服务无法处理该请求，因为该请求包含无效的目标系统。 |
The WS-Management service cannot process the request because the request contains an invalid target system. |
| 0x80338063 | WS-Management 服务无法处理 Create 请求，因为目标已存在。 |
The WS-Management service cannot process a Create request because the target already exists. |
| 0x80338064 | WS-Management 服务不支持该授权模式。 |
The WS-Management service does not support the mode of authorization. |
| 0x80338065 | 客户端不支持确认。 |
The client does not support acknowledgment. |
| 0x80338066 | 数据源不支持操作超时。 |
The data source does not support timeouts for the operation. |
| 0x80338067 | WS-Management 服务不支持区域设置。 |
The WS-Management service does not support the locale. |
| 0x80338068 | WS-Management 服务不支持过期时间。 |
The WS-Management service does not support the expiration time. |
| 0x80338069 | WS-Management 服务不重试传递。 |
The WS-Management service does not retry deliveries. |
| 0x8033806A | 事件源不支持检测信号。 |
The event source does not support heartbeats. |
| 0x8033806B | 事件源不支持书签。 |
The event source does not support bookmarks. |
| 0x8033806C | WS-Management 服务不支持 MaxItems 的配置。 |
The WS-Management service does not support the configuration for MaxItems. |
| 0x8033806D | WS-Management 服务不支持 MaxTime 的配置。 |
The WS-Management service does not support the configuration for MaxTime. |
| 0x8033806E | WS-Management 服务不支持 MaxEnvelopeSize 配置中的值。 |
The WS-Management service does not support the value in the configuration for MaxEnvelopeSize. |
| 0x8033806F | 事件源不支持 MaxEnvelopePolicy。 |
The event source does not support the MaxEnvelopePolicy. |
| 0x80338070 | WS-Management 服务不支持未筛选的枚举。 |
The WS-Management service does not support unfiltered enumeration. |
| 0x80338071 | WS-Management 服务不支持不安全的地址。 |
The WS-Management service does not support insecure addresses. |
| 0x80338072 | WS-Management 服务不支持格式不匹配。 |
The WS-Management service does not support format mismatch. |
| 0x80338073 | WS-Management 服务不支持安全令牌的格式。 |
The WS-Management service does not support the format of the security token. |
| 0x80338074 | 服务返回一个响应，表明不支持该方法。 |
The service returned a response that indicates that the method is unsupported. |
| 0x80338075 | WS-Management 服务不支持指定的媒体类型。 |
The WS-Management service does not support the specified media type. |
| 0x80338076 | WS-Management 服务不支持寻址模式。 |
The WS-Management service does not support the addressing mode. |
| 0x80338077 | WS-Management 服务不支持片断传输。 |
The WS-Management service does not support fragment transfer. |
| 0x80338078 | 客户端在初始化枚举之前发送了一个请求。 |
The client sent a request before the enumeration was initialized. |
| 0x80338079 | WS-Management 服务无法找到可以处理该请求的组件。 |
The WS-Management service failed to locate the component that can process the request. |
| 0x8033807A | 资源 URI 的查询字符串中发生语法错误。 |
A syntax error occurred in the query string for the resource URI. |
| 0x8033807B | 配置的 MAC 不在计算机上启用的 DHCP 适配器列表中。 |
The MAC that is configured is not in the list of enabled DHCP adapters on the computer. |
| 0x8033807C | 配置的 MAC 地址没有任何单播地址。 |
The MAC address that is configured does not have any unicast addresses. |
| 0x8033807D | WS-Management 服务无法在具有已配置 MAC 地址的适配器中找到动态 IP 地址。 |
The WS-Management service cannot find the dynamic IP address on the adapter with the configured MAC address. |
| 0x8033807E | WS-Management 服务无法处理该请求，因为该请求中的信封过小。 |
The WS-Management service cannot process the request because the envelope size in the request is too small. |
| 0x8033807F | WS-Management 服务无法处理该请求。EndPointReference 包含的嵌套 EndPointReference 数超出WS-Management 支持的数目。 |
The WS-Management service cannot process the request. The EndPointReference contains more nested EndPointReferencesthan WS-Management supports. |
| 0x80338080 | WS-Management 服务无法初始化该请求。 |
The WS-Management service cannot initialize the request. |
| 0x80338081 | WS-Management 服务无法处理该请求，因为该请求中的超时标头无效。 |
The WS-Management service cannot process the request because the timeout header in the request is invalid. |
| 0x80338082 | WS-Management 服务无法找到请求的证书。 |
The WS-Management service cannot find the certificate that was requested. |
| 0x80338083 | WS-Management 服务无法处理该请求。数据源无法返回请求的结果。 |
The WS-Management service cannot process the request. The data source failed to return results for the request. |
| 0x80338084 | 由于上一个 Pull 请求失败，枚举无效。 |
The enumeration is invalid because previous Pull request failed. |
| 0x80338085 | WS-Management 服务无法更改相互配置。 |
The WS-Management service cannot change a mutual configuration. |
| 0x80338086 | WS-Management 服务不支持指定的枚举模式。 |
The WS-Management service does not support the specified enumeration mode. |
| 0x80338087 | WS-Management 服务无法保证返回请求区域中的所有数据，因为某些数据源可能无法符合要求。使用区域设置作为提示重新发送远程请求(SOAP 标头应该设置 mustUnderstand=\"false\") |
The WS-Management service cannot guarantee that all data is returned in the requested locale as somedata sources may not be able to comply. Resend the remote request with locale as a hint (the SOAPheader should have mustUnderstand=\"false\") |
| 0x80338088 | WSMan 组策略配置已损坏。 |
The WSMan group policy configuration is corrupted. |
| 0x80338089 | 指定的侦听程序地址无效。可以使用下列格式之一指定地址: *、IP:、MAC:。请更改侦听程序地址，然后重试请求。 |
The listener address specified is invalid. The address can be specified in one of the following formats: *, IP:, MAC:.Change the listener address and try the request again. |
| 0x8033808A | 无法更改 GPO 控制的设置。 |
Cannot change GPO controlled setting. |
| 0x8033808B | 客户端正试图从单个订阅会话同时接收多个事件。这是不支持的。 |
The client is attempting to concurrently receive events from a single subscription session.This is not supported. |
| 0x8033808C | 源发送批事件的速度快于订户可以接受的速度。如果没有为订阅指定确认，且在客户端消化完这些事件之前又有新事件从源到达时，可能会发生这种问题。 |
The source is sending event batches faster than the subscriber can consume.This can happen if acknowledgments are not specified for the subscription andnew events are arriving from the source before the client has consumed them. |
| 0x8033808D | 源发送事件的连接与客户端施加的安全限制不匹配。 |
The source is sending events in a connection that did not match the security restrictions imposed by the client. |
| 0x8033808E | WS-Management 客户端无法处理该请求。事件源标识与客户端订阅的计算机的标识不匹配。 |
The WS-Management client cannot process the request. The event source identity does not match the identity of the machine that the client subscribed to. |
| 0x8033808F | 客户端无法启动有效的侦听程序，以根据指定的输入设置接收订阅事件。 |
The client could not start a valid listener to receive subscription events based on the specified input settings. |
| 0x80338090 | 此资源不支持该片断路径方言。 |
The fragment path dialect is not supported for this resource. |
| 0x80338091 | 无法执行片断级操作。如果指定片断方言，则不能缺少片断路径。 |
Cannot execute the Fragment-Level operation. The fragment path cannot be missing if the fragment dialect is specified. |
| 0x80338092 | 无法执行片断级操作，因为片断方言的值无效。 |
Cannot execute the Fragment-Level operation because of invalid value for the fragment dialect. |
| 0x80338093 | 无法执行片断级操作，因为片断路径无效。请检查片断路径字符串的语法。还需要检查片断路径字符串中属性名称的拼写和大小写: 它们必须与资源属性的拼写和大小写相匹配。 |
Cannot execute the Fragment-Level operation because the fragment path is invalid. Check the syntax of the fragment path string.Also check the spelling and the case of the property names in the fragment path string: they have to match the spelling and the case of the resource properties. |
| 0x80338094 | 指定的批参数与指定的事件传递模式不兼容。如果为不同的模式传递其它特定模式的 batchSettings，可能发生这种问题。例如，\"MaxItems\" 和\"MaxLatency\" 等批设置与单个事件推模式或拉模式不兼容。 |
The specified batch parameter is incompatible with the specified event delivery mode. This can happen if batchSettings for a specific mode arepassed for a different mode. For example, batchSettings like \"MaxItems\" and\"MaxLatency\" are not compatible with single event push mode or pull mode. |
| 0x80338095 | 从推订阅源到客户端的连接测试失败。如果从事件源所在的服务器计算机上无法到达启动推订阅的客户端计算机，则可能发这种问题。可能的原因包括防火墙或某些其他网络边界。修改订阅以使用基于订阅的拉。 |
The connectivity test from the push subscription source to the client failed. This can happen if the client machine initiating the push subscriptionis unreachable from the server machine where the event source is located. Possible reasons include firewall or some other network boundary.Modify subscription to use Pull based subscription. |
| 0x80338096 | 订阅数据包的 EndTo 元素地址无效或与 NotifyTo 元素地址不匹配。对于订阅，在订阅请求中不需要有 EndTo 元素。如果有该元素，则它的地址应该与 NotifyTo 元素中指定的地址相匹配。 |
The subscribe packet had an EndTo element address that does not match the NotifyTo element address or it was invalid. For subscription the EndTo elementneed not be present in the subscription request. If it exists then it's address should match the address specified in NotifyTo element. |
| 0x80338097 | 事件源发送了标头无法被客户端处理的事件数据包。如果格式错误或标头包含客户端无法理解的 mustUnderstand 属性，则可能发生这种问题。 |
The event source sent an event packet whose header could not be processed by the client. This can happen if it was malformedor if the header had a mustUnderstand attribute that could not be understood by the client. |
| 0x80338098 | 尝试操作正在关闭的会话。如果另一个线程正在关闭所使用的会话，则会发生这种问题。 |
An operation is being attempted on a session that is being closed.This can happen if the session that is being used is also being closedby another thread. |
| 0x80338099 | 建立该订阅会话的侦听程序不再有效。如果 WSMAN 服务侦听程序配置已更改并且订阅已经处于活动状态且使用了一个删除的配置，则可能发生这种问题。 |
The listener on which the subscription session was established is no longer valid. This can happen if the WSMAN service listener configuration has been changedand a subscription was already active and using one of the configurations that was deleted. |
| 0x8033809A | 系统无法加载插件。 |
The system failed to load the plugin. |
| 0x8033809B | 设置了此订阅的远程计算机上的 WS-Management 服务已请求关闭该订阅。如果正在关闭远程计算机上的 WS-Management 服务，则可能发生这种问题。要解决该问题，请在远程计算机上重新启动 WS-Management 服务，然后重新创建订阅。 |
The WS-Management service on the remote machine with which this subscription had been set up has requested that the subscription be closed.This can happen if the WS-Management service on the remote machine was being shutdown.To correct this problem restart the WS-Management service on the remote machine and re-create the subscription. |
| 0x8033809C | 事件源无法将事件传递到客户端。可能是因为网络问题阻止源连接到客户端，才发生这种问题。 |
The event source was unable to deliver events to the client.This can happen due to network issues preventing the source from connectingto the client. |
| 0x8033809D | 出现未知的安全错误。 |
An unknown security error occurred. |
| 0x8033809E | 事件源已取消订阅会话。 |
The event source cancelled the subscription session. |
| 0x8033809F | TrustedHosts 列表包含无效的主机名或主机名样式。 |
TrustedHosts list contains an invalid hostname or hostname pattern. |
| 0x803380A0 | 订阅数据包在传递部分没有 NotifyTo 元素。 |
The subscribe packet does not have NotifyTo element in the delivery section. |
| 0x803380A1 | 订阅数据包在 NotifyTo 部分没有 Address 元素。 |
The subscribe packet does not have Address element in the NotifyTo section. |
| 0x803380A2 | 订阅数据包在 NotifyTo 部分包含无效的地址。 |
The subscribe packet contains invalid Address in the NotifyTo section. |
| 0x803380A3 | 订阅数据包在传递部分包含无效的区域设置值。 |
The subscribe packet contains invalid Locale value in the delivery section. |
| 0x803380A4 | 订阅数据包包含无效的检测信号值。 |
The subscribe packet contains invalid heartbeat value. |
| 0x803380A6 | WS-Management 服务不支持指定资源的选项功能。从请求中删除选项，然后重试。 |
The WS-Management service does not support the options feature for the specified resource. Remove the options from the request and retry. |
| 0x803380A7 | 订阅数据包包含的批处理大小值小于支持的值。 |
The subscribe packet contains batch size value which is smaller than supported value. |
| 0x803380A8 | WS-Management 服务无法处理该订阅请求。传递模式无效或缺失。 |
The WS-Management service cannot process the subscribe request. The delivery mode is either invalid or missing. |
| 0x803380A9 | WS-Management 服务无法处理该请求。找不到提供程序方法。 |
The WS-Management service cannot process the request. The provider method was not found. |
| 0x803380AA | WinRM 客户端无法创建推送订阅，原因是没有任何已配置的侦听器匹配指定的主机名和传输，或者是由选定侦听器使用的端口上没有已启用的防火墙例外。更改主机名和传输，创建相应的防火墙例外，或运行 winrm 快速配置。 |
The WinRM client could not create a push subscription because there are no listeners configured that match the specified hostname and transport, or because there is no enabled firewall exception on the port used by the selected listener.Change the hostname and transport, create an appropriate firewall exception, or run winrm quickconfig. |
| 0x803380AB | WinRM 客户端无法处理请求，原因是已指定凭据具有“无身份验证”标记。不应使用“无身份验证”选项指定任何用户名、密码或客户端证书。 |
The WinRM client could not process the request because credentials were specified along with the 'no authentication' flag. No user name, password or client certificate should be specified with the 'no authentication' option. |
| 0x803380AC | WinRM 客户端无法处理该请求。为此请求指定的标志无效。请删除或更改无效的标志，然后重试请求。 |
The WinRM client cannot process the request. An invalid flag was specified for this request.Remove or change the invalid flag and try the request again. |
| 0x803380AD | WinRM 客户端无法处理该请求。该请求只能指定一种身份验证机制。如果设置了“无身份验证”标志，则不应指定身份验证机制。请更改请求以仅指定一种身份验证机制或“无身份验证”，然后重试。 |
The WinRM client cannot process the request. The request must specify only one authentication mechanism.If the No Authentication flag is set, no authentication mechanism should be specified.Change the request to specify only one authentication mechanism or 'no authentication' and try again. |
| 0x803380AE | WinRM 客户端无法处理该请求。只有在身份验证机制是“协商”或 Kerberos 时才能使用 SPN 服务器端口。请删除 SPN 服务器端口或更改身份验证机制，然后重试请求。 |
The WinRM client cannot process the request. The SPN Server Port can only be used when the authentication mechanism is Negotiate or Kerberos.Remove the SPN Server Port or change the authentication mechanism and try the request again. |
| 0x803380AF | WinRM 客户端无法处理该请求。在使用智能卡或默认证书时，请求不能包含凭据。请删除凭据或更改身份验证机制，然后重试请求。 |
The WinRM client cannot process the request. The request must not include credentials when using a smart card or default certificate.Remove the credentials or change the authentication mechanism and try the request again. |
| 0x803380B0 | WinRM 客户端无法处理该请求。在使用基本身份验证机制或摘要式身份验证机制时，请求必须包含用户名和密码。请添加用户名和密码或更改身份验证机制，然后重试请求。 |
The WinRM client cannot process the request. Requests must include user name and password when Basic or Digest authentication mechanism is used.Add the user name and password or change the authentication mechanism and try the request again. |
| 0x803380B1 | WinRM 客户端无法处理该请求。在对身份验证使用证书时，请求必须包含用户名和密码。请删除用户名和密码或更改身份验证机制，然后重试请求。 |
The WinRM client cannot process the request. Requests must not include user name and password when a certificate is used for authentication.Remove the user name and password or change the authentication mechanism and try the request again. |
| 0x803380B2 | WinRM 客户端无法处理该请求。在指定 WSManFlagCredUsernamePassword 标志时，请求必须包含凭据。添加凭据或删除 WSManFlagCredUsernamePassword 标志，然后重试请求。 |
The WinRM client cannot process the request. Requests must include credentials if they specify the following flag: WSManFlagCredUsernamePassword.Add the credentials or remove the WSManFlagCredUsernamePassword flag and try the request again. |
| 0x803380B3 | WinRM 客户端无法处理该请求。带有凭据的请求必须包含 WSManFlagCredUsernamePassword 标志。请添加标志或删除凭据，然后重试请求。 |
The WinRM client cannot process the request. Requests with credentials must include the following flag: WSManFlagCredUsernamePassword.Add the flag or remove the credentials and try the request again. |
| 0x803380B4 | WinRM 客户端无法处理该请求。在对身份验证使用证书时，请求必须包含证书指纹。请更改请求使其包含证书指纹，然后再试一次。 |
The WinRM client cannot process the request. Requests must include the certificate thumbprint when a certificate is used for authentication.Change the request to include the certificate thumbprint and try again. |
| 0x803380B5 | WinRM 客户端无法处理该请求。请求必须包含用于身份验证的证书类型。请更改请求使其包含该证书类型，然后再试一次。 |
The WinRM client cannot process the request. Requests must include the type of certificate to use for authentication.Change the request to include the type of the certificate and try again. |
| 0x803380B6 | WinRM 客户端无法处理该请求。请求必须包含用于身份验证的证书的位置(计算机或用户证书存储区)。请更改请求使其包含证书的位置，然后再试一次。 |
The WinRM client cannot process the request. Requests must include the location (machine or user certificate store) of the certificate used for authentication.Change the request to include the location of the certificate and try again. |
| 0x803380B7 | WinRM 客户端无法处理该请求。证书结构不完整。请更改证书结构，然后重试请求。 |
The WinRM client cannot process the request. The certificate structure was incomplete.Change the certificate structure and try the request again. |
| 0x803380B8 | WinRM 客户端无法处理该请求。不能为本地请求提供凭据。请删除凭据，然后重试请求。 |
The WinRM client cannot process the request. Credentials must not be provided for local requests.Remove the credentials and try the request again. |
| 0x803380B9 | WinRM 客户端无法处理该请求。不能为本地请求提供连接选项。请删除连接选项，然后重试请求。 |
The WinRM client cannot process the request. Connection options must not be provided for local requests.Remove the connection options and try the request again. |
| 0x803380BA | WinRM 客户端无法处理该请求。WSManCreateSession 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManCreateSession function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380BB | WinRM 客户端无法处理该请求。WSManEnumerate 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManEnumerate function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380BC | WinRM 客户端无法处理该请求。WSManSubscribe 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManSubscribe function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380BD | WinRM 客户端无法处理该请求。应该包含请求结果的参数为 NULL。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. The parameter that should contain the result of the request is null.Change the request to include the missing parameter and try again. |
| 0x803380BE | WinRM 客户端无法处理该请求。请求缺少会话或枚举句柄。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. The request is missing the session or enumeration handle.Change the request to include the missing parameter and try again. |
| 0x803380BF | WinRM 客户端无法处理该请求。资源 URI 不能是 \"\" (空白或空字符串)或 NULL。请更改资源 URI，然后重试请求。 |
The WinRM client cannot process the request. The resource URI must not be \"\" (blank or empty string) or NULL.Change the resource URI and try the request again. |
| 0x803380C0 | WinRM 客户端无法处理该请求。资源定位器无效。请更改资源定位器，然后重试请求。 |
The WinRM client cannot process the request. The resource locator was invalid.Change the resource locator and try the request again. |
| 0x803380C1 | WinRM 客户端无法处理该请求。输入的 XML 不能是 \"\" (空白或空字符串)或 NULL。请更改输入的 XML，然后重试。 |
The WinRM client cannot process the request. The input XML must not be \"\" (blank or empty string) or NULL.Change the input XML and try the request again. |
| 0x803380C2 | WinRM 客户端无法处理该请求。批处理中要检索元素数目过小。请更改批处理中元素最大数目的值，然后重试请求。 |
The WinRM client cannot process the request. The maximum number of elements to be retrieved in a batch is too small.Change the value for the maximum number of elements in a batch and try the request again. |
| 0x803380C3 | WinRM 客户端无法处理该请求。批处理中要检索字符的最大数目过小。请更改批处理中字符最大数目的值，然后重试请求。 |
The WinRM client cannot process the request. The maximum number of characters to be retrieved in a batch is too small.Change the value for the maximum number of characters in a batch and try the request again. |
| 0x803380C4 | WinRM 客户端无法处理该请求。操作 URI 不能为 \"\" (空白或空字符串)或 NULL。请更改操作 URI，然后重试请求。 |
The WinRM client cannot process the request. The action URI must not be \"\" (blank or empty string) or NULL.Change the action URI and try the request again. |
| 0x803380C5 | WinRM 客户端无法处理该请求。检测信号间隔必须大于 0。请更改检测信号间隔，然后重试请求。 |
The WinRM client cannot process the request. The heartbeat interval must be greater than 0.Change the heartbeat interval and try the request again. |
| 0x803380C6 | WinRM 客户端无法处理该请求。请求必须包含且只能包含一种传递模式。请更改请求使其仅包含一种传递模式，然后再试一次。 |
The WinRM client cannot process the request. The request must contain one and only one delivery mode.Change the request to contain only one delivery mode and try again. |
| 0x803380C7 | WinRM 客户端无法处理该请求。关于信封大小的策略，请求包含了多个设置。请更改请求使其仅包含该策略的一个设置，然后再试一次。 |
The WinRM client cannot process the request. The request contained multiple settings for the policy regarding the maximum envelope size.Change the request to contain only one setting for the policy and try again. |
| 0x803380C8 | WinRM 客户端无法处理该请求。该请求包含过期时间，但是未指定是相对时间还是绝对时间。请更改请求使其指定过期时间的类型(绝对或相对)，然后再试一次。 |
The WinRM client cannot process the request. The request contained an expiration time, but did not specify if it was absolute or relative.Change the request to specify the type of the expiration time (absolute or relative) and try again. |
| 0x803380C9 | WinRM 客户端无法处理该请求。请求指定了过期时间的类型(绝对或相对)，但是未包含过期时间。请更改请求使其包含过期时间，然后再试一次。 |
The WinRM client cannot process the request. The request specified the type of the expiration time (absolute or relative) but it did not contain an expiration time.Change the request to include the expiration time and try again. |
| 0x803380CA | WinRM 客户端无法处理该请求。拉订阅请求包含与推订阅相关的标志。请更改标志，然后重试请求。 |
The WinRM client cannot process the request. The pull subscription request contained flags related to a push subscription.Change the flags and try the request again. |
| 0x803380CB | WinRM 客户端无法处理该请求，因为推送订阅请求包含不支持的传递传输。当前仅支持 HTTP 和 HTTPS 传输。请更改传递传输，然后重试该请求。 |
The WinRM client cannot process the request because the push subscription request contained an unsupported delivery transport. HTTP and HTTPS are the only currently supported transports.Change the delivery transport and try the request again. |
| 0x803380CC | WinRM 客户端无法处理该请求。强制订阅的传递地址太长。请更改传递地址，然后重试请求。 |
The WinRM client cannot process the request. The delivery address for push subscriptions was too long.Change the delivery address and try the request again. |
| 0x803380CD | WinRM 客户端无法处理该请求。请求包含压缩选项，但是它包含不能识别的值。请更改压缩选项的值，然后重试请求。 |
The WinRM client cannot process the request. The request contained the compression option but contained an unrecognized value.Change the value for the compression option and try the request again. |
| 0x803380CE | WinRM 客户端无法处理该请求。WSManDeliverEndSubscriptionNotification 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEndSubscriptionNotification function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380CF | WinRM 客户端无法处理该请求。WSManDeliverEvents 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEvents function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D0 | WinRM 客户端无法处理该请求。WSManGetBookmark 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManGetBookmark function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D1 | WinRM 客户端无法处理该请求。WSManDecodeObject 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManDecodeObject function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D2 | WinRM 客户端无法处理该请求。WSManEncodeObject(Ex) 函数需要参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManEncodeObject(Ex) function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D3 | WinRM 客户端无法处理该请求。WSManEnumeratorAddObject 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddObject function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D4 | WinRM 客户端无法处理该请求。WSManEnumeratorNextObject 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorNextObject function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D5 | WinRM 客户端无法处理该请求。WSManConstructError 函数需要参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManConstructError function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803380D6 | WinRM 服务无法处理该请求。对于本地会话，不支持推订阅。请将订阅类型更改为“拉”，然后再试一次。 |
The WinRM service cannot process the request. Push subscriptions are not supported for local session. Change subscription type to Pull and try again. |
| 0x803380D7 | WinRM 客户端无法处理该请求。未加密标志仅适用于 HTTP 传输。请删除未加密标志或更改传输，然后再试一次请求。 |
The WinRM client cannot process the request. The unencrypted flag only applies to the HTTP transport.Remove the unencrypted flag or change the transport and try again the request. |
| 0x803380D8 | WinRM 客户端无法处理该请求。在同时指定了 HTTP 传输时，证书参数无效。请删除证书参数或更改传输，然后再试一次请求。 |
The WinRM client cannot process the request. Certificate parameters are not valid when the HTTP transport is also specified.Remove the certificate parameters or change the transport and try again the request. |
| 0x803380D9 | WinRM 客户端无法处理该请求。连接字符串的格式应该为: [://][:][/]，其中 transport 是 \"http\" 或 \"https\"。Transport、port 和 suffix 是可选的。host 可以是主机名或 IP 地址。对于 IPv6 地址，请使用括号将地址括起来 - 例如 \"http://[1::2]:80/wsman\"。请更改连接字符串，然后重试请求。 |
The WinRM client cannot process the request. The connection string should be of the form [://][:][/] where transport is one of \"http\" or \"https\".Transport, port and suffix are optional. The host may be a hostname or an IP address.For IPv6 addresses, enclose the address in brackets - e.g. \"http://[1::2]:80/wsman\".Change the connection string and try the request again. |
| 0x803380DA | WinRM 客户端无法处理该请求。连接字符串包含不支持的传输。有效的传输为 \"http\" 或 \"https\"。请更改连接字符串，然后重试请求。 |
The WinRM client cannot process the request. The connection string contains an unsupported transport.Valid transports are \"http\" or \"https\".Change the connection string and try the request again. |
| 0x803380DB | WinRM 客户端无法处理该请求，因为连接字符串中指定的端口无效。请验证端口，然后重试该请求。有效值介于 1 和 65535 之间。请更改端口值，然后重试该请求。 |
The WinRM client cannot process the request because the port specified in the connection string is not valid.Verify the port and retry the request.Valid values are between 1 and 65535.Change the value for port and try the request again. |
| 0x803380DC | WinRM 客户端无法处理该请求。配置中指定的端口无效。有效值介于 1 和 65535 之间。请更改端口值，然后重试请求。 |
The WinRM client cannot process the request. The port specified in the configuration is invalid.Valid values are between 1 and 65535.Change the value for port and try the request again. |
| 0x803380DD | WinRM 服务无法处理该请求。WSMAN_FLAG_SEND_HEARTBEAT 标志要求事件枚举数为空。请更改标志或更改事件枚举数，然后重试请求。 |
The WinRM service cannot process the request. WSMAN_FLAG_SEND_HEARTBEAT flag requires the event enumerator to be empty.Change the flag or change the event enumerator and try the request again. |
| 0x803380DE | WinRM 客户端无法处理该请求。当前在客户端配置中禁用未加密通讯。请更改客户端配置，然后重试请求。 |
The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration.Change the client configuration and try the request again. |
| 0x803380DF | WinRM 客户端无法处理该请求。当前在客户端配置中禁用基本身份验证。请更改客户端配置，然后重试请求。 |
The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration.Change the client configuration and try the request again. |
| 0x803380E0 | WinRM 客户端无法处理该请求。当前在客户端配置中禁用摘要式身份验证。请更改客户端配置，然后重试请求。 |
The WinRM client cannot process the request. Digest authentication is currently disabled in the client configuration.Change the client configuration and try the request again. |
| 0x803380E1 | WinRM 客户端无法处理该请求。当前在客户端配置中禁用协商身份验证。请更改客户端配置，然后重试请求。如果这是针对本地配置的请求，请使用一个仍处于启用状态的身份验证机制。若要使用 Kerberos，请指定本地计算机名作为远程目标。若要使用基本身份验证，请指定本地计算机名作为远程目标，指定基本身份验证并提供用户名和密码。 |
The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client configuration.Change the client configuration and try the request again.If this is a request for the local configuration, use one of the enabled authentication mechanisms still enabled.To use Kerberos, specify the local computer name as the remote destination. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. |
| 0x803380E2 | WinRM 客户端无法处理该请求。当前在客户端配置中禁用 Kerberos 身份验证。请更改客户端配置，然后重试请求。 |
The WinRM client cannot process the request. Kerberos authentication is currently disabled in the client configuration.Change the client configuration and try the request again. |
| 0x803380E3 | WinRM 客户端无法处理该请求。当前已在客户端配置中禁用证书身份验证。更改客户端配置并重试该请求。 |
The WinRM client cannot process the request. Certificate authentication is currently disabled in the client configuration.Change the client configuration and try the request again. |
| 0x803380E4 | WinRM 客户端无法处理该请求。如果身份验证方案与 Kerberos 不同，或者客户端计算机未加入到域中，则必须使用 HTTPS 传输或者必须将目标计算机添加到 TrustedHosts 配置设置。使用 winrm.cmd 配置 TrustedHosts。请注意，TrustedHosts 列表中的计算机可能未经过身份验证。通过运行以下命令可获得有关此内容的更多信息: winrm help config。 |
The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain,then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting.Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.You can get more information about that by running the following command: winrm help config. |
| 0x803380E5 | WinRM 客户端无法处理该请求。只有在目标计算机是 TrustedHosts 列表的一部分或指定了“允许使用隐式凭据进行协商”选项时，才能使用默认凭据通过 HTTP 进行协商。 |
The WinRM client cannot process the request. Default credentials with Negotiate over HTTP can be used only if the target machine is part of the TrustedHosts list or the Allow implicit credentials for Negotiate option is specified. |
| 0x803380E6 | WinRM 客户端无法处理该请求。如果 SSL 配置将与其他服务共享，则 CertificateThumbprint 属性必须为空。 |
The WinRM client cannot process the request. The CertificateThumbprint property must be empty when the SSL configuration will be shared with another service. |
| 0x803380E7 | WinRM 客户端无法处理该请求。CertificateThumbprint 属性不能为 \"\" (空白或空字符串)或 NULL。 |
The WinRM client cannot process the request. The CertificateThumbprint property must not be \"\" (blank or empty string) or NULL. |
| 0x803380E8 | WinRM 客户端无法处理该请求。WinRM 客户端试图根据请求为一对 IP 地址和端口创建 SSL 配置，但是该 SSL 配置已经被其他服务拥用且无法共享。请使用不同的 IP 地址和端口组合，然后重试请求。 |
The WinRM client cannot process the request. The WinRM client tried to create an SSL configuration for a pair of IP address and port according to the request,but the SSL configuration for that pair is owned by another service and cannot be shared. Use a different IP address and port combination and try the request again. |
| 0x803380E9 | WinRM 客户端无法处理该请求。提供的证书 CN 和主机名不匹配。 |
The WinRM client cannot process the request. The certificate CN and the hostname that were provided do not match. |
| 0x803380EB | WinRM 客户端无法处理该请求。当传输为 HTTP 时，证书指纹必须为空。HTTP 不使用证书指纹。 |
The WinRM client cannot process the request. When HTTP is the transport, the Certificate thumbprint must be blank.HTTP does not use the Certificate thumbprint. |
| 0x803380EC | WinRM 客户端无法处理该请求。IP 筛选器无效。使用语法 IP1-IP2 指定范围。使用 \",\" 作为分隔符将多个范围分隔开。* 用于指明服务应侦听计算机上的所有可用 IP。在使用 * 时，将忽略筛选器中的其他范围。如果筛选器为空，则服务不侦听任何地址。例如，如果要将服务限制为仅侦听 IPv4 地址，则应该将 IPv6 筛选器留空。%n示例 IPv4 筛选器:2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22%n 示例 IPv6 筛选器:3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 |
The WinRM client cannot process the request. The IP Filter is invalid.Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using , as delimiter.* is used to indicate that the service should listen on all available IPs on the machine.When * is used, other ranges in the filter are ignored. If filter is blank, the service doesn't listen on any address.For example, if service should be restricted to listen on only IPv4 addresses, IPv6 filter should be left empty.%nExample IPv4 filters:2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22%n Example IPv6 filters:3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 |
| 0x803380ED | WinRM 客户端无法处理该请求。输入的 XML 修改实例的选择器或关键字。无法通过更改关键字来创建新实例或更改实例的标识。请更改输入的 XML，然后重试请求。 |
The WinRM client cannot process the request. The input XML modifies selectors or keys for the instance.You cannot create a new instance or change the identity of an instance by changing the keys.Change the input XML and try the request again. |
| 0x803380EE | WinRM 客户端无法处理该请求。未将证书的“增强型密钥用法”(EKU)字段设置为“服务器身份验证”。使用具有正确 EKU 的证书重试请求。 |
The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to \"Server Authentication\".Retry the request with a certificate that has the correct EKU. |
| 0x803380EF | WinRM 客户端无法处理该请求。从目标计算机得到的响应中没有任何结果。 |
The WinRM client cannot process the request. The response from the destination computer does not include any results. |
| 0x803380F0 | WinRM 客户端无法处理该请求。对创建请求的响应不包含有效的终结点引用。找不到 ResourceCreated 元素或者该元素中没有有效的内容。 |
The WinRM client cannot process the request. The response to a create request did not contain a valid end point reference.The ResourceCreated element was not found or did not contain valid content. |
| 0x803380F1 | WinRM 客户端无法处理该请求。从目标计算机得到的响应中不包含有效的 SOAP 枚举上下文。 |
The WinRM client cannot process the request. The response from the destination computer does not contain a valid SOAP enumeration context. |
| 0x803380F2 | WinRM 客户端无法处理该请求。从目标计算机得到的响应包含 WS-Management FragmentTransfer 标头，但是主体的内容未使用 WS-Management XmlFragment 包装器进行包装。 |
The WinRM client cannot process the request. The response from the destination computer contains a WS-Management FragmentTransfer header but the content of the body is not wrapped by the WS-Management XmlFragment wrapper. |
| 0x803380F3 | WinRM 客户端无法处理该请求。从目标计算机得到的响应包含一个或多个无效的 SOAP 标头。 |
The WinRM client cannot process the request. The response from the destination computer contains one or more invalid SOAP headers. |
| 0x803380F4 | WinRM 客户端无法处理该请求。它无法从来自目标计算机的响应中找到任何 SOAP 标头或主体元素。 |
The WinRM client cannot process the request. It cannot find any SOAP Headers or Body elements in the response from the destination computer. |
| 0x803380F5 | WinRM 客户端无法处理该请求。目标计算机对请求返回空响应。 |
The WinRM client cannot process the request. The destination computer returned an empty response to the request. |
| 0x803380F6 | WinRM 客户端无法处理该请求。目标计算机返回无效的 SOAP 错误。 |
The WinRM client cannot process the request. The destination computer returned an invalid SOAP fault. |
| 0x803380F7 | WinRM 客户端无法处理该请求。它无法确定从目标计算机得到的 HTTP 响应的内容类型。内容类型缺少或无效。 |
The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. |
| 0x803380F8 | WinRM 客户端无法处理该请求。从目标计算机得到的 HTTP 响应的格式与请求的格式不同。可能发送的是 Unicode 请求数据包，而收到的是 ANSI 数据包。 |
The WinRM client cannot process the request. The HTTP response from the destination computer was not in the same format as the request. A Unicode request packet may have been sent and an ANSI packet received. |
| 0x803380F9 | WinRM 客户端无法处理该请求。加密的邮件正文格式无效，不能被解密。请确保服务正在根据规格加密邮件正文。 |
The WinRM client cannot process the request. The encrypted message body has an invalid format and cannot be decrypted. Ensure that the service is encrypting the message body according to the specifications. |
| 0x803380FA | WinRM 客户端无法处理该请求。资源 URI 无效: 它没有包含关键字，而所选类并非 Singleton。要访问非 Singleton 类的实例，必须提供关键字。使用下列命令获取有关如何构造资源 URI 的详细信息: \"winrm help uris\"。 |
The WinRM client cannot process the request. The resource URI is not valid: it does not contain keys, but the class selected is not a singleton.To access an instance which is not a singleton, keys must be provided.Use the following command to get more information in how to construct a resource URI: \"winrm help uris\". |
| 0x803380FB | WinRM 客户端无法处理该请求。具有 WQL 筛选器的枚举操作的资源 URI 不能包含关键字并且类名必须为 \"*\" (星号)。使用下列命令获取有关如何构造资源 URI 的详细信息: \"winrm help uris\"。 |
The WinRM client cannot process the request. The resource URI for an enumeration operation with WQL filter must not contain keys and the class name must be '*' (star).Use the following command to get more information in how to construct a resource URI: \"winrm help uris\". |
| 0x803380FC | WS-Management 标识操作仅在远程会话上可用。 |
The WS-Management identification operation is only available on remote sessions. |
| 0x803380FD | 使用“推”传递模式的订阅操作仅在远程会话上可用。 |
Subscribe operation with Push delivery mode is only available on remote sessions. |
| 0x803380FE | 订阅管理器地址无效。未从订阅请求所发送到的地址收到响应。 |
The subscription manager address is invalid. The response was not received from the address to which the subscription request was sent. |
| 0x803380FF | 插件仅支持使用“拉”传递模式的订阅。 |
Only subscriptions with Pull delivery mode are supported by the plugin. |
| 0x80338100 | WinRM 无法处理该请求，因为 WMI 对象包含的嵌套的嵌入式对象层次过多。 |
WinRM cannot process the request because the WMI object contains too many levels of nested embedded objects. |
| 0x80338101 | WS-Management 服务无法处理该请求。它不支持检索包含 CIM_REFERENCE 类型属性的 WMI 对象以及其属性包含远程计算机名称的属性值。 |
The WS-Management service cannot process the request. It does not support retrieving a WMI object that contains a property of type CIM_REFERENCE and the value of that property contains a remote machine name. |
| 0x80338102 | WS-Management 服务无法处理该请求。WMI 服务报告 WMI 提供程序无法执行请求的操作。 |
The WS-Management service cannot process the request. The WMI service reported that the WMI provider could not perform the requested operation. |
| 0x80338103 | WS-Management 服务无法处理该请求。从 WMI 服务或 WMI 提供程序检索的值无效。 |
The WS-Management service cannot process the request. A value retrieved from the WMI service or the WMI provider is invalid. |
| 0x80338104 | WS-Management 服务无法处理该请求。WMI 服务返回“访问被拒绝”错误。 |
The WS-Management service cannot process the request. The WMI service returned an 'access denied' error. |
| 0x80338105 | WS-Management 服务无法处理该请求。WMI 提供程序返回“访问被拒绝”错误。 |
The WS-Management service cannot process the request. The WMI provider returned an 'access denied' error. |
| 0x80338106 | WS-Management 服务无法处理该请求。在连接到指定计算机上的 WMI 服务时出现“访问被拒绝”错误。 |
The WS-Management service cannot process the request. An 'access denied' error was received when connecting to the WMI service on the computer specified. |
| 0x80338107 | WS-Management 服务无法处理该请求，因为筛选器 XML 无效。 |
The WS-Management service cannot process the request because the filter XML is invalid. |
| 0x80338108 | WS-Management 服务无法处理该请求。枚举操作的资源 URI 不能包含关键字。 |
The WS-Management service cannot process the request. The resource URI for an Enumerate operation must not contain keys. |
| 0x80338109 | 无法执行片断级操作，因为片断路径包含 \"\" (空白或空字符串)或 NULL。请更改片断路径的值，然后重试请求。 |
Cannot execute the Fragment-Level operation because the fragment path contains either \"\" (blank or empty string) or NULL.Change the value of the fragment path and try the request again. |
| 0x8033810A | WinRM 客户端无法处理该请求。从目标计算机收到的响应包含无效的字符，因此无法进行处理。 |
The WinRM client cannot process the request. The response received from the destination machine contains invalid characters and cannot be processed. |
| 0x8033810B | WinRM 客户端无法处理该请求。当目标是 IP 地址时，不能使用 Kerberos 身份验证。请指定 DNS 或 NetBIOS 目标或者指定基本或协商身份验证。 |
The WinRM client cannot process the request.Kerberos authentication cannot be used when the destination is an IP address.Specify a DNS or NetBIOS destination or specify Basic or Negotiate authentication. |
| 0x8033810C | WinRM 客户端无法处理该请求。如果客户端计算机未加入域，则不能对 Kerberos 身份验证使用隐式凭据。请使用显式凭据或指定 Kerberos 以外的其他身份验证机制。 |
The WinRM client cannot process the request. Kerberos authentication cannot be used with implicit credentials if the client computer is not joined to a domain.Use explicit credentials or specify a different authentication mechanism than Kerberos. |
| 0x8033810D | WinRM 客户端无法处理该请求。该批设置参数无效。 |
The WinRM client cannot process the request. The batch settings parameter is invalid. |
| 0x8033810E | WinRM 客户端无法处理该请求。如果没有指定身份验证机制或指定 Kerberos，则不能对远程主机名称使用 \"localhost\" 或 \"127.0.0.1\" 或 \"[::1]\"。可以明确指定 Kerberos 以外的身份验证机制或者将远程主机指定为 DNS 名称或 NetBIOS 名称。 |
The WinRM client cannot process the request. If you do not specify an authentication mechanism or you specify Kerberos, then you cannot use \"localhost\" or \"127.0.0.1\" or \"[::1]\" for the remote host name.You can explicitly specify a different authentication mechanism than Kerberos or specify the remote host as a DNS name or NetBIOS name. |
| 0x8033810F | WinRM 客户端从远程 WS-Management 服务收到一个未知的 HTTP 状态代码。 |
The WinRM client received an unknown HTTP status code from the remote WS-Management service. |
| 0x80338110 | WinRM 客户端从远程 WS-Management 服务收到一个 HTTP 重定向状态代码。WinRM 不支持重定向。 |
The WinRM client received a HTTP redirect status code from the remote WS-Management service. WinRM does not support redirects. |
| 0x80338111 | WinRM 客户端向远程 WS-Management 服务发送一个请求，并得到通知请求大小超过配置的 MaxEnvelopeSize 配额。 |
The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota. |
| 0x80338112 | 到指定远程主机的连接被拒绝。请验证 WS-Management 服务正在远程主机上运行，且已配置为侦听正确端口和 HTTP URL 上的请求。 |
The connection to the specified remote host was refused.Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. |
| 0x80338113 | WinRM 客户端已将请求发送到 HTTP 服务器，并得到一个说明 HTTP URL 不可用的响应。这通常由一个不支持 WS-Management 协议的 HTTP 服务器所返回。 |
The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.This is usually returned by a HTTP server that does not support the WS-Management protocol. |
| 0x80338115 | 无法创建 HTTPS 上 的 WinRM 侦听程序，因为该计算机不具有适当的证书。若要用于 SSL，证书必须具有与主机名匹配并适合于服务器身份验证且未过期、吊销或自签名的 CN。 |
Cannot create a WinRM listener on HTTPS because this machine does not have an appropriate certificate. To be used for SSL, a certificate must have a CN matching the hostname, be appropriate for Server Authentication, and not be expired, revoked, or self-signed. |
| 0x80338116 | 防火墙不允许异常；无法设置 WinRM 以进行远程访问。 |
Firewall does not allow exceptions; WinRM cannot be setup for remote access. |
| 0x80338117 | 无法为远程访问配置 Windows 远程管理(WinRM)服务，因为组策略不允许本地防火墙更改。请检查组策略设置以允许本地防火墙例外，并将 WinRM 添加到防火墙例外。 |
The Windows Remote Management (WinRM) service cannot be configured for remote access because Group Policy does not allow local firewall changes. Check the Group Policy settings to allow local firewall exceptions and add WinRM to the firewall exceptions. |
| 0x80338118 | WinRM 客户端无法处理该请求，因为选择器名称无效。请更改选择器名称，然后重试该请求。 |
The WinRM client cannot process the request because the selector name is not valid. Change the selector name and retry the request. |
| 0x80338119 | WS-Management 服务不支持指定的编码类型。 |
The WS-Management service does not support the encoding type specified. |
| 0x8033811A | WS-Management 服务无法处理该请求，因为选择器值与已知资源不匹配，或者该资源处于脱机状态。稍后在该资源联机时重试该请求，或尝试其他选择器。 |
The WS-Management service cannot process the request because the selector values do not match a known resource, or the resource is offline. Retry the request later when the resource is online, or try a different selector. |
| 0x8033811B | WS-Management 服务无法处理该请求，因为请求中的标头无效。 |
The WS-Management service cannot process the request because the a header in the request is invalid. |
| 0x8033811C | 为枚举指定的过期时间无效。请将过期时间指定为一段持续时间。 |
The expiration time specified for enumeration was invalid. Specify the expiration time as a duration. |
| 0x8033811D | WS-Management 服务收到一个指定了最大元素数量的请求，但是该服务不支持此功能。在不指定该元素的情况下重试该请求。 |
The WS-Management service received a request which specified a maximum number of elements, but the service does not support this feature.Retry the request without this element specified. |
| 0x8033811E | WS-Management 服务无法处理该请求。WMI 提供程序返回了一个“无效参数”的错误。 |
The WS-Management service cannot process the request. The WMI provider returned an 'invalid parameter' error. |
| 0x8033811F | WinRM 客户端无法处理该请求。该请求必须包含一个且仅包含一个枚举模式。请将该请求更改为仅包含一个枚举模式，然后再试一次。 |
The WinRM client cannot process the request. The request must contain one and only one enumeration mode.Change the request to contain only one enumeration mode and try again. |
| 0x80338120 | WinRS 客户端无法处理该请求。该请求被指定了无效的标志。请删除或更改此无效的标志，然后重试该请求。 |
The WinRS client cannot process the request. An invalid flag was specified for this request.Remove or change the invalid flag and try the request again. |
| 0x80338121 | WinRS 客户端无法处理该请求。要求的其中一个参数为空或为零。请更改该请求，使其包含所缺少的参数，然后再试一次。 |
The WinRS client cannot process the request. One of the parameters required is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338122 | 数据源无法处理筛选器。该筛选器可能丢失、无效或太复杂而无法处理。如果服务只支持筛选器方言的子集(例如 XPath 级别 1)，则可能会返回此错误，表示有效筛选器表达式不在受支持的子集内。更改筛选器，然后重试请求。 |
The data source could not process the filter. The filter might be missing, invalid or too complex to process.If a service only supports a subset of a filter dialect (such as XPath level 1), it may return this fault for validfilter expressions outside of the supported subset.Change the filter and try the request again. |
| 0x80338123 | WinRM 客户端无法处理该请求。WSManEnumeratorAddEvent 函数需要的参数之一为 NULL 或零。请更改请求使其包含缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddEvent function is null or zero. Change the request to include the missing parameter and try again. |
| 0x80338124 | WinRM 客户端无法处理该请求。WSManEnumeratorAddObject 函数的对象参数为 NULL 或零，但枚举模式为对象 或 ObjectAndEPR。 |
The WinRM client cannot process the request. The object parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is Object or ObjectAndEPR. |
| 0x80338125 | WinRM 客户端无法处理该请求。WSManEnumeratorAddObject 函数的 EPR 参数为 NULL 或零，但枚举模式为 EPR 或 ObjectAndEPR。 |
The WinRM client cannot process the request. The EPR parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is EPR or ObjectAndEPR. |
| 0x80338126 | WinRM 无法完成该操作。请验证指定的计算机名称有效，可以通过网络访问该计算机，以及启用了 WinRM 服务的防火墙例外并允许从此计算机中进行访问。默认情况下，公用配置文件的 WinRM 防火墙例外仅限访问同一本地子网中的远程计算机。 |
WinRM cannot complete the operation.Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. |
| 0x80338128 | WinRS 客户端无法处理接收请求，因为外壳插件已针对请求返回空插件。 |
The WinRS client cannot process the Receive request because the shell plugin returned an empty response to the request. |
| 0x80338129 | WinRM 外壳程序客户端无法处理该请求。WSManCreateShell 功能所需的参数之一为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812A | WinRM 外壳程序客户端无法处理该请求。WinrsCloseShell 功能所需的参数之一为为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WinrsCloseShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812B | WinRS 客户端无法处理请求。WinrsFreeCreateShellResult 函数所需的参数为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. The parameter required for the WinrsFreeCreateShellResult function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812C | WinRM 外壳程序客户端无法处理该请求。WSManRunShellCommand 功能所需的参数之一为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812D | WinRS 客户端无法处理请求。WinrsFreeRunCommandResult 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. The parameter required for the WinrsFreeRunCommandResult function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812E | WinRM 外壳程序客户端无法处理该请求。WSManSignalShell 功能所需的参数之一为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033812F | WinRM 外壳程序客户端无法处理该请求。WSMansReceiveShellOutput 功能所需的参数之一为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSMansReceiveShellOutput function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338130 | WinRS 客户端无法处理请求。WinrsFreePullResult 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. The parameter required for the WinrsFreePullResult function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338131 | WinRS 客户端无法处理请求。WinrsPull 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. One of the parameters required for the WinrsPull function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338132 | WinRS 客户端无法处理请求。WinrsCloseReceiveHandle 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. The parameter required for the WinrsCloseReceiveHandle function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338133 | WinRM 外壳程序客户端无法处理该请求。WSManSendShellInput 功能所需的参数之一为空或零。更改请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338134 | WinRS 客户端无法处理请求。WinrsPus 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. One of the parameters required for the WinrsPush function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338135 | WinRS 客户端无法处理请求。WinrsCloseSendHandle 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. The parameter required for the WinrsCloseSendHandle function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338136 | WinRS 客户端无法处理请求。WinrsGet 函数所需的参数之一为空或零。请将请求更改为包含缺少的参数并重试。 |
The WinRS client cannot process the request. One of the parameters required for the WinrsGet function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338137 | WS-Management 服务不支持指定的多形性模式。请尝试更改指定的多形性模式，然后再试一次。 |
The WS-Management service does not support the specified polymorphism mode. Try changing the polymorphism mode specified, and try again. |
| 0x80338138 | WS-Management 服务无法处理该请求，因为服务端上不支持指定的 URI。请使用本地会话重试。 |
The WS-Management service cannot process the request because the specified URI is not supported on the service side. Retry the request with local session. |
| 0x80338139 | WS-Management 服务无法处理该请求。使用 DMTF 资源 URI 访问的是非 DMTF 类。请使用非 DMTF 资源 URI 重试。 |
The WS-Management service cannot process the request. A DMTF resource URI was used to access a non-DMTF class. Try again using a non-DMTF resource URI. |
| 0x8033813A | WS-Management 服务无法处理该请求。存储库中的 DMTF 类使用了请求的类中的其他主要版本号。可以使用非 DMTF 资源 URI 访问此类。 |
The WS-Management service cannot process the request. The DMTF class in the repository uses a different major version number from the requested class. This class can be accessed using a non-DMTF resource URI. |
| 0x8033813B | WS-Management 服务无法处理该请求。资源 URI 和 __cimnamespace 选择器已尝试使用其他命名空间。请尝试删除 __cimnamespace 选择器或使用 DMTF 资源 URI。如果将非 DMTF 资源 URI 与 __cimnamespace 选择器一起使用，则命名空间必须匹配。 |
The WS-Management service cannot process the request. The resource URI and __cimnamespace selector attempted to use different namespaces. Try removing the __cimnamespace selector or using a DMTF resource URI. If a non-DMTF resource URI is used with a __cimnamespace selector, the namespaces must match. |
| 0x8033813C | WS-Management 客户端无法处理该请求。若要使用 WSManSubscribe API，用户必须在网络服务帐户下运行。强制订阅当前不支持其他帐户。 |
The WS-Management client cannot process the request. To use the WSManSubscribe API the user has to be running under Network Service account. No other account is supported currently for push subscriptions. |
| 0x8033813D | WS-Management 客户端无法处理该请求。未将事件源计算机加入域。若要设置到事件源的强制订阅会话，必须将该源连接到域。若要解决此问题，请将事件源计算机加入域，或将 PULL 用作订阅的传递模式。 |
The WS-Management client cannot process the request. The event source machine is not joined to a domain.To set up a push subscription session to an event source the source has to be connected to a domain.To fix this problem either join the event source machine to a domain or use PULL as the delivery mode for the subscription. |
| 0x8033813E | WS-Management 客户端无法处理该请求。未将订户计算机加入域。若要设置到事件源的强制订阅会话，必须将该订户计算机连接到域。若要解决此问题，请将订户计算机加入域，或将 PULL 用作订阅的传递模式。 |
The WS-Management client cannot process the request. The subscriber machine is not joined to a domain.To set up a push subscription session to an event source, the subscriber machine has to be connected to a domain.To fix this problem either join the subscriber machine to a domain or use PULL as the delivery mode for the subscription. |
| 0x8033813F | WinRM 客户端无法处理该请求，因为它正在尝试更新只读设置。请从命令中删除此设置，然后再试一次。 |
The WinRM client cannot process the request because it is trying to update a read-only setting.Remove this setting from the command and try again. |
| 0x80338140 | WinRS 客户端无法处理该请求。服务器无法设置代码页。你可能希望使用 CHCP 命令将客户端代码页更改为 437 并以英文形式接收结果。 |
The WinRS client cannot process the request. The server cannot set Code Page.You may want to use the CHCP command to change the client Code Page to 437 and receive the results in English. |
| 0x80338141 | Not used. To be removed. |
Not used. To be removed. |
| 0x80338143 | WS-Management 客户端从服务器接收过多结果。服务器操作运行切勿返回多于客户端指定的项目。 |
The WS-Management client received too many results from the server.The server implementation should never return more items than are specified by the client. |
| 0x80338144 | WinRM 客户端无法处理该请求。已将证书指纹与用户名或密码一起指定。只能指定一种凭据类型。请删除与要使用的身份验证机制不对应的凭据类型，然后重试该请求。 |
The WinRM client cannot process the request. A certificate thumbprint was specified together with a user name or password. Only one credentials type can be specified. Remove the credentials type that does not correspond to the intended authentication mechanism and retry the request. |
| 0x80338145 | WinRM 客户端无法处理该请求。指定使用身份验证机制的标志不正确。删除或更改无效标志，然后再次尝试请求。 |
The WinRM client cannot process the request. The flag that specifies the authentication mechanism to use is incorrect.Remove or change the invalid flag and try the request again. |
| 0x80338146 | WinRM 客户端无法处理该请求。没有指定身份验证机制时，只允许使用用户名和密码凭据。如果要使用不同类型的凭据，需要指定身份验证机制。指定身份验证机制或正确凭证，然后再次尝试请求。 |
The WinRM client cannot process the request. When an authentication mechanism is not specified, only user name and password credentials are allowed.If you want to use a different type of credentials then you need to specify the authentication mechanism.Specify the authentication mechanism or the correct credentials and try the request again. |
| 0x80338147 | WinRM 客户端无法处理该请求。对于需要用户帐户凭据的身份验证机制，必须同时指定用户名和密码。指定缺少的用户名或密码，然后重新尝试请求。 |
The WinRM client cannot process the request. For authentication mechanisms that require the credentials of an user account, both user name and password must be specified.Specify the missing user name or password and try the request again. |
| 0x80338148 | WinRM 客户端无法处理该请求。如果使用的是计算机证书，必须在使用者可选名称扩展名或“使用者名称”字段中包含 DNS 名称，而不能包含 UPN 名称。如果使用的是用户证书，使用者可选名称扩展名必须包含 UPN 名称，而不能包含 DNS 名称。请更改证书结构，然后重试该请求。 |
The WinRM client cannot process the request. If you are using a machine certificate, it must contain a DNS name in the Subject Alternative Name extension or in the Subject Name field, and no UPN name.If you are using a user certificate, the Subject Alternative Name extension must contain a UPN name and must not contain a DNS name.Change the certificate structure and try the request again. |
| 0x80338149 | WinRM Shell 客户端无法处理该请求。传递给 WSManCreateShell 函数的环境变量名之一为空或零。将请求更改为包含缺少的参数，然后再次尝试。 |
The WinRM Shell client cannot process the request. One of the environment variable name passed to the WSManCreateShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033814A | 尝试操作关闭的外壳程序。如果正在使用的外壳程序被另一线程关闭，会发生这种情况。 |
An operation is being attempted on a shell that is being closed. This can happen if the shell that is being used is also being closed by another thread. |
| 0x8033814B | WinRM Shell 客户端无法处理该请求。传递给 WSManCreateShell 函数的流 ID 名称之一为空或零。将请求更改为包含缺少的参数，然后再次尝试。 |
The WinRM Shell client cannot process the request. One of the stream id name passed to the WSManCreateShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033814C | WinRM Shell 客户端无法处理该请求。传递给 WSMan Shell 函数的 shell 句柄无效。只有当 WSManCreateShell 函数成功完成时，shell 句柄才有效。将请求更改为包含有效的 shell 句柄，然后再次尝试。 |
The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid.The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. |
| 0x8033814D | WinRM Shell 客户端无法处理该请求。传递给 WSMan Shell 函数的 command 句柄无效。只有当 WSManRunShellCommand 函数成功完成时，command 句柄才有效。将请求更改为包含有效的 shell 句柄，然后再次尝试。 |
The WinRM Shell client cannot process the request. The command handle passed to the WSMan Shell function is not valid.The command handle is valid only when WSManRunShellCommand function completes successfully. Change the request including a valid shell handle and try again. |
| 0x8033814E | WinRM Shell 客户端无法处理该请求。传递给 WSManRunShellCommand 函数的参数值之一为空或零。将请求更改为包含缺少的参数，然后再次尝试。 |
The WinRM Shell client cannot process the request. One of the argument value passed to the WSManRunShellCommand function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033814F | 尝试操作关闭的命令。如果正在使用的 command 句柄被另一线程释放，会发生这种情况。 |
An operation is being attempted on a command that is being closed. This can happen if the command handle that is being used is also being freedby another thread. |
| 0x80338150 | WinRM Shell 客户端无法处理该请求。传递给 WSManSendShellInput 函数的 WSMAN_STREAM_ELEMENT 内的流 ID 索引无效。流 ID 索引应该是传递给 WSManCreateShell 函数的 inputStreamSet 数组内的索引。使用有效索引更改请求，然后再次尝试。 |
The WinRM Shell client cannot process the request. The stream id index from within WSMAN_STREAM_ELEMENT passed to the WSManSendShellInput function is invalid.The stream id index should be an index from within inputStreamSet array passed to the WSManCreateShell function.Change the request with a valid index and try again. |
| 0x80338152 | 只能远程完成更新 WINRM 服务配置证书映射存储的 WS-Management 操作。 |
The WS-Management operations to update the certificate mapping store of the WINRM service config can only be done remotely. |
| 0x80338153 | WINRM 证书映射配置存储已达到内部限制，无法创建更多条目。删除一些条目，然后再次尝试。 |
The WINRM certificate mapping configuration store has reached an internal limit and cannot create any more entries. Remove some entries and try again. |
| 0x80338154 | 由于无法验证用户凭证，因而无法完成 WINRM 证书映射配置操作。请检查用于映射此证书的用户名和密码，并验证它是否为非域帐户，然后再次尝试。 |
The WINRM certificate mapping configuration operation cannot be completed because the user credentials could not be verified. Please check the username and password used for mapping this certificate and verify that it is a non-domain account and try again. |
| 0x80338155 | WinRM 客户端无法处理该请求。证书的增强型密钥用法(EKU)字段没有设置为“客户端身份验证”。使用具有正确 EKU 的证书再次尝试申请。 |
The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to \"Client Authentication\".Retry the request with a certificate that has the correct EKU. |
| 0x80338156 | WinRM 客户端无法处理该请求。证书指纹已经指定，但缺少下列标志: WSManFlagUseClientCertificate。添加该标志，然后再次尝试请求。 |
The WinRM client cannot process the request. A certificate thumbprint was specified, but the following flag is missing: WSManFlagUseClientCertificate.Add the flag and try the request again. |
| 0x80338157 | WinRM 客户端无法处理该请求。下列标志不能一起指定: WSManFlagUseClientCertificate 和 WSManFlagCredUsernamePassword。删除其中一个标志，然后再次尝试请求。 |
The WinRM client cannot process the request. The following flags cannot be specified together: WSManFlagUseClientCertificate and WSManFlagCredUsernamePassword.Remove one of the flags and try the request again. |
| 0x80338158 | WinRM 客户端无法处理请求，因为指定的 CustomRemoteShell URI 无效。CustomRemoteShell URI 应该以 WinRM 外壳程序资源 URI 前缀开始: \"http://schemas.microsoft.com/wbem/wsman/1/windows/shell\"。URI 不应包含无效字符，包括 \"*\"、\"?\"、空白字符和制表符。CustomRemoteShell URI 不能长于 1023 个字符。 |
The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid.CustomRemoteShell URI should start with WinRM shell resource URI prefix: \"http://schemas.microsoft.com/wbem/wsman/1/windows/shell\".The URI should not contain invalid characters including '*', '?', white spaces and tabs.The CustomRemoteShell URI cannot be longer than 1023 characters. |
| 0x80338159 | WinRM 客户端无法处理该请求，因为指定的 CustomRemoteShell URI 无效。Windows 命令外壳程序 URI (\"http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd\") 不能是 CustomRemoteShell URI。 |
The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid.Windows command shell URI (\"http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd\") cannot be a CustomRemoteShell URI. |
| 0x8033815A | WinRM 客户端无法处理该请求，其原因是为 CustomRemoteShell 表项指定的处理路径无效。处理路径应该是绝对路径，应该指向现有的可执行程序。 |
The WinRM client cannot process the request because the process path specified for the CustomRemoteShell table entry is invalid.The process path should be absolute and should point to an existing executable. |
| 0x8033815C | WinRM 客户端无法处理该请求，因为提供的安全描述符无效。 |
The WinRM client cannot process the request because the provided security descriptor is invalid. |
| 0x8033815D | WinRM 服务无法处理该请求，因为 DeliverTo 中包含的 WS-Policy 过于复杂或者使用该服务不理解的结构。WinRM 服务支持 wsp:ExactlyOne 元素下面的单层策略声明。 |
The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo is too complex or uses a structure not understood by the service.The WinRM service supports a single layer of policy assertions underneath a wsp:ExactlyOne element. |
| 0x8033815E | WinRM 服务无法处理该请求，因为 DeliverTo 中包含的 WS-Policy 没有包含该服务可以遵从的任何选项。WinRM 服务支持下列配置文件: 基于 HTTP 的协商或 Kerberos，基于 HTTPS 的协商或 Kerberos，以及使用颁发者指纹通过 HTTPS 相互进行的证书身份验证。 |
The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo does not contain any options that the service can comply with.The WinRM service supports the following profiles: Negotiate or Kerberos over HTTP, Negotiate or Kerberos over HTTPS, and mutual certificate authentication over HTTPS using issuer thumbprints. |
| 0x8033815F | WinRM 服务无法处理该请求，因为 DeliverTo 中的 wsman:ConnectionRetry 元素无效。 |
The WinRM service cannot process the request because the wsman:ConnectionRetry element in the DeliverTo is invalid. |
| 0x80338160 | WinRM 无法更改此配置。提供给证书映射操作的 URI 无效。它必须包含至少一个字符。它不能包含内部空白字符。它不能包含 \"?\" 字符。使用 \"*\" 作为最后一个字符可以指定前缀。URI 不能长于 1023 个字符。 |
WinRM cannot make the configuration change. The URI supplied for the certificate mapping operation is not valid. It must contain at least one character.It must not contain internal whitespace.It must not contain '?' character.A prefix may be specified by using \"*\" as the last character.The URI cannot be longer than 1023 characters. |
| 0x80338161 | WinRM 无法更改此配置。用于证书映射操作的使用者无效。 它必须包含至少一个字符。 它最多只能包含一个 \"*\" 字符，并且应将该字符作为第一个字符。(这可能是唯一一个字符，在这种情况下，它匹配所有使用者)。 使用者字段不能长于 1023 个字符。 |
WinRM cannot make the configuration change.The Subject used for the certificate mapping operation is not valid. It must contain at least one character. It must contain at most one \"*\" character which should be the first character.(This may be the only character in which case it matches all subjects). The Subject cannot be longer than 1023 characters. |
| 0x80338162 | WinRM 无法更改此配置，因为用于证书映射操作的颁发者无效。 由颁发者指纹标识的证书必须出现在计算机“受信任的根证书颁发机构”或“中间证书颁发机构”存储中。 证书的密钥用法必须允许密钥签署其他证书。 |
WinRM cannot make the configuration change because the Issuer used for the certificate mapping operation is not valid. The certificate identified by the issuer thumbprint must be present in the machine \"Trusted Root Certification Authorities\" or \"Intermediate Certification Authorities\" store. The certificate must have key usage that allows it to sign other certificates. |
| 0x80338163 | WinRM 客户端无法处理该请求，因为 WSMAN_ALLOWED_PUBLISHERS 参数中的类型字段无效。收集器启动的订阅必须使用 WSMAN_SINGLE_PUBLISHER，并且源启动的订阅必须使用 WSMAN_MULTIPLE_PUBLISHERS。 |
The WinRM client cannot process the request because the type field in the WSMAN_ALLOWED_PUBLISHERS argument is invalid.Collector-initiated subscriptions must use WSMAN_SINGLE_PUBLISHER and Source-initiated subscriptions must use WSMAN_MULTIPLE_PUBLISHERS. |
| 0x80338164 | WinRM 客户端无法处理该请求，因为发送重试参数无效。如果请求发送重试，deliveryRetryInterval 和 deliveryRetryAttempts 字段必须都不为零。 |
The WinRM client cannot process the request because the delivery retry parameters are invalid.If delivery retry is requested, the deliveryRetryInterval and deliveryRetryAttempts fields must both be nonzero. |
| 0x80338165 | WinRM 客户端无法处理该请求。所需的 WSMAN_ALLOWED_PUBLISHERS 设置为空或零。将请求更改为包含缺少的参数，然后再次尝试。 |
The WinRM client cannot process the request.The required WSMAN_ALLOWED_PUBLISHERS settings is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338166 | WinRM 客户端无法处理该请求，因为没有为客户端证书使用者筛选器指定任何颁发者。当使用客户端证书身份验证时，请指定至少一个颁发者指纹。 |
The WinRM client cannot process the request because client certificate subject filters were specified without any issuers.When using client certificate authentication, specify at least one issuer thumbprint. |
| 0x80338167 | WinRM 客户端无法处理该请求，因为订阅不包含域源，或包含非域源。使用 WSMAN_MULTIPLE_PUBLISHERS 的订阅必须指定安全描述符和/或颁发者列表。 |
The WinRM client cannot process the request because the subscription contains no domain or non-domain sources.Subscriptions using WSMAN_MULTIPLE_PUBLISHERS must specify either a security descriptor or an issuer list or both. |
| 0x80338168 | WinRM 服务无法处理该请求，因为订阅管理器返回了无效的枚举结果。m:Subscription XML 对象或 m:Version 元素缺失或无效。 |
The WinRM service cannot process the request because the subscription manager returned invalid enumeration results.The m:Subscription XML object or m:Version element is missing or invalid. |
| 0x80338169 | 由于此计算机上的网络连接类型之一设置为公用，因此 WinRM 防火墙例外将不运行。将网络连接类型更改为域或专用，然后再次尝试。 |
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public.Change the network connection type to either Domain or Private and try again. |
| 0x8033816A | WinRM 无法更改配置。用于更新证书映射配置的密码无效。 它不能长于 255 个字符。 |
WinRM cannot make the configuration change.The Password used for updating the certificate mapping configuration is not valid. It cannot be longer than 255 characters. |
| 0x8033816B | WinRM 无法更改配置。用于更新证书映射配置的密码无效。用于配置证书映射的用户帐户密码不能为空。 |
WinRM cannot make the configuration change.The Password used for updating the certificate mapping configuration is not valid. A user account used for configuring a certificate mapping cannot have a blank password. |
| 0x8033816C | WinRM 无法更改配置。用于更新或创建证书映射配置的凭据无效。凭据由成对提供的密码和用户名组成。 |
WinRM cannot make the configuration change.The credential used for updating or creating the certificate mapping configuration is not valid. The credential consists of both Password and UserName being supplied together in a pair. |
| 0x8033816D | WinRM 服务执行操作，提供程序返回有关操作成功或失败的不确定信息。状态标记为失败，但没有给出错误代码。 |
The WinRM service executed an operation and the provider returned inconclusive information regarding success or failure of the operation.The status was marked as failed, but no error code was given. |
| 0x8033816E | 远程计算机上的 WS-Management 服务无法处理外壳程序请求。如果远程计算机上的 WS-Management 服务被关闭，会出现这种情况。若要解决此问题，请重新启动远程计算机上的 WS-Management 服务，并重新发送外壳程序请求。 |
The WS-Management service on the remote machine cannot process the shell request.This can happen if the WS-Management service on the remote machine was being shutdown.To correct this problem restart the WS-Management service on the remote machine and re-send the shell request. |
| 0x8033816F | WinRM 服务无法处理该请求。URI 参数是 CustomRemoteShell 表的项，不能修改。 |
The WinRM service cannot process the request. The URI parameter is the key to CustomRemoteShell table and cannot be modified. |
| 0x80338170 | WinRM 客户端接收到 HTTP 服务器错误状态(500)，但远程服务并未包含有关失败原因的任何其他信息。 |
The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. |
| 0x80338171 | WinRM 客户端接收到 HTTP 错误请求状态(400)，但远程服务并未包含有关失败原因的任何其他信息。 |
The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure. |
| 0x80338172 | WinRM 服务无法更改配置。不能通过覆盖正文中的选择器项值更改使用者、URI 或颁发者的选择器项值。 |
The WinRM service cannot make the configuration change.The selector keys of Subject, URI or Issuer cannot be changed by overriding the selector key value in the body. |
| 0x80338173 | WinRM 客户端无法处理该请求，因为它接收了 HTML 错误包。 |
The WinRM client cannot process the request because it received an HTML error packet. |
| 0x80338174 | WinRM 客户端无法处理该请求。WSManInitialize 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManInitialize function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338175 | WinRM 客户端无法处理该请求。为 WSManInitialize API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManInitialize API call.Remove or change the invalid flag and try the call again. |
| 0x80338176 | WinRM 客户端无法处理该请求。为 WSManDeinitialize API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManDeinitialize API call.Remove or change the invalid flag and try the call again. |
| 0x80338177 | WinRM 客户端无法处理该请求。WSManSetSessionOption 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338178 | WinRM 客户端无法处理该请求。WSManSetSessionOption 函数所要求的参数之一无效。请更改无效参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is invalid.Change the invalid parameter and try again. |
| 0x80338179 | WinRM 客户端无法处理该请求。获取会话选项所要求的参数之一无效。请更改无效参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required to get a session option is invalid.Change the invalid parameter and try again. |
| 0x8033817B | WinRM 客户端无法处理该请求。为 WSManCreateShell API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManCreateShell API call.Remove or change the invalid flag and try the call again. |
| 0x8033817C | WinRM 客户端无法处理该请求。为 WSManCloseShell API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManCloseShell API call.Remove or change the invalid flag and try the call again. |
| 0x8033817D | WinRM 客户端无法处理该请求。为 WSManCloseCommand API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManCloseCommand API call.Remove or change the invalid flag and try the call again. |
| 0x8033817E | WinRM 外壳程序客户端无法处理该请求。WSManCloseShell 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033817F | WinRM 外壳程序客户端无法处理该请求。WSManCloseCommand 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseCommand function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338181 | WinRM 客户端无法处理该请求。为 WSManRunShellCommand API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManRunShellCommand API call.Remove or change the invalid flag and try the call again. |
| 0x80338182 | WinRM 客户端无法处理该请求。调用 WSManCloseShellOperationEx API 之前，必须等待 WSManRunShellCommand API 调用完成。 |
The WinRM client cannot process the request. You must wait for the WSManRunShellCommand API call to complete before calling WSManCloseShellOperationEx API. |
| 0x80338183 | WinRM 客户端无法处理该请求。对命令请求的响应未包含有效 CommandResponse 元素。CommandResponse 元素找不到或包含无效的内容。 |
The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element.The CommandResponse element was not found or did not contain valid content. |
| 0x80338184 | WinRM 客户端无法处理该请求。OptionSet 元素无效。请更改该请求，以包括有效的 OptionSet 元素，然后再试一次。 |
The WinRM client cannot process the request. The OptionSet element is invalid.Change the request to include a valid OptionSet element and try again. |
| 0x80338185 | WinRM 客户端无法处理该请求。对命令请求的响应未包含有效 CommandResponse 元素。CommandId 元素找不到或包含无效的内容。 |
The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element.The CommandId element was not found or did not contain valid content. |
| 0x80338187 | WinRM 客户端无法处理该请求。为 WSManSignalShell API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManSignalShell API call.Remove or change the invalid flag and try the call again. |
| 0x80338189 | WinRM 客户端无法处理该请求。为 WSManSendShellInput API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManSendShellInput API call.Remove or change the invalid flag and try the call again. |
| 0x8033818A | WinRM 客户端无法处理该请求。为 WSManSendShellInput API 调用指定的参数无效。应使用 WSMAN_DATA_TYPE_BINARY 类型以二进制格式指定 streamData 参数。请更改该无效的参数，然后重试此调用。 |
The WinRM client cannot process the request. An invalid parameter was specified for the WSManSendShellInput API call. streamData parameter should be specified in binary format using WSMAN_DATA_TYPE_BINARY type. Change the invalid parameter and try the call again. |
| 0x8033818B | WinRM 外壳程序客户端无法处理该请求。传递给 WSManSendShellInput 函数的流名称无效。在使用 WSManCreateShell 函数创建外壳程序期间，应作为输入流的一部分指定输入流名称。将请求更改为包括有效的输入流名称，然后再试一次。 |
The WinRM Shell client cannot process the request. The stream name passed to the WSManSendShellInput function is not valid.The input stream name should be specified as part of the input streams during shell creation using WSManCreateShell function. Change the request including a valid input stream name and try again. |
| 0x8033818C | WinRM 外壳程序客户端无法处理该请求。WSManReceiveShellOutput 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManReceiveShellOutput function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033818D | WinRM 外壳程序客户端无法处理该请求。传递给 WSManReceiveShellOutput 函数的流或流列表无效。在使用 WSManCreateShell 函数创建外壳程序期间，应作为输出流的一部分指定所需的流名称。请更改请求，以包括有效的所需流，然后再试一次。 |
The WinRM Shell client cannot process the request. The stream or list of streams passed to the WSManReceiveShellOutput function is not valid.The desired stream names should be specified as part of the output streams during shell creation using WSManCreateShell function. Change the request including valid desired streams and try again. |
| 0x8033818E | WinRM 客户端无法处理该请求。为 WSManReceiveShellOutput API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManReceiveShellOutput API call.Remove or change the invalid flag and try the call again. |
| 0x8033818F | WinRM 客户端无法处理该请求。对接收请求的响应未包含有效 ReceiveResponse 元素。ReceiveResponse 元素找不到或包含无效的内容。 |
The WinRM client cannot process the request. The response to a Receive request did not contain a valid ReceiveResponse element.The ReceiveResponse element was not found or did not contain valid content. |
| 0x80338190 | WSMan 插件配置已损坏。 |
The WSMan plugin configuration is corrupted. |
| 0x80338191 | 指定的文件路径不是绝对的、不在 system32 目录中或无效。 |
The file path specified is either not absolute, not in the system32 directory, or not valid. |
| 0x80338192 | 指定的文件不存在。 |
The file specified does not exist. |
| 0x80338193 | WSMan 扩展无法读取 IIS 配置。 |
The WSMan extension failed to read IIS configuration. |
| 0x80338194 | WinRM 客户端无法处理该请求。区域设置选项无效。请更改区域设置，然后再试一次。 |
The WinRM client cannot process the request. The locale option is invalid.Change the locale and try again. |
| 0x80338195 | WinRM 客户端无法处理该请求。用户界面语言选项无效。请更改用户界面语言，然后再试一次。 |
The WinRM client cannot process the request. The UI language option is invalid.Change the UI language and try again. |
| 0x80338196 | WinRM 客户端无法处理该请求。WSManGetErrorMessage 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManGetErrorMessage function is null or zero.Change the request to include the missing parameter and try again. |
| 0x80338197 | WinRM 客户端无法处理该请求。语言代码参数无效。语言代码参数应为 NULL 或有效 RFC 3066 语言代码。请更改语言代码，然后重试此请求。 |
The WinRM client cannot process the request. The language code parameter is invalid. The language code parameter should be either NULL or a valid RFC 3066 language code.Change the language code and try the request again. |
| 0x80338198 | WinRM 客户端无法处理该请求。为 WSManGetErrorMessage API 调用指定的标志无效。请删除或更改无效的标志，然后重试此调用。 |
The WinRM client cannot process the request. An invalid flag was specified for the WSManGetErrorMessage API call.Remove or change the invalid flag and try the call again. |
| 0x80338199 | WinRM 服务无法处理该请求，因为需要将该请求发送到其他计算机。请使用重定向信息将该请求发送到新计算机。 |
The WinRM service cannot process the request because the request needs to be sent to a different machine.Use the redirect information to send the request to a new machine. |
| 0x8033819A | WinRM 客户端无法处理该请求。指定要使用的代理身份验证机制的标志不正确。请删除或更改无效的标志，然后重试此请求。 |
The WinRM client cannot process the request. The flag that specifies the proxy authentication mechanism to use is incorrect. Remove or change the invalid flag and try the request again. |
| 0x8033819B | WinRM 客户端无法处理该请求。未正确指定代理身份验证的凭据。用户名和密码凭据必须全部有效。请指定正确的凭据，然后重试此请求。 |
The WinRM client cannot process the request. The credentials for proxy authentication are not specified correctly. Both user name and password credentials must be valid.Specify the correct credentials and try the request again. |
| 0x8033819C | WinRM 客户端无法处理该请求。代理访问类型不正确。请使用代理访问类型标志之一；不能组合使用这些标志。请更改无效的代理访问类型，然后重试该请求。 |
The WinRM client cannot process the request. The proxy access type is incorrect. Use one of the proxy access type flags; the flags cannot be combined.Change the invalid proxy access type and try the request again. |
| 0x8033819D | WinRM 客户端无法处理该请求。与服务器选项的直接连接无法与非空代理身份验证数据一起使用。请更改无效的代理访问类型或使用空代理身份验证数据，然后重试此请求。 |
The WinRM client cannot process the request. The direct connection to the server option cannot be used with non empty proxy authentication data. Change the invalid proxy access type or use empty proxy authentication data and try the request again. |
| 0x8033819E | WinRM 客户端无法处理该请求。WSManGetSessionOptionAsDword 函数所要求的参数之一为 null 或为零。请更改该请求，以包括所缺少的参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is null or zero.Change the request to include the missing parameter and try again. |
| 0x8033819F | WinRM 客户端无法处理该请求。WSManGetSessionOptionAsDword 函数所要求的参数之一无效。请更改无效参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is invalid.Change the invalid parameter and try again. |
| 0x803381A0 | WinRM 客户端无法处理该请求。WSManGetSessionOptionAsString 函数所要求的参数之一无效。请更改无效参数，然后再试一次。 |
The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsString function is invalid.Change the invalid parameter and try again. |
| 0x803381A1 | WinRM 客户端无法处理该请求。使用 CredSSP 身份验证机制时，请求必须包括用户名和密码。请添加用户名和密码或更改身份验证机制，然后重试此请求。 |
The WinRM client cannot process the request. Requests must include user name and password when CredSSP authentication mechanism is used.Add the user name and password or change the authentication mechanism and try the request again. |
| 0x803381A2 | WinRM 客户端无法处理该请求。当前在客户端配置中已禁用 CredSSP 身份验证。更改客户端配置，然后重试该请求。还必须在服务器配置中启用 CredSSP 身份验证。此外，还必须编辑组策略，以允许向目标计算机委派凭据。使用 gpedit.msc 并查看以下策略: 计算机配置 - 管理模板 - 系统 - 凭据委派 - 允许委派新的凭据。请验证它是否启用以及是否配置为适合目标计算机的 SPN。例如，对于目标计算机名 \"myserver.domain.com\"，SPN 可以是以下内容之一: WSMAN/myserver.domain.com 或 WSMAN/*.domain.com |
The WinRM client cannot process the request.CredSSP authentication is currently disabled in the client configuration.Change the client configuration and try the request again.CredSSP authentication must also be enabled in the server configuration.Also, Group Policy must be edited to allow credential delegation to the target computer.Use gpedit.msc and look at the following policy: Computer Configuration - Administrative Templates - System - Credentials Delegation - Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer.For example, for a target computer name \"myserver.domain.com\", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com |
| 0x803381A3 | WinRM 客户端无法处理该请求。计算机策略不允许向目标计算机委派用户凭据。请使用 gpedit.msc 并查看下列策略: 计算机配置 - 管理模板 - 系统 - 凭据委派 - 允许委派新的凭据。验证已启用并使用与目标计算机相应的 SPN 对其进行配置。例如，对于目标计算机名 myserver.domain.com，SPN 可以是下列值之一: WSMAN/myserver.domain.com 或 WSMAN/*.domain.com。 |
The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer.Use gpedit.msc and look at the following policy: Computer Configuration - Administrative Templates - System - Credentials Delegation - Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer.For example, for a target computer name \"myserver.domain.com\", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com. |
| 0x803381A4 | WinRM 客户端无法处理该请求。计算机策略不允许向目标计算机委派用户凭据，因为该计算机不受信任。如果你通过以下命令将 WSMAN 服务配置为使用有效的证书，则可以验证目标计算机的标识: winrm set winrm/config/service @{CertificateThumbprint=\"\"}或者你可以检查事件查看器，以查看指定无法创建下列 SPN 的事件: WSMAN/。如果找到此事件，可以使用 setspn.exe 手动创建 SPN。如果存在 SPN，但 CredSSP 无法使用 Kerberos 验证目标计算机的标识，并且你仍希望允许向目标计算机委派用户凭据，请使用 gpedit.msc 并查看下列策略: 计算机配置 - 管理模板 - 系统 - 凭据委派 - 允许新的凭据用于仅 NTLM 服务器身份验证。验证已启用并使用与目标计算机相应的 SPN 对其进行配置。例如，对于目标计算机名 myserver.domain.com，SPN 可以是下列值之一: WSMAN/myserver.domain.com 或 WSMAN/*.domain.com。请在这些更改之后重新尝试该请求。 |
The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer because the computer is not trusted.The identity of the target computer can be verified if you configure the WSMAN service to use a valid certificate using the following command: winrm set winrm/config/service @{CertificateThumbprint=\"\"} Or you can check the Event Viewer for an event that specifies that the following SPN could not be created: WSMAN/. If you find this event, you can manually create the SPN using setspn.exe . If the SPN exists, but CredSSP cannot use Kerberos to validate the identity of the target computer and you still want to allow the delegation of the user credentials to the target computer, use gpedit.msc and look at the following policy: Computer Configuration - Administrative Templates - System - Credentials Delegation - Allow Fresh Credentials with NTLM-only Server Authentication. Verify that it is enabled and configured with an SPN appropriate for the target computer.For example, for a target computer name \"myserver.domain.com\", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com.Try the request again after these changes. |
| 0x803381A5 | WS-Management 服务无法处理该请求。已超过此用户并发外壳程序的最大数目。关闭现有外壳程序或提高此用户的配额。 |
The WS-Management service cannot process the request.The maximum number of concurrent shells for this user has been exceeded.Close existing shells or raise the quota for this user. |
| 0x803381A6 | WS-Management 服务无法处理该请求。已超过此用户并发操作的最大数目。结束此用户现有的操作，或提高此用户的配额。 |
The WS-Management service cannot process the request.The maximum number of concurrent operations for this user has been exceeded.Close existing operations for this user, or raise the quota for this user. |
| 0x803381A7 | WS-Management 服务无法处理该请求。已超过此用户的负载配额。以较慢速率发送将来的请求或提高此用户的配额。 |
The WS-Management service cannot process the request.The load quota for this user has been exceeded.Send future requests at a slower rate or raise the quota for this user. |
| 0x803381A8 | WS-Management 服务无法处理该请求。已超过系统的负载配额。以较慢速率发送将来的请求或提高系统配额。 |
The WS-Management service cannot process the request.The load quota for the system has been exceeded.Send future requests at a slower rate or raise the system quota. |
| 0x803381A9 | WS-Management 服务无法在给定的令牌下完成授权。同一用户的早期授权尝试已导致不同令牌。用户记录将被吊销并且将对下一请求重新进行身份验证。 |
The WS-Management service cannot complete the authorization under the given token.A previous authorization attempt for the same user resulted in a different token.The user record will be revoked and the next request will reauthorize. |
| 0x803381AA | 如果未返回重定向错误 (ERROR_WSMAN_REDIRECT_REQUESTED)，则应用程序尝试从会话检索 HTTP 重定向位置。需要更新应用程序，以便在返回此错误后仅检索该位置。 |
An application tried to retrieve the HTTP Redirect location from the session when no redirect error (ERROR_WSMAN_REDIRECT_REQUESTED) was returned.The application needs to be updated so as to only retrieve the location after this error is returned. |
| 0x803381AB | WS-Management 服务无法处理该请求。已超过执行外壳程序操作的用户的最大数目。请在稍后重试或提高并发外壳程序用户的配额。 |
The WS-Management service cannot process the request.The maximum number of users executing shell operations has been exceeded.Retry after some time or raise the quota for concurrent shell users. |
| 0x803381AC | WS-Management 服务无法处理该请求。此服务已配置为不接受任何远程外壳程序请求。 |
The WS-Management service cannot process the request.The service is configured to not accept any remote shell requests. |
| 0x803381AD | WS-Management 服务无法针对枚举完成拉操作，因为 wsman:MaxEnvelopeSize、wsen:MaxCharacters 或 wsen:MaxElements 参数不同于为枚举指定的参数。应用程序需要为拉指定与为枚举指定的相同参数。 |
The WS-Management service cannot complete the Pull operation for the enumeration because the wsman:MaxEnvelopeSize, wsen:MaxCharacters or wsen:MaxElements parameters differ from those specified to the enumeration.The application needs to specify the same parameters for Pull as were specified for the enumeration. |
| 0x803381AE | WinRM 服务无法处理该请求，因为它正在尝试更新已否决的设置。请从命令中删除此设置，然后再试一次。 |
The WinRM service cannot process the request because it is trying to update a deprecated setting.Remove this setting from the command and try again. |
| 0x803381AF | WS-Management 服务无法处理配置设置。安全元素包括与其父资源元素不匹配的 URI。 |
The WS-Management service cannot process the configuration settings.A Security element contains a URI that does not match its parent Resource element. |
| 0x803381B0 | WinRM 客户端无法处理该请求。允许协商身份验证选项的隐式凭据仅对 HTTPS 传输有效。删除允许协商身份验证选项的隐式凭据，然后重试此请求。 |
The WinRM client cannot process the request. Allow implicit credentials for Negotiate authentication option is only valid for HTTPS transport.Remove the allow implicit credentials for Negotiate authentication option and try the request again. |
| 0x803381B1 | WinRM 客户端无法处理该请求。如果已指定 HTTP 传输，则设置代理信息无效。请删除代理信息或更改传输并重试该请求。 |
The WinRM client cannot process the request. Setting proxy information is not valid when the HTTP transport is specified.Remove the proxy information or change the transport and try the request again. |
| 0x803381B2 | WinRM 客户端无法处理该请求。如果远程计算机的身份验证机制为 Kerberos，则设置代理信息无效。请删除代理信息或更改身份验证机制并重试该请求。 |
The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is Kerberos.Remove the proxy information or change the authentication mechanism and try the request again. |
| 0x803381B3 | WinRM 客户端无法处理该请求。如果远程计算机的身份验证机制为 CredSSP，则设置代理信息无效。请删除代理信息或更改身份验证机制并重试该请求。 |
The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is CredSSP.Remove the proxy information or change the authentication mechanism and try the request again. |
| 0x803381B4 | WinRM 客户端无法处理该请求。请求必须仅为代理指定一个身份验证机制。请更改请求以仅指定一个身份验证机制，然后再试一次。 |
The WinRM client cannot process the request. The request must specify only one authentication mechanism for proxy.Change the request to specify only one authentication mechanism and try again. |
| 0x803381B5 | WinRM 客户端收到来自服务器的重定向错误，因为服务器不对应。唯一能够正确报告重定向错误的时间是在用户授权期间。这会导致来自服务器的格式不正确的重定向响应，其中包括重定向终结点。 |
The WinRM client received a redirect error from the server when it is not appropriate. The only time a redirect error can be reported correctly is during the authorization of a user.This would result in a properly formatted redirect response from the server that includes the redirect endpoint. |
| 0x803381B6 | WinRM 服务收到来自授权插件的重定向错误，因为重定向位置太长。 |
The WinRM service received a redirect error from an authorization plug-in where the redirect location was too long. |
| 0x803381B7 | WinRM 服务收到重定向客户端但位置 URL 无效的 HTTP 重定向消息。 |
The WinRM service received a HTTP redirect message redirecting the client but the location URL is invalid. |
| 0x803381B8 | WinRM 服务无法处理该请求。通道绑定标记强化级别(CbtHardeningLevel)的值无效。有效值为 \"None\"、\"Relaxed\" 和 \"Strict\"。请更改 CbtHardeningLevel 的值并重试。 |
The WinRM service cannot process the request. The Channel Binding Token Hardening Level (CbtHardeningLevel) value is invalid.The valid values are \"None\", \"Relaxed\" and \"Strict\". Change the CbtHardeningLevel value and try again. |
| 0x803381B9 | WinRM 客户端无法处理该请求，因为无法解析该服务器名称。 |
The WinRM client cannot process the request because the server name cannot be resolved. |
| 0x803381BA | 无法建立 SSL 连接。请验证远程主机上的服务是否正确配置为侦听 HTTPS 请求。有关在目标(通常是 IIS 或 WinRM)上运行的 WS 管理服务，请查阅日志和文档。如果目标是 WinRM 服务，则在目标上运行以下命令来分析和配置 WinRM 服务: \"winrm quickconfig -transport:https\"。 |
The SSL connection cannot be established.Verify that the service on the remote host is properly configured to listen for HTTPS requests.Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: \"winrm quickconfig -transport:https\". |
| 0x803381BB | WinRM 客户端无法处理该请求。可以在下列条件下将默认身份验证与 IP 地址结合使用: 传输为 HTTPS 或目标位于 TrustedHosts 列表中，并且提供了显式凭据。使用 winrm.cmd 配置 TrustedHosts。请注意，TrustedHosts 列表中的计算机可能未经过身份验证。有关如何设置 TrustedHosts 的详细信息，请运行以下命令: winrm help config。 |
The WinRM client cannot process the request.Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided.Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.For more information on how to set TrustedHosts run the following command: winrm help config. |
| 0x803381BC | WinRM 客户端无法处理该请求。自定义远程 Shell 已被弃用，因此无法使用。 |
The WinRM client cannot process the request.Custom Remote Shell has been deprecated and cannot be used. |
| 0x803381BD | WinRM 客户端无法处理该请求。所使用的功能已被弃用，因此无法使用。 |
The WinRM client cannot process the request.The feature in use has been deprecated and cannot be used. |
| 0x803381BE | 在连接字符串中指定 HTTP 时，WinRM 客户端已使用参数指定使用 SSL。 |
The WinRM client used a parameter to specify the use of SSL while specifying http in the connection string. |
| 0x803381BF | WinRM 服务无法处理此请求，因为无法更改此资源 URI 的安全性。 |
The WinRM service cannot process the request because the security for this resource URI cannot be changed. |
| 0x803381C0 | WinRM 服务无法处理该请求。枚举请求要求使用基于选择器的筛选器以指定 Shell 标识符。 |
The WinRM service cannot process the request. The enumeration request expects a selector based filter to specify the shell identifier. |
| 0x803381C1 | WinRM 服务无法处理此请求。不支持对 shell 命令的终结点资源的枚举。 |
The WinRM service cannot process the request. The enumeration of end point resources for shell commands is not supported. |
| 0x803381C2 | WinRM Shell 客户端无法处理该请求，因为 Shell 名称长度超过 255 个字符。 |
The WinRM Shell client cannot process the request because the shell name has exceeded 255 characters in length. |
| 0x803381C3 | 无法完成 WinRM runAs 配置操作，因为无法验证用户凭据。请确认用于配置的用户名和密码有效，然后重试该操作。 |
The WinRM runAs configuration operation cannot be completed because the user credentials could not be verified.Verify that the username and password used for configuration are valid and retry the operation. |
| 0x803381C4 | WinRM 服务无法处理该请求，因为 WinRS Shell 实例当前已断开连接。 |
The WinRM service cannot process the request because the WinRS shell instance is currently disconnected. |
| 0x803381C5 | WinRM 服务无法处理该请求。该 WinRS Shell 实例不支持断开连接和重新连接操作，因为该实例是由较早的 WinRS 客户端创建的，或者其提供程序不支持断开连接操作。 |
The WinRM service cannot process the request. This WinRS shell instance does not support disconnect and reconnect operationsbecause it was created by an older WinRS client or its provider does not support the disconnect operation. |
| 0x803381C6 | WinRM 服务无法处理该请求，因为 WinRS Shell 实例连接到不同的客户端。 |
The WinRM service cannot process the request because the WinRS shell instance is connected to a different client. |
| 0x803381C7 | WinRM 外壳程序客户端无法处理该请求。WSManDisconnectShell 函数所需的参数之一为空或零。更改该请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManDisconnectShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803381C8 | WinRM 外壳程序客户端无法处理该请求。WSManReconnectShell 函数所需的参数之一为空或零。更改该请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803381C9 | WinRM 外壳程序客户端无法处理该请求。WSManConnectShell 函数所需的参数之一为空或零。更改该请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShell function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803381CA | WinRM 外壳程序客户端无法处理该请求。WSManConnectShellCommand 函数所需的参数之一为空或零。更改该请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShellCommand function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803381CB | WinRM 客户端无法处理该请求。正文响应不是有效的连接请求响应。 |
The WinRM client cannot process the request. The body response is not a valid connect request response. |
| 0x803381CC | WinRM Shell 客户端无法处理该请求。当前正在终止或已终止该命令。 |
The WinRM Shell client cannot process the request. The command is currently terminating or was terminated. |
| 0x803381CD | WinRM 服务无法处理此请求。WinRS shell 实例当前已连接到其他客户端。 |
The WinRM service cannot process the request. The WinRS shell instance is currently connected to a different client. |
| 0x803381CE | 在断开连接操作期间，WinRM 客户端与 WinRM 服务通信时遇到错误。Shell 已断开连接，并且流可能会突然暂停。 |
The WinRM client encountered an error while communicating with the WinRM service during the disconnect operation.The shell has been disconnected and the streams were possibly suspended abruptly. |
| 0x803381CF | WinRM 客户端无法处理此请求。不能对已经断开连接的 WinRS shell 实例执行断开连接操作。 |
The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell instance that is already disconnected. |
| 0x803381D0 | WinRM 客户端无法处理该请求。无法在当前连接的 WinRS Shell 实例上执行重新连接操作。 |
The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell instance that is currently connected. |
| 0x803381D1 | 订阅组策略更改通知时遇到错误。 |
An error was encountered while subscribing to the Group Policy change notification. |
| 0x803381D2 | WinRM 外壳程序客户端无法处理该请求。WSManReconnectShellCommand 函数所需的参数之一为空或零。更改该请求以包括缺少的参数并重试。 |
The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShellCommand function is null or zero.Change the request to include the missing parameter and try again. |
| 0x803381D3 | WinRM 客户端无法处理该请求。无法在当前连接的 WinRS Shell 命令实例上执行重新连接操作。 |
The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell command instance that is currently connected. |
| 0x803381D4 | WinRM 服务无法处理该请求，因为客户端指定的命令 ID 不是有效的 GUID。请修改该请求，然后重试该请求。 |
The WinRM service cannot process the request because the command ID specified by the client is not a valid GUID. Modify the request and retry the request. |
| 0x803381D5 | WinRM 服务无法处理该请求，因为客户端指定的 Shell ID 不是有效的 GUID。请提供有效的 ID，然后再试一次。 |
The WinRM service cannot process the request because the shell ID specified by the client is not a valid GUID. Provide a valid ID and try again. |
| 0x803381D6 | WinRM 服务无法处理该请求。具有客户端指定的命令 ID 的命令已存在。 |
The WinRM service cannot process the request. A command already exists with the command ID specified by the client. |
| 0x803381D7 | WinRM 服务无法处理该请求。具有客户端指定的 Shell ID 的资源已存在。 |
The WinRM service cannot process the request. A resource already exists with the shell ID specified by the client. |
| 0x803381D8 | WinRM 客户端无法处理该请求。无法在断开连接的 WinRS Shell 命令实例上执行断开连接操作。 |
The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell command instance that is disconnected. |
| 0x803381D9 | WS-Management 服务无法处理此请求。订阅操作的资源 URI 不得包含键。 |
The WS-Management service cannot process the request. The resource URI for the Subscribe operation must not contain keys. |
| 0x803381DA | WinRM 客户端无法处理该请求。为 WSManDisconnectShell 方法指定的标志无效。请删除或更改该标志，然后重试该操作。 |
The WinRM client cannot process the request. A flag that is not valid was specified for the WSManDisconnectShell method.Remove or change the flag and retry the operation. |
| 0x803381DB | WinRM 客户端无法处理该请求，因为命令句柄与提供的 Shell 句柄没有关联。 |
The WinRM client cannot process the requestbecause the command handle is not associated with the provided shell handle. |
| 0x803381DC | WS-Management 服务在 OperationTimeout 中指定的时间内未收到扩展语义操作的响应。 |
The WS-Management service did not receive a response for an extended semantics operation within the timeframe specified in the OperationTimeout setting. |
| 0x803381DD | WS-Management 服务配置为不允许远程请求。 |
The WS-Management service is configured to not allow remote requests. |
| 0x803381DE | WS-Management 服务无法处理此请求，因为当前已断开此流的连接。 |
The WS-Management service cannot process the request because the stream is currently disconnected. |
| 0x803381DF | 创建新的 Shell 失败。请验证是否正确配置了 RunAsPassword 值，并且“不允许 WinRM 存储 RunAs 凭据”组策略设置为“已禁用”或“未配置”。要允许 WinRM 存储 RunAs 凭据，请将该组策略设置更改为“已禁用”。 |
The creation of a new Shell failed. Verify that the RunAsPassword value is correctly configured and that the Group Policy setting \"Disallow WinRM from storing RunAs credentials\" is Disabled or Not Configured.To enable WinRM to store RunAs credentials, change this Group Policy setting to Disabled. |
| 0x803381E0 | 提供的插件配置 XML 无效。要允许 WinRM 存储 RunAs 凭据，请将“不允许 WinRM 存储 RunAs 凭据”组策略设置更改为“已禁用”。 |
The supplied plugin configuration XML is not valid.To enable WinRM to store RunAs credentials, change the \"Disallow WinRM from storing RunAs credentials\" Group Policy setting to Disabled. |
| 0x803381E1 | WinRM 客户端无法处理此请求，因为 XML 实例与服务器提供的类架构不匹配。 |
The WinRM client cannot process the request because the XML instance does not match the class schema provided by the server. |
| 0x803381E2 | WinRM 客户端无法处理该请求，因为 XML 包含不支持的类型。请验证 XML，然后重试该操作。 |
The WinRM client cannot process the request because the XML contains an unsupported type. Verify the XML and retry the operation. |
| 0x803381E3 | WS-Management 服务无法处理该请求。该服务配置为拒绝此插件的远程连接请求。 |
The WS-Management service cannot process the request.The service is configured to reject remote connection requests for this plugin. |
| 0x803381E4 | WS-Management 服务无法处理该请求。此用户已超过该插件允许的最大并发 Shell 数。请关闭至少一个打开的 Shell，或提高此用户的插件配额。 |
The WS-Management service cannot process the request. This user has exceeded the maximum number of concurrent shells allowed for this plugin.Close at least one open shell or raise the plugin quota for this user. |
| 0x803381E5 | WS-Management 服务无法处理该请求。已超过此插件执行远程操作的最大用户数。请稍后重试该请求，或提高并发用户配额。 |
The WS-Management service cannot process the request. The maximum number of users executing remote operations has been exceeded for this plugin.Retry the request later or raise the quota for concurrent users. |
| 0x803381E6 | WS-Management 服务无法处理该请求。已超过此插件允许的最大并发 Shell 数。请稍后重试该请求，或提高每个插件的最大 Shell 配额。 |
The WS-Management service cannot process the request. The maximum number of concurrent shells allowed for this plugin has been exceeded.Retry the request later or raise the Maximum Shells per Plugin quota. |
| 0x803381E7 | WS-Management 服务无法处理该请求。已超过此插件允许的最大并发操作数。请稍后重试该请求，或提高每个插件的最大操作配额。 |
The WS-Management service cannot process the request. The maximum number of concurrent operations allowed for this plugin has been exceeded.Retry the request later or raise the Maximum Operations per Plugin quota. |
| 0x803381E8 | WS-Management 服务无法处理该请求。此用户已超过允许的最大并发操作数。请稍后重试该请求，或提高每个用户的最大操作配额。 |
The WS-Management service cannot process the request. This user has exceeded the maximum number of allowed concurrent operations.Retry the request later or raise the Maximum Operations per User quota. |
| 0x803381E9 | WS-Management 服务无法处理该请求。已超过每个 Shell 的最大并发命令数。请稍后重试该请求，或提高每个 Shell 的最大命令配额。 |
The WS-Management service cannot process the request. The maximum number of concurrent commands per shell has been exceeded.Retry the request later or raise the Maximum Commands per Shell quota. |
| 0x803381EA | WS-Management 服务无法处理该请求。没有足够的资源来处理此操作。请稍后重试该操作，或关闭一个或多个当前运行的操作。 |
The WS-Management service cannot process the request.There are not enough resources available to process this operation.Retry the operation later or close one or more of the currently running operations. |
| 0x803381EB | WinRM 客户端无法处理此请求，因为无法创建 MI 反序列化程序。 |
The WinRM client cannot process the request because the MI Deserializer cannot be created. |
| 0x803381EC | WinRM 客户端无法处理此请求，因为无法反序列化元数据。 |
The WinRM client cannot process the request because the metadata could not be deserialized. |
| 0x803381ED | WinRM 客户端无法处理该请求，因为无法从服务器中检索元数据。 |
The WinRM client cannot process the request because the metadata failed to be retrieved from the server. |
| 0x803381EE | WinRM 客户端无法处理此请求，因为无法创建 WinRM 会话。 |
The WinRM client cannot process the request because a WinRM session could not be created. |
| 0x803381EF | WinRM 客户端无法处理该请求，因为目标对象已将一个关键属性设置为 NULL。不能将不完整的对象作为操作目标。 |
The WinRM client cannot process the request because the target object has a key property set to NULL.Incomplete objects cannot be used as the target of an operation. |
| 0x803381F0 | WinRM 客户端无法处理该请求，因为无法验证服务器身份。如果服务器身份可信，请将其添加到 TrustedHosts 列表中，然后重试该请求。使用 winrm.cmd 配置 TrustedHosts。请注意，可能不会验证 TrustedHosts 列表中的计算机。有关如何设置 TrustedHosts 的详细信息，请运行以下命令: winrm help config |
The WinRM client cannot process the request as the server identity could not be verified. If the identity of the server is trusted, add it to the TrustedHosts list and retry the request.Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.For more information on how to set TrustedHosts, run the following command: winrm help config |
| 0x803381F1 | WinRM 客户端无法处理该请求，因为不支持八进制字符串数组类型。 |
The WinRM client cannot process the request because the octet string array type is not supported. |
| 0x803381F2 | WS-Management 服务无法处理请求。请求的 IdleTimeout 超出允许的范围。 |
The WS-Management service cannot process the request. The requested IdleTimeout is outside the allowed range. |
| 0x803381F3 | WinRM 客户端无法处理该请求，因为没有提供足够的元数据。应用程序不允许将所有属性作为字符串返回，但服务器不支持正确地键入属性。请更改该请求以允许将所有属性作为字符串返回，然后重试该请求。 |
The WinRM client cannot process the request because insufficient metadata is available.The application does not allow all properties to be returned as strings, but the server does not support correctly typing the properties.Change the request to allow all properties to be returned as strings and retry the request. |
| 0x803381F4 | WinRM 客户端无法处理请求，因为 MI_OperationOptions 同时包含资源 URI 和资源 URI 前缀。请仅指定其中的一个选项，然后重试。 |
The WinRM client cannot process the request because the MI_OperationOptions contained both a Resource URI and a Resource URI Prefix. Specify only one of these two options and try again. |
| 0x803381F5 | WinRM 客户端无法处理请求，因为同时指定了 keysOnly 和 WSMAN_ENUMERATIONMODE_OBJECTONLY。这两个设置不兼容。请删除 WSMAN_ENUMERATIONMODE_OBJECTONLY 选项或将 keysOnly 设置为 MI_FALSE，然后重试该请求。 |
The WinRM client cannot process the request because keysOnly and WSMAN_ENUMERATIONMODE_OBJECTONLY were specified at the same time.These two settings are incompatible.Remove the WSMAN_ENUMERATIONMODE_OBJECTONLY option, or set keysOnly to MI_FALSE, and retry the request. |
| 0x803381F6 | WinRM 客户端无法处理该请求，因为类名无效。请提供有效的类名或设置资源 URI 选项，然后重试该请求。 |
The WinRM client cannot process the request because the class name is not valid.Supply a valid class name or set the Resource URI option and retry the request. |
| 0x803381F7 | 订阅数据包在传递部分中包含无效的编码值。 |
The subscribe packet contains an Encoding value that is not valid in the delivery section. |
| 0x803381F8 | WinRM 客户端无法处理该请求。目标计算机名称必须为主机名或 IP 地址，并且不能是 URL。若要使用 IPv6 地址，请用括号括住该地址，如下所示:“[::1]”。传输、端口号和 URL 前缀可通过设置适当的目标选项控制。请更改目标计算机名字符串，然后重试该操作。 |
The WinRM client cannot process the request.The destination computer name must be a hostname or an IP address, and must not be a URL.To use an IPv6 address, enclose the address in brackets, like the following: \"[::1]\".The transport, port number, and URL prefix may be controlled by setting the appropriate destination options.Change the destination computer name string and retry the operation. |
| 0x803381F9 | 服务器不支持 WS-Management 标识操作。请跳过请求的 TestConnection 部分，然后重试。 |
The server does not support WS-Management Identify operations. Skip the TestConnection part of the request and try again. |
| 0x803381FA | WS-Management 服务无法处理此操作。尝试运行此操作的客户端会话无法使用。这可能与最近重新启动 WS-Management 服务有关。如果重新执行此操作未出现意外行为，请新建客户端会话，然后重试此操作。 |
The WS-Management service cannot process the operation. The operation is being attempted on a client session that is unusable. This may be related to a recent restart of the WS-Management service. Please create a new client session and retry the operation if re-executing the operation does not have undesired behavior. |
| 0x803381FB | WS-Management 服务无法处理该操作。尝试创建虚拟帐户失败。请确保 WinRM 服务正在作为本地系统运行并且已启用 TCB 特权。 |
The WS-Management service cannot process the operation. An attempt to create a virtual account failed. Ensure that WinRM service is running as Local System and that it has TCB privilege enabled. |
| 0x803381FC | WS-Management 服务无法处理该操作。虚拟帐户功能只能在 Windows 7、Server 2008 R2 及更高平台中使用。 |
The WS-Management service cannot process the operation. Virtual account feature is only available in Windows 7, Server 2008 R2 and above. |
| 0x803381FD | WS-Management 服务无法处理该操作。尝试使用配置的 RunAs 托管服务帐户登录失败。 |
The WS-Management service cannot process the operation. An attempt to logon using the configured RunAs Managed Service Account failed. |
| 0x803381FE | WS-Management 服务无法处理该操作。尝试查询映射凭据失败。如果与 WinRM 服务关联的安全上下文自最初映射凭据以来已更改，则会出现这种情况。 |
The WS-Management service cannot process the operation. An attempt to query mapped credential failed. This will happen if the security context associated with WinRM service has changed since the credential was originally mapped. |
| 0x90000001 | Microsoft-Windows-Windows Remote Management |
Microsoft-Windows-Windows Remote Management |
| 0x90000002 | Microsoft-Windows-WinRM/Operational |
Microsoft-Windows-WinRM/Operational |
| 0x90000003 | Microsoft-Windows-WinRM/Analytic |
Microsoft-Windows-WinRM/Analytic |
| 0xB0000002 | 正在初始化 WSMan API |
Initializing WSMan API |
| 0xB0000003 | 初始化 WSMan API 失败，错误代码 %1 |
Initialization of WSMan API failed, error code %1 |
| 0xB0000004 | 正在取消初始化 WSMan API |
Deinitializing WSMan API |
| 0xB0000005 | 取消初始化 WSMan API 失败，错误代码 %1 |
Deinitialization of WSMan API failed, error code %1 |
| 0xB0000006 | 正在创建 WSMan 会话。连接字符串为: %1 |
Creating WSMan Session. The connection string is: %1 |
| 0xB0000007 | WSMan 创建会话操作失败，错误代码 %1 |
WSMan Create Session operation failed, error code %1 |
| 0xB0000008 | 正在关闭 WSMan 会话 |
Closing WSMan Session |
| 0xB0000009 | 关闭 WSMan 会话失败，错误代码 %1 |
Closing WSMan Session failed, error code %1 |
| 0xB000000A | 已成功完成使用值(%3)设置 WSMan 会话选项(%1) - %2 的操作。 |
Setting WSMan Session Option (%1) - %2 with value (%3) completed successfully. |
| 0xB000000B | 正在创建 WSMan 外壳程序，ResourceUri 为 %1，ShellId 为 %2 |
Creating WSMan shell with the ResourceUri: %1 and ShellId: %2 |
| 0xB000000C | WSMan 外壳程序创建失败，错误代码 %1 |
WSMan shell creation failed, error code %1 |
| 0xB000000D | 正在运行 CommandId 为 %1 的 WSMan 命令 |
Running WSMan command with CommandId: %1 |
| 0xB000000E | 运行 WSMan 命令失败，错误代码 %1 |
Running WSMan command failed, error code %1 |
| 0xB000000F | 正在关闭 WSMan 命令 |
Closing WSMan command |
| 0xB0000010 | 正在关闭 WSMan 外壳程序 |
Closing WSMan shell |
| 0xB000001C | 拒绝访问错误: %1 API 调用方与应用程序对象的创建者不匹配 |
Access Denied error: the %1 API caller does not match the creator of the application object |
| 0xB000001D | WSMan API 初始化已成功完成 |
Initialization of WSMan API completed successfuly |
| 0xB000001E | 取消初始化 WSMan API 已成功完成 |
Deinitialization of WSMan API completed successfuly |
| 0xB000001F | WSMan 创建会话操作已成功完成 |
WSMan Create Session operation completed successfuly |
| 0xB0000020 | 设置 WSMan 会话选项(%1) - %2 失败，错误代码为 %3。 |
Setting WSMan Session Option (%1) - %2 failed, error code %3. |
| 0xB0000021 | 关闭 WSMan 会话已成功完成 |
Closing WSMan Session completed successfuly |
| 0xB0000025 | 关闭 WSMan 外壳程序失败，错误代码 %1 |
Closing WSMan shell failed, error code %1 |
| 0xB0000026 | 关闭 WSMan 命令失败，错误代码 %1 |
Closing WSMan command failed, error code %1 |
| 0xB0000028 | 结束 WSMan %1 操作失败，错误代码 %2 |
Closing WSMan %1 operation failed, error code %2 |
| 0xB0000029 | 已开始为应用程序 %1 加载 WinRM 协议处理程序。 |
The WinRM protocol handler has began loading for application %1. |
| 0xB000002A | WinRM 协议处理程序已完成卸载。 |
The WinRM protocol handler completed unloading. |
| 0xB000002B | 由于以下错误，提前卸载了 WinRM 协议处理程序: %2。 |
The WinRM protocol handler unloaded prematurely due to the following error: %2. |
| 0xB000002C | WinRM 协议处理程序已开始在以下目标中创建会话: %1。 |
The WinRM protocol handler started to create a session at the following destination: %1. |
| 0xB000002D | WinRM 协议处理程序已关闭此会话。 |
The WinRM protocol handler closed the session. |
| 0xB000002E | 由于以下错误，提前关闭了 WinRM 协议会话: %2。 |
The WinRM protocol session closed prematurely due to the following error: %2. |
| 0xB000002F | WinRM 协议会话开始对服务器执行 %1 类型的操作。该操作访问 %2 命名空间中的类 %3。 |
The WinRM protocol session began an operation of type %1 to the server. The operation accesses class %3 under the %2 namespace. |
| 0xB0000030 | WinRM 协议会话已成功完成该操作。 |
The WinRM protocol session successfully completed the operation. |
| 0xB0000031 | 由于以下错误，WinRM 协议操作失败: %2。 |
The WinRM protocol operation failed due to the following error: %2. |
| 0xB0000054 | 已超过执行外壳程序操作的用户的最大数目(%1)。%n请稍后重试或提高并发外壳程序用户的配额。 |
The maximum number of users (%1) executing shell operations has been exceeded.%nRetry after sometime or raise the quota for concurrent shell users. |
| 0xB0000055 | 允许 %1 用户的并发外壳程序的最大数目为 %2，已超过该最大数目。%n关闭现有外壳程序或提高此用户的配额。 |
The %1 user is allowed a maximum number of %2 concurrent shells, which has been exceeded.%nClose existing shells or raise the quota for this user. |
| 0xB0000056 | WSMan 服务无法启动主机进程以处理给定的请求。请确保正确注册了 WSMan 提供程序的主机服务器和代理。错误代码 %1 |
The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. Error code %1 |
| 0xB0000057 | WSMan 主机进程意外终止。错误代码 %1 |
The WSMan host process was unexpectedly terminated. Error code %1 |
| 0xB000005A | RunAs 已被组策略禁用；WSMan 服务已清除所有 RunAs 凭据。 |
RunAs was disabled by Group Policy; WSMan service has erased all RunAs credentials. |
| 0xB000005B | 正在使用 ResourceUri %1 在服务器上创建 WSMan shell |
Creating WSMan shell on server with ResourceUri: %1 |
| 0xB0000083 | 已从网络层收到重定向状态代码；状态: 302 (HTTP_STATUS_REDIRECT)；位置: %1 |
Received redirect status code from Network layer; status: 302 (HTTP_STATUS_REDIRECT); location: %1 |
| 0xB0000084 | WSMan 操作 %1 已成功完成 |
WSMan operation %1 completed successfully |
| 0xB0000087 | 作为 ERROR_WINHTTP_CANNOT_CONNECT 的结果，正在使用下一个代理重新发送请求 |
Re-sending the request as a result of ERROR_WINHTTP_CANNOT_CONNECT, using next proxy |
| 0xB0000088 | 作为 ERROR_WINHTTP_NAME_NOT_RESOLVED 的结果，正在使用下一个代理重新发送请求 |
Re-sending the request as a result of ERROR_WINHTTP_NAME_NOT_RESOLVED, using next proxy |
| 0xB0000089 | 网络层已返回 ERROR_WINHTTP_NAME_NOT_RESOLVED - 无法解析服务器名称。正在中止操作 |
Network layer returned ERROR_WINHTTP_NAME_NOT_RESOLVED - The server name cannot be resolved. Aborting the operation |
| 0xB000008A | 客户端从网络层得到一个超时(ERROR_WINHTTP_TIMEOUT) |
The client got a timeout from the network layer (ERROR_WINHTTP_TIMEOUT) |
| 0xB000008B | 客户端从网络层得到一个登录失败(ERROR_WINHTTP_LOGIN_FAILURE) |
The client got a login failure from the network layer (ERROR_WINHTTP_LOGIN_FAILURE) |
| 0xB000008E | WSMan 操作 %1 失败，错误代码 %2 |
WSMan operation %1 failed, error code %2 |
| 0xB0000091 | 已使用 resourceUri %2 启动 WSMan 操作 %1 |
WSMan operation %1 started with resourceUri %2 |
| 0xB00000A1 | %1 |
%1 |
| 0xB00000A2 | 对用户的身份验证失败。凭据无效。 |
Authenticating the user failed. The credentials didn't work. |
| 0xB00000A3 | 该服务器不支持客户端请求的身份验证机制(%1)。%n由服务器报告的可能身份验证机制: %2 %3 %4 %5 %6 |
The authentication mechanism (%1) requested by the client is not supported by the server.%nPossible authentication mechanisms reported by server: %2 %3 %4 %5 %6 |
| 0xB00000A4 | 目标计算机(%1)返回“拒绝访问”错误。请验证你的凭据是否正确。 |
The destination computer (%1) returned an 'access denied' error. Verify your credentials are correct. |
| 0xB00000A5 | 客户端不支持代理请求的身份验证机制。唯一支持的身份验证机制是协商、基本或摘要式身份验证。%n代理报告的可能身份验证机制: %1 %2 %3 %4 %5 |
The authentication mechanism requested by the proxy is not supported by the client. The only proxy authentication mechanism supported are Negotiate, Basic or Digest. %nPossible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5 |
| 0xB00000AB | 对代理的用户身份验证失败。凭据无效。 |
Authenticating the user with the proxy failed. The credentials didn't work. |
| 0xB00000AC | 目标计算机(%1:%2)上的服务器证书包含以下错误: %3 %4 %5 %6 %7 %8 %9 %10。请修复服务器证书，然后再试一次。 |
The server certificate on the destination computer (%1:%2) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10. Fix the server certificate and try again. |
| 0xB00000C0 | 用户授权失败，错误为 %1 |
The authorization of the user failed with error %1 |
| 0xB00000C1 | 将使用 WinRM 虚拟帐户 %3 (%4)执行用户 %1 (%2)的请求 |
Request for user %1 (%2) will be executed using WinRM virtual account %3 (%4) |
| 0xB00000D0 | Winrm 服务正在启动 |
The Winrm service is starting |
| 0xB00000D1 | Winrm 服务已成功启动 |
The Winrm service started successfully |
| 0xB00000D2 | WinRM 服务无法启动，因为在初始化过程中出现故障。错误代码是 %1 |
The WinRM service is unable to start because of a failure during initialization. The error code is %1 |
| 0xB00000D3 | Winrm 服务正在停止 |
The Winrm service is stopping |
| 0xB00000D4 | Winrm 服务已成功停止 |
The Winrm service was stopped successfully |
| 0xB00000D5 | WSMan 服务无法加载当前的配置设置，因为这些设置已损坏。该服务已改用默认的设置启动。%n%n 用户操作 %n 使用以下命令还原默认值: %n%n winrm invoke Restore winrm/config @{} |
The WSMan service could not load current configuration settings as the settings are corrupted. The service is started with default settings instead. %n%n User Action %n Use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} |
| 0xB00000D6 | WSMan 客户端无法加载当前的配置设置，因为这些设置已损坏。该服务正在改用默认的设置运行。%n%n 用户操作 %n 启动 WinRM 服务并使用以下命令还原默认值: %n%n winrm invoke Restore winrm/config @{} |
The WSMan client could not load current configuration settings as the settings are corrupted. The client is operating with default settings instead. %n%n User Action %n Start the WinRM service and use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} |
| 0xB00000D8 | WSMan 服务无法重新启动标记为“自动重新启动”的插件。收到的错误代码为: %1。 |
The WSMan service failed to restart the plugins marked for AutoRestart. The error code received was %1. |
| 0xB00000D9 | WSMan 服务无法在服务启动时重新启动 %1 插件。收到的错误代码为 %2。 |
The WSMan service failed to restart the %1 plugin on service startup. The error code received was %2. |
| 0xB00000DA | WSMan 服务已在服务启动时成功重新启动以下插件: %1。 |
The WSMan service successfully restarted the following plugin on service startup: %1. |
| 0xB00000DB | WSMan shell 实例 %1 将不再支持断开连接重新连接功能，因为客户端发送了一个不支持的请求。 |
The WSMan shell instance %1 will no longer support disconnect reconnect functionality because a non-supported request was sent by the client. |
| 0xB00000E5 | WinRM %1 无法注册组策略更改通知。错误代码为 %2。 |
The WinRM %1 failed to register for group policy change notifications. The error code is %2. |
| 0xB00000E6 | 删除注册表项 %1 导致访问被拒绝。如果该注册表项未明确标记为只读，则可能会出现问题。 |
Deletion of registry key %1 resulted in access denied. If this registry entry is not marked specifically as read only, this seems like a potential issue. |
| 0xB000011B | 报告操作 %1 的上下文的插件 |
Plug-in reporting context for operation %1 |
| 0xB000011C | 报告操作 %1 的数据对象的插件 |
Plug-in reporting data object for operation %1 |
| 0xB000011D | 报告操作 %1 的数据对象和 EPR 的插件 |
Plug-in reporting data object and EPR for operation %1 |
| 0xB000011E | 报告操作 %1 的数据对象和书签的插件 |
Plug-in reporting data object and bookmark for operation %1 |
| 0xB000011F | 报告操作接收的数据的插件 |
Plug-in reporting data for operation Receive |
| 0xB0000120 | 报告 %1 的操作完成的插件 |
Plug-in reporting operation complete for %1 |
| 0xB0000121 | 正在获取参数 %1 和操作 %2 的操作信息的插件 |
Plug-in getting operational information for parameter %1 and operation %2 |
| 0xB0000122 | 报告用户 %1 的授权已完成，错误代码为 %2 的插件 |
Plug-in reporting the authorization for user %1 completed with error code %2 |
| 0xB0000123 | 报告操作 %2 和 ResourceUri %3 的授权操作已完成，错误为 %1 的插件 |
Plug-in reporting the authorization operation completed with error %1 for operation %2 and ResourceUri %3 |
| 0xB0000124 | 正在更新用户 %1 的配额，错误代码为 %2%n maxAllowedConcurrentShells=%3%n maxAllowedConcurrentOperations=%4%n timeslotSize=%5%n maxAllowedOperationsPerTimeslot=%6 |
Updating the quota for the user %1 with error code %2%n maxAllowedConcurrentShells=%3%n maxAllowedConcurrentOperations=%4%n timeslotSize=%5%n maxAllowedOperationsPerTimeslot=%6 |
| 0xB0000134 | 名为 WSManPluginGetConfiguration 的插件使用参数 %1，并获得返回值 %2。 |
The plugin called WSManPluginGetConfiguration with the parameter %1 and obtained a return value of %2. |
| 0xB0000135 | 名为 WSManPluginReportCompletion 的插件使用参数 %1，并获得返回值 %2。 |
The plugin called WSManPluginReportCompletion with the parameter %1 and obtained a return value of %2. |
| 0xB0000136 | 正在关闭插件 %1，因为其空闲时间超过配置的 HostIdleTimeoutSecs 配额。 |
The plugin %1 is being shut down because it was idle for longer than the configured HostIdleTimeoutSecs quota. |
| 0xB0000137 | 发出 WSMan 命令的信号失败，错误代码为 %1 |
Signaling WSMan command failed, error code %1 |
| 0xB0000138 | 正在发出 WSMan 命令的信号 |
Signaling WSMan command |
| 0xB0000139 | 正在将输入发送到命令 |
Sending input to the command |
| 0xB000013A | 正在将输入发送到外壳程序 |
Sending input to the shell |
| 0xB000013B | 发送输入操作失败，错误代码为 %1 |
Sending input operation failed, error code %1 |
| 0xB000013C | 正在调入 WSMan 以接收外壳程序的输出 |
Calling into WSMan to receive output from the shell |
| 0xB000013D | WSMan 接收操作失败，错误代码为 %1 |
WSMan receive operation failed, error code %1 |
| 0xB000013E | 正在调入 WSMan 以接收命令的输出 |
Calling into WSMan to receive output from the command |
| 0xB000013F | 获取错误代码 %1 的消息已成功完成。languageCode 参数为: %2 |
Getting message for error code %1 completed successfully. The languageCode parameter was: %2 |
| 0xB0000140 | 正在获取 WSMan 会话选项(%1) - %2。 |
Getting WSMan Session Option (%1) - %2. |
| 0xB0000141 | 正在发出 WSMan 外壳程序的信号 |
Signaling WSMan shell |
| 0xB0000142 | 正在发出 WSMan 外壳程序的信号，错误代码为 %1 |
Signaling WSMan shell, error code %1 |
| 0xB0000143 | 正在关闭 WSMan 操作 |
Closing WSMan operation |
| 0xB0000144 | 关闭 WSMan %1 操作已成功完成 |
Closing WSMan %1 operation completed successfully |
| 0xB0000145 | 正在断开具有以下 ID 的 Shell 连接: %1 |
Disconnecting shell with Id : %1 |
| 0xB0000146 | 断开 Shell 连接失败，错误代码为 %1 |
Disconnecting shell failed, error code %1 |
| 0xB0000147 | 正在重新连接具有以下 ID 的 Shell: %1 |
Reconnecting shell with Id : %1 |
| 0xB0000148 | 重新连接 Shell 失败，错误代码为 %1 |
Reconnecting shell failed, error code %1 |
| 0xB0000149 | 正在连接具有以下 ID 的 Shell: %1 |
Connecting shell with Id : %1 |
| 0xB000014A | 连接 Shell 失败，错误代码为 %1 |
Connecting shell failed, error code %1 |
| 0xB000014B | 正在重新连接具有以下 ID 的 Shell 命令: %1 |
Reconnecting shell command with Id : %1 |
| 0xB000014C | 重新连接 Shell 命令失败，错误代码为 %1 |
Reconnecting shell command failed, error code %1 |
| 0xB000014D | 正在连接具有以下 ID 的 Shell 命令: %1 |
Connecting shell command with Id : %1 |
| 0xB000014E | 连接 Shell 命令失败，错误代码为 %1 |
Connecting shell command failed, error code %1 |
| 0xB0000201 | 代理自动检测完成。%n代理列表: %1 %n绕过列表: %2 |
Proxy AutoDetect done.%nProxy list: %1 %nBypass list: %2 |
| 0xB0000202 | 正在设置代理信息 %n 代理列表: %1 %n绕过列表: %2 |
Setting proxy info %n Proxy list: %1 %n Bypass list: %2 |
| 0xB0000303 | SOAP [正在发送 %2 个总文本块(%3 个字节)中索引 %1 的客户端] %4 |
SOAP [client sending index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000304 | SOAP [正在接收 %2 个总文本块(%3 个字节)中索引 %1 的侦听程序] %4 |
SOAP [listener receiving index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000306 | 允许 %1 用户的并发操作的最大数目为 %2，已超过该最大数目。%n关闭此用户的现有操作，或提高此用户的配额。 |
The %1 user is allowed a maximum number of %2 concurrent operations, which has been exceeded.%nClose existing operations for this user, or raise the quota for this user. |
| 0xB0000307 | 已超过每 %2 秒 %1 个请求的用户负载配额。%n以较慢速率发送将来的请求或提高 %3 用户的配额。%n来自此用户的下一请求将被拒绝至少 %4 毫秒。 |
The user load quota of %1 requests per %2 seconds has been exceeded.%nSend future requests at a slower rate or raise the quota for the %3 user.%nThe next request from this user will not be approved for at least %4 milliseconds. |
| 0xB0000308 | 已超过每 %2 秒 %1 个请求的系统负载配额。%n以较慢速率发送将来的请求或提高系统配额。%n来自用户 %3 的下一请求将被拒绝至少 %4 毫秒。 |
The system load quota of %1 requests per %2 seconds has been exceeded.%nSend future requests at a slower rate or raise the system quota.%nThe next request from the user %3 will not be approved for at least %4 milliseconds. |
| 0xB000030C | WinRM %1 遇到网络连接问题。 |
The WinRM %1 has encountered network connectivity issues. |
| 0xB000030D | WinRM 客户端正在尝试重新建立网络连接。 |
The WinRM Client is attempting to re-establish a network connection. |
| 0xB000030E | WinRM 服务已检测到客户端的新网络连接。 |
The WinRM Service has detected a new network connection from the client. |
| 0xB000030F | WinRM %1 已成功重新建立网络连接。 |
The WinRM %1 has successfully re-established a network connection. |
| 0xB0000310 | WinRM %1 无法重新建立网络连接，正在报告错误。 |
The WinRM %1 failed to re-establish a network connection and is reporting a failure. |
| 0xB0000311 | 已为用户 %1 启动 WSMan 主机进程。 |
The WSMan host process was started for user %1. |
| 0xB0000312 | 已为用户 %1 终止 WSMan 主机进程。 |
The WSMan host process was terminated for user %1. |
| 0xB0000313 | 正在将操作 %1 的请求发送到目标计算机和端口 %2:%3 |
Sending the request for operation %1 to destination machine and port %2:%3 |
| 0xB0000314 | 正在处理操作 %1 的客户端请求 |
Processing client request for operation %1 |
| 0xB0000315 | 正在使用 的 ResourceURI 输入操作 %1 的插件 |
Entering the plugin for operation %1 with a ResourceURI of |
| 0xB0000316 | 正在保留操作 %1 的插件 |
Leaving the plugin for operation %1 |
| 0xB0000317 | WinRM 服务无法枚举 DASH/SMASH 规范，发生 MI 错误: %1。 |
The WinRM service failed to enumerate DASH/SMASH specifications with MI error: %1. |
| 0xB0000401 | 正在发送 ActionURI 的响应错误数据包: %1 |
Sending response error packet for ActionURI: %1 |
| 0xB0000402 | SOAP [正在接收 %2 个总文本块(%3 个字节)中索引 %1 的客户端] %4 |
SOAP [client receiving index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000403 | SOAP [正在发送 %2 个总文本块(%3 个字节)中索引 %1 的侦听程序] %4 |
SOAP [listener sending index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000411 | 正在关闭枚举 |
Enumeration is shutting down |
| 0xB0000413 | 正在关闭订阅 |
Subscription is shutting down |
| 0xB0000415 | 已从网络层收到响应；状态: 200 (HTTP_STATUS_OK) |
Received the response from Network layer; status: 200 (HTTP_STATUS_OK) |
| 0xB0000416 | %1 操作的扩展语义回调超时。 |
An extended semantics callback timed out for the %1 operation. |
| 0xB0000417 | 已从网络层收到响应；状态: %1 |
Received the response from Network layer; status: %1 |
| 0xB0000418 | 由于传输失败，正在将 HTTP 错误发送回客户端。%nHTTP 状态代码为 %1%n错误代码为 %2 |
Sending HTTP error back to the client due to a transport failure.%nThe HTTP status code is %1%nThe error code is %2 |
| 0xB0000419 | 正在发送操作的超时响应: %1 |
Sending timeout response for operation: %1 |
| 0xB000041A | 正在发送操作 %1 的响应 |
Sending response for operation %1 |
| 0xB000041D | 由于 WSMan Shell 断开连接，WSMan 操作 %1 被暂停。 |
WSMan operation %1 got suspended because of WSMan Shell disconnection. |
| 0xB000041E | 由于 WSMan Shell 重新连接，WSMan 操作 %1 正在恢复。 |
WSMan operation %1 resuming because of WSMan Shell reconnection. |
| 0xB000050B | 作为来自网络层的 HTTP 401 响应的结果，网络层自动登录策略设置为低 |
Network layer AutoLogon policy was set to Low as a result of a HTTP 401 response from Network layer |
| 0xB000050C | 网络层自动登录策略设置为高 |
Network layer AutoLogon policy was set to High |
| 0xB000050D | 选中的身份验证机制为 %1 |
The chosen authentication mechanism is %1 |
| 0xB000050E | 正在将 HTTP 401 响应发送到客户端并在发送响应之后断开连接 |
Sending HTTP 401 response to the client and disconnect the connection after sending the response |
| 0xB000050F | 用户 %1 已使用 %2 身份验证成功进行验证身份 |
User %1 authenticated successfully using %2 authentication |
| 0xB0000510 | 通过使用者为 %1 的客户端证书进行的身份验证已成功完成 |
The authentication using client certificate with subject %1 done successfully |
| 0xB0000511 | 正在使用 %1 机制对用户进行身份验证 |
Authenticating the user using %1 mechanism |
| 0xB0000600 | 正在授权用户 |
Authorizing the user |
| 0xB0000601 | 用户授权已成功完成 |
The authorization of the user was done successfully |
| 0xB0000730 | 处理操作时遇到错误。%n错误代码: %1%n错误字符串:%2 |
An error was encountered while processing an operation.%nError Code: %1%nError String:%2 |
| 0xB0000731 | 处理操作时遇到错误。%n错误代码: %1 |
An error was encountered while processing an operation.%nError Code: %1 |
| 0xB0000732 | 额外信息。有关详细信息，请参阅 XML 参数。 |
Extra information. Refer to the XML parameters for more details. |
| 0xB0000733 | 已终止客户端 %1 的未经身份验证的连接。 |
An unauthenticated connection from client %1 is terminated. |
| 0xB0000800 | [文件名:- %1；行:- %2；功能:- %3；] %4 |
[Filename:- %1; Line:- %2; Function:- %3;] %4 |
| 0xB0000801 | [文件名:- %1；行:- %2；功能:- %3；错误代码:- %4] %5 |
[Filename:- %1; Line:- %2; Function:- %3; ErrorCode:- %4] %5 |
| 0xB0010132 | WinRM 服务已加载以下插件: %1 (%2) |
The WinRM service loaded the following plugin: %1 (%2) |
| 0xB0010133 | WinRM 服务已卸载以下插件: %1 (%2) |
The WinRM service unloaded the following plugin: %1 (%2) |
| 0xC007C403 | WinRM 服务正在停止，因为注册 IP 地址的更改时出现故障。%n%n 用户操作 %n 重新启动 WinRM 服务。%n%n 其他数据 %n 错误代码为 %1。 |
The WinRM service is stopping because there was a failure registering for changes to the IP addresses. %n%n User Action %n Restart the WinRM service. %n%n Additional Data %n The error code was %1. |
| 0xC007C404 | WinRM 服务正在停止，因为注册配置的更改时出现故障。%n%n 用户操作 %n 重新启动 WinRM 服务。%n%n 其他数据 %n 错误代码为 %1。 |
The WinRM service is stopping because there was a failure registering for changes to the configuration. %n%n User Action %n Restart the WinRM service. %n%n Additional Data %n The error code was %1. |