| 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 | 顯示目前處理程序識別碼 (PID) |
Displays the current process ID (PID) |
| 0x00072775 | 由於 WinRM 服務無法接聽至少一個位址及連接埠，所以 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) 失敗。登錄了另一個處理程序來接聽 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 (%1) 的 ACL 是否設為 Network Service。%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 Information Services (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 篩選器]。 |
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 系統管理員可使用 setspn.exe 公用程式來建立 SPN。 |
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 服務正在為 WS-Management 要求接聽預設 %1 連接埠 %2 與 %1 (相容性) 連接埠 %3。%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啟用並觀察遠端管理分析記錄，並查看識別碼為 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 |
| 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 服務無法處理該要求。操作識別碼 %1 的長度超過預期長度。 |
The WS-Management service cannot process the request. The operation id %1 is larger than expected. |
| 0x4033C35F | ProvSysException，ErrorCode=%1!d!，訊息=%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 找不到具有指定識別碼 (%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-Management ResourceURI 項目。 |
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-Addressing MessageID 項目。 |
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-Addressing To 項目。 |
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-Addressing FaultTo 項目。該項目重複，或者不是 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-Management Locale 項目。該項目重複，或者不符合系統地區設定。 |
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 封包未包含正確的列舉內容識別碼項目。連入的 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 服務無法處理該要求。無法識別 SOAP 封包中的列舉內容識別碼。該封包可能不正確，或是操作逾時。 |
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 封包中的訂閱內容識別碼。該封包可能無效，或是該操作已經逾時。 |
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 服務收到包含要執行 %1 操作之要求的 SOAP 封包。此操作要求主體中只能有單一元素。在 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 (一般讀取 = WSManGet, WSManEnumerate, WSManSubscribe)、GW (一般寫入 = WSManPut, WSManCreate, WSManDelete) 或GX (一般執行 = WSManInvoke)GA (全部一般化) |
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 服務無法處理該設定要求。此動作需要項目名稱為 %1 的輸入 XML，而且不需要任何參數。 |
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-Management 服務無法處理該要求。使用者沒有 %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 項目，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 | 因為 URI 包含 WS-Management 無法處理的不正確識別碼，所以 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 模式，或該設定已遺失。 |
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 | 因為此服務不支援動作: %1，所以 WS-Management 服務無法處理該要求。 |
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 包含下列內容的不明 CIM 類型: %1。 |
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 例項中包含不正確的 datetime 值 (%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)，但該項目並未代表字串內容。只有字串內容才能是空的。若要指定 Null 值，請新增 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 datetime 類型不接受超過 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 服務無法處理該要求。該要求包含不正確的 datetime.字串 %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 服務無法處理該要求。datetime 值的項目只能有一個子項，而且不能有混合內容。 |
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 服務無法處理該要求。datetime 內容中的項目具有不正確的名稱: %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 | 因為無法將字串 (%1) 轉換為浮點數值，所以 WS-Management 服務無法處理該要求。該值太大。請確定該字串代表的類型正確。 |
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) 不正確。方法 %2 不存在於類別 %3。 |
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 服務無法執行該設定操作。位址=%1 且傳輸=%2 之設定的接聽程式已存在。您必須先刪除現有的接聽程式，才能使用相同的位址與傳輸值來重新建立。 |
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 ResourceURI 元素，所以 WS-Management 服務無法處理該要求。 |
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() 函數套用到陣列、物件、datetime 或參照內容。 |
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 已選取機碼內容，但無法更新該機碼。 |
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 服務上自動設定接聽程式」原則必須設定為「尚未設定」，才能為相同的位址與傳輸建立新的接聽程式，或是修改現有的接聽程式。 |
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 外掛程式 |
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 | %n該 SSL 憑證不正確。 |
%nThe SSL certificate is invalid. |
| 0x4033C432 | %n該 SSL 憑證已撤銷。 |
%nThe SSL certificate was revoked. |
| 0x4033C433 | %n該 SSL 憑證是由不明的憑證授權單位所簽署。 |
%nThe SSL certificate is signed by an unknown certificate authority. |
| 0x4033C434 | %n該 SSL 憑證包含一般名稱 (CN)，但該名稱不符合主機名稱。 |
%nThe SSL certificate contains a common name (CN) that does not match the hostname. |
| 0x4033C435 | %n該 SSL 憑證已到期。 |
%nThe SSL certificate is expired. |
| 0x4033C436 | %n該 SSL 憑證不適用於伺服器驗證。 |
%nThe SSL certificate is not appropriate for server authentication. |
| 0x4033C437 | %n在 SSL 程式庫中發生內部錯誤。 |
%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 服務無法處理該要求，因為 date-time 項目或簡單內容包含子項目。 |
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 | 從 R2 移轉的 WinRM 設定已損毀。接聽程式設定不正確。 |
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 封包未包含正確的訂閱識別碼項目。連入的取消訂閱要求應該包含具有參照內容項目 (從訂閱回應取得) 的標頭項目。 |
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 服務無法處理該設定要求。此動作需要項目名稱為 %1 的輸入 XML。 |
WinRM cannot process the configuration request. This action requires input XML with an element name of %1. |
| 0x4033C463 | 在 %1://%2 上建立 WinRM 接聽程式，以接受對於此電腦之任何 IP 的 WS-Man 要求。 |
Create a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine. |
| 0x4033C464 | 已在 %1://%2 上建立 WinRM 接聽程式，以接受對於此電腦之任何 IP 的 WS-Man 要求。 |
Created 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. |
| 0x4033C467 | 已啟用 %1://%2 上的 WinRM 接聽程式。 |
Enabled 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 | 訂閱封包有一個地區設定項目缺少 lang 屬性。地區設定項目需要 lang 屬性。 |
The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element. |
| 0x4033C481 | WinRM 無法處理該設定要求。此動作需要項目名稱為 %1 而值為 \"http\" 或 \"https\" 的輸入 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 遠端殼層的要求失敗，因為在伺服器上找不到殼層。可能的原因為: 指定的 ShellId 不正確或殼層不再存在於伺服器上。請提供正確的 ShellId，或建立新殼層，然後重試此操作。 |
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 與初始的 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 遠端殼層無法處理該要求。殼層外掛程式傳回的命令識別碼是空的。 |
The Windows Remote Shell cannot process the request. The command id returned from the shell plugin is empty. |
| 0x4033C48F | Windows 遠端殼層無法處理該要求。WS-Addressing 動作 URI 無效。有效的動作包括命令、接收、傳送和訊號。請參閱 Windows 遠端殼層文件，取得如何建構動作 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 遠端殼層無法處理該要求。SequenceId 項目是空的或無效。 |
The Windows Remote Shell cannot process the request. The SequenceId element is empty or invalid. |
| 0x4033C491 | Windows 遠端殼層無法處理該要求。所計算的回應封包大小超過允許的最大信封大小。 |
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 遠端殼層無法處理該要求。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 | 每個殼層例項只能有一個未執行的命令。不論命令提前終止或執行完成，在所有情況下，都必須使用 Signal 做為最後一個訊息，才能終止命令。請在接收到 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)。下列類型的內容不支援進行篩選: datetime、reference、object 以及 array。 |
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 | 不允許變更已設定 certmapping 項目的簽發者、主體或 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 無效。未預期元素: \"%2\" 的屬性: \"%1\" 或其命名空間無效。 |
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 | WinRM 用戶端無法處理該要求。用戶端不支援 Proxy 要求的驗證機制。僅支援的 Proxy 驗證機制為交涉、基本或摘要。Proxy 回報的可能驗證機制為: %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 提供者主機伺服器與 Proxy 已正確登錄。 |
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. |
| 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 傳輸不支援 Proxy。請將傳輸變更為 HTTPS 並指定有效的 Proxy 資訊，然後再試一次。 |
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 時，不支援 Proxy。請將驗證機制變更為交涉、摘要或基本，然後再試一次。 |
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 殼層執行個體已在處理連線作業。 |
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 無效。外掛程式無法同時支援殼層功能與其他功能。 |
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\" 的並行殼層最大數目 %1!d!。請關閉現有殼層，或提高此使用者的外掛程式配額。 |
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\" 允許的並行殼層上限 %1!d! 。請稍後重試該要求，或提高每個外掛程式配額的殼層上限。 |
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\" 針對每個殼層允許的並行命令上限 %1!d! 。請稍後重試該要求，或提高每個殼層配額的命令上限。 |
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 服務無法處理要求。類別 %1 不存在於 %2 命名空間中。 |
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 | 因為 XML 包含不支援的類型 (%1)，所以 WinRM 用戶端無法處理該要求。 |
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 驗證時發生下列錯誤：Kerberos 無法辨識電腦 %1。請確認電腦存在於網路上、提供的名稱拼字正確，以及用來存取電腦的 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 Encoding 元素，但該元素無效、重複、不受支援，或是太長。 |
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 殼層執行個體。 |
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 殼層執行個體。 |
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 | 自動偵測 Proxy 設定 |
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 動作 URI 無效。請參閱說明文件，取得如何建構動作 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-Management 服務的記錄與文件。如果目的地是 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 | 因為要求封包無有效的 SOAP 主體，所以 WS-Management 服務無法處理該要求。 |
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 服務無法處理該要求。 |
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-Addressing 動作 URI 和資源不相容，所以 WS-Management 服務無法處理該要求。 |
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 動作 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 EndpointReference的格式。 |
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 | 因為 XML 無效，所以 WS-Management 服務無法處理該要求。 |
The WS-Management service cannot process the request because the XML is invalid. |
| 0x80338044 | 因為 URI 包含非預期的選取器，所以 WS-Management 服務無法處理該要求。 |
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 | 因為 URI 包含太多選擇器，所以 WS-Management 服務無法處理該要求。 |
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 | 因為 XML 內容的值無效，所以 WS-Management 服務無法處理該要求。 |
The WS-Management service cannot process the request because the XML content has invalid values. |
| 0x80338057 | 因為 XML 內容的值遺失，所以 WS-Management 服務無法處理該要求。 |
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 | 因為 URI 中的 XML 片段無效，所以 WS-Management 服務無法處理該要求。 |
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 | 因為該要求包含的目標資源 URI 無效，所以 WS-Management 服務無法處理該要求。 |
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 服務無法處理「建立」要求。 |
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 服務不支援 MaxItems 設定中的值。 |
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 | 電腦上已啟用的 DHCP 介面卡清單上沒有已設定的 MAC。 |
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 所含的巢狀EndPointReferences 比 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 | 因為前一個提取要求失敗，所以列舉無效。 |
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. |
| 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 | 無法執行 Fragment-Level 操作。若指定片段方言，則也必須指定片段路徑。 |
Cannot execute the Fragment-Level operation. The fragment path cannot be missing if the fragment dialect is specified. |
| 0x80338092 | 無法執行 Fragment-Level 操作，因為片段方言的值不正確。 |
Cannot execute the Fragment-Level operation because of invalid value for the fragment dialect. |
| 0x80338093 | 無法執行 Fragment-Level 操作，因為片段路徑不正確。請檢查片段路徑字串的語法。此外，請您也檢查片段路徑字串中內容名稱的拼字與大小寫: 它們必須符合資源內容的拼字與大小寫。 |
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\" 兩者與單一事件 push 模式或 pull 模式不相容。 |
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 項目位址不正確。對於訂閱，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 | 訂閱封包的 delivery 區段中沒有 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 區段中包含不正確的 Address。 |
The subscribe packet contains invalid Address in the NotifyTo section. |
| 0x803380A3 | 訂閱封包的 delivery 區段中包含不正確的 Locale 值。 |
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 用戶端無法建立 push 訂閱。請變更主機名稱與傳輸、建立適當的防火牆例外，或執行 winrm quickconfig。 |
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 | 因為認證是搭配 'no authentication' 旗標指定，所以 WinRM 用戶端無法處理該要求。使用 'no authentication' 選項時，不應該指定使用者名稱、密碼或用戶端憑證。 |
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 用戶端無法處理要求。該要求只能指定一個驗證機制。若已設定 No Authentication 的旗標，則不應指定任何驗證機制。請變更要求，僅指定一個驗證機制或指定 'no authentication'，然後再試一次。 |
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 Server Port。請移除 SPN Server Port 或變更驗證機制，然後再次嘗試該要求。 |
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 用戶端無法處理該要求。當 transport 是 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 | 無法執行 Fragment-Level 操作，因為片段路徑包含 \"\" (空白或空字串) 或 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 用戶端無法處理要求。其中一個需要的參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 或零，但列舉模式為 Object 或 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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 用戶端無法處理該要求。WinrsPush 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 用戶端無法處理此要求。事件來源電腦並未加入網域。若要將發送訂閱工作階段安裝到事件來源，該來源必須連線到網域。若要修正此問題，請將事件來源電腦加入網域，或使用提取做為訂閱的傳遞模式。 |
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 用戶端無法處理此要求。用戶電腦未加入網域。若要將發送訂閱工作階段安裝到事件來源，該用戶電腦必須連線到網域若要修正此問題，請將用戶電腦加入網域，或使用提取做為訂閱的傳遞模式。 |
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 | WiRM 用戶端無法處理該要求。未指定驗證機制時，只允許使用者名稱與密碼認證。若想要使用不同類型的認證，則需要指定驗證機制。請指定驗證機制或正確的認證，然後再次嘗試該要求。 |
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 殼層用戶端無法處理該要求。其中一個傳送給 WSManCreateShell 函數的環境變數名稱是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 殼層用戶端無法處理該要求。其中一個傳送給 WSManCreateShell 函數的串流識別碼名稱是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 殼層用戶端無法處理該要求。傳送給 WSMan 殼層函數的殼層控制碼無效。只有在順利完成 WSManCreateShell 函數時，殼層控制碼才有效。請變更要求以包含有效的殼層控制碼，然後再試一次。 |
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 殼層用戶端無法處理該要求。傳送給 WSMan 殼層函數的命令控制碼無效。只有在順利完成 WSManRunShellCommand 函數時，命令控制碼才有效。請變更要求以包含有效的殼層控制碼，然後再試一次。 |
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 殼層用戶端無法處理該要求。其中一個傳送給 WSManRunShellCommand 函數的引數值是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 | 於正在關閉的命令上嘗試操作。若另一個執行緒也正在釋出使用的命令控制代碼，就會發生此問題。 |
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 殼層用戶端無法處理該要求。傳送給 WSManSendShellInput 函數之 WSMAN_STREAM_ELEMENT 內的串流識別碼索引無效。串流識別碼索引應該是傳送給 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 | 因為指定的 CustomRemoteShell URI 無效，所以 WinRM 用戶端無法處理該要求。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 | 因為指定的 CustomRemoteShell URI 無效，所以 WinRM 用戶端無法處理該要求。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 | 因為指定給 CustomRemoteShell 表格項目的處理程序路徑無效，所以 WinRM 用戶端無法處理該要求。處理程序路徑應該是絕對路徑，而且應該指向現有可執行檔。 |
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 | 因為內含於 DeliverTo 的 WS-Policy 太複雜或使用的是 WinRM 服務無法辨識的屬性，所以 WinRM 服務無法處理該要求。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 | 因為內含於 DeliverTo 的 WS-Policy 未含 WinRM 服務可以遵守的任何選項，所以 WinRM 服務無法處理該要求。WinRM 服務支援下列設定檔: 透過 HTTP 的 Negotiate 或 Kerberos、透過 HTTPS 的 Negotiate 或 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 | 因為 DeliverTo 中的 wsman:ConnectionRetry 項目無效，所以 WinRM 服務無法處理該要求。 |
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 | 因為 WSMAN_ALLOWED_PUBLISHERS 引數中的 type 欄位無效，所以 WinRM 用戶端無法處理該要求。收集器起始訂閱必須使用 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 設定是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 錯誤封包，所以 WinRM 用戶端無法處理該要求。 |
The WinRM client cannot process the request because it received an HTML error packet. |
| 0x80338174 | WinRS 用戶端無法處理該要求。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 | WinRS 用戶端無法處理該要求。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 用戶端無法處理該要求。您必須等待 WSManRunShellCommand API 呼叫完成，才能呼叫 WSManCloseShellOperationEx 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 呼叫指定的旗標無效。streamData 參數應使用 WSMAN_DATA_TYPE_BINARY 類型以二進位格式來指定。請變更無效的參數，然後再次嘗試該呼叫。 |
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. |
| 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 用戶端無法處理該要求。UI 語言選項無效。請變更 UI 語言，然後再試一次。 |
The WinRM client cannot process the request. The UI language option is invalid.Change the UI language and try again. |
| 0x80338196 | WinRS 用戶端無法處理該要求。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 | WinRS 用戶端無法處理該要求。語言代碼參數無效。語言代碼參數應為 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 用戶端無法處理該要求。指定應使用的 Proxy 驗證機制之旗標不正確。請移除或變更無效的旗標，然後再次嘗試該要求。 |
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 用戶端無法處理該要求。Proxy 驗證的認證未正確指定。使用者名稱與密碼認證皆必須有效。請指定正確的認證，然後再次嘗試該要求。 |
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 用戶端無法處理該要求。Proxy 存取類型不正確。請使用其中一個 Proxy 存取類型旗標; 這些旗標無法予以結合。請變更無效的 Proxy 存取類型，然後重試該要求。 |
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 用戶端無法處理該要求。直接連線伺服器選項無法與非空白 Proxy 驗證資料搭配使用。請變更無效的 Proxy 存取類型或使用空白的 Proxy 驗證資料，然後再次嘗試該要求。 |
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 | WinRS 用戶端無法處理該要求。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 傳輸時，設定 Proxy 資訊無效。移除 Proxy 資訊或變更傳輸，然後再次嘗試該要求。 |
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 時，設定 Proxy 資訊無效。移除 Proxy 資訊或變更驗證機制，然後再次嘗試該要求。 |
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 時，設定 Proxy 資訊無效。移除 Proxy 資訊或變更驗證機制，然後再次嘗試該要求。 |
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 用戶端無法處理該要求。要求只能指定一個 Proxy 的驗證機制。變更要求並僅指定一個驗證機制，然後再次嘗試該要求。 |
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 服務收到重新導向用戶端的 HTTP 重新導向訊息，但位置 URL 不正確。 |
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-Management 服務的記錄與文件。如果目的地是 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 用戶端無法處理要求。自訂遠端殼層已過時且無法再使用。 |
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 | 因為無法變更這個資源 URI 的安全性，所以 WinRM 服務無法處理該要求。 |
The WinRM service cannot process the request because the security for this resource URI cannot be changed. |
| 0x803381C0 | WinRM 服務無法處理該要求。列舉要求需要有可指定殼層識別碼的選取器篩選器。 |
The WinRM service cannot process the request. The enumeration request expects a selector based filter to specify the shell identifier. |
| 0x803381C1 | WinRM 服務無法處理該要求。不支援殼層命令的端點資源列舉。 |
The WinRM service cannot process the request. The enumeration of end point resources for shell commands is not supported. |
| 0x803381C2 | WinRM 殼層用戶端無法處理要求，因為殼層名稱的長度已超過 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 殼層執行個體目前已中斷連線。 |
The WinRM service cannot process the request because the WinRS shell instance is currently disconnected. |
| 0x803381C5 | WinRM 服務無法處理要求。WinRS 殼層執行個體不支援中斷連線及重新連線作業，因為它是由舊版 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 殼層執行個體已連線至不同的用戶端。 |
The WinRM service cannot process the request because the WinRS shell instance is connected to a different client. |
| 0x803381C7 | WinRM 殼層用戶端無法處理該要求。WSManDisconnectShell 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 殼層用戶端無法處理該要求。命令目前正在終止或已終止。 |
The WinRM Shell client cannot process the request. The command is currently terminating or was terminated. |
| 0x803381CD | WinRM 服務無法處理該要求。WinRS 殼層執行個體目前已連線至不同的用戶端。 |
The WinRM service cannot process the request. The WinRS shell instance is currently connected to a different client. |
| 0x803381CE | WinRM 用戶端在中斷連線作業期間與 WinRM 服務通訊時發生錯誤。已中斷殼層的連線，而且串流可能已突然暫停。 |
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 殼層執行個體上執行中斷連線作業。 |
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 殼層執行個體上執行重新連線作業。 |
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 函數所需的其中一個參數是 Null 或零。請變更要求以包含遺失的參數，然後再試一次。 |
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 殼層命令執行個體上執行重新連線作業。 |
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 服務無法處理該要求，因為用戶端所指定的命令識別碼不是有效的 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 服務無法處理要求，因為用戶端指定的殼層識別碼不是有效的 GUID。請提供有效的識別碼，然後再試一次。 |
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 服務無法處理該要求。命令已具有用戶端所指定的命令識別碼。 |
The WinRM service cannot process the request. A command already exists with the command ID specified by the client. |
| 0x803381D7 | WinRM 服務無法處理該要求。資源已具有用戶端所指定的殼層識別碼。 |
The WinRM service cannot process the request. A resource already exists with the shell ID specified by the client. |
| 0x803381D8 | WinRM 用戶端無法處理該要求。無法在已中斷連線的 WinRS 殼層命令執行個體上執行中斷連線作業。 |
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 用戶端無法處理該要求，因為命令控制碼未與提供的殼層控制碼相關聯。 |
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 | 建立新殼層失敗。請確定已正確設定 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 | 因為 XML 執行個體與伺服器所提供的類別結構描述不符，所以 WinRM 用戶端無法處理要求。 |
The WinRM client cannot process the request because the XML instance does not match the class schema provided by the server. |
| 0x803381E2 | 因為 XML 包含不支援的類型，所以 WinRM 用戶端無法處理要求。請確認 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 服務無法處理要求。此使用者已超過此外掛程式允許的並行殼層數目上限。請至少關閉一個開啟的殼層，或提高此使用者的外掛程式配額。 |
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 服務無法處理要求。已超過此外掛程式允許的並行殼層數目上限。請稍後再次嘗試此要求，或提高每個外掛程式配額的殼層上限。 |
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 服務無法處理要求。已超過每個殼層的並行命令數目上限。請稍後重試該要求，或提高每個殼層配額的命令上限。 |
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 | 因為 MI_OperationOptions 同時包含資源 URI 與資源 URI 首碼，所以 WinRM 用戶端無法處理要求。僅指定這兩個選項的其中一個，然後再試一次。 |
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 | 因為同時指定 keysOnly 與 WSMAN_ENUMERATIONMODE_OBJECTONLY，所以 WinRM 用戶端無法處理要求。這兩個設定不相容。請移除 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 | 訂閱封包在在傳遞區段中包含無效的 Encoding 值。 |
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 service 服務是以本機系統帳戶執行，且已啟用 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 | 正在使用 ResourceUri %1 和 ShellId %2 建立 WSMan 殼層 |
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 提供者主機伺服器與 Proxy 已正確登錄。錯誤碼為 %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 於伺服器上建立 WSMan 殼層: %1 |
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 而使用下一部 Proxy 重新傳送要求 |
Re-sending the request as a result of ERROR_WINHTTP_CANNOT_CONNECT, using next proxy |
| 0xB0000088 | 由於 ERROR_WINHTTP_NAME_NOT_RESOLVED 而使用下一部 Proxy 重新傳送要求 |
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 | 用戶端不支援 Proxy 要求的驗證機制。支援的 Proxy 驗證機制只有交涉、基本或摘要。%nProxy 回報的可能驗證機制為: %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 | 使用 Proxy 驗證使用者失敗。認證無法運作。 |
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 殼層執行個體 %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 | 外掛程式使用參數 %1 呼叫 WSManPluginGetConfiguration，而且取得傳回值 %2。 |
The plugin called WSManPluginGetConfiguration with the parameter %1 and obtained a return value of %2. |
| 0xB0000135 | 外掛程式使用參數 %1 呼叫 WSManPluginReportCompletion，而且取得傳回值 %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 | 正在中斷下列識別碼的殼層連線: %1 |
Disconnecting shell with Id : %1 |
| 0xB0000146 | 中斷殼層連線失敗，錯誤碼 %1 |
Disconnecting shell failed, error code %1 |
| 0xB0000147 | 正在重新連線下列識別碼的殼層: %1 |
Reconnecting shell with Id : %1 |
| 0xB0000148 | 重新連線殼層失敗，錯誤碼 %1 |
Reconnecting shell failed, error code %1 |
| 0xB0000149 | 正在連線下列識別碼的殼層: %1 |
Connecting shell with Id : %1 |
| 0xB000014A | 連線殼層失敗，錯誤碼 %1 |
Connecting shell failed, error code %1 |
| 0xB000014B | 正在重新連線下列識別碼的殼層命令: %1 |
Reconnecting shell command with Id : %1 |
| 0xB000014C | 重新連線殼層命令失敗，錯誤碼 %1 |
Reconnecting shell command failed, error code %1 |
| 0xB000014D | 正在連線下列識別碼的殼層命令: %1 |
Connecting shell command with Id : %1 |
| 0xB000014E | 連線殼層命令失敗，錯誤碼 %1 |
Connecting shell command failed, error code %1 |
| 0xB0000201 | Proxy 自動偵測完成。%nProxy 清單: %1 %n略過清單: %2 |
Proxy AutoDetect done.%nProxy list: %1 %nBypass list: %2 |
| 0xB0000202 | 設定 Proxy 資訊 %n Proxy 清單: %1 %n 略過清單: %2 |
Setting proxy info %n Proxy list: %1 %n Bypass list: %2 |
| 0xB0000303 | SOAP [用戶端傳送索引 %1 的 %2 個總區塊 (%3 個位元組)] %4 |
SOAP [client sending index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000304 | SOAP [接聽程式接收索引 %1 的 %2 個總區塊 (%3 個位元組)] %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至少 %4 毫秒內不會核准使用者 %3 的下一個要求。 |
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 [用戶端接收索引 %1 的 %2 個總區塊 (%3 個位元組)] %4 |
SOAP [client receiving index %1 of %2 total chunks (%3 bytes)] %4 |
| 0xB0000403 | SOAP [接聽程式傳送索引 %1 的 %2 個總區塊 (%3 個位元組)] %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 殼層中斷連線，所以 WSMan 作業 %1 已暫停。 |
WSMan operation %1 got suspended because of WSMan Shell disconnection. |
| 0xB000041E | 因為 WSMan 殼層重新連線，所以正在繼續 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 | 使用 %2 驗證成功驗證使用者 %1 |
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. |