| 0x1 | 尚未實作函數或功能。 |
The function or feature is not yet implemented. |
| 0x2 | WS_TYPE 值 '%1' 需要類型描述。 |
A type description is required for WS_TYPE value '%1'. |
| 0x3 | 未指定 WS_TYPE 值 '%1' 的類型描述。 |
A type description may not be specified for WS_TYPE value '%1'. |
| 0x4 | WS_TYPE '%1' 不能與指定的 WS_FIELD_MAPPING 值一起使用。 |
The WS_TYPE '%1' may not be used with the specified WS_FIELD_MAPPING value. |
| 0x5 | WS_TYPE '%1' 不能當做選擇性欄位。 |
The WS_TYPE '%1' may not be used as an optional field. |
| 0x6 | WS_TYPE '%1' 不支援指定 WS_DEFAULT_VALUE。 |
The WS_TYPE '%1' does not support specifying a WS_DEFAULT_VALUE. |
| 0x7 | WS_TYPE '%1' 只能當做結構的欄位。 |
The WS_TYPE '%1' may only be used as a field of a structure. |
| 0x8 | WS_TYPE '%1' 不能當做 nillable 值。 |
The WS_TYPE '%1' can not be used as a nillable value. |
| 0x9 | WS_TYPE '%1' 不能與 WS_FIELD_POINTER 一起使用。 |
The WS_TYPE '%1' may not be used with WS_FIELD_POINTER. |
| 0xA | WS_TYPE '%1' 值無效。 |
The WS_TYPE '%1' value was not valid. |
| 0xB | 指定的類型不支援一或多個指定的 WS_FIELD_OPTIONS '%1'。 |
One or more of the specified WS_FIELD_OPTIONS '%1' was not supported for the given type. |
| 0xC | 一或多個指定的 WS_FIELD_OPTIONS '%1' 無效。 |
One or more of the specified WS_FIELD_OPTIONS '%1' was invalid. |
| 0xD | 使用指定的 WS_FIELD_OPTIONS '%1' 時，不能指定預設值。 |
A default value may not be specified when using the specified WS_FIELD_OPTIONS '%1'. |
| 0xE | 使用指定的 WS_FIELD_MAPPING '%1' 時，不能指定預設值。 |
A default value may not be specified when using the specified WS_FIELD_MAPPING '%1'. |
| 0xF | 欄位位移/大小已超出結構的範圍。 |
The field offset/size was outside of the containing structure. |
| 0x10 | WS_TYPE '%1' 可能未指定類型描述。 |
A type description may not be specified for the WS_TYPE '%1'. |
| 0x11 | 無法辨識或支援這種繫結類型。 |
The binding type was not recognized or supported. |
| 0x12 | 無法辨識或支援內容識別碼 '%1'。 |
The property ID '%1' was not recognized or supported. |
| 0x13 | 內容識別碼 '%1' 在內容清單中指定一次以上。 |
The property ID '%1' was specified more than once in the list of properties. |
| 0x14 | 因為正在傳送訊息，所以無法關閉輸出的通道。 |
The channel could not be shut down for output because a message is being sent. |
| 0x15 | 因為通道已經關閉，所以無法完成操作。 |
The operation could not be completed because the channel has been shut down. |
| 0x16 | 因為通道正在關閉工作階段，所以無法完成操作。 |
The operation could not be completed because the channel is in the process of shutting down the session. |
| 0x17 | 因為通道處於錯誤狀態中，所以操作無法完成。 |
The operation could not be completed because the channel is in a faulted state. |
| 0x18 | 因為中繼資料物件處於錯誤狀態中，所以操作無法完成。 |
The operation could not be completed because the metadata object is in a faulted state. |
| 0x19 | 因為原則物件處於錯誤狀態中，所以操作無法完成。 |
The operation could not be completed because the policy object is in a faulted state. |
| 0x1A | 因為中繼資料物件處於已解決狀態中，所以操作無法完成。 |
The operation could not be completed because the metadata object is in the resolved state. |
| 0x1B | 位址版本 '%1' 無效。 |
The addressing version '%1' was invalid. |
| 0x1C | 訊息 '%1' 的位址版本與通道 '%2' 不相符。 |
The addressing version of the message '%1' does not match that of the channel '%2'. |
| 0x1D | 訊息 '%1' 的信封版本與通道 '%2' 不相符。 |
The envelope version of the message '%1' does not match that of the channel '%2'. |
| 0x1E | 目前的訊息狀態 '%1' 不適用於要求的操作。 |
The current message state '%1' was not appropriate for the requested operation. |
| 0x1F | 指定的重複標頭選項 '%1' 無效。 |
The specified repeating header option '%1' was invalid. |
| 0x20 | 編寫時，訊息中已存在含空白命名空間的標頭 '%1'。 |
The header '%1' with an empty namespace was present in the message when it was written. |
| 0x21 | 訊息包含一個沒有命名空間的標頭 '%1'。 |
The message contained a header '%1' that did not have a namespace. |
| 0x22 | 本文元素 '%1' 沒有命名空間。 |
The body element '%1' did not have a namespace. |
| 0x23 | 自訂標頭 '%1' 沒有命名空間。 |
The custom header '%1' did not have a namespace. |
| 0x24 | 只預期一個標頭，但訊息卻存在兩個或多個標頭。 |
There were two or more headers present in the message when only one was expected. |
| 0x25 | 目前的通道狀態 '%1' 不適用於要求的操作。 |
The current channel state '%1' was not appropriate for the requested operation. |
| 0x26 | 操作需要伺服器通道。 |
The operation requires a server channel. |
| 0x27 | 目前的接聽程式狀態 '%1' 不適用於要求的操作。 |
The current listener state '%1' was not appropriate for the requested operation. |
| 0x28 | 指定的十進位值無效。 |
The specified decimal value was not valid. |
| 0x29 | URL 比對選項 '%1' 無效。 |
The URL matching options '%1' were invalid. |
| 0x2A | 收到的傳輸 URL '%1' 與端點 URL '%2' 不相符。 |
The received transport URL '%1' did not match the endpoint URL '%2'. |
| 0x2B | 收到的收件者標頭 '%1' 與端點 URL '%2' 不相符。 |
The received To header '%1' did not match the endpoint URL '%2'. |
| 0x2C | URL 配置與端點的 URL 配置不相符。 |
The URL scheme did not match the URL scheme of the endpoint. |
| 0x2D | URL 中的連接埠號碼與端點的連接埠號碼不相符。 |
The port number in the URL did not match the port number of the endpoint. |
| 0x2E | URL 的主機部分與端點的主機不相符。 |
The host portion of the URL did not match the host of the endpoint. |
| 0x2F | URL 的路徑部分與端點的路徑不相符。 |
The path portion of the URL did not match the path of the endpoint. |
| 0x30 | URL 包含一個查詢字串，不過端點並不需要查詢字串。 |
The URL contained a query string but the endpoint did not expect a query string. |
| 0x31 | URL 路徑 '%1' 無效。 |
The URL path '%1' is not valid. |
| 0x32 | 無法取得電腦名稱。 |
Unable to get computer name. |
| 0x33 | URL '%1' 的配置不適用於這個通道。預期為配置 '%2'。 |
The URL '%1' has an incorrect scheme for this channel. The scheme '%2' was expected. |
| 0x34 | 目前的接聽程式狀態不適用於要求的操作。 |
The current listener state was not appropriate for the requested operation. |
| 0x35 | 因為通道已經中止，所以無法完成操作。 |
The operation could not be completed because the channel has been aborted. |
| 0x36 | 因為接聽程式已經中止，所以無法完成操作。 |
The operation could not be completed because the listener has been aborted. |
| 0x37 | 因為接聽程式正在結束，所以無法完成操作。 |
The operation could not be completed because the listener is closing. |
| 0x38 | 因為物件的目前狀態所致，所以無法完成操作。 |
The operation could not be completed due to the state of the object. |
| 0x39 | 框架格式中的整數值超過最大值。 |
An integer value in the framing format exceeded the maximum value. |
| 0x3A | 透過字串的框架長度超過配額。 |
The length of the framing via string exceeded the quota. |
| 0x3B | 框架錯誤字串的長度超過配額。 |
The length of the framing fault string exceeded the quota. |
| 0x3C | 內容類型字串的長度超過配額。 |
The length of the content type string exceeded the quota. |
| 0x3D | 緩衝的通訊協定記錄長度超過配額。 |
The length of the buffered protocol record exceeded the quota. |
| 0x3E | 內容類型 '%1' 的格式不正確。 |
The content type '%1' was not correctly formed. |
| 0x3F | 相同的參數在內容類型中出現一次以上。 |
The same parameter appeared more than once in the content type. |
| 0x40 | 遠端端點無法啟動。 |
The remote endpoint was unable to start. |
| 0x41 | 已經從端點收到無法辨識的錯誤，值為 '%1'。 |
An unrecognized fault with the value '%1' was received from the endpoint. |
| 0x42 | 已經收到意外的框架記錄。預期的記錄是 '%2'，但是收到的記錄是 '%1'。 |
An unexpected framing record was received. Record '%2' was expected, but record '%1' was received. |
| 0x43 | 已經收到框架記錄類型 '%1'，但是不適用於這個框架格式版本。 |
The framing record type '%1' was received but is not valid for this framing format version. |
| 0x44 | 內容類型不符合預期值。 |
The content type did not match the expected value. |
| 0x45 | 內容類型 '%1/%2' 不符合預期值 '%3/%4'。 |
The content type '%1/%2' did not match the expected value '%3/%4'. |
| 0x46 | 不支援指定的內容類型。 |
The specified content type was not supported. |
| 0x47 | 無法將訊息發送至服務。 |
The message could not be dispatched to the service. |
| 0x48 | 無法辨識指定的框架模式。 |
The specified mode of framing was not recognized. |
| 0x49 | 讀取框架資訊時，提早到達資料流的結尾。 |
There was an premature end of stream while reading framing information. |
| 0x4A | 不支援此框架模式。 |
The framing mode was not supported. |
| 0x4B | 訊息大小超過伺服器的配額。 |
The size of the message exceeded the quota of the server. |
| 0x4C | 目前寫入的訊息大小超過 %1 位元組的配額。 |
The size of the message being written exceeds the quota of %1 bytes. |
| 0x4D | 目前讀取的訊息大小超過 %1 位元組的配額。 |
The size of the message being read exceeds the quota of %1 bytes. |
| 0x4E | 訊息中處理的標頭數目超過配額 ('%1')。 |
The number of headers processed in the message exceeds the quota ('%1'). |
| 0x4F | 應該要有訊息，但是通道上已沒有訊息。 |
A message was expected but no more messages were available on the channel. |
| 0x50 | 需要的標頭本機名稱為 '%1'，而且命名空間為 '%2'，但是在訊息中找不到。 |
A header with local name '%1' and namespace '%2' was required, but was not present in the message. |
| 0x51 | 需要的錯誤詳細資料元素本機名稱為 '%1'，而且命名空間為 '%2'，但是在錯誤中找不到。 |
A fault detail element with local name '%1' and namespace '%2' was required, but was not present in the fault. |
| 0x52 | 需要了解的標頭本機名稱為 '%1'，而且命名空間為 '%2'，但是無法了解。 |
A header with local name '%1' and namespace '%2' was required to be understood, but was not understood. |
| 0x53 | 訊息標頭之必須了解的屬性值不是 '0' 或 '1'。 |
The value of the must understand attribute of the message header was not '0' or '1'. |
| 0x54 | 由於訊息並未包含動作標頭，所以在收到含傳輸地址的回覆時，不能指定多個訊息描述。 |
Multiple message descriptions can not be specified when receiving a reply with transport addressing, because the message does not contain an action header. |
| 0x55 | 應該要有動作標頭，但是在訊息中找不到。 |
The action header was expected but was not present in the message. |
| 0x56 | 無法辨識動作 '%1'。 |
The action '%1' was not recognized. |
| 0x57 | 傳送操作正在進行中。 |
A send operation is in progress. |
| 0x58 | 接收操作正在進行中。 |
A receive operation is in progress. |
| 0x59 | 接受操作正在進行中。 |
An accept operation is in progress. |
| 0x5A | 指定的編碼需要工作階段，因此無效。 |
The specified encoding is not valid because it requires a session. |
| 0x5B | 通道類型 '%1' 無效或者不可以用於特定的通道繫結。 |
The channel type '%1' was not valid or can not be used with the specific channel binding. |
| 0x5C | 自訂通道需要自訂通道回呼，但是未指定。 |
The custom channel callbacks are required for a custom channel but were not specified. |
| 0x5D | 自訂接聽程式需要自訂通道回呼，但是未指定。 |
The custom channel callbacks are required for a custom listener but were not specified. |
| 0x5E | 必須使用 WsCreateChannelForListener 來建立通道類型 '%1'。 |
The channel type '%1' must be created using WsCreateChannelForListener. |
| 0x5F | 通道傳輸模式對這個函數而言不正確。 |
The channel transfer mode is not correct for this function. |
| 0x60 | HTTP 要求標頭 '%1' 無效。 |
The HTTP request header '%1' was invalid. |
| 0x61 | 字元 '%1' 不是有效的 HTTP 標頭字元。 |
The character '%1' is not a valid HTTP header character. |
| 0x62 | HTTP 標頭對應是 NULL。 |
The HTTP header mapping was NULL. |
| 0x63 | HTTP 狀態文字太長。 |
The HTTP status text was too long. |
| 0x64 | HTTP 標頭對應 '%1' 指定一次以上。 |
The HTTP header mapping '%1' was specified more than once. |
| 0x65 | HTTP 標頭對應選項 '%1' 無效。 |
The HTTP header mapping option '%1' was invalid. |
| 0x66 | HTTP 回應對應選項 '%1' 無效。 |
The HTTP response mapping option '%1' was invalid. |
| 0x67 | HTTP 要求對應選項 '%1' 無效。 |
The HTTP request mapping option '%1' was invalid. |
| 0x68 | 要求的資源暫時位於不同 URI 之下。 |
The requested resource resides temporarily under a different URI. |
| 0x69 | 服務暫時超載。 |
The service is temporarily overloaded. |
| 0x6A | 找不到要求的資源。 |
The requested resource was not found. |
| 0x6B | 可在一或多個位置取得要求的資源。 |
The requested resource is available at one or more locations. |
| 0x6C | 伺服器不再提供要求的資源，因此不知道任何轉寄地址。 |
The requested resource is no longer available at the server, and no forwarding address is known. |
| 0x6D | 要求的資源已經移動。 |
The requested resource has moved. |
| 0x6E | 要求的資源需要使用者驗證。 |
The requested resource requires user authentication. |
| 0x6F | 伺服器了解要求，但是無法完成。 |
The server understood the request, but cannot fulfill it. |
| 0x70 | 需要 Proxy 驗證。 |
Proxy authentication is required. |
| 0x71 | 伺服器無法處理要求。 |
The server was unable to process the request. |
| 0x72 | 要求等候閘道時逾時。 |
The request timed out waiting for a gateway. |
| 0x73 | 伺服器等候要求時逾時。 |
The server timed out waiting for the request. |
| 0x74 | HTTP 要求格式不正確。 |
The HTTP request was incorrectly formed. |
| 0x75 | HTTP 伺服器不支援要求中使用的方法。 |
The HTTP server did not support the method used in the request. |
| 0x76 | HTTP 伺服器找不到可接受的回應格式。 |
The HTTP server did not find an acceptable response format. |
| 0x77 | 伺服器不支援這種格式的 HTTP 要求。 |
The format of the HTTP request was not supported by the server. |
| 0x78 | 無法辨識 HTTP 伺服器的回應。 |
The response from the HTTP server was not recognized. |
| 0x79 | 伺服器已經傳回 HTTP 狀態碼 '%1'。 |
The server returned HTTP status code '%1'. |
| 0x7A | 伺服器已經傳回包含文字 '%2' 的 HTTP 狀態碼 '%1'。 |
The server returned HTTP status code '%1' with text '%2'. |
| 0x7B | 用戶端不支援伺服器所需的任何 HTTP 驗證配置。 |
The client did not support any of the HTTP authentication schemes required by the server. |
| 0x7C | HTTP 回應指出有錯誤，但是訊息並未包含錯誤。 |
The HTTP response indicated an error, but the message did not contain a fault. |
| 0x7D | 要求中遺漏 SOAPAction HTTP 標頭。 |
The SOAPAction HTTP header was missing from the request. |
| 0x7E | SOAPAction HTTP 標頭在要求中出現一次以上。 |
The SOAPAction HTTP header appeared more than once in the request. |
| 0x7F | SOAPAction HTTP 標頭的格式不正確。 |
The SOAPAction HTTP header was not correctly formatted. |
| 0x80 | SOAPAction HTTP 標頭不符合動作標頭。 |
The SOAPAction HTTP header did not match the Action header. |
| 0x81 | 與 '%1' 的端點通訊時發生錯誤。 |
There was an error communicating with the endpoint at '%1'. |
| 0x82 | 主機名稱 '%1' 在清單中出現一次以上。 |
The host name '%1' appeared more than once in the list. |
| 0x83 | 信封版本 '%1' 無效。 |
The envelope version '%1' was not valid. |
| 0x84 | 命名空間 '%3' 的元素 '%2' 不應該有屬性 '%1'。 |
The attribute '%1' was not expected on the element '%2' from namespace '%3'. |
| 0x85 | 這個位址版本不支援這種位址標頭。 |
The addressing header is not supported for the version of addressing. |
| 0x86 | HTTP 動詞不是 'POST'。 |
The HTTP verb was not 'POST'. |
| 0x87 | 指定的 URL 是 NULL。 |
The URL specified is NULL. |
| 0x88 | 配置 '%1' 無效。 |
The scheme '%1' is not valid. |
| 0x89 | 配置識別碼 '%1' 無效。 |
The scheme id '%1' is not valid. |
| 0x8A | 連接埠 '%1' 無效。 |
The port '%1' is not valid. |
| 0x8B | 字元 '%1' 不是有效的百分比編碼序列。 |
The characters '%1' are not a valid percent-encoded sequence. |
| 0x8C | 應該要有字元 '%1'。 |
The characters '%1' were expected. |
| 0x8D | 字元 '%1' 不是有效的主機名稱。 |
The characters '%1' are not a valid host name. |
| 0x8E | 字元 '%1' 不是有效的連接埠。 |
The characters '%1' are not a valid port. |
| 0x8F | 字元 '%1' 並非預期的。 |
The characters '%1' are not expected. |
| 0x90 | URL '%1' 無效。 |
The URL '%1' is not valid. |
| 0x91 | 指定的接收選項 '%1' 無效。 |
The specified receive option '%1' is not valid. |
| 0x92 | 指定的編碼 '%1' 無效。 |
The specified encoding '%1' is not valid. |
| 0x93 | 訊息層級安全性不可以用於信封版本 'none'。 |
Message-level security may not be used with envelope version 'none'. |
| 0x94 | 原始編碼不可以用於這個通道。 |
The raw encoding can not be used with this channel. |
| 0x95 | 原始編碼需要對應狀態碼與狀態文字。 |
The raw encoding requires that the status code and status text be mapped. |
| 0x96 | 信封版本 'none' 不可以用於這個通道。 |
Envelope version 'none' may be not be used with this channel. |
| 0x97 | 信封版本 'none' 需要傳輸地址。 |
Envelope version 'none' requires transport addressing. |
| 0x98 | 編碼 '%1' 不可以用於信封版本 '%2'。 |
The encoding '%1' can not be used with the envelope version '%2'. |
| 0x99 | HTTP 動詞無效。 |
The HTTP verb was invalid. |
| 0x9A | HTTP 標頭值的長度超過配額。 |
The length of the HTTP header value exceeded the quota. |
| 0x9B | 遺漏 HTTP 標頭值。 |
The HTTP header value was missing. |
| 0x9C | 已經多次嘗試新增 HTTP 標頭。 |
An attempt was made to add the HTTP header more than once. |
| 0x9D | HTTP 標頭數目超過配額。 |
The number of HTTP headers exceeded the quota. |
| 0x9E | 指定的編碼值無效。 |
The specified encoding value is not valid. |
| 0x9F | HTTP 標頭無效。 |
The HTTP header was invalid. |
| 0xA0 | 系統無法產生唯一識別碼。 |
The system was unable to generate a unique ID. |
| 0xA1 | 回覆訊息的識別碼值關係不符合要求的訊息識別碼。 |
The relates to ID value of the reply message did not match the request message ID. |
| 0xA2 | 不支援要求的框架升級。 |
The requested framing upgrade was not supported. |
| 0xA3 | 用戶端正在要求未登錄到伺服器的框架升級 '%1'。 |
The client is requesting the framing upgrade '%1' which is not registered on the server. |
| 0xA4 | 用戶端正在要求框架升級 '%1'，但是伺服器預期的是 '%2'。 |
The client is requesting the framing upgrade '%1', but the server expects '%2'. |
| 0xA5 | 用戶端已經完成通訊協定資料流，但是未與所有登錄的框架升級進行交涉。預期的伺服器框架升級名稱: '%1'。 |
The client completed the protocol stream without negotiating all registered framing upgrades. Expected server framing upgrade name: '%1'. |
| 0xA6 | 框架升級 '%1' 資料區塊不足。 |
The framing upgrade '%1' data block is not sufficient. |
| 0xA7 | 處理資料時使用的標頭與尾端總大小溢位。 |
The total size of the header and trailer used for processing data overflows. |
| 0xA8 | 要處理的傳送資料大小大於傳送資料大小上限。 |
The size of the send data to be processed is larger than the maximum send data size. |
| 0xA9 | 框架升級通訊協定狀態無效。 |
The framing upgrade protocol is in an invalid state. |
| 0xAA | 指定的 URL 包含片段。 |
The specified URL contained a fragment. |
| 0xAB | 應該是通道的結尾，但找到的是訊息的開頭。 |
End of channel was expected, but the start of a message was found instead. |
| 0xAC | 訊息已經定址。 |
The message has already been addressed. |
| 0xAD | 指定的 URL 包含查詢字串。 |
The specified URL contained a query string. |
| 0xAE | 工作階段字典資料格式不正確。 |
The session dictionary data was not correctly formed. |
| 0xAF | 工作階段字典字串 '%1' 指定給工作階段一次以上。 |
The session dictionary string '%1' was specified more than once for the session. |
| 0xB0 | 工作階段字典的大小超過配額。 |
The size of the session dictionary exceeded the quota. |
| 0xB1 | 無法建立事件物件。 |
The event object was not able to be created. |
| 0xB2 | 無法設定控制代碼的檔案完成通知模式。 |
The file completion notification mode for the handle could not be set. |
| 0xB3 | 無法初始化通訊端程式庫。 |
The socket library was not able to be initialized. |
| 0xB4 | 停用 HTTP 要求的 Cookie 時發生錯誤。 |
There was an error disabling cookies on the HTTP request. |
| 0xB5 | 形成 HTTP 要求時發生錯誤。 |
There was an error forming the HTTP request. |
| 0xB6 | 設定 HTTP 要求的逾時時發生錯誤。 |
There was an error setting the timeout for the HTTP request. |
| 0xB7 | 傳送 HTTP 要求時發生錯誤。 |
There was an error sending the HTTP request. |
| 0xB8 | 接收 HTTP 回覆時發生錯誤。 |
There was an error receiving the HTTP reply. |
| 0xB9 | 剖析 HTTP 回覆時發生錯誤。 |
There was an error parsing the HTTP reply. |
| 0xBA | HTTP 回覆遺漏必要的標頭。 |
The HTTP reply was missing a required header. |
| 0xBB | 建立 TCP 通訊端時發生錯誤。 |
There was an error creating the TCP socket. |
| 0xBC | 將 TCP 通訊端繫結至位址時發生錯誤。 |
There was an error binding the TCP socket to an address. |
| 0xBD | 設定專用位址通訊端選項時發生錯誤。 |
There was an error setting the exclusive address socket option. |
| 0xBE | 設定僅 IPv6 通訊端選項時發生錯誤。 |
There was an error setting the IPv6 only socket option. |
| 0xBF | 從 TCP 通訊端接收時發生錯誤。 |
There was an error receiving from the TCP socket. |
| 0xC0 | 在 TCP 通訊端傳送資料時發生錯誤。 |
There was an error sending data on the TCP socket. |
| 0xC1 | 結束 TCP 通訊端時發生錯誤。 |
There was an error closing the TCP socket. |
| 0xC2 | 關閉 TCP 通訊端的輸出時發生錯誤。 |
There was an error shutting down output for the TCP socket. |
| 0xC3 | 連線 TCP 通訊端時發生錯誤。 |
There was an error connecting the TCP socket. |
| 0xC4 | 繫結 TCP 接聽通訊端時發生錯誤。 |
There was an error binding the TCP listen socket. |
| 0xC5 | 取得接聽通訊端的接受功能時發生錯誤。 |
There was an error getting the accept function for the listen socket. |
| 0xC6 | 取得通訊端的連線功能時發生錯誤。 |
There was an error getting the connect function for the socket. |
| 0xC7 | 指定的 IP 位址 '%1' 不符合 IP 版本 '%2'。 |
The specified IP address '%1' does not match the IP version '%2'. |
| 0xC8 | 當 IPv6 位址 '%1' 做為 URL 中的主機名稱時，必須括在方括弧中。 |
The IPv6 address '%1' must be enclosed in brackets when used as a host name in a URL. |
| 0xC9 | 剖析 IP 位址時發生錯誤。 |
There was an error parsing the IP address. |
| 0xCA | IP 位址 '%1' 無效或者不符合指定的 IP 版本。 |
The IP address '%1' was invalid or did not match the specified IP version. |
| 0xCB | 通訊端位址的大小不正確。 |
The size of the socket address was not correct. |
| 0xCC | 通訊端位址的位址家族 '%1' 不正確。 |
The address family '%1' of the socket address was not correct. |
| 0xCD | 通道不支援工作階段。 |
The channel does not support sessions. |
| 0xCE | 更新通訊端的接受內容時發生錯誤。 |
There was an error updating the accept context for the socket. |
| 0xCF | 更新通訊端的連線內容時發生錯誤。 |
There was an error updating the connect context for the socket. |
| 0xD0 | 在 TCP 通訊端接聽時發生錯誤。 |
There was an error listening on the TCP socket. |
| 0xD1 | 接受 TCP 通訊端時發生錯誤。 |
There was an error accepting a TCP socket. |
| 0xD2 | 建立 UDP 通訊端時發生錯誤。 |
There was an error creating the UDP socket. |
| 0xD3 | 在 UDP 通訊端傳送資料時發生錯誤。 |
There was an error sending data on the UDP socket. |
| 0xD4 | 從 UDP 通訊端接收時發生錯誤。 |
There was an error receiving from the UDP socket. |
| 0xD5 | 將 UDP 通訊端繫結至位址時發生錯誤。 |
There was an error binding the UDP socket to an address. |
| 0xD6 | 建立 HTTP 要求佇列時發生錯誤。 |
There was an error creating the HTTP request queue. |
| 0xD7 | 接收 HTTP 要求時發生錯誤。 |
There was an error receiving the HTTP request. |
| 0xD8 | 傳送 HTTP 回覆時發生錯誤。 |
There was an error sending the HTTP reply. |
| 0xD9 | 無法建立計時器物件。 |
Unable to create timer object. |
| 0xDA | 無法判斷 DNS 主機名稱 '%1' 與連接埠 '%2' 的 IP 位址。 |
Unable to determine IP addresses for DNS host name '%1' and port '%2'. |
| 0xDB | 未傳回 DNS 主機名稱 '%1' 與連接埠 '%2' 可用的 IP 位址。 |
No usable IP addresses were returned for DNS host name '%1' and port '%2'. |
| 0xDC | 無法初始化 HTTP 程式庫。 |
The HTTP library failed to initialized. |
| 0xDD | 無法開啟回覆通道。 |
A reply channel can not be opened. |
| 0xDE | 無法載入動態連結程式庫 '%1'。 |
The dynamic link library '%1' could not be loaded. |
| 0xDF | 找不到來自動態連結程式庫 '%1' 的匯入 '%2'。 |
The import '%2' from dynamic link library '%1' could not be found. |
| 0xE0 | 無法取得模組 '%1' 的控制代碼。 |
Unable to get the handle for the module '%1'. |
| 0xE1 | 欄位對應類型為 '%1' 的欄位處於不正確的位置，或者不可以用於這個內容。 |
A field with field mapping type '%1' was in an incorrect position, or may not be used in this context. |
| 0xE2 | 結構選項 '%1' 無效。 |
The struct option '%1' is not valid. |
| 0xE3 | 已經指定抽象結構選項，但是這個類型不包含類型屬性。 |
The abstract struct option was specified but the type does not contain a type attribute. |
| 0xE4 | 因為結構標示成抽象，所以無法將結構序列化或還原序列化。 |
The struct can not be serialized or de-serialized because it is marked abstract. |
| 0xE5 | 支援衍生的結構不可以用於這個內容。 |
A structure that supports derivation may not be used in this context. |
| 0xE6 | 欄位對應類型 '%1 不可以用於這個內容。 |
The field mapping type '%1' may not be used in this context. |
| 0xE7 | 指定的 LANGID 為 0。 |
The specified LANGID was zero. |
| 0xE8 | 未重設錯誤物件之前，不可以設定 LANGID。 |
The LANGID may not be set without first resetting the error object. |
| 0xE9 | 錯誤原因為: '%1'。 |
The fault reason was: '%1'. |
| 0xEA | 錯誤碼 '%1' 不是失敗碼。 |
The error code '%1' was not a failure code. |
| 0xEB | 無法初始化重要區段。 |
Unable to initialize critical section. |
| 0xEC | 執行階段記憶體配置需要比堆積 (其限制為 %2 個位元組) 中之可用記憶體多 %1 位元組的記憶體。 |
A runtime memory allocation requires %1 bytes more than what is available in the heap with a limit of %2 bytes. |
| 0xED | 端點位址擴充類型 '%1' 無效。 |
The endpoint address extension type '%1' is invalid. |
| 0xEE | 端點位址中的擴充元素太多。 |
There were too many extension elements in the endpoint address. |
| 0xEF | 遺漏端點位址的中繼資料參照。 |
The metadata reference in the endpoint address was missing. |
| 0xF0 | 遺漏端點位址中的 URI 值。 |
The URI value in the endpoint address was missing. |
| 0xF1 | ReplyTo/FaultTo 位址不是匿名的。 |
The ReplyTo/FaultTo address is not anonymous. |
| 0xF2 | 遺漏 ReplyTo 標頭。 |
The ReplyTo header is missing. |
| 0xF3 | XML 讀取器未放在屬性中。 |
The XML reader was not positioned in an attribute. |
| 0xF4 | XML 寫入器未放在屬性中。 |
The XML writer was not positioned in an attribute. |
| 0xF5 | XML 寫入器已放在屬性中。 |
The XML writer was positioned in an attribute. |
| 0xF6 | 無法將值剖析為 URI。 |
The value could not be parsed as a URI. |
| 0xF7 | 必須指定元素名稱與命名空間。 |
The element name and namespace must be specified. |
| 0xF8 | 字串包含內嵌的 0。 |
The string contained an embedded zero. |
| 0xF9 | 指定的大小不是該類型的正確大小。類型需要 '%1' 位元組，但是指定的是 '%2' 位元組。 |
The size specified was not the correct size for the type. The type requires '%1' bytes, but '%2' bytes were specified. |
| 0xFA | 指定的類型必須以指標讀取。 |
The specified type must be read as a pointer. |
| 0xFB | 指定的類型必須以指標寫入。 |
The specified type must be written as a pointer. |
| 0xFC | 值 '%1' 不是有效的 WS_READ_OPTION。 |
The value '%1' was not valid as a WS_READ_OPTION. |
| 0xFD | 讀取選項值 '%1' 不可以用於這個內容。 |
The read option value '%1' may not be used in this context. |
| 0xFE | 需要堆積物件才能讀取這種類型。 |
A heap object is required to read this type. |
| 0xFF | XML 中應該有一個值，但是找不到任何值。 |
A value was expected in the XML, but none was found. |
| 0x100 | 資源字串太大。 |
The resource string was too large. |
| 0x101 | 欄位類型不支援 XML 屬性對應。 |
The field type does not support an XML attribute mapping. |
| 0x102 | 收到的訊息的本文中有錯誤。 |
The body of the received message contained a fault. |
| 0x103 | 目前沒有傳送或接收被放棄的訊息。 |
The message being abandoned is not currently being sent or received. |
| 0x104 | 因為內部錯誤，所以伺服器無法處理要求。 |
The server was unable to process the request due to an internal error. |
| 0x105 | |
|
| 0x106 | 嘗試配置 '%1' 位元組記憶體失敗。 |
An attempt to allocate '%1' bytes of memory failed. |
| 0x107 | 無法建立完成連接埠。 |
A completion port could not be created. |
| 0x108 | 無法將工作安排至另一個執行緒的佇列。 |
Work could not be queued to another thread. |
| 0x109 | 無法建立執行緒。 |
A thread could not be created. |
| 0x10A | 無法建立管道。 |
A pipe could not be created. |
| 0x10B | 無法開啟管道。 |
A pipe could not be opened. |
| 0x10C | 無法連接管道。 |
A pipe could not be connected. |
| 0x10D | 無法建立 I/O 封包。 |
An I/O packet could not be created. |
| 0x10E | 緩衝區的長度 (%1) 不夠大，無法完成操作。 |
The buffer of length (%1) was not large enough to complete the operation. |
| 0x10F | 緩衝區的長度是 '%2' 個位元組，但是正確的應該是 '%1' 個位元組。 |
The length of the buffer was '%2' bytes, but '%1' bytes were expected. |
| 0x110 | 已經超過緩衝區的長度上限。 |
The maximum length of a buffer was exceeded. |
| 0x111 | 已經超過字串的長度上限。 |
The maximum length of a string was exceeded. |
| 0x112 | 字串 '%1' 包含字元值 0，該值在這個內容中不正確。 |
The string '%1' contains character value zero, which is not legal in this context. |
| 0x113 | 字元 '%1' 無法剖析為帶正負號的 32 位元整數，或者它的值超出帶正負號 32 位元整數的範圍。 |
The characters '%1' either cannot be parsed as a signed 32 bit integer, or its value is out of range of a signed 32 bit integer. |
| 0x114 | 字元 '%1' 無法剖析為帶正負號的 64 位元整數，或者它的值超出帶正負號 64 位元整數的範圍。 |
The characters '%1' either cannot be parsed as a signed 64 bit integer, or its value is out of range of a signed 64 bit integer. |
| 0x115 | 字元 '%1' 無法剖析為無正負號的 32 位元整數，或者它的值超出無正負號 32 位元整數的範圍。 |
The characters '%1' either cannot be parsed as an unsigned 32 bit integer, or its value is out of range of an unsigned 32 bit integer. |
| 0x116 | 字元 '%1' 無法剖析為無正負號的 64 位元整數，或者它的值超出無正負號 64 位元整數的範圍。 |
The characters '%1' either cannot be parsed as an unsigned 64 bit integer, or its value is out of range of an unsigned 64 bit integer. |
| 0x117 | 字元 '%1' 無法剖析為 64 位元浮點數，或者它的值超出 64 位元浮點數的範圍。 |
The characters '%1' either cannot be parsed as a 64 bit floating point number, or its value is out of range of a 64 bit floating point number. |
| 0x118 | 字元 '%1' 無法剖析為 128 位元定點數字，或者它的值超出 128 位元定點數字的範圍。 |
The characters '%1' either cannot be parsed as a 128 bit fixed point number, or its value is out of range of a 128 bit fixed point number. |
| 0x119 | 字元 '%1' 無法剖析為布林值 ('true'、'false'、'1' 或 '0')。 |
The characters '%1' cannot be parsed as a bool ('true', 'false', '1', or '0'). |
| 0x11A | 因為超出範圍，所以帶正負號的 32 位元整數 %1 無法轉換成帶正負號的 8 位元整數。 |
The signed 32 bit integer %1 could not be converted to a signed 8 bit integer because it is out of range. |
| 0x11B | 因為超出範圍，所以帶正負號的 32 位元整數 %1 無法轉換成帶正負號的 16 位元整數。 |
The signed 32 bit integer %1 could not be converted to a signed 16 bit integer because it is out of range. |
| 0x11C | 因為超出範圍，所以帶正負號的 32 位元整數 %1 無法轉換成無正負號的 8 位元整數。 |
The signed 32 bit integer %1 could not be converted to an unsigned 8 bit integer because it is out of range. |
| 0x11D | 因為超出範圍，所以帶正負號的 32 位元整數 %1 無法轉換成無正負號的 16 位元整數。 |
The signed 32 bit integer %1 could not be converted to an unsigned 16 bit integer because it is out of range. |
| 0x11E | 因為超出範圍，所以無正負號的 32 位元整數 %1 無法轉換成無正負號的 16 位元整數。 |
The unsigned 32 bit integer %1 could not be converted to an unsigned 16 bit integer because it is out of range. |
| 0x11F | 因為超出範圍，所以帶正負號的 32 位元整數 %1 無法轉換成無正負號的 64 位元整數。 |
The signed 32 bit integer %1 could not be converted to an unsigned 64 bit integer because it is out of range. |
| 0x120 | 因為超出範圍，所以帶正負號的 64 位元整數 %1 無法轉換成帶正負號的 32 位元整數。 |
The signed 64 bit integer %1 could not be converted to a signed 32 bit integer because it is out of range. |
| 0x121 | 因為超出範圍，所以帶正負號 64 位元整數 %1 無法轉換成無正負號的 32 位元整數。 |
The signed 64 bit integer %1 could not be converted to an unsigned 32 bit integer because it is out of range. |
| 0x122 | 因為超出範圍，所以帶正負號的 64 位元整數 %1 無法轉換成無正負號的 64 位元整數。 |
The signed 64 bit integer %1 could not be converted to an unsigned 64 bit integer because it is out of range. |
| 0x123 | 因為超出範圍，所以無正負號的 64 位元整數 %1 無法轉換成帶正負號的 32 位元整數。 |
The unsigned 64 bit integer %1 could not be converted to a signed 32 bit integer because it is out of range. |
| 0x124 | 因為超出範圍，所以無正負號的 64 位元整數 %1 無法轉換成帶正負號的 64 位元整數。 |
The unsigned 64 bit integer %1 could not be converted to a signed 64 bit integer because it is out of range. |
| 0x125 | dateTime 格式 '%1' 無效。 |
The dateTime format '%1' is not valid. |
| 0x126 | 年份 %1 超出範圍 (1 - 9999)。 |
The year %1 is out of range (1 - 9999). |
| 0x127 | 月份 %1 超出範圍 (1 - 12)。 |
The month %1 is out of range (1 - 12). |
| 0x128 | The day %3 is out of range for year %1, month %2. |
The day %3 is out of range for year %1, month %2. |
| 0x129 | 值 '%1' 無法剖析為日期。 |
The value '%1' could not be parsed as a date. |
| 0x12A | 值 '%1' 無法剖析為 GUID。 |
The value '%1' could not be parsed as a GUID. |
| 0x12C | 值 '%1' 無法剖析為合格名稱。 |
The value '%1' could not be parsed as a qualified name. |
| 0x12D | 值 '%1' 無法剖析為時間長度。 |
The value '%1' could not be parsed as a timespan. |
| 0x12E | 其中一個時間元件超出範圍。天數必須小於 %1、時數小於 24、分鐘數小於 60、秒數小於 60。如果分鐘數和秒數為 0，則允許時數的值為 24。 |
One of the time components is out of range. The number of days must be less than %1, hours less than 24, minutes less than 60, seconds less than 60. A value of 24 is permitted for hours if minutes and seconds are zero. |
| 0x12F | 因為會超出無正負號 32 位元整數的範圍，所以無法新增無正負號 32 位元整數 %1 與 %2。 |
The unsigned 32 bit integers %1 and %2 could not be added because it would be out of the range of an unsigned 32 bit integer. |
| 0x130 | 因為會超出無正負號 32 位元整數的範圍，所以無法乘上無正負號 32 位元整數 %1 與 %2。 |
The unsigned 32 bit integers %1 and %2 could not be multiplied because it would be out of the range of an unsigned 32 bit integer. |
| 0x131 | 已經超出陣列的長度上限。 |
The maximum length of an array was exceeded. |
| 0x132 | 因為會超出無正負號 64 位元整數的範圍，所以無法新增無正負號 64 位元整數 %1 與 %2。 |
The unsigned 64 bit integers %1 and %2 could not be added because it would be out of the range of an unsigned 64 bit integer. |
| 0x133 | 因為會超出無正負號 64 位元整數的範圍，所以無法乘上無正負號 64 位元整數 %1 與 %2。 |
The unsigned 64 bit integers %1 and %2 could not be multiplied because it would be out of the range of an unsigned 64 bit integer. |
| 0x134 | 因為 xml 文件意外結束，所以格式不正確。至少需要額外 '%1' 位元組。 |
The xml document is not correctly formed because it ended unexpectedly. At least '%1' additional bytes are needed. |
| 0x135 | 因為 xml 文件的大小超過預期，所以無法讀取。資料無法放入大小為 '%1' 位元組的緩衝區。 |
The xml document could not be read because it was larger than expected. The data did not fit within the buffer size of '%1' bytes. |
| 0x136 | 寫入的位元組數目超出指定的 %1 位元組的配額。 |
The numbers of bytes written exceeded the specified quota of %1 bytes. |
| 0x137 | 值 '%1' 包含無效的非 ASCII 字元 '%2'。 |
The value '%1' contains the non-ASCII character '%2' which is not valid. |
| 0x138 | 編碼的位元組數目 (%1) 不等於預期的位元組數目 (%2)。 |
The number of bytes encoded (%1) did not equal the number of bytes expected (%2). |
| 0x139 | 解碼的字元數目 (%1) 不等於預期的字元數目 (%2)。 |
The number of characters decoded (%1) did not equal the number of characters expected (%2). |
| 0x13A | base64 序列中的字元數目 (%1) 無效。base64 序列應該是 4 個字元的倍數。 |
The number of characters (%1) in the base64 sequence is not valid. A base64 sequence should be a multiple of four characters. |
| 0x13B | 字元 '%1' 不是有效的 4 個字元 base64 序列。 |
The characters '%1' are not a valid 4 character base64 sequence. |
| 0x13C | 值 %1 不是有效的字元集。 |
The value %1 is not a valid charset. |
| 0x13D | 值 '%1' 不是有效的字元集。 |
The value '%1' is not a valid charset. |
| 0x13E | 值 %1 不是有效的 Unicode 字元。 |
The value %1 is not a valid Unicode character. |
| 0x13F | 值 (%2, %1) 不是 utf16 編碼序列。 |
The values (%2, %1) are not a utf16 encoded sequence. |
| 0x140 | 值 %1 不是有效的 utf8 編碼前導位元組。 |
The value %1 is not a valid utf8 encoded lead byte. |
| 0x141 | %1、%2 這兩個值不是有效的 2 位元組 utf8 編碼序列。 |
The values %1, %2 are not a valid 2 byte utf8 encoded sequence. |
| 0x142 | %1、%2 和 %3 這三個值不是有效的 3 位元組 utf8 編碼序列。 |
The values %1, %2, %3 are not a valid 3 byte utf8 encoded sequence. |
| 0x143 | %1、%2、%3 和 %4 這四個值不是有效的 4 位元組 utf8 編碼序列。 |
The values %1, %2, %3, %4 are not a valid 4 byte utf8 encoded sequence. |
| 0x144 | 值 '%1' 以部分的 utf8 編碼序列結尾。 |
The value '%1' ends with a partial utf8 encoded sequence. |
| 0x145 | 值 '%1' 以部分的 utf16 編碼序列結尾。 |
The value '%1' ends with a partial utf16 encoded sequence. |
| 0x146 | xml 包含未預期的節點類型 (%1)。 |
The xml contains the unexpected node type (%1). |
| 0x147 | xml 包含無效的字典參照。 |
The xml contains an invalid dictionary reference. |
| 0x148 | xml 包含無效的合格項。 |
The xml contains an invalid qualified. |
| 0x149 | xml 包含無效的多位元組編碼整數。 |
The xml contains an invalid multibyte encoded integer. |
| 0x14A | xml 包含無效的長度。 |
The xml contains an invalid length. |
| 0x14B | 指定的 moveTo 值 (%1) 無效。 |
The moveTo value specified (%1) is invalid. |
| 0x14C | 無法移除 xml 緩衝區的根節點。 |
The root node of an xml buffer may not be removed. |
| 0x14D | 無法移除 xml 緩衝區的結尾元素。 |
An end element of an xml buffer may not be removed. |
| 0x14E | 值 %1 對首碼或 localName 而言無效。 |
The value '%1' is not a valid for a prefix or localName. |
| 0x14F | 字元參照 '%1' 無效。 |
The character reference '%1' is not valid. |
| 0x150 | 字元值 '%1' 無效。 |
The character value %1 is not valid. |
| 0x151 | 應該要有字元 '%1'，但是找不到。 |
The characters '%1' were expected but not found. |
| 0x152 | 應該要有結尾元素 '%1'，但是找不到。 |
The end element '%1' was expected but not found. |
| 0x153 | 應該要有字元 '\\' 或 '\"'。 |
The character '\\' or '\"' was expected. |
| 0x154 | 字元 '%1' 不是有效的元素內容。 |
The characters '%1' are not valid as element content. |
| 0x155 | 字元 '%1' 不是有效的屬性內容。 |
The characters '%1' are not valid as attribute content. |
| 0x156 | 首碼 '%1' 未繫結至任何命名空間。 |
The prefix '%1' is not bound to any namespace. |
| 0x157 | 命名空間 '%1' 未繫結至任何首碼。 |
The namespace '%1' is not bound to any prefix. |
| 0x158 | 含空白首碼的屬性不可以繫結至空白的命名空間。 |
An attribute with an empty prefix cannot be bound to the empty namespace. |
| 0x159 | 因為首碼開頭是 'xml'，所以首碼 '%1' 不可以繫結至命名空間 '%2'。 |
The prefix '%1' cannot be bound to the namespace '%2' because the prefix begins with 'xml'. |
| 0x15A | 無法將首碼 '%1' 繫結至空白的命名空間。 |
The prefix '%1' cannot be bound to the empty namespace. |
| 0x15B | 因為首碼繫結至 '%2'，所以首碼 '%1' 不可以繫結至命名空間 '%3'。 |
The prefix '%1' cannot be bound to namespace '%3' because it is bound to '%2'. |
| 0x15C | 已經超過文件在 %1 領域中命名空間的數量上限。 |
The maximum number of namespaces in scope of %1 for the document was exceeded. |
| 0x15D | 應該要有 CR/LF，但是找不到。 |
A CR/LF was expected but not found. |
| 0x15E | 找到多個名稱為 '%1' 的 mime 標頭。 |
Multiple mime headers with the name '%1' were found. |
| 0x15F | 找不到 mime 標頭 '%1'。 |
The mime header '%1' could not be found. |
| 0x160 | 無法剖析 mime 標頭。 |
The mime header could not be parsed. |
| 0x161 | 找不到 mime 邊界 '%1'，或者它後面不是接著 CR/LF。 |
The mime boundary '%1' was not be found, or it was not followed by CR/LF. |
| 0x162 | 找不到由指定之 moveTo 值 (%1) 所指出的位置。 |
A position indicated by the specified moveTo value (%1) was not found. |
| 0x163 | 無法移動讀取器位置。 |
The reader position could not be moved. |
| 0x164 | 無法移動寫入器位置。 |
The writer position could not be moved. |
| 0x165 | 寫入器的必須放在元素中才能寫入屬性。 |
The writer must be positioned on an element to write an attribute. |
| 0x166 | 寫入器的必須放在元素或屬性中才能寫入 xmlns 屬性。 |
The writer must be positioned on an element or attribute to write an xmlns attribute. |
| 0x167 | 寫入器已經在寫入屬性。 |
The writer is already writing an attribute. |
| 0x168 | 寫入器目前未寫入屬性。 |
The writer is not currently writing an attribute. |
| 0x169 | 必須先結束目前的屬性，才能執行這項操作。 |
The current attribute must be ended before this operation can be performed. |
| 0x16A | 屬性只能寫入一個值。 |
Only one value for an attribute may be written. |
| 0x16B | 尚未設定寫入器的輸出。 |
The output for the writer has not been set. |
| 0x16C | 寫入器已經在寫入 CDATA。 |
The writer is already writing CDATA. |
| 0x16D | 寫入器目前未寫入 CDATA。 |
The writer is not currently writing CDATA. |
| 0x16E | 必須先結束 CDATA 才能寫入元素。 |
The CDATA must be ended before an element can be written. |
| 0x16F | 必須先結束 CDATA 才能寫入結尾元素。 |
The CDATA must be ended before an end element can be written. |
| 0x170 | 尚未設定讀取器的輸入。 |
The input for the reader has not been set. |
| 0x171 | 有兩個 xmlns 屬性具備相同的首碼 '%1'。 |
There are two xmlns attributes with the same prefix '%1'. |
| 0x172 | 有兩個屬性具備相同的名稱 '%1' 和命名空間 '%2'。 |
There are two attributes with the same name '%1' and namespace '%2'. |
| 0x173 | 預期的開始元素名稱是 '%1'，而且命名空間是 '%2'。 |
A start element with the name '%1' and namespace '%2' was expected. |
| 0x174 | 預期的開始元素名稱是 '%1'。 |
A start element with the name '%1' was expected. |
| 0x175 | 預期的開始元素命名空間是 '%1'。 |
A start element with the namespace '%1' was expected. |
| 0x176 | 應該要有開始元素。 |
A start element was expected. |
| 0x177 | 應該要有結尾元素。 |
An end element was expected. |
| 0x178 | 找到名稱是 '%1' 而且命名空間是 '%2' 的開始元素，但不是預期的開始元素。 |
A start element with the name '%1' and namespace '%2' was found, but not expected. |
| 0x179 | 找到文字 '%1'，但不是預期的文字。 |
The text '%1' was found, but not expected. |
| 0x17A | 找到文字，但不是預期的文字。 |
Text was found, but not expected. |
| 0x17B | 找到結尾元素，但不是預期的結尾元素。 |
An end element was found, but not expected. |
| 0x17C | 找到開始 CDATA，但不是預期的開始 CDATA。 |
An start CDATA was found, but not expected. |
| 0x17D | 找到結尾 CDATA，但不是預期的結尾 CDATA。 |
An end CDATA was found, but not expected. |
| 0x17E | 找到輸入來源的結尾，但不是預期的結尾。 |
The end of the input source was found, but not expected. |
| 0x17F | 讀取器的必須放在元素中才能尋找屬性。 |
The reader must be positioned on an element to find an attribute. |
| 0x180 | 在名稱為 '%3' 而且命名空間為 '%4' 的元素上，找不到名稱為 '%1' 而且命名空間為 '%2' 的屬性。 |
The attribute with the name '%1' and namespace '%2' was not found on the element with name '%3' and namespace '%4'. |
| 0x181 | 讀取器已經在讀取屬性。 |
The reader is already reading an attribute. |
| 0x182 | 讀取器的必須放在元素中才能讀取屬性。 |
The reader must be positioned on an element to read an attribute. |
| 0x183 | 指定的屬性索引 (%1) 超出範圍。命名空間為 '%4' 的元素 '%3' 只有 %2 個屬性。 |
The attribute index specified (%1) is out of range. There are only %2 attributes on the element '%3' with namespace '%4'. |
| 0x184 | 讀取器目前未讀取屬性。 |
The reader is not currently reading an attribute. |
| 0x185 | XML 讀取器處理輸入來源時，列 %1、欄 %2 發生錯誤。 |
An error occurred at row %1, column %2 when the XML reader is processing the input source. |
| 0x186 | 讀取器位於輸入來源的結尾，因此無法繼續讀取。 |
The reader is at the end of the input source and cannot advance further. |
| 0x187 | 標頭屬性 '%1' 無效。 |
The header attributes '%1' are invalid. |
| 0x188 | 資源參數索引無效。 |
The resource parameter index was invalid. |
| 0x189 | 指定的資源參數太多。 |
Too many resource parameters were specified. |
| 0x18A | 字串索引無效。 |
The string index was invalid. |
| 0x18B | URL 旗標 '%1' 無效。 |
The URL flags '%1' are invalid. |
| 0x18C | 訊息大小上限 '%1' 無效。 |
The max message size '%1' is invalid. |
| 0x18D | 訊息開始大小上限 '%1' 無效。 |
The max message start size '%1' is invalid. |
| 0x18E | 錯誤公開值 '%1' 無效。 |
The fault disclosure value '%1' is invalid. |
| 0x18F | 訊息排清大小上限 '%1' 無效。 |
The max message flush size '%1' is invalid. |
| 0x190 | 標頭類型 '%1' 無效。 |
The header type '%1' is invalid. |
| 0x191 | 指定的緩衝區大小無效。 |
The buffer size specified was invalid. |
| 0x192 | xml 字串的識別碼無效。 |
The id of the xml string was invalid. |
| 0x193 | 內容的大小必須是 4 的倍數。 |
The size of the property must be a multiple of 4. |
| 0x194 | 錯誤動作為 NULL。 |
The fault action is NULL. |
| 0x195 | 錯誤為 NULL。 |
The fault is NULL. |
| 0x196 | 錯誤碼為 NULL。 |
The fault code is NULL. |
| 0x197 | 未指定錯誤原因。 |
No fault reasons were specified. |
| 0x198 | 儲存配置值的指標為 NULL。 |
The pointer that stores the allocated value is NULL. |
| 0x199 | 錯誤字串索引無效。 |
The error string index is invalid. |
| 0x19B | 字串為 NULL。 |
The string is NULL. |
| 0x19C | 標頭屬性為 NULL。 |
The header attributes are NULL. |
| 0x19D | 指定的讀取器物件無效。 |
The reader object specified is invalid. |
| 0x19E | 指定的寫入器物件無效。 |
The writer object specified is invalid. |
| 0x19F | 指定的緩衝區物件無效。 |
The buffer object specified is invalid. |
| 0x1A0 | 指定的訊息物件無效。 |
The message object specified is invalid. |
| 0x1A1 | 指定的堆積物件無效。 |
The heap object specified is invalid. |
| 0x1A2 | 指定的通道物件無效。 |
The channel object specified is invalid. |
| 0x1A3 | 指定的接聽程式物件無效。 |
The listener object specified is invalid. |
| 0x1A4 | 指定的中繼資料物件無效。 |
The metadata object specified is invalid. |
| 0x1A5 | 指定的原則物件無效。 |
The policy object specified is invalid. |
| 0x1A6 | 指定的原則替代計數為 NULL。 |
The policy alternative count specified is NULL. |
| 0x1A7 | 指定的端點位址為 NULL。 |
The endpoint address specified is NULL. |
| 0x1A8 | 指定的中繼資料端點結構為 NULL。 |
The metadata endpoints structure specified is NULL. |
| 0x1A9 | 指定的安全性繫結限制結構為 NULL。 |
The security binding constraint structure specified is NULL. |
| 0x1AA | 指定的錯誤物件無效。 |
The error object specified is invalid. |
| 0x1AB | 指定的值是 NULL。 |
The value specified is NULL. |
| 0x1AC | 指定的 localName 為 NULL。 |
The localName specified is NULL. |
| 0x1AD | 指定的 localName 長度為 0。 |
The localName specified has a length of zero. |
| 0x1AE | 指定的命名空間為 NULL。 |
The namespace specified is NULL. |
| 0x1AF | 指定的字元數為 NULL。 |
The character count specified is NULL. |
| 0x1B0 | 指定的位元組計數為 NULL。 |
The byte count specified is NULL. |
| 0x1B1 | 指定的屬性索引為 NULL。 |
The attribute index specified is NULL. |
| 0x1B2 | 指定的緩衝區為 NULL。 |
The buffers specified is NULL. |
| 0x1B3 | 在索引 '%1' 指定的緩衝區為 NULL。 |
The buffer specified at index '%1' is NULL. |
| 0x1B4 | 指定的編碼為 NULL。 |
The encoding specified is NULL. |
| 0x1B5 | 指定的讀取器輸入為 NULL。 |
The reader input specified is NULL. |
| 0x1B6 | 指定的寫入器輸出為 NULL。 |
The writer output specified is NULL. |
| 0x1B7 | 指定的位置為 NULL。 |
The position specified is NULL. |
| 0x1B8 | 指定的位置無效。 |
The position specified is invalid. |
| 0x1B9 | 指定的首碼為 NULL。 |
The prefix specified is NULL. |
| 0x1BA | 指定的屬性值為 NULL。 |
The attribute value specified is NULL. |
| 0x1BB | 指定的註解為 NULL。 |
The comment specified is NULL. |
| 0x1BC | 指定的文字為 NULL。 |
The text specified is NULL. |
| 0x1BD | 指定的節點為 NULL。 |
The node specified is NULL. |
| 0x1BE | 指定的回呼為 NULL。 |
The callback specified is NULL. |
| 0x1BF | 指定的文字清單在索引 %1 有 NULL 文字。 |
The list of text specified has a NULL text at index %1. |
| 0x1C0 | 指定的訊息描述為 NULL。 |
The message description specified is NULL. |
| 0x1C1 | 指定的錯誤詳細資料描述為 NULL。 |
The fault detail description specified is NULL. |
| 0x1C2 | 指定的陣列為 NULL。 |
The array specified is NULL. |
| 0x1C3 | 指定的陣列計數為 NULL。 |
The array count specified is NULL. |
| 0x1C4 | 指定的字典為 NULL。 |
The dictionary specified is NULL. |
| 0x1C5 | 指定的訊息為 NULL。 |
The message specified is NULL. |
| 0x1C6 | 指定的文字清單在索引 %1 有巢狀結構清單。 |
The list of text specified has a nested list at index %1. |
| 0x1C7 | 編碼類型 ('%1') 無效。 |
The encoding type (%1) is not valid. |
| 0x1C8 | 在 MTOM 編碼中，編碼類型 ('%1') 無效。 |
The encoding type (%1) is not valid within the MTOM encoding. |
| 0x1C9 | 值類型 ('%1') 無效。 |
The value type (%1) is not valid. |
| 0x1CA | 文字類型 ('%1') 無效。 |
The text type (%1) is not valid. |
| 0x1CB | 節點類型 ('%1') 無效。 |
The node type (%1) is not valid. |
| 0x1CC | 縮排值 (%1) 太大。縮排值上限為 %2。 |
The indent value (%1) is too large. The maximum indent value is %2. |
| 0x1CD | 訊息初始化類型 (%1) 無效。 |
The message initialization type (%1) is not valid. |
| 0x1CE | 指定的對齊方式 ('%1') 無效。 |
The specified alignment (%1) is not valid. |
| 0x1CF | 指定的 xml 字串為 NULL。 |
The xml string specified is null. |
| 0x1D0 | 未使用這個接聽器來建立指定的通道。 |
The channel specified was not created with this listener. |
| 0x1D1 | 無法抓取環境變數 '%1'。 |
Could not retrieve the environment variable '%1'. |
| 0x1D2 | 通道的目前傳送狀態不允許這項操作。 |
The operation is not allowed in the current send state of the channel. |
| 0x1D3 | 通道的目前接收狀態不允許這項操作。 |
The operation is not allowed in the current receive state of the channel. |
| 0x1D4 | 無法遞增指定之模組控制代碼的參照。 |
Unable to increment the reference to the specified module handle. |
| 0x1D5 | 無法取得模組的控制代碼。 |
Unable to get handle of module. |
| 0x1D6 | 已經超出允許的文件深度 %1 上限。 |
The maximum allowed depth of %1 for the document was exceeded. |
| 0x1D7 | 已經超出允許的文件原則擴充 %1 上限。 |
The maximum allowed policy extensions of %1 for the document was exceeded. |
| 0x1D8 | 已經超出文件中元素的 %1 屬性數目上限。 |
The maximum number of attributes of %1 for an element in the document was exceeded. |
| 0x1D9 | 命名空間 '%2' 的原則擴充 '%1' 在原則中出現一次以上。 |
The policy extension '%1' from namespace '%2' appeared more than once in the policy. |
| 0x1DA | 文件的最上層只允許一個元素。 |
Only one element is permitted at the top-level of the document. |
| 0x1DB | 文件的最上層有非空白文字。 |
There is non-whitespace text at the top-level of the document. |
| 0x1DC | 文件的最上層有非空白文字 '%1'。 |
There is non-whitespace text '%1' at the top-level of the document. |
| 0x1DD | 未寫入符合的開始元素。 |
A matching start element was not written. |
| 0x1DE | 文件最上層的 CDATA 無效。 |
CDATA is not valid at the top-level of the document. |
| 0x1DF | mtom 格式不可以用於片段。 |
The mtom format cannot be used with fragments. |
| 0x1E0 | 指定的 IP 版本 (%1) 無效。 |
The specified IP version (%1) was invalid. |
| 0x1E1 | 回呼模型 %1 無效。 |
The callback model %1 was invalid. |
| 0x1E2 | 傳輸模式 %1 無效。 |
The transfer mode %1 was invalid. |
| 0x1E3 | Cookie 模式 %1 無效。 |
The cookie mode %1 was invalid. |
| 0x1E4 | 因為工作項目無法排入執行緒集區的佇列，所以無法叫用回呼。 |
The callback could not be invoke long because the work item could not be queued to the threadpool. |
| 0x1E5 | 指定的物件無效。它可能已經被釋放。 |
The specified object was not valid. It may already have been freed. |
| 0x1E6 | 非同步內容結構中的回呼是 NULL。 |
The callback in the async context structure was NULL. |
| 0x1E7 | 因為接聽程式的狀態為 '%1'，所以無法釋放它。 |
The listener could not be freed because it is in state '%1'. |
| 0x1E8 | 因為通道的狀態為 '%1'，所以無法釋放它。 |
The channel could not be freed because it is in state '%1'. |
| 0x1E9 | 因為 IO 擱置中，所以無法放棄訊息。 |
The message could not be abandoned because IO is pending. |
| 0x1EA | 還原序列化的資料大小小於指定的大小下限。 |
The size of the de-serialized data was less than the specified minimum size. |
| 0x1EB | 還原序列化的資料大小超過指定的大小上限。 |
The size of the de-serialized data exceeded the specified maximum size. |
| 0x1EC | 還原序列化的值小於指定的最小值。 |
The de-serialized value was less than the specified minimum value. |
| 0x1ED | 還原序列化的值大於指定的最大值。 |
The de-serialized value was greater than the specified maximum value. |
| 0x1EE | 還原序列化的值不是預期的值。 |
The de-serialized value was not the expected value. |
| 0x1EF | 還原序列化的項目數小於指定的最小計數。 |
The number of de-serialized items was less than the specified minimum count. |
| 0x1F0 | 還原序列化的項目數大於指定的最大計數。 |
The number of de-serialized items was greater than the specified maximum count. |
| 0x1F1 | 在列舉中，值 %1 不是有效的名稱。 |
The value '%1' was not a valid name within the enumeration. |
| 0x1F2 | 名稱為 '%2' 而且命名空間為 '%3' 的元素，應該要有 'xml:%1' 屬性。 |
The 'xml:%1' attribute was expected for the element with name '%2' and namespace '%3'. |
| 0x1F3 | 可能未指定 WS_TYPE 的 WS_DEFAULT_VALUE。 |
A WS_DEFAULT_VALUE may not be specified for the WS_TYPE. |
| 0x1F4 | 指定的 WS_DEFAULT_VALUE 大小對 WS_TYPE 而言不正確。 |
The specified WS_DEFAULT_VALUE was the incorrect size for the WS_TYPE. |
| 0x1F5 | 計數欄位為 NULL。 |
The count field is NULL. |
| 0x1F6 | WS_ELEMENT_DESCRIPTION 的元素命名空間為 NULL。 |
The element namespace of the WS_ELEMENT_DESCRIPTION is NULL. |
| 0x1F7 | WS_ELEMENT_DESCRIPTION 的元素命名空間不是 NULL。 |
The element namespace of the WS_ELEMENT_DESCRIPTION is not NULL. |
| 0x1F8 | WS_ELEMENT_DESCRIPTION 為 NULL。 |
The WS_ELEMENT_DESCRIPTION is NULL. |
| 0x1F9 | WS_ATTRIBUTE_DESCRIPTION 為 NULL。 |
The WS_ATTRIBUTE_DESCRIPTION is NULL. |
| 0x1FA | WS_ATTRIBUTE_DESCRIPTION 的屬性本機名稱為 NULL。 |
The attribute local name of the WS_ATTRIBUTE_DESCRIPTION is NULL. |
| 0x1FB | WS_ATTRIBUTE_DESCRIPTION 的屬性命名空間為 NULL。 |
The attribute namespace of the WS_ATTRIBUTE_DESCRIPTION is NULL. |
| 0x1FC | WS_STRUCT_DESCRIPTION 的類型本機名稱為 NULL。 |
The type local name of the WS_STRUCT_DESCRIPTION is NULL. |
| 0x1FD | WS_STRUCT_DESCRIPTION 的類型命名空間為 NULL。 |
The type namespace of the WS_STRUCT_DESCRIPTION is NULL. |
| 0x1FE | WS_FIELD_DESCRIPTION 的欄位本機名稱為 NULL。 |
The field local name of the WS_FIELD_DESCRIPTION is NULL. |
| 0x1FF | WS_FIELD_DESCRIPTION 的欄位命名空間為 NULL。 |
The field namespace of the WS_FIELD_DESCRIPTION is NULL. |
| 0x200 | WS_FIELD_DESCRIPTION 的欄位本機名稱不是 NULL。 |
The field local name of the WS_FIELD_DESCRIPTION is not NULL. |
| 0x201 | WS_FIELD_DESCRIPTION 的欄位命名空間不是 NULL。 |
The field namespace of the WS_FIELD_DESCRIPTION is not NULL. |
| 0x202 | WS_FIELD_DESCRIPTION 的欄位項目本機名稱為 NULL。 |
The field item local name of the WS_FIELD_DESCRIPTION is NULL. |
| 0x203 | WS_FIELD_DESCRIPTION 的欄位項目命名空間為 NULL。 |
The field item namespace of the WS_FIELD_DESCRIPTION is NULL. |
| 0x204 | WS_FIELD_DESCRIPTION 的欄位項目本機名稱不是 NULL。 |
The field item local name of the WS_FIELD_DESCRIPTION is not NULL. |
| 0x206 | WS_FIELD_DESCRIPTION 的欄位項目範圍不是 NULL。 |
The field item range of the WS_FIELD_DESCRIPTION is not NULL. |
| 0x207 | WS_CUSTOM_TYPE_DESCRIPTION 中的回呼為 NULL。 |
A callback in the WS_CUSTOM_TYPE_DESCRIPTION is NULL. |
| 0x208 | 指定用來接受還原序列化值的指標為 NULL。 |
The pointer specified to accept the de-serialized value is NULL. |
| 0x209 | 名稱為 '%1' 而且命名空間為 '%2' 的元素不是預期的元素選擇之一。 |
The element with name '%1' and namespace '%2' was not one of the expected element choices. |
| 0x20A | 名稱為 '%1' 而且命名空間為 '%2' 的元素不是預期的元素萬用字元之一。 |
The element with name '%1' and namespace '%2' was not one of the expected element wildcards. |
| 0x20B | 名稱為 '%1' 而且命名空間為 '%2' 的屬性不是預期的屬性萬用字元之一。 |
The attribute with name '%1' and namespace '%2' was not one of the expected attribute wildcards. |
| 0x20C | 名稱為 '%1' 而且命名空間為 '%2' 的屬性不是預期的屬性。 |
The attribute with name '%1' and namespace '%2' was not expected. |
| 0x20D | 值 '%1' 不是有效的聯集選擇。 |
The value '%1' was not a valid choice for the union. |
| 0x20E | 已經指定 NULL WS_FIELD_DESCRIPTION。 |
A NULL WS_FIELD_DESCRIPTION was specified. |
| 0x20F | 已經指定 WS_STRUCT_DESCRIPTION 。 |
A NULL WS_STRUCT_DESCRIPTION was specified. |
| 0x210 | 值 '%1' 不是有效的 WS_WRITE_OPTION。 |
The value '%1' is not a valid as a WS_WRITE_OPTION. |
| 0x211 | 要序列化的值為 NULL，但該值是必要的。 |
The value being serialized was NULL but is required. |
| 0x212 | 在 WS_ENUM_DESCRIPTION 中，值 %1 不是有效的值。 |
The value '%1' was not a valid value within the WS_ENUM_DESCRIPTION. |
| 0x213 | 目前要序列化的 WS_XML_BUFFER 可能只有一個元素。 |
The WS_XML_BUFFER being serialized may only have a single element. |
| 0x214 | 值 '%1' 超出陣列的範圍。 |
The value '%1' was outside the bounds of the array. |
| 0x215 | 大小為 '%2' 之索引 '%1' 所代表的範圍超出陣列的範圍。 |
The index '%1' with size '%2' represents a range that was outside the bounds of the array. |
| 0x216 | WS_ENUM_VALUE 的列舉名稱是 NULL。 |
The enum name of the WS_ENUM_VALUE was NULL. |
| 0x217 | URL 配置 '%1' 不支援中繼資料抓取。 |
The URL scheme '%1' was not supported for metadata retrieval. |
| 0x218 | URL '%1' 包含片段。 |
The URL '%1' contained a fragment. |
| 0x219 | WSDL 文件包含來自命名空間 '%2' 而且名稱為 '%1' 的必要擴充性元素，不過無法辨識。 |
The WSDL document contained an extensibility element with name '%1' from namespace '%2' that was required but not recognized. |
| 0x21A | URL '%1' 的原則已定義一次以上。 |
The policy with URL '%1' was defined more than once. |
| 0x21B | 來自命名空間 '%2' 而且名稱為 '%1' 的 portType 已定義一次以上。 |
The portType with name '%1' from namespace '%2' was defined more than once in the WSDL document. |
| 0x21C | 在任何 WSDL 文件中找不到來自命名空間 '%2' 而且名稱為 '%1' 的 portType。 |
The portType with name '%1' from namespace '%2' could not be found in any of the WSDL documents. |
| 0x21D | 在任何 WSDL 文件中找不到來自命名空間 '%2' 而且名稱為 '%1' 的訊息。 |
The message with name '%1' from namespace '%2' could not be found in any of the WSDL documents. |
| 0x21E | 來自命名空間 '%2' 而且名稱為 '%1' 的繫結在 WSDL 文件已定義一次以上。 |
The binding with name '%1' from namespace '%2' was defined more than once in the WSDL document. |
| 0x21F | 在任何 WSDL 文件中找不到來自命名空間 '%2' 而且名稱為 '%1'的繫結。 |
The binding with name '%1' from namespace '%2' could not be found in any of the WSDL documents. |
| 0x220 | 來自命名空間 '%2' 而且名稱為 '%1' 的服務在 WSDL 文件中已定義一次以上。 |
The service with name '%1' from namespace '%2' was defined more than once in the WSDL document. |
| 0x221 | 來自命名空間 '%2' 而且名稱為 '%1' 的訊息在 WSDL 文件中已定義一次以上。 |
The message with name '%1' from namespace '%2' was defined more than once in the WSDL document. |
| 0x222 | 有一個原則參照了 URL '%1'，但是在中繼資料文件中找不到。 |
A policy was referenced with the URL '%1' but could not be located within the set of metadata documents. |
| 0x223 | WSDL 文件中來自命名空間 '%3' 的 portType '%2' 有重複的訊息 '%1'。 |
There was a duplicate message '%1' in portType '%2' from namespace '%3' in the WSDL document. |
| 0x224 | WSDL 文件中來自命名空間 '%3' 的 portType '%2' 有遺漏的訊息 '%1'。 |
There was a missing message '%1' in portType '%2' from namespace '%3' in the WSDL document. |
| 0x225 | 繫結操作未參照 WSDL 文件中 portType 操作的所有訊息。 |
A binding operation did not reference all the messages in the portType operation in the WSDL document. |
| 0x226 | 繫結操作已經參照了 portType 中的訊息，但是該訊息未對應至 WSDL 文件中參照訊息的類型。 |
A binding operation referenced messages in the portType that did not correspond to type of the referencing message in the WSDL document. |
| 0x227 | 單一繫結操作已經參照 WSDL 文件中不同 portType 操作的訊息。 |
A single binding operation referenced messages in different portType operations in the WSDL document. |
| 0x228 | 繫結操作有一個與 WSDL 文件中 portType 操作不同的訊息交換模式。 |
A binding operation had a message exchange pattern than the portType operation in the WSDL document. |
| 0x229 | 繫結操作在 WSDL 文件中參照相同的 portType 訊息一次以上。 |
A binding operation referenced the same portType message more than once in the WSDL document. |
| 0x22A | 輸入訊息已指定給 WSDL 文件的操作一次以上。 |
An input message was specified more than once for the operation in the WSDL document. |
| 0x22B | 輸出訊息已指定給 WSDL 文件的操作一次以上。 |
An output message was specified more than once for the operation in the WSDL document. |
| 0x22C | WSDL 文件中的錯誤訊息順序無效。 |
A fault message was in an invalid order in the WSDL document. |
| 0x22D | WSDL 文件中的錯誤訊息未命名。 |
A fault message was not named in the WSDL document. |
| 0x22E | WSDL 文件中的輸入訊息順序無效。 |
An input message was in an invalid order in the WSDL document. |
| 0x22F | WSDL 文件中的輸出訊息順序無效。 |
An output message was in an invalid order in the WSDL document. |
| 0x230 | WSDL 文件中的操作沒有指定任何訊息。 |
No messages were specified for an operation in the WSDL document. |
| 0x231 | 來自命名空間 '%2' 的原則宣告 '%1' 在原則中出現一次以上。 |
The policy assertion '%1' from namespace '%2' appeared more than once in the policy. |
| 0x232 | 原則替代索引 '%1' 無效。 |
The policy alternative index '%1' was invalid. |
| 0x233 | 已經到達中繼資料文件的限制 %1。 |
The limit of %1 metadata documents was reached. |
| 0x234 | 處理原則文件時超出 %1 的深度限制。 |
The depth limit of %1 was exceeded while processing a policy document. |
| 0x235 | 處理原則文件時超出 %1 的原則替代限制。 |
The limit of %1 policy alternatives was exceeded while processing a policy document. |
| 0x236 | 中繼資枓位址的主機名稱 '%1' 未列入建立中繼資料物件時指定的可接受主機名稱清單。 |
The host name '%1' of the metadata address was not in the list of acceptable host names specified when the metadata object was created. |
| 0x237 | 原則限制結構為 NULL。 |
The policy constraints structure was NULL. |
| 0x238 | WSDL 文件指定的繫結有一個以上的 soap 繫結元素。 |
There was more than one soap binding element for a given binding in the WSDL document. |
| 0x239 | 內容限制中允許的值陣列大小無效。大小必須是內容值大小的倍數。 |
The size of the allowed values array in the property constraint was invalid. The size must be a multiple of the size of the property value. |
| 0x23A | 原則宣告索引無效。 |
The policy assertion index was invalid. |
| 0x23B | 安全性繫結限制類型 %1 無效。 |
The security binding constraint type %1 was not valid. |
| 0x23C | 安全性繫結限制類型 %1 出現一次以上。 |
The security binding constraint type '%1' appeared more than once. |
| 0x23D | 安全性繫結限制類型 %1 只能與 TCP 通道繫結一起使用。 |
The security binding constraint type %1 can only be used with a TCP channel binding. |
| 0x23F | 指定的傳輸層安全性繫結限制不只一個。 |
More than one transport-level security binding constraint was specified. |
| 0x240 | 沒有傳輸安全性繫結限制時，不可以使用訊息安全性繫結限制類型。 |
A message security binding constraint type can not be used without a transport security binding constraint. |
| 0x241 | 這種通道類型不支援位址版本 (%1)。 |
The addressing version (%1) is not supported for this type of channel. |
| 0x242 | 指定的類型 '%1' 不可以用於標頭類型 '%2'。 |
The specified type '%1' may not be used with header type '%2'. |
| 0x243 | 原則替代中的編碼不符合指定的需求。 |
The encoding in the policy alternative did not meet the specified requirements. |
| 0x244 | 中繼資料中指定的傳輸類型與需要的類型不同。 |
The transport type specified in the metadata was different than the one required. |
| 0x245 | 原則替代中的位址版本設定與需要的設定不同。 |
The addressing version setting in the policy alternative was different than the one required. |
| 0x246 | 原則替代中的信任版本設定與需要的設定不同。 |
The trust version setting in the policy alternative was different than the one required. |
| 0x247 | 中繼資料中的信封版本設定與需要的設定不同。 |
The envelope version setting in the metadata was different than the one required. |
| 0x248 | 原則替代中的安全性時間戳記設定與需要的設定不同。 |
The security timestamp setting in the policy alternative as different than the one required. |
| 0x249 | 宣告類型 '%1' 未列入宣告限制集合。 |
There claim type '%1' was not listed in the set of claim constraints. |
| 0x24A | 原則需要用戶端挑戰，但是不支援。 |
The policy required a client challenge but it is not supported. |
| 0x24B | 原則需要伺服器挑戰，但是不支援。 |
The policy required a server challenge but it is not supported. |
| 0x24C | 原則中的要求安全性權杖範本包含多組的宣告類型。 |
The request security token template in the policy contained multiple sets of claim types. |
| 0x24D | 原則中的要求安全性權杖範本未包含任何宣告類型。 |
The request security token template in the policy did not contain any claim types. |
| 0x24E | 需要來自命名空間 '%2' 的原則宣告 '%1'，但是未出現在原則替代中。 |
The policy assertion '%1' from namespace '%2' was required but was not present in the policy alternative. |
| 0x24F | 尚未處理來自命名空間 '%2' 的原則宣告 '%1'。 |
The policy assertion '%1' from namespace '%2' was not handled. |
| 0x250 | 不支援要求的原則擴充類型 '%1'。 |
The requested policy extension type '%1' is not supported. |
| 0x251 | 原則中不明宣告之 '%1' 的名稱長度或 '%2' 的命名空間長度太長。 |
The name length of '%1' or the namespace length of '%2' for an unknown assertion in the policy is too long. |
| 0x252 | 原則應該是空的，但是至少包含了一個替代原則。 |
The policy was expected to be empty but contained at least one alternative. |
| 0x253 | 原則包含一個以上而且是這個內容不支援的替代原則。 |
The policy contained more than one alternative, which is not supported in this context. |
| 0x254 | 原則與含 URL '%1' 的端點比對時發生錯誤。 |
There was error matching policy for the endpoint with URL '%1'. |
| 0x255 | 原則與名稱為 '%1' 而且命名空間為 '%2' 的訊息比對時發生錯誤。 |
There was an error matching policy for the message with name '%1' and namespace '%2'. |
| 0x256 | 原則與名稱為 '%1' 而且命名空間為 '%2' 的操作比對時發生錯誤。 |
There was an error matching policy for the operation with name '%1' and namespace '%2'. |
| 0x257 | 代表要使用之傳輸安全性權杖類型的原則宣告遺失或者無法辨識。 |
The policy assertion representing the type of transport security token to use was missing or was not recognized. |
| 0x259 | 代表要使用之 HTTP 標頭驗證配置的原則宣告遺失或者無法辨識。 |
The policy assertion representing the HTTP header authentication scheme to use was missing or was not recognized. |
| 0x25A | 原則替代指定的安全性標頭配置與需要的配置不同。 |
The policy alternative specified a security header layout that was different than the one required. |
| 0x25B | 原則替代指定的安全性演算法套件名稱與需要的套件不同。 |
The policy alternative specified a security algorithm suite name that was different than the one required. |
| 0x25C | 原則替代指定的安全性版本與需要的版本不同。 |
The policy alternative specified a version of security that was different than the one required. |
| 0x25D | 原則替代未包含必要的使用者名稱權杖。 |
The policy alternative did not contain a username token but one was required. |
| 0x25E | 原則替代指定的使用者名稱權杖版本與需要的版本不同。 |
The policy alternative specified a different username token version than the one required. |
| 0x25F | 原則替代指定的 X.509 權杖版本與需要的版本不同。 |
The policy alternative specified a different X.509 token version than the one required. |
| 0x260 | 原則替代指定的權杖包含值與需要的值不同。 |
The policy alternative specified a token inclusion value than the one required. |
| 0x261 | 原則替代指定的傳輸權杖類型與需要的類型不同。 |
The policy alternative specified a transport token type that was different than the one required. |
| 0x262 | 原則替代指定的傳輸保護等級與需要的等級不同。 |
The policy alternative specified a transport protection level that was different than the one required. |
| 0x263 | 原則替代指定的 HTTP 標頭驗證配置與需要的配置不同。 |
The policy alternative specified a HTTP header authentication scheme that was different than the one required. |
| 0x264 | 原則替代未包含必要的 kerberos 權杖。 |
The policy alternative did not contain a kerberos token but one was required. |
| 0x265 | 原則替代未包含必要的 X.509 權杖。 |
The policy alternative did not contain a X.509 token but one was required. |
| 0x266 | 原則替代未包含必要的已發行權杖。 |
The policy alternative did not contain an issued token but one was required. |
| 0x267 | 原則替代指定的 kerberos 權杖版本與需要的版本不同。 |
The policy alternative specified a different kerberos token version than the one required. |
| 0x268 | 原則替代指定的應簽署部分與需要的部分不同。 |
The policy alternative specified a different part to sign than was required. |
| 0x269 | 原則替代指定的一種以上的 X.509 權杖參照方法。 |
The policy alternative specified more than one way of referencing the X.509 token. |
| 0x26A | 原則替代未包含必要的安全對話權杖。 |
The policy alternative did not contain a secure conversation token but one was required. |
| 0x26B | 原則需要衍生金鑰，但是不支援。 |
The policy required a derived key but it is not supported. |
| 0x26C | 原則需要外部 URI 參照，但是不支援。 |
The policy required an external URI reference but it is not supported. |
| 0x26D | 原則替代指定的安全對話權杖版本與需要的版本不同。 |
The policy alternative specified a different secure conversation token version than the one required. |
| 0x26E | 原則替代指定的 Entropy 設定與需要的設定不同。 |
The policy alternative specified different entropy settings than the one required. |
| 0x26F | 指定的逾時值太大。 |
The specified timeout value is too large. |
| 0x270 | %1 毫秒後操作逾時。 |
The operation timed out after %1 milliseconds. |
| 0x271 | 尚未傳送訊息的開頭。 |
The start of the message has not yet been sent. |
| 0x272 | 尚未收到訊息的開頭。 |
The start of the message has not yet been received. |
| 0x273 | 訊息不是通道預期的訊息物件。 |
The message was a different message object than expected by the channel. |
| 0x274 | 當通道處於串流處理模式時，才可以使用內容。 |
The property is only available when the channel is in streaming mode. |
| 0x275 | 當通道處於已緩衝模式時，才可以使用內容。 |
The property is only available when the channel is in buffered mode. |
| 0x276 | 正在中止服務主機。 |
Service Host is aborting. |
| 0x277 | 指定的操作內容物件無效。 |
The operation context object specified is invalid. |
| 0x278 | 傳遞的 serviceHost 參數無效。 |
The serviceHost parameter passed in is invalid. |
| 0x279 | 引數 'value' 不可以是 NULL。 |
Argument 'value' cannot be NULL. |
| 0x27A | 引數 'endpoints' 不可以是 NULL。 |
Argument 'endpoints' cannot be NULL. |
| 0x27B | 引數 'address' 不可以是 NULL。 |
Argument 'address' cannot be NULL. |
| 0x27C | 引數 'operationDescription' 不可以是 NULL。 |
Argument 'operationDescription' cannot be NULL. |
| 0x27D | 傳回訊息中的動作與操作說明不相符。 |
Action in the return message does not match the operation description. |
| 0x27E | 服務操作的 'heap' 引數不可以是 NULL。 |
'heap' argument cannot be NULL for a service operation. |
| 0x27F | 指定通道的預設訊息處理常式時，並行處理不可以大於 1。 |
When a default message handler on a channel is specified concurrency cannot be greater than one. |
| 0x280 | 非工作階段通道的並行處理不可以大於 1。 |
Non session based Channels cannot have concurrency greater than one. |
| 0x281 | soap.udp 配置需要連接埠號碼。 |
The soap.udp scheme requires a port number. |
| 0x282 | 這個平台不支援在沒有先中止 HTTP 接聽程式的情況下，於接受操作期間中止這種類型的通道。 |
Aborting this type of channel during an accept operation without first aborting the HTTP listener is not supported on this platform. |
| 0x283 | 這個平台不支援中止含擱置中傳送或接收的 HTTP 回覆通道。 |
Aborting an HTTP reply channel with a pending send or receive is not supported on this platform. |
| 0x284 | 這個平台不支援串流的輸出傳輸模式。 |
The streamed output transfer mode is not supported on this platform. |
| 0x285 | 無法開啟輸入通道。 |
An input channel can not be opened. |
| 0x286 | 無法設定通訊端選項 (等級 %1 與選項 %2)。 |
Unable to set socket option (level %1 and option %2). |
| 0x287 | 無法設定通訊端的 Keep Alive 設定值。 |
Unable to set the keep alive setting for the socket. |
| 0x288 | 因為通道尚未設定多點傳送的功能，所以無法設定內容。 |
The property can not be set because the channel has not been configured for multicast. |
| 0x289 | 通道已設定多點傳送的功能，但是未指定特定的位址。 |
The channel has been configured for multicast, but a specific address was not specified. |
| 0x28A | 將 IP 位址轉換成字串時發生錯誤。 |
There was an error converting the IP address to a string. |
| 0x28B | 在端點位址中發現多個端點識別元素。 |
Multiple endpoint identity elements were found in endpoint address. |
| 0x28C | 端點識別元素無效。 |
Invalid endpoint identity element. |
| 0x28D | 端點識別無效。 |
Invalid endpoint identity. |
| 0x28E | 傳遞的 'serviceProxy' 參數無效。 |
The 'serviceProxy' parameter passed in is invalid. |
| 0x28F | 目前的服務 Proxy 狀態 '%1' 不適用於要求的操作。 |
The current service proxy state '%1' was not appropriate for the requested operation. |
| 0x290 | 已經呼叫 'WsAbortServiceProxy'，因此正在中止服務 Proxy。 |
'WsAbortServiceProxy' was called, as a result Service Proxy is aborting. |
| 0x291 | 已放棄服務 Proxy 上的呼叫。 |
The call on the service proxy is abandoned. |
| 0x292 | 元素描述類型不正確。 |
Incorrect element description type. |
| 0x293 | 呼叫的逾時已到期，因此放棄呼叫。 |
The timeout for the call expired, the call has been abandoned as a result. |
| 0x294 | 不支援處理指示。 |
Processing instructions are not supported. |
| 0x295 | 宣告的屬性 '%1:%2' 無效。 |
The attribute '%1:%2' is not valid on a declaration. |
| 0x296 | 宣告需要屬性 'version'。 |
The attribute 'version' is required on a declaration. |
| 0x297 | 宣告中值為 '%1' 的屬性 'version' 無效。值必須是 '1.0'。 |
The attribute 'version' with value '%1' is not valid on a declaration. The value must be '1.0'. |
| 0x298 | 宣告中值為 '%1' 的屬性 'standalone' 無效。值必須是 'yes' 或 'no'。 |
The attribute 'standalone' with value '%1' is not valid on a declaration. The value must be 'yes' or 'no' on a declaration. |
| 0x299 | 宣告的屬性 '%1' 無效。 |
The attribute '%1' is not valid on a declaration. |
| 0x29A | 在 xml 宣告指定的編碼屬性不符合指定給讀取器的編碼。 |
The encoding attribute specified on the xml declaration does not match the encoding specified for the reader. |
| 0x29B | 宣告中值為 '%1' 的屬性 'encoding' 無效。值必須是'utf8'、'utf-16'、'utf-16le' 或 'utf-16be'。 |
The attribute 'encoding' with value '%1' is not valid on a declaration. The value must be one of 'utf8', 'utf-16', 'utf-16le' or 'utf-16be'. |
| 0x29C | 文件已編碼為 utf-16LE 或 utf16-BE，但是長度無效。長度必須是 2 的倍數。 |
The document is encoded as utf-16LE or utf16-BE but has an invalid length. The length must be a multiple of two. |
| 0x29D | 這個通道繫結不支援安全性。 |
Security is not supported for this channel binding. |
| 0x29E | 提供的安全性描述空白。 |
The security description supplied is empty. |
| 0x29F | 安全性描述中的安全性繫結重複。 |
A security binding was repeated in the security description. |
| 0x2A0 | 安全性描述中的安全性繫結無效。 |
Invalid security binding in security description. |
| 0x2A1 | 這個安全性設定對用戶端而言是無效的。 |
This security setting is invalid for client. |
| 0x2A2 | 這個安全性設定對伺服器而言是無效的。 |
This security setting is invalid for server. |
| 0x2A3 | 這個繫結不支援自訂識別。 |
Custom identities are not supported for this binding. |
| 0x2A4 | 安全性內容不適用於選擇的安全性繫結。 |
The security properties are not applicable to the chosen security bindings. |
| 0x2A5 | 指定的安全性繫結使用方式 ('%1') 不適用於安全性描述中所指定的訊息安全性繫結 ('%2')。 |
The specified security binding usage ('%1') is not applicable for the specified message security binding ('%2') in security description. |
| 0x2A6 | 指定的訊息安全性繫結只能在保護訊息時與其他繫結 (例如 SSL 繫結) 一起使用。 |
The specified message security binding can only be used with an additional binding (such as the SSL binding) for message protection. |
| 0x2A7 | 需要使用者名稱認證，但是未提供。 |
Username credential is required, but not supplied. |
| 0x2A8 | 指定的 WS_REQUEST_SECURITY_TOKEN_ACTION 無效。 |
The specified WS_REQUEST_SECURITY_TOKEN_ACTION is invalid. |
| 0x2A9 | 權杖要求不支援金鑰大小規格，或者該規格無效。 |
Unsupported or invalid key size specification for token request. |
| 0x2AA | 權杖要求不支援金鑰類型規格，或者該規格無效。 |
Unsupported or invalid key type specification for token request. |
| 0x2AB | WsRequestSecurityToken 需要安全通道。 |
A secure channel is required for WsRequestSecurityToken. |
| 0x2AC | 收到的 RequestSecurityToken 訊息包含不正確的要求類型。 |
The RequestSecurityToken message received contained an incorrect request type. |
| 0x2AD | 收到的 RequestSecurityToken 訊息格式錯誤。 |
The RequestSecurityToken message received was not in the correct format. |
| 0x2AE | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。 |
The RequestSecurityTokenResponse message received was not in the correct format. |
| 0x2AF | 收到的 RequestSecurityTokenResponse 訊息包含重複的元素。 |
The RequestSecurityTokenResponse message received contained a duplicate element. |
| 0x2B0 | 傳回的發行權杖金鑰類型不符合要求的金鑰類型。 |
The key type of the issued token returned did not match the requested key type. |
| 0x2B1 | 傳回的發行權杖金鑰大小不符合需求。 |
The key size of the issued token returned did not match the requirements. |
| 0x2B2 | 發行權杖的要求金鑰大小不符合需求。 |
The requested key size for the issued token did not match the requirements. |
| 0x2B3 | RequestSecurityToken 與 RequestSecurityTokenResponse 訊息之間的內容屬性不相符。 |
The context attribute did not match between RequestSecurityToken and RequestSecurityTokenResponse messages. |
| 0x2B4 | 伺服器傳回的權杖尚未生效。收到權杖時，它們必須是有效的。 |
The server returned a token that is not yet valid. Tokens must be valid when they are received. |
| 0x2B5 | 伺服器傳回的權杖太早到期而無法使用，或者權杖早已到期。 |
The server returned a token that expires too soon to be usable or that has already expired. |
| 0x2B6 | WS_TRUST_VERSION '%1' 無效或不支援。 |
The WS_TRUST_VERSION '%1' is not valid or not supported. |
| 0x2B7 | WS_SECURE_CONVERSATION_VERSION '%1' 無效或不支援。 |
The WS_SECURE_CONVERSATION_VERSION '%1' is not valid or not supported. |
| 0x2B8 | 無法產生隨機數字。 |
Unable to generate a random number. |
| 0x2B9 | 應用程式與啟動程序安全性的設定不相容。 |
The configuration of the application and bootstrap security are incompatible. |
| 0x2BA | 關閉資訊安全內容時無法執行信任交換。 |
Cannot perform trust exchange while the security context is being closed. |
| 0x2BB | 因為已經停止更新，所以無法更新資訊安全內容繫結的資訊安全內容。 |
Unable to renew security context of the security context binding as renew is disabled. |
| 0x2BC | 對要求的操作而言，資訊安全內容繫結的資訊安全內容狀態是無效的。 |
The security context of the security context binding was in an invalid state for the requested operation. |
| 0x2BD | 通道必須至少接收一個訊息，才能傳送訊息。 |
The channel must receive at least one message before it can be used to send messages. |
| 0x2BE | 伺服器已經拒絕由資訊安全內容繫結所提供的資訊安全內容。 |
The server rejected the security context provided by the security context binding. |
| 0x2BF | 更新權杖時需要設定 WS_REQUEST_SECURITY_TOKEN_PROPERTY_EXISTING_TOKEN。 |
Renewing a token requires WS_REQUEST_SECURITY_TOKEN_PROPERTY_EXISTING_TOKEN to be set. |
| 0x2C0 | WS_REQUEST_SECURITY_TOKEN_PROPERTY_EXISTING_TOKEN 不可以與 WS_REQUEST_SECURITY_TOKEN_ACTION_ISSUE 或 WS_REQUEST_SECURITY_TOKEN_ACTION_NEW_CONTEXT 一起設定。 |
WS_REQUEST_SECURITY_TOKEN_PROPERTY_EXISTING_TOKEN may not be set with WS_REQUEST_SECURITY_TOKEN_ACTION_ISSUE or WS_REQUEST_SECURITY_TOKEN_ACTION_NEW_CONTEXT. |
| 0x2C1 | WS_TRUST_VERSION_FEBRUARY_2005 不支援 bearer 金鑰類型做為要求參數。 |
WS_TRUST_VERSION_FEBRUARY_2005 does not support bearer key types as a request parameter. |
| 0x2C2 | 需要 XML 格式的權杖，但是未提供。 |
The XML form of the token is required, but not supplied. |
| 0x2C3 | 需要 XML 格式的權杖連結參照，但是未提供。 |
The XML form of the token's attached reference is required, but not supplied. |
| 0x2C4 | 提供的安全性金鑰類型無效。 |
The security key type supplied is invalid. |
| 0x2C5 | 只有 Windows Vista 以及更新的平台才支援 NCRYPT 金鑰控制代碼。 |
NCRYPT key handle is supported only on Windows Vista and later platforms. |
| 0x2C6 | 只有在 Windows Vista 之前的平台上才支援 CAPI 金鑰控制代碼。 |
CAPI key handle is supported only on pre-Windows Vista platforms. |
| 0x2C7 | 提供的對稱安全性金鑰無效。 |
The symmetric security key supplied is invalid. |
| 0x2C8 | 提供給 XML 權杖的 WS_XML_BUFFER 必須剛好只有一個最上層元素。 |
Exactly one top level element must be present in the WS_XML_BUFFER supplied for XML tokens. |
| 0x2C9 | WS_XML_TOKEN_MESSAGE_SECURITY_BINDING 中遺漏必要的 XML 權杖。 |
The required XML token is missing from WS_XML_TOKEN_MESSAGE_SECURITY_BINDING. |
| 0x2CA | WS_XML_TOKEN_MESSAGE_SECURITY_BINDING 中提供的權杖類型錯誤。 |
The token supplied in the WS_XML_TOKEN_MESSAGE_SECURITY_BINDING is of the wrong type. |
| 0x2CB | WsRequestSecurityToken 中提供的權杖類型錯誤。 |
The token supplied in WsRequestSecurityToken is of the wrong type. |
| 0x2CD | WS_SAML_MESSAGE_SECURITY_BINDING 只能在伺服器端使用。 |
The WS_SAML_MESSAGE_SECURITY_BINDING may be used only on the server side. |
| 0x2CE | 在 WS_SAML_MESSAGE_SECURITY_BINDING 指定的 WS_SAML_AUTHENTICATOR 無效。 |
The WS_SAML_AUTHENTICATOR specified in WS_SAML_MESSAGE_SECURITY_BINDING in invalid. |
| 0x2CF | 操作的安全性演算法無效。 |
Invalid security algorithm for operation. |
| 0x2D0 | SAML 宣告無效。 |
Invalid SAML assertion. |
| 0x2D1 | SAML 宣告版本無效。 |
Invalid SAML assertion version. |
| 0x2D2 | 無法解密 SAML 證明金鑰。該金鑰無效。 |
Unable to decrypt the SAML proof key. The key was invalid. |
| 0x2D3 | 金鑰解密失敗。 |
Key decryption failed. |
| 0x2D4 | 金鑰識別碼無效。 |
Invalid key identifier. |
| 0x2D5 | 指定的對稱金鑰無效。 |
The asymmetric key specified s invalid. |
| 0x2D6 | 無法載入私密金鑰。 |
Unable to load the private key. |
| 0x2D7 | 無法載入憑證的私密金鑰。 |
Unable to load the private key for the certificate. |
| 0x2D8 | 無法載入憑證的公開金鑰。 |
Unable to load the public key for the certificate. |
| 0x2D9 | 無法取得對稱金鑰的金鑰大小。 |
Unable to get the key size of the asymmetric key. |
| 0x2DA | 無法建立密碼編譯雜湊。 |
Unable to create cryptographic hash. |
| 0x2DB | 無法對資料進行雜湊。 |
Unable to hash data. |
| 0x2DC | 無法簽署資料的雜湊。 |
Unable to sign hash of data. |
| 0x2DD | 使用訊息簽章時，時間戳記使用方式不能是 WS_SECURITY_TIMESTAMP_USAGE_NEVER。 |
When a message signature is used, the timestamp usage cannot be WS_SECURITY_TIMESTAMP_USAGE_NEVER. |
| 0x2DE | 遺漏執行加密編譯操作時必要的私密金鑰。 |
Required private key missing for performing a cryptographic operation. |
| 0x2DF | 權杖引數不可以是 NULL。 |
The token argument cannot be NULL. |
| 0x2E0 | 提供的使用者名稱認證無效。 |
The username credential supplied is invalid. |
| 0x2E1 | 在認證中提供的使用者名稱不可以空白。 |
The username supplied in the credential cannot be empty. |
| 0x2E2 | 需要 WS_VALIDATE_PASSWORD_CALLBACK，但是未提供。 |
WS_VALIDATE_PASSWORD_CALLBACK is required, but not supplied. |
| 0x2E3 | 安全性繫結中的憑證認證規格無效。 |
Invalid certificate credential specification in security binding. |
| 0x2E4 | 只有 Windows Vista 和更新的版本才提供自訂憑證認證的簽發者清單回呼功能。 |
The issuer list callback feature of custom cert credential is available only on Windows Vista and above. |
| 0x2E5 | 安全性繫結中的指紋憑證認證規格無效。 |
Invalid thumbprint certificate credential specification in security binding. |
| 0x2E6 | 在安全性描述中，HTTPS URI 配置必須與 WS_SSL_TRANSPORT_SECURITY_BINDING 一起使用。 |
An HTTPS URI scheme must be used along with a WS_SSL_TRANSPORT_SECURITY_BINDING in the security description. |
| 0x2E7 | 在伺服器上使用 WS_SSL_TRANSPORT_SECURITY_BINDING 時，localCertCredential 必須是 NULL。必須使用 httpcfg.exe 之類的工具，在 HTTP.sys 設定中指定伺服器憑證。 |
When using WS_SSL_TRANSPORT_SECURITY_BINDING on the server, localCertCredential must be NULL. The server certificate must be specified in HTTP.sys configuration using a tool such as httpcfg.exe. |
| 0x2E8 | 針對 SSL，只允許預設 (簽章和加密) 保護等級。 |
For SSL, only the default (sign + encrypt) protection level is allowed. |
| 0x2E9 | 針對 HTTP 標頭驗證，WS_SSL_TRANSPORT_SECURITY_BINDING 也必須包括在安全性描述中以便保護傳輸 (偏好選項)，或者安全性描述內容 WS_SECURITY_PROPERTY_TRANSPORT_PROTECTION_LEVEL 必須明確設定成 WS_PROTECTION_LEVEL_NONE (不建議)。 |
For HTTP header authentication, either WS_SSL_TRANSPORT_SECURITY_BINDING must also be included in the security description for transport protection (preferred), or the security description property WS_SECURITY_PROPERTY_TRANSPORT_PROTECTION_LEVEL must be explicitly set to WS_PROTECTION_LEVEL_NONE (not recommended). |
| 0x2EA | 在伺服器端，只有 Windows Vista 和更新的版本才支援 HTTP 標頭驗證安全性連繫結。 |
On the server side, the HTTP header authentication security binding is supported only on Windows Vista and above. |
| 0x2EB | 針對 HTTP 標頭驗證，必須在用戶端上指定 Windows 認證。 |
For HTTP header authentication, the Windows credential must be specified only on the client. |
| 0x2EC | 不支援的 HTTP 標頭驗證配置。 |
Unsupported HTTP header authentication scheme. |
| 0x2ED | Passport 標頭驗證配置不可以和其他驗證配置一起使用。 |
Passport header authentication scheme cannot be combined with other authentication schemes. |
| 0x2EE | 只有用戶端支援 Passport 驗證配置。 |
Passport authentication scheme is only supported on the client. |
| 0x2EF | Passport 標頭驗證配置不支援認證類型 '%1'。 |
Passport header authentication scheme does not support the credential type '%1'. |
| 0x2F1 | 無法啟用 WinHTTP Passport 驗證支援。 |
Unable to enable the WinHTTP Passport authentication support. |
| 0x2F2 | WS_HTTP_HEADER_AUTH_SECURITY_BINDING 遺漏必要的用戶端認證。 |
Required client credentials are missing for WS_HTTP_HEADER_AUTH_SECURITY_BINDING. |
| 0x2F3 | 只有基礎配置才支援在串流輸出傳輸模式下進行 HTTP 標頭驗證。 |
The streamed output transfer mode is supported with HTTP header authentication only for the basic scheme. |
| 0x2F4 | 無法設定 HTTP 伺服器驗證需求。 |
Unable to set HTTP server authentication requirements. |
| 0x2F5 | 無法在 HTTP 要求上設定安全性旗標。 |
Unable to set security flags on HTTP request. |
| 0x2F6 | 無法在 HTTP 要求上設定連線數目上限選項。 |
Unable to set maximum connections option on HTTP request. |
| 0x2F7 | 無法針對 HTTP 要求上的 SSL 設定安全通訊協定。 |
Unable to set secure protocols for SSL on HTTP request. |
| 0x2F8 | HTTP 用戶端連線數目上限不可以為 0。 |
Maximum HTTP client connections limit cannot be zero. |
| 0x2F9 | 嘗試在儲存位置 '%1' 的存放區 '%2' 尋找憑證 '%3' 時發生錯誤。 |
There was an error when trying to find certificate '%3' in store '%2' at store location '%1'. |
| 0x2FB | 嘗試在儲存位置 '%1' 的存放區 '%2' 尋找憑證 '%3' 時，找到多個相符的憑證。 |
More than one match when trying to find certificate '%3' in store '%2' at store location '%1'. |
| 0x2FD | 嘗試從回呼取得憑證時發生錯誤。 |
There was an error when trying to get a certificate from callback. |
| 0x2FE | 需要憑證，但已遺失。 |
The certificate is required but missing. |
| 0x2FF | 無法從憑證取得指紋。 |
Unable to get thumbprint from certificate. |
| 0x300 | 無法複製憑證內容。 |
The certificate context could not be duplicated. |
| 0x301 | 無法編碼憑證主體名稱。 |
The certificate subject name could not be encoded. |
| 0x302 | 要求中沒有預期的 HTTP 標頭驗證資訊。 |
The expected HTTP header authentication information was not present in the request. |
| 0x303 | HTTP 標頭驗證資訊無效。 |
The HTTP header authentication information was invalid. |
| 0x304 | 用戶端需要 HTTP 標頭驗證，但是伺服器不支援該驗證。 |
The client requires HTTP header authentication and the server does not support it. |
| 0x305 | 這個要求的 HTTP 標頭驗證失敗: 驗證狀態 '%1'，安全性狀態 '%2'。 |
HTTP header authentication was not successful for this request: auth status '%1', sec status '%2'. |
| 0x306 | 指定給目標伺服器的 WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL 不適用於指定的 HTTP 標頭驗證配置。 |
The specified WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL for the target server is not valid for the specified HTTP header authentication scheme. |
| 0x307 | 指定給 Proxy 伺服器的 WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL 不適用於指定的 HTTP 標頭驗證配置。 |
The specified WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL for the proxy server is not valid for the specified HTTP header authentication scheme. |
| 0x308 | 收到的 SSL 用戶端憑證未通過驗證: CERT_TRUST_STATUS '%1'。 |
The SSL client certificate received did not pass validation: CERT_TRUST_STATUS '%1'. |
| 0x309 | 安全性標頭中並沒有所有必要的安全性權杖。 |
Not all required security tokens were present in the security header. |
| 0x30A | 指定的資訊安全內容不存在。 |
The specified security context does not exist. |
| 0x30B | 已經到達有效的資訊安全內容數目上限。已拒絕目前的內容。 |
The maximum number of active security contexts has been reached. The current context was rejected. |
| 0x30C | 已經更新資訊安全內容的例項。無法再次更新它。只可更新前次更新後所產生的例項。 |
The instance of the security context was already renewed. It cannot be renewed again. Only the instance that resulted from the prior renew can be renewed. |
| 0x30D | 已經撤銷資訊安全內容。 |
The security context was already revoked. |
| 0x30E | 指定的資訊安全內容物件無效。 |
The security context object specified is invalid. |
| 0x30F | 目前更新的資訊安全內容不存在。 |
The security context being renewed does not exist. |
| 0x310 | 嘗試更新無法更新的資訊安全內容。 |
Attempting to renew a security context that cannot be renewed. |
| 0x311 | 用來更新資訊安全內容的身分識別不符合內容建立時所使用的身分識別。 |
The identity used for renewing the security context does not match the identity used when establishing the context. |
| 0x312 | 資訊安全內容權杖參照的資訊安全內容不存在。 |
The security context referenced by the security context token does not exist. |
| 0x313 | SAML 宣告超出它的有效期限。 |
The SAML assertion was outside of its validity duration. |
| 0x314 | 安全性標頭版本 '%1' 無效或不受支援。 |
The security header version '%1' is not valid or not supported. |
| 0x315 | 安全性 Entropy 模式 '%1' 無效或不受支援。 |
The security entropy mode '%1' is not valid or not supported. |
| 0x316 | 安全對話版本 '%1' 無效或不受支援。 |
The secure conversation version '%1' is not valid or not supported. |
| 0x317 | 安全性標頭時間戳記使用方式 '%1' 無效或不受支援。 |
The security header timestamp usage '%1' is not valid or not supported. |
| 0x318 | 安全性標頭配置 '%1' 無效或不受支援。 |
The security header layout '%1' is not valid or not supported. |
| 0x319 | 已同時指定 WS_SECURITY_PROPERTY_ALGORITHM_SUITE_NAME 與 WS_SECURITY_PROPERTY_ALGORITHM_SUITE 內容。只能指定其中一項。 |
Both the WS_SECURITY_PROPERTY_ALGORITHM_SUITE_NAME and the WS_SECURITY_PROPERTY_ALGORITHM_SUITE properties were specified. Only one may be specified. |
| 0x31A | 演算法套件名稱 '%1' 無效或不受支援。 |
The algorithm suite name '%1' is not valid or not supported. |
| 0x31B | 在簽章中找不到 KeyInfo 元素。 |
KeyInfo element was not found in the signature. |
| 0x31C | 提供的金鑰不符合金鑰長度需求。 |
Provided key does not meet the key length requirements. |
| 0x31D | 簽章包含重複的參照。 |
Signature contains a duplicate reference. |
| 0x31E | 簽章無效。 |
Signature is invalid. |
| 0x31F | 簽章的 KeyInfo 元素無效。 |
KeyInfo element of the signature is invalid. |
| 0x320 | 在簽章中指定的規範化方法無效。 |
Canonicalization method specified in the signature is invalid. |
| 0x321 | 在簽章中指定的簽署方法無效。 |
Signature method specified in the signature is invalid. |
| 0x322 | 在簽章中指定的轉換無效。 |
Transform specified in the signature is invalid. |
| 0x323 | 無法驗證簽章中的參照。 |
A reference in the signature could not be validated. |
| 0x324 | 應該要有安全性時間戳記，但是找不到。 |
Security timestamp was expected but not found. |
| 0x325 | 發現未預期的簽章元素。 |
Unexpected signature element was encountered. |
| 0x326 | 嘗試多次以相同的權杖簽署。 |
Attempted to sign with same token more than once. |
| 0x327 | 不支援訊息層級加密。 |
Message-level encryption is not supported. |
| 0x328 | 發現未預期的時間戳記。 |
Unexpected timestamp was encountered. |
| 0x329 | 在安全性標頭中找不到預期的簽章元素。 |
Expected signature element was not found in the security header. |
| 0x32B | 在安全性描述中指定的任何訊息安全性繫結，並不需要接收訊息中的權杖。 |
Token in received message was not expected by any message security binding specified in the security description. |
| 0x32C | 需要本機名稱為 '%1' 且命名空間為 '%2' 的安全性標頭，但是在訊息中找不到。傳送者那邊可能未設定訊息安全性。 |
A security header with local name '%1' and namespace '%2' was required, but was not present in the message. The sender may not have been configured with message security. |
| 0x32D | 需要 SSL 用戶端憑證，但是找不到。 |
An SSL client certificate was required, but not presented. |
| 0x32E | 叫用使用者名稱/密碼驗證回呼時發生錯誤。 |
There was an error while invoking the username/password validation callback. |
| 0x32F | 驗證訊息中提供的使用者名稱/密碼配對失敗。 |
Authentication failed for the username/password pair supplied in the message. |
| 0x330 | 叫用 SAML 驗證回呼時發生錯誤。 |
There was an error while invoking the SAML validation callback. |
| 0x331 | 驗證訊息中收到的 SAML 宣告失敗。 |
Authentication failed for the SAML assertion received in the message. |
| 0x332 | 目前的通道安全性設定沒有要求的安全性內容識別碼 '%1'。 |
The requested security property ID '%1' is not available for the current channel security settings. |
| 0x333 | 指定的輸出類型 '%1' 無效。 |
The specified output type '%1' is invalid. |
| 0x334 | 指定的輸入類型 '%1' 無效。 |
The specified input type '%1' is invalid. |
| 0x335 | 用戶端服務操作不支援指定的類型 '%1'。 |
The specified type '%1' is not supported for client side service operations. |
| 0x336 | 指定的參數類型 '%1' 無效。 |
The specified parameter type '%1' is invalid. |
| 0x337 | 叫用服務授權回呼時發生錯誤。 |
There was an error while invoking the service authorization callback. |
| 0x338 | 拒絕存取服務。 |
Access denied to the service. |
| 0x339 | 引數 'cancelCallback' 不可以是 NULL。 |
Argument 'cancelCallback' cannot be NULL. |
| 0x33A | WS_SERVICE_ENDPOINT 的內容 'WS_SERVICE_ENDPOINT_PROPERTY_MAX_ACCEPTING_CHANNELS' 不可以為 '0'。 |
Cannot have '0' for property 'WS_SERVICE_ENDPOINT_PROPERTY_MAX_ACCEPTING_CHANNELS' on the WS_SERVICE_ENDPOINT. |
| 0x33B | 當 WS_OPERATION_DESCRIPTION 的 parameterDescription 為 NULL 時，參數描述計數為 %1。 |
The count for parameter description is %1 while parameterDescription is NULL on WS_OPERATION_DESCRIPTION. |
| 0x33C | 參數計數為 0，但是 WS_OPERATION_DESCRIPTION 的 'parameterDescription' 並不是 NULL。 |
Parameter count is zero but the 'parameterDescription' on WS_OPERATION_DESCRIPTION is non NULL. |
| 0x33D | 中繼資料版本 '%1' 不符合執行階段版本 '%2'。 |
The metadata version '%1' does not match the runtime version '%2'. |
| 0x33E | WS_OPERATION_DESCRIPTION 的 'stubCallback' 不可以是 NULL。 |
'stubCallback' on the WS_OPERATION_DESCRIPTION cannot be NULL. |
| 0x33F | WS_OPERATION_DESCRIPTION 的 'inputMessageDescription' 不可以是 NULL。 |
'inputMessageDescription' on the WS_OPERATION_DESCRIPTION cannot be NULL. |
| 0x340 | 指定的通道類型 %1 無法支援雙向操作。 |
The given channel type %1 cannot support two way operations. |
| 0x341 | WS_MESSAGE_DESCRIPTION 的 'action' 不可以是 NULL。 |
'action' on the WS_MESSAGE_DESCRIPTION cannot be NULL. |
| 0x342 | WS_MESSAGE_DESCRIPTION 的 'elementDescription' 不可以是 NULL。 |
'elementDescription' on the WS_MESSAGE_DESCRIPTION cannot be NULL. |
| 0x343 | WS_CONTRACT_DESCRIPTION 的 'operations' 不可以是 NULL。 |
'operations' on WS_CONTRACT_DESCRIPTION cannot be NULL. |
| 0x344 | WS_CONTRACT_DESCRIPTION 的 'operationCount' 不可以是 0。 |
'operationCount' on WS_CONTRACT_DESCRIPTION cannot be 0. |
| 0x345 | WS_SERVICE_ENDPOINT 的 'contract' 不可以是 NULL。 |
'contract' on WS_SERVICE_ENDPOINT cannot be NULL. |
| 0x346 | 因為服務 Proxy 的狀態為 '%1'，所以無法釋放它。 |
The service proxy could not be freed because it is in state '%1'. |
| 0x347 | 因為服務主機的狀態為 '%1'，所以無法釋放它。 |
The service host could not be freed because it is in state '%1'. |
| 0x348 | 無法等候 HTTP 連線中斷。 |
Unable to wait for HTTP connection to disconnect. |
| 0x349 | 無法建立 HTTP 伺服器工作階段。 |
Unable to create HTTP server session. |
| 0x34A | 無法將 URL 新增至 HTTP 要求佇列。 |
Unable to add URL to HTTP request queue. |
| 0x34B | 無法建立 HTTP URL 群組。 |
Unable to create HTTP URL group. |
| 0x34C | 無法將 URL 新增至 HTTP URL 群組。 |
Unable to add URL to HTTP URL group. |
| 0x34D | 無法將 URL 繫結至 HTTP 要求佇列。 |
Unable to bind URL to HTTP request queue. |
| 0x34E | 當用戶端仍然等候回覆時，伺服器卻關閉了通道。 |
The server closed the channel, while the client was still expecting a reply. |
| 0x34F | HTTP URL '%1' 無效。 |
The HTTP URL '%1' was not valid. |
| 0x350 | 安全性繫結中的 Windows 用戶端認證規格無效。 |
Invalid windows client credential specification in security binding. |
| 0x351 | 只有 Windows 7 以及更新的版本才支援不透明的 Windows 認證類型。 |
The opaque Windows credential type is supported only on Windows7 and later. |
| 0x352 | 無法複製不透明的 Windows 認證。 |
Unable to duplicate opaque Windows credential. |
| 0x353 | 無效的 Windows 認證類型 '%1'。 |
Invalid windows credential type '%1'. |
| 0x354 | 遺漏認證。 |
Credential is missing. |
| 0x355 | 必須有伺服器主體名稱才能執行相互驗證。 |
The server principal name is required to perform mutual authentication. |
| 0x356 | 這個認證類型不支援要求的安全性封裝。 |
Requested security package is not supported for this credential type. |
| 0x357 | SSP 交涉所處的狀態無法執行要求的操作。 |
The SSP negotiation is not in a state to perform the requested operation. |
| 0x358 | 無法從認證建立 Windows 認證內容。 |
Unable to create windows credential context from credentials. |
| 0x359 | 無法建立 SPN '%1' 的資訊安全內容。 |
Unable to create security context for SPN '%1'. |
| 0x35A | 無法從用戶端的認證來建立資訊安全內容。 |
Unable to create security context from the client's credentials. |
| 0x35B | 無法藉由完成驗證權杖來建立資訊安全內容。 |
Unable to create security context by completing the authentication token. |
| 0x35C | 為建立的資訊安全內容查詢屬性 ('%1') 失敗。 |
Failed to query the attribute ('%1') for the established security context. |
| 0x35D | 無法從建立的資訊安全內容查詢使用者權杖。 |
Unable to query the user token from the established security context. |
| 0x35E | 無法使用建立的資訊安全內容來提供資料機密性。 |
Unable to provide data confidentiality using the established security context. |
| 0x35F | 無法使用建立的資訊安全內容來讀取機密資料。 |
Unable to read confidential data using the established security context. |
| 0x360 | 無法使用建立的資訊安全內容來提供資料完整性。 |
Unable to provide data integrity using the established security context. |
| 0x361 | 無法使用建立的資訊安全內容來驗證資料完整性。 |
Unable to verify data integrity using the established security context. |
| 0x362 | 無法保護應用程式記憶體中的純文字密碼。 |
Failed to protect the clear text secret in the application memory. |
| 0x363 | 無法從保護的密碼中還原純文字密碼。 |
Failed to recover the clear text secret from the protected secret. |
| 0x364 | 無法為建立的資訊安全內容交涉資料完整性支援。 |
Unable to negotiate data integrity support for the established security context. |
| 0x365 | 無法為建立的資訊安全內容交涉資料機密性支援。 |
Unable to negotiate data confidentiality support for the established security context. |
| 0x366 | 無法使用 SSP '%1' 封裝為建立的資訊安全內容執行相互驗證。 |
Unable to perform mutual authentication using SSP '%1' package for the established security context. |
| 0x367 | 指定的模擬等級值 '%1' 無效。 |
The specified impersonation level value '%1' is invalid. |
| 0x368 | 指定的保護等級值 '%1' 無效。 |
The specified protection level value '%1' is invalid. |
| 0x369 | 指定的 Windows SSP 封裝值 '%1' 無效。 |
The specified Windows SSP package value '%1' is invalid. |
| 0x36A | 無法為建立的資訊安全內容交涉識別模擬等級。 |
Unable to negotiate identify impersonation level for the established security context. |
| 0x36B | 無法為建立的資訊安全內容交涉委派模擬等級。 |
Unable to negotiate delegate impersonation level for the established security context. |
| 0x36C | 無法為建立的資訊安全內容交涉模擬的模擬等級。 |
Unable to negotiate impersonate impersonation level for the established security context. |
| 0x36D | 無法為建立的資訊安全內容交涉匿名的模擬等級。 |
Unable to negotiate anonymous impersonation level for the established security context. |
| 0x36E | 伺服器不允許匿名用戶端。 |
Server does not allow anonymous clients. |
| 0x36F | NegotiateStream 交握框架 (類型: '%1') 中指定的裝載大小 '%2' 小於預期的值。 |
The specified payload size '%2' in the NegotiateStream handshake frame (type: '%1') is smaller than expected. |
| 0x370 | 用戶端在初始化交握通訊協定之前收到了 NegotiateStream 框架。 |
The client received NegotiateStream frame prior to initiating the handshake protocol. |
| 0x371 | NegotiateStream 交握框架 (類型: '%1') 中指定的裝載大小 '%2' 並不是預期的大小。 |
The specified payload size '%2' in the NegotiateStream handshake frame (type: '%1') is unexpected. |
| 0x372 | NegotiateStream 交握框架中指定的交握類型 '%1' 無效。 |
The specified handshake type '%1' in the NegotiateStream handshake frame is invalid. |
| 0x373 | NegotiateStream 資料裝載超出限制的大小。 |
The NegotiateStream data payload is larger than the limit. |
| 0x374 | 不支援 NegotiateStream 交握框架 (類型: '%1') 中指定的版本 (主要: %2，次要: %3)。 |
the specified version (Major: %2, Minor: %3) in the NegotiateStream handshake frame (type: '%1') is not supported. |
| 0x375 | 收到的 NegotiateStream 錯誤交握框架指出驗證失敗。 |
Received NegotiateStream error handshake frame indicating authentication failure. |
| 0x376 | NegotiateStream 驗證失敗。 |
NegotiateStream authentication failed. |
| 0x377 | NegotiateStream 框架升級失敗。 |
The NegotiateStream framing upgrade failed. |
| 0x378 | 不支援指定的安全性演算法 '%1'。 |
The specified security algorithm '%1' is not supported. |
| 0x379 | 不支援指定的安全性演算法識別碼 '%1'。 |
The specified security algorithm id '%1' is not supported. |
| 0x37A | 指定的安全性演算法識別碼 '%1' 不適用於要求的操作。 |
The specified security algorithm id '%1' is not valid for the requested operation. |
| 0x37B | 'WS_SECURITY_ALGORITHM_SUITE' 內容結構不支援指定內容 ('properties' 欄位必須是 NULL 而且 'propertyCount' 欄位必須是 0)。 |
'WS_SECURITY_ALGORITHM_SUITE' property structure does not support specifying properties ('properties' field must be NULL and 'propertyCount' field must be 0). |
| 0x37C | 指定的對稱金鑰大小 '%1' 下限太小。 |
The specified minimum symmetric key size '%1' is too small. |
| 0x37D | 指定的對稱金鑰大小 '%1' 上限太大。 |
The specified maximum symmetric key size '%1' is too big. |
| 0x37E | 指定的非對稱金鑰大小 '%1' 下限太小。 |
The specified minimum asymmetric key size '%1' is too small. |
| 0x37F | 指定的非對稱金鑰大小 '%1' 上限太大。 |
The specified maximum asymmetric key size '%1' is too big. |
| 0x380 | 無法使用安全性演算法 '%1' 搭配對稱金鑰來簽署資料。 |
Failed to sign data using the security algorithm '%1' with a symmetric key. |
| 0x381 | 無法使用安全性演算法 '%1' 進行資料的摘要操作。 |
Failed to digest data using the security algorithm '%1'. |
| 0x382 | 指定的安全性演算法 '%1' 不可以用於摘要操作。 |
The specified security algorithm '%1' cannot be used for digest operation. |
| 0x383 | 指定的安全性演算法 '%1' 不可以用於對稱簽章操作。 |
The specified security algorithm '%1' cannot be used for symmetric signature operation. |
| 0x384 | 指定的安全性演算法 '%1' 不可以用於非對稱簽章操作。 |
The specified security algorithm '%1' cannot be used for asymmetric signature operation. |
| 0x385 | 已同時從多個執行緒叫用單一執行緒物件，或者從相同的執行緒重新輸入。 |
The single-threaded object was invoked from multiple threads simultaneously, or was re-entered from the same thread. |
| 0x386 | localName 為 '%1' 而且命名空間為 '%2' 的元素不可以明確寫入 MTOM 寫入器。 |
The element with localName '%1' with the namespace '%2' cannot explicitly be written to an MTOM writer. |
| 0x387 | MTOM 寫入器已經產生 MIME 部分，因此不會再寫入其他的 XML 文件。 |
The MTOM writer has generated the MIME parts so no more of the XML document may be written. |
| 0x388 | MTOM 寫入器必須關閉所有開啟的元素，然後才可以要求這個內容。 |
The MTOM writer must close all open elements before requesting this property. |
| 0x389 | MIME-Version 標頭應該是 '1.0'。 |
The MIME-Version header should be '1.0'. |
| 0x38A | 應該要有 Content-Type 標頭 '%1'，但是找到的是 '%2'。 |
The Content-Type header '%1' was expected, but '%2' was found. |
| 0x38B | 應該要有含類型參數 '%1' 的 Content-Type 標頭，但找到的是 '%2'。 |
The Content-Type header with type parameter '%1' was expected, but '%2' was found. |
| 0x38C | 應該要有 Content-Transfer-Encoding 標頭 '%1'，但找到的是 '%2'。 |
The Content-Transfer-Encoding header '%1' was expected, but '%2' was found. |
| 0x38D | MIME 邊界字串 '%1' 無效。它的長度是 0、小於 70 個字元，或包含無效的字元。 |
The MIME boundary string '%1' is invalid. It is either zero length, longer than 70 characters, or contains an invalid character. |
| 0x38E | 字元 '%1' 無法剖析為以十六進位編碼的無正負號 32 位元整數，或者它的值超出無正負號 32 位元整數的範圍。 |
The characters '%1' either cannot be parsed as an unsigned 32 bit integer encoded in hexadecimal, or its value is out of range of an unsigned 32 bit integer. |
| 0x38F | 值 '%1' 不是有效的 Content-ID URL (cid)。 |
The value '%1' is not a valid Content-ID URL (cid). |
| 0x390 | 找不到 MIME 部分 '%1'。 |
The MIME part '%1' was not found. |
| 0x391 | 參照 MIME 部分 '%1' 一次以上。 |
The MIME part '%1' was referenced more than once. |
| 0x392 | XOP Include 元素的屬性 '%1' 必須是 'http://www.w3.org/2004/08/xop/include' 以外的合格命名空間。 |
The attribute '%1' on the XOP Include element must be namespace qualified from a namespace other than 'http://www.w3.org/2004/08/xop/include'. |
| 0x393 | Include 元素只能包含 'http://www.w3.org/2004/08/xop/include' 以外的合格命名空間元素。 |
The Include element may only contain namespace qualified elements from a namespace other than 'http://www.w3.org/2004/08/xop/include'. |
| 0x394 | Include 元素未包含 href 屬性。 |
The Include element does not contain an href attribute. |
| 0x395 | Content-ID '%1' 出現在多個 MIME 部分。 |
The Content-ID '%1' appears in multiple MIME parts. |
| 0x396 | 當 start、start-info 以及 boundary 是從 MIME 標頭讀取時，便不可以指定它們。 |
The start, start-info, and boundary should not be specified when they are to be read from the MIME header. |
| 0x397 | 已經超出文件的 MIME 部分 (%1) 數目上限。 |
The maximum number of MIME parts (%1) for the document was exceeded. |
| 0x398 | 比文件 (%1) 的 MIME 部分大小上限多出 (%2) 個位元組。 |
The maximum size of the MIME parts for the document (%1) was exceeded by (%2) bytes. |
| 0x399 | 包含指定金鑰的項目已經存在字典中。 |
An entry with the specified key already exists in the dictionary. |
| 0x39A | 已經超出字典項目數目上限。 |
The maximum number of dictionary entries was exceeded. |
| 0x39B | WS_PARAMETER_TYPE_MESSAGES 不允許搭配任何其他類型的參數。 |
WS_PARAMETER_TYPE_MESSAGES are not allowed with any other type of parameters. |
| 0x39C | 在 ('%1') 的 WS_PARAMETER_DESCRIPTION 中指定的欄位索引有一個索引 ('%2')。針對輸入 WS_MESSAGE_DESCRIPTION 的指定 WS_ELEMENT_DESCRIPTION 而言，該索引值大於 WS_STRUCT_DESCRIPTION 中呈現的欄位總數。 |
The field index specified in WS_PARAMETER_DESCRIPTION at ('%1') has an index ('%2') which is greater than the total fields present in the WS_STRUCT_DESCRIPTION for the given WS_ELEMENT_DESCRIPTION for the input WS_MESSAGE_DESCRIPTION. |
| 0x39D | NULL WS_FIELD_DESCRIPTION 已經指定給輸入 WS_MESSAGE_DESCRIPTION 的 WS_ELEMENT_DESCRIPTION 的 WS_STRUCT_DESCRIPTION。 |
A NULL WS_FIELD_DESCRIPTION was specified for the given WS_STRUCT_DESCRIPTION for the given WS_ELEMENT_DESCRIPTION for the input WS_MESSAGE_DESCRIPTION. |
| 0x39E | 只允許一個 WS_PARAMTER_TYPE_MESSAGES 做為 'in' 參數。 |
Only one WS_PARAMTER_TYPE_MESSAGES is allowed as an 'in' parameter. |
| 0x39F | 只允許一個 WS_PARAMTER_TYPE_MESSAGES 做為 'out' 參數。 |
Only one WS_PARAMTER_TYPE_MESSAGES is allowed as an 'out' parameter. |
| 0x3A0 | 在 ('%1') 的 WS_PARAMETER_DESCRIPTION 中指定的欄位索引有一個索引 ('%2')。針對輸出 WS_MESSAGE_DESCRIPTION 的指定 WS_ELEMENT_DESCRIPTION 而言，該索引值大於 WS_STRUCT_DESCRIPTION 中呈現的欄位總數。 |
The field index specified in WS_PARAMETER_DESCRIPTION at ('%1') has an index ('%2') which is greater than the total fields present in the WS_STRUCT_DESCRIPTION for the given WS_ELEMENT_DESCRIPTION for the output WS_MESSAGE_DESCRIPTION. |
| 0x3A1 | NULL WS_FIELD_DESCRIPTION 已經指定給輸出 WS_MESSAGE_DESCRIPTION 的 WS_ELEMENT_DESCRIPTION 的 WS_STRUCT_DESCRIPTION。 |
A NULL WS_FIELD_DESCRIPTION was specified for the given WS_STRUCT_DESCRIPTION for the given WS_ELEMENT_DESCRIPTION for the output WS_MESSAGE_DESCRIPTION. |
| 0x3A2 | 當服務操作依據 WS_PARAMETER_DESCRIPTION 而使用 'in' 參數時，會指定 NULL WS_MESSAGE_DESCRIPTION。 |
A NULL WS_MESSAGE_DESCRIPTION is specified when the service operation has 'in' parameter(s) as per the WS_PARAMETER_DESCRIPTION. |
| 0x3A3 | 已經為輸入 WS_MESSAGE_DESCRIPTION 的 WS_ELEMENT_DESCRIPTION 指定 NULL WS_STRUCT_DESCRIPTION。 |
A NULL WS_STRUCT_DESCRIPTION is specified for the WS_ELEMENT_DESCRIPTION for the input WS_MESSAGE_DESCRIPTION. |
| 0x3A4 | 類型 WS_PARAMETER_TYPE_MESSAGES 的參數不可以是 'in/out'。 |
A parameter of type WS_PARAMETER_TYPE_MESSAGES cannot be 'in/out'. |
| 0x3A5 | 當服務操作依據 WS_PARAMETER_DESCRIPTION 而使用 'out' 參數時，會指定 NULL WS_MESSAGE_DESCRIPTION。 |
A NULL WS_MESSAGE_DESCRIPTION is specified when the service operation has 'out' parameter(s) as per the WS_PARAMETER_DESCRIPTION. |
| 0x3A6 | 已經為輸出 WS_MESSAGE_DESCRIPTION 的 WS_ELEMENT_DESCRIPTION 指定 NULL WS_STRUCT_DESCRIPTION。 |
A NULL WS_STRUCT_DESCRIPTION is specified for the WS_ELEMENT_DESCRIPTION for the output WS_MESSAGE_DESCRIPTION. |
| 0x3A7 | 已經啟動規範化。 |
Canonicalization has already been started. |
| 0x3A8 | 未啟動規範化。 |
Canonicalization has not been started. |
| 0x3A9 | 指定的 xml 規範化演算法 (%1) 無效。 |
The specified xml Canonicalization Algorithm (%1) is not valid. |
| 0x3AA | 指定要省略的 localName 是空的。 |
The localName specified to be omitted is empty. |
| 0x3AB | 當深度比開始規範化的深度更低時，無法進行規範化。 |
Cannot canonicalize at a depth lower than where Canonicalization was started. |
| 0x3AC | 規範化結束的深度必須與其開始的深度相同。 |
Canonicalization must be ended at the same depth where it was started. |
| 0x3AD | 無法辨識或不支援 %1 識別碼 '%2'。 |
The %1 id '%2' was not recognized or supported. |
| 0x3AE | %1 識別碼 '%2' 在內容清單中指定一次以上。 |
The %1 id '%2' was specified more than once in the list of properties. |
| 0x3AF | %1 識別碼 '%2' 不適用於目前的操作。 |
The %1 id '%2' is not valid for the current operation. |
| 0x3B0 | 指定給 %1 識別碼 '%2' 的緩衝區無效。它不應該是 NULL。 |
The buffer specified for %1 id '%2' is invalid. It should not be NULL. |
| 0x3B1 | 指定給 %1 識別碼 '%2' 的緩衝區無效。緩衝區的長度是 '%3' 位元組，但應該是 '%4' 位元組。 |
The buffer specified for %1 id '%2' is invalid. The length of the buffer was '%3' bytes, but '%4' bytes were expected. |
| 0x3B2 | 指定給 %1 識別碼 '%2' 的緩衝區無效。緩衝區的長度是 '%3' 位元組，這不是預期的陣列元素大小順序，預期的是 '%4' 位元組。 |
The buffer specified for %1 id '%2' is invalid. The length of the buffer was '%3' bytes which is not in the order of the size of the expected array element which is '%4' bytes. |
| 0x3B3 | 無法複製 %1 識別碼 '%2'。 |
Failed to clone %1 id '%2'. |
| 0x3B4 | %1 陣列是 NULL 或者陣列計數為 0。 |
Either the %1 array is NULL or the count of the array is zero. |
| 0x3B5 | 指定給內容識別碼 %1 的緩衝區無效。它不應該是 NULL。 |
The buffer specified for property id '%1' is invalid. It should not be NULL. |
| 0x3B6 | 指定給內容識別碼 %1 的緩衝區無效。緩衝區的長度是 '%2' 位元組，但應該是 '%3' 位元組。 |
The buffer specified for property id '%1' is invalid. The length of the buffer was '%2' bytes, but '%3' bytes were expected. |
| 0x3B7 | 因為讀取器正處於錯誤狀態，因此操作無法完成。 |
The operation could not be completed because the reader is in a faulted state. |
| 0x3B8 | 因為寫入器正處於錯誤狀態，因此操作無法完成。 |
The operation could not be completed because the writer is in a faulted state. |
| 0x3B9 | WS_SERVICE_HOST 的端點數目不可以超出 %1。 |
The number of endpoints on a WS_SERVICE_HOST cannot exceed %1. |
| 0x3BA | 指定的字串值包含 '%1' 個字元。允許的長度上限是 '%2' 個字元。 |
The string value specified has '%1' characters. The maximum allowed length is '%2' characters. |
| 0x3BB | 指定的 startInfo 是 %1 個字元。startInfo 的長度上限是 '%2'。 |
The startInfo specified was %1 characters. The maximum length of the startInfo is '%2'. |
| 0x3BC | 指定的 startUri 是 %1 個字元。startInfo 的長度上限是 '%2'。 |
The startUri specified was %1 characters. The maximum length of the startInfo is '%2'. |
| 0x3BD | 指定的 URL 是 %1 個字元。URL 的長度上限是 '%2'。 |
The URL specified was %1 characters. The maximum URL length is '%2'. |
| 0x3BE | 已經超出錯誤字串數目上限。錯誤字串數目上限是 %1。 |
The maximum number of error strings was exceeded. The maximum number of error strings is %1. |
| 0x3BF | 介面索引清單包含 %1 個項目。介面索引的數目上限是 %2。 |
The list of interface indices's had %1 items. The maximum number of interface in dices is %2. |
| 0x3C0 | 找不到指定之 langid (%1) 的地區設定名稱。 |
The locale name for the specified langid (%1) could not be found. |
| 0x3C1 | 目前的操作不允許 %1 識別碼 '%2' 的值。 |
The value for %1 id '%2' is not allowed for current operation. |
| 0x3C2 | 指定的 dateTime 是 NULL。 |
The dateTime specified is NULL. |
| 0x3C3 | 指定的 fileTime 是 NULL。 |
The fileTime specified is NULL. |
| 0x3C4 | 指定的 fileTime 無法轉換成 dateTime。 |
The fileTime specified cannot be converted to a dateTime. |
| 0x3C5 | 指定的 dateTime 無法轉換成 fileTime。 |
The dateTime specified cannot be converted to a fileTime. |
| 0x3C6 | 值 '%1' 不是有效的 WS_DATETIME。 |
The value '%1' is not a valid WS_DATETIME. |
| 0x3C7 | 值 '%1' 不是有效的類型對應。 |
The value '%1' is not a valid type mapping. |
| 0x3C8 | 字元 '%1' 無法剖析為 xsd:duration。 |
The characters '%1' cannot be parsed as an xsd:duration. |
| 0x3C9 | 指定的期間包含無效的毫秒值或滴答值。 |
The duration specified contains an invalid value for the milliseconds or ticks. |
| 0x3CA | 指定的期間是 NULL。 |
The duration specified is NULL. |
| 0x3CB | 無法比較期間。只有當兩個有效的期間均指定了年份與月份，或者二者均指定了天數、小時數、分鐘數、秒數、毫秒數以及滴答計數後，才可以進行比較。 |
The duration cannot be compared. Two valid Durations can be compared only if they they both have years and months specified, or if both have only days, hours, minutes, seconds, milliseconds and ticks specified. |
| 0x3CC | 指定的 contentType 屬性必須包含 utf-8 或 utf-16 文字。 |
The contentType attribute specified must contain utf-8 or utf-16 text. |
| 0x3CD | 字元 '%1' 無法寫入註解。 |
The characters '%1' cannot be written in a comment. |
| 0x3CE | 無法開啟目前的資訊安全內容。OpenThreadToken 因 '%1' 而失敗。 |
Unable to open the current security context. OpenThreadToken failed with '%1'. |
| 0x3CF | 無法模擬使用者資訊安全內容。ImpersonateLoggedOnUser 因 '%1' 而失敗。 |
Unable to impersonate the user security context. ImpersonateLoggedOnUser failed with '%1'. |
| 0x3D0 | Kerberos AP_REQ 安全性繫結不支援 multi-leg kerberos 驗證。 |
Kerberos AP_REQ security binding does not support multi-leg kerberos authentication. |
| 0x3D1 | 不支援收到之二進位安全性權杖的編碼類型 %1。 |
Encoding type %1 of the received binary security token is not supported. |
| 0x3D2 | 已經到達允許的呼叫數目最大值的配額上限。請變更 'WS_PROXY_PROPERTY_MAX_PENDING_CALLS' 來進行調整。 |
Maximum quota of allowed maximum calls reached. Change the 'WS_PROXY_PROPERTY_MAX_PENDING_CALLS' to adjust. |
| 0x3D3 | 雙工通道類型不支援雙向訊息。 |
Two way messages not supported for the duplex channel type. |
| 0x3D4 | 輸入通道類型不支援雙向訊息。 |
Two way messages not supported for the input channel type. |
| 0x3D5 | 無法複製控制代碼。 |
Unable to duplicate handle. |
| 0x3D6 | 指定的權杖控制代碼無效。 |
The specified token handle is not valid. |
| 0x3D7 | 無法在這種狀態下呼叫編碼寫入回呼。 |
The encoding write callback cannot be called in this state. |
| 0x3D8 | 無法在這種狀態下呼叫解碼讀取回呼。 |
The decoding read callback cannot be called in this state. |
| 0x3D9 | TCP 工作階段的自訂內容類型應該是 '%1'，但實際上是 '%2'。 |
The custom content type for the TCP session should be '%1', but was '%2'. |
| 0x3DA | 不支援內容編碼 '%1'。 |
The content encoding '%1' is not supported. |
| 0x3DB | 當欄位本身指向 NULL 時，WS_SERVICE_METADATA 的 'documents' 欄位計數並不是 0。 |
A count for the 'documents' field in WS_SERVICE_METADATA is non zero while the field itself points to NULL. |
| 0x3DC | 當 WS_SERVICE_METADATA 的 'serviceName' 欄位不是 NULL 時，'serviceNs' 不可以是 NULL。 |
When the 'serviceName' field in WS_SERVICE_METADATA is non NULL, 'serviceNs' must not be NULL. |
| 0x3DD | 當 WS_SERVICE_METADATA 的 'serviceNs' 欄位不是 NULL時，'serviceName' 不可以是 NULL。 |
When the 'serviceNs' field in WS_SERVICE_METADATA is non NULL, 'serviceName' must not be NULL. |
| 0x3DE | 當 WS_SERVICE_METADATA 的 'documents' 欄位不是 NULL 時，'count' 欄位為 0。 |
The 'count' field is zero while the 'documents' field in WS_SERVICE_METADATA is non NULL. |
| 0x3DF | 當 WS_SERVICE_METADATA 的 'serviceName' 欄位不是 NULL 時，'count' 欄位為 0。 |
The 'count' field is zero while the 'serviceName' field in WS_SERVICE_METADATA is non NULL. |
| 0x3E0 | 當 WS_SERVICE_METADATA 的 'serviceNs' 欄位不是 NULL 時，'count' 欄位為 0。 |
The 'count' field is zero while the 'serviceNs' field in WS_SERVICE_METADATA is non NULL. |
| 0x3E1 | WS_SERVICE_ENDPOINT_METADATA 的 'portName' 欄位不可以是 NULL。 |
The 'portName' field on the WS_SERVICE_ENDPOINT_METADATA cannot be NULL. |
| 0x3E2 | WS_SERVICE_ENDPOINT_METADATA 的 'bindingName' 欄位不可以是 NULL。 |
The 'bindingName' field on the WS_SERVICE_ENDPOINT_METADATA cannot be NULL. |
| 0x3E3 | WS_SERVICE_ENDPOINT_METADATA 的 'bindingNs' 欄位不可以是 NULL。 |
The 'bindingNs' field on the WS_SERVICE_ENDPOINT_METADATA cannot be NULL. |
| 0x3E4 | 只有 WS_CHANNEL_TYPE_DUPLEX_SESSION 和 WS_CHANNEL_TYPE_REPLY 通道類型才支援 Ws-MetadataExchange。 |
Ws-MetadataExchange only supported on WS_CHANNEL_TYPE_DUPLEX_SESSION and WS_CHANNEL_TYPE_REPLY channel types. |
| 0x3E5 | WS_UDP_CHANNEL_BINDING 不支援 Ws-MetadataExchange。 |
Ws-MetadataExchange not supported for WS_UDP_CHANNEL_BINDING. |
| 0x3E6 | 當 WS_SERVICE_HOST 處於 'WS_SERVICE_HOST_STATE_OPENING' 狀態時，目前的操作無效。 |
Current operation is invalid when the WS_SERVICE_HOST is in 'WS_SERVICE_HOST_STATE_OPENING' state. |
| 0x3E7 | 當 WS_SERVICE_HOST 處於 'WS_SERVICE_HOST_STATE_OPEN' 狀態時，目前的操作無效。 |
Current operation is invalid when the WS_SERVICE_HOST is in 'WS_SERVICE_HOST_STATE_OPEN' state. |
| 0x3E8 | 當 WS_SERVICE_HOST 處於 'WS_SERVICE_HOST_STATE_CLOSING' 狀態時，目前的操作無效。 |
Current operation is invalid when the WS_SERVICE_HOST is in 'WS_SERVICE_HOST_STATE_CLOSING' state. |
| 0x3E9 | 當 WS_SERVICE_HOST 處於 'WS_SERVICE_HOST_STATE_CLOSED' 狀態時，目前的操作無效。 |
Current operation is invalid when the WS_SERVICE_HOST is in 'WS_SERVICE_HOST_STATE_CLOSED' state. |
| 0x3EA | 目前的操作已經中止。 |
The current operation is already aborted. |
| 0x3EB | 操作無法在 WS_SHORT_CALLBACK 下執行。 |
The operation cannot run under WS_SHORT_CALLBACK. |
| 0x3EC | 寫入器必須寫入元素，才能執行此操作。 |
The writer must be writing an element in order to perform this operation. |
| 0x3ED | 方法表格不能有 'NULL' 函式指標。 |
Method table cannot have a 'NULL' function pointer. |
| 0x3EE | 'WS_SERVICE_CONTRACT' 上的 'contractDescription' 與 'defaultMessageHandlerCallback' 兩個欄位不能是 NULL。 |
Both 'contractDescription' and 'defaultMessageHandlerCallback' field on 'WS_SERVICE_CONTRACT' cannot be NULL. |
| 0x3EF | 如果已經指定合約描述，則 WS_SERVICE_CONTRACT 上的 'methodTable' 就不能是 NULL。 |
If contract description is specified 'methodTable' on WS_SERVICE_CONTRACT cannot be NULL. |
| 0x3F0 | 有多個操作共用相同的動作。 |
More than one operation share the same action. |
| 0x3F1 | WS_SERVICE_ENDPOINT_PROPERTY_MAX_ACCEPTING_CHANNELS 內容的值不可以大於所指定 WS_SERVICE_ENDPOINT 上 WS_SERVICE_ENDPOINT_PROPERTY_MAX_CHANNELS 的內容值。 |
Value for property WS_SERVICE_ENDPOINT_PROPERTY_MAX_ACCEPTING_CHANNELS cannot be greater than value for property WS_SERVICE_ENDPOINT_PROPERTY_MAX_CHANNELS on the given WS_SERVICE_ENDPOINT. |
| 0x3F2 | 未知的 WS_OPERATION_STYLE。 |
Unknown WS_OPERATION_STYLE. |
| 0x3F3 | 如果 WS_SERVICE_HOST 上未設定中繼資料文件，則無法啟用 WS_SERVICE_ENDPOINT 上的 WS-MetadataExchange。 |
Cannot enable WS-MetadataExchange on a WS_SERVICE_ENDPOINT if no metadata documents are set on WS_SERVICE_HOST. |
| 0x3F4 | URL '%1' 使用 HTTP 或 HTTPS 以外的配置開啟 HTTP 接聽程式。 |
Url '%1' uses scheme other than HTTP or HTTPS to open an HTTP listener. |
| 0x3F5 | 不支援指定的 encodingType '%1'。 |
The specified encodingType '%1' is not supported. |
| 0x3F6 | mtom 文件的 charSet 預期的是 '%1'，但找到的是 '%2'。 |
The charSet of the mtom document was expected to be '%1', but '%2' was found. |
| 0x3F7 | 使用 WS_XML_WRITER_RAW_ENCODING 時，只會寫入 base64 內容。 |
Only base64 content may be written when using WS_XML_WRITER_RAW_ENCODING. |
| 0x3F8 | 無法抓取目前使用者的 IE Proxy 設定。 |
Unable to retrieve IE proxy settings for the current user. |
| 0x3F9 | 無法設定 HTTP 要求的 Proxy 設定。 |
Unable to configure proxy settings for the HTTP request. |
| 0x3FA | 對 'WS_HTTP_PROXY_SETTING_MODE_CUSTOM' 指定通道內容 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE' 時，必須指定通道內容 'WS_CHANNEL_PROPERTY_CUSTOM_HTTP_PROXY'。 |
When specifying channel property 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE' to 'WS_HTTP_PROXY_SETTING_MODE_CUSTOM', channel property 'WS_CHANNEL_PROPERTY_CUSTOM_HTTP_PROXY' must be specified. |
| 0x3FB | 通道內容 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE' 的值無效。 |
Invalid value for channel property 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE'. |
| 0x3FC | 'WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT' 不能有 'NULL' 回呼。 |
'WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT' cannot have a 'NULL' callback. |
| 0x3FD | 'WS_CALL_PROPERTY_RECEIVE_MESSAGE_CONTEXT' 不能有 'NULL' 回呼。 |
'WS_CALL_PROPERTY_RECEIVE_MESSAGE_CONTEXT' cannot have a 'NULL' callback. |
| 0x3FE | 為單向呼叫或目前的內容不支援該輸出訊息。 |
Either the call is one-way or the output message is not supported under the current context. |
| 0x3FF | WS_SERVICE_ENDPOINT 內容 WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_TYPE 的值無效。 |
Invalid value for WS_SERVICE_ENDPOINT property WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_TYPE. |
| 0x400 | 'WS_SERVICE_ACCEPT_CHANNEL_CALLBACK' 不能有 'NULL' 回呼。 |
'WS_SERVICE_ACCEPT_CHANNEL_CALLBACK' cannot have a 'NULL' callback. |
| 0x401 | 'WS_SERVICE_CLOSE_CHANNEL_CALLBACK' 不能有 'NULL' 回呼。 |
'WS_SERVICE_CLOSE_CHANNEL_CALLBACK' cannot have a 'NULL' callback. |
| 0x402 | 'WS_CUSTOM_HTTP_PROXY' 欄位 'servers' 不能指向 'NULL' 字串。 |
'WS_CUSTOM_HTTP_PROXY' field 'servers' cannot point to a 'NULL' string. |
| 0x403 | 'WS_HTTP_MESSAGE_MAPPING' 上的 'requestHeaderMappings' 在索引 '%1' 有 'NULL' 項目。 |
The 'requestHeaderMappings' on 'WS_HTTP_MESSAGE_MAPPING' has a 'NULL' entry at index '%1'. |
| 0x404 | 'WS_HTTP_MESSAGE_MAPPING' 上的 'responseHeaderMappings' 在索引 '%1' 有 'NULL' 項目。 |
The 'responseHeaderMappings' on 'WS_HTTP_MESSAGE_MAPPING' has a 'NULL' entry at index '%1'. |
| 0x405 | 'WS_SECURITY_BINDING_PROPERTY_HTTP_HEADER_AUTH_TARGET' 內容值 '%1' 無效。 |
'WS_SECURITY_BINDING_PROPERTY_HTTP_HEADER_AUTH_TARGET' property value '%1' is invalid. |
| 0x406 | 用於 Proxy 伺服器的 HTTP 標頭驗證安全性繫結不支援指定多個標頭驗證配置。 |
HTTP header authentication security binding against the proxy server does not support specifying multiple header authentication schemes. |
| 0x407 | 用於 Proxy 伺服器的 HTTP 標頭驗證安全性繫結不支援使用 Passport 驗證。 |
HTTP header authentication security binding against the proxy server does not support using Passport authentication. |
| 0x408 | 'WS_SECURITY_CONTEXT_MESSAGE_SECURITY_BINDING' 安全性繫結結構必須具備有效的啟動程序安全性描述。 |
'WS_SECURITY_CONTEXT_MESSAGE_SECURITY_BINDING' security binding structure must have a valid bootstrap security description. |
| 0x409 | 通道不支援內容編碼。 |
The channel doesn't support content encodings. |
| 0x40A | 指定的 serviceEndpoint 是 NULL。 |
The serviceEndpoint specified is NULL. |
| 0x40B | WS_BINDING_TEMPLATE_TYPE '%1' 無效。 |
The WS_BINDING_TEMPLATE_TYPE '%1' is invalid. |
| 0x40D | 指定的繫結原則描述是 NULL。 |
The binding policy description specified is NULL. |
| 0x40E | 傳輸安全性繫結 %1 的數目無效。資訊安全內容訊息繫結範本中必須 (而且只能) 指定一個傳輸安全性繫結。 |
Number of transport security binding %1 is invalid. One and only one transport security binding must be specified in security context message binding templates. |
| 0x40F | 使用者範本與原則描述中均已指定 %1 識別碼 '%2'。 |
The %1 id '%2' is specified in both user template and policy description. |
| 0x410 | 目前的 'WS_ENCODING' 不允許針對為端點啟用的中繼資料交換提供 HTTP GET 支援。 |
Current 'WS_ENCODING' does not permit to have HTTP GET support for metadata exchange enabled for the endpoint. |
| 0x411 | 如果在指定的 'WS_SERVICE_ENDPOINT' 上啟用了對中繼資料交換的 HTTP GET 支援，則為 'WS_HTTP_HEADER_MAPPING' 指定的對應 'headerMappingOptions' 值必須是 0。 |
The value specified for the mapping 'headerMappingOptions' for 'WS_HTTP_HEADER_MAPPING' must be zero if HTTP GET support for metadata exchange is enabled on the given 'WS_SERVICE_ENDPOINT' . |
| 0x412 | 目前的 'WS_ENCODING' 不允許有相關聯的 'WS_CONTRACT_DESCRIPTION'。 |
Current 'WS_ENCODING' does not permit to have an associated 'WS_CONTRACT_DESCRIPTION'. |
| 0x413 | 在指定 'WS_SERVICE_ENDPOINT' 上指定的 'WS_ENCODING' 不支援 Ws-Metadata Exchange v1.1。 |
Ws-Metadata Exchange v1.1 not supported for the given 'WS_ENCODING' on the given 'WS_SERVICE_ENDPOINT'. |
| 0x414 | 針對 'WS_SERVICE_ENDPOINT' 上指定的 'WS_ENCODING'，'WS_SERVICE_ENDPOINT' 內容 'WS_SERVICE_ENDPOINT_PROPERTY_MAX_CONCURRENCY' 的值只能是 '1'。 |
The value for 'WS_SERVICE_ENDPOINT' property 'WS_SERVICE_ENDPOINT_PROPERTY_MAX_CONCURRENCY' can only be '1' for the given 'WS_ENCODING' for the 'WS_SERVICE_ENDPOINT'. |
| 0x415 | 目前的 'WS_ENCODING' 只支援用於 'WS_HTTP_CHANNEL_BINDING'。 |
The current 'WS_ENCODING' is only supported for 'WS_HTTP_CHANNEL_BINDING'. |
| 0x416 | 對於 HTTP GET 中繼資料交換，'WS_SERVICE_METADATA_DOCUMENT' 項目必須要有唯一名稱。 |
For HTTP GET metadata exchange 'WS_SERVICE_METADATA_DOCUMENT' entries must have unique names. |
| 0x417 | 在端點啟用中繼資料交換的 HTTP GET，或是為指定的 'WS_SERVICE_ENDPOINT' 在相關聯的 'WS_SERVICE_CONTRACT' 上指定 'defaultMessageCallbackHandler'。 |
Either enable HTTP GET for metadata exchange on the endpoint or specify a 'defaultMessageCallbackHandler' on the associated 'WS_SERVICE_CONTRACT' for the given 'WS_SERVICE_ENDPOINT'. |
| 0x418 | 不允許在 'WS_SERVICE_METADATA' 的 'documents' 欄位上為'WS_SERVICE_METADATA_DOCUMENT*' 陣列指定 'NULL' 項目。 |
A 'NULL' entry for the 'WS_SERVICE_METADATA_DOCUMENT*' array as specified on the 'documents' field of 'WS_SERVICE_METADATA' is not allowed. |
| 0x419 | 'WS_SERVICE_METADATA_DOCUMENT' 的 'content' 欄位不能是 'NULL'。 |
The 'content' field of a 'WS_SERVICE_METADATA_DOCUMENT' cannot be 'NULL'. |
| 0x41A | 如果已為指定的 'WS_SERVICE_ENDPOINT' 啟用 HTTP GET 中繼資料支援，則 'WS_LISTENER_PROPERTY_ID' 識別碼 'WS_LISTENER_PROPERTY_TRANSPORT_URL_MATCHING_OPTIONS' 不能設定 'WS_MATCH_URL_EXACT_PATH'。 |
The 'WS_LISTENER_PROPERTY_ID' id 'WS_LISTENER_PROPERTY_TRANSPORT_URL_MATCHING_OPTIONS' must not have the setting 'WS_MATCH_URL_EXACT_PATH' if HTTP GET Metadata support is enabled for the given 'WS_SERVICE_ENDPOINT'. |
| 0x41B | 如果已為指定的 'WS_SERVICE_ENDPOINT' 啟用 HTTP GET 中繼資料支援，則 'WS_LISTENER_PROPERTY_ID' 識別碼 'WS_LISTENER_PROPERTY_TO_HEADER_MATCHING_OPTIONS' 不能設定 'WS_MATCH_URL_EXACT_PATH'。 |
The 'WS_LISTENER_PROPERTY_ID' id 'WS_LISTENER_PROPERTY_TO_HEADER_MATCHING_OPTIONS' must not have the setting 'WS_MATCH_URL_EXACT_PATH' if HTTP GET Metadata support is enabled for the given 'WS_SERVICE_ENDPOINT'. |
| 0x41C | 只有當 'WS_SERVICE_ENDPOINT_ID' 識別碼 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_TYPE' 設定為 'WS_METADATA_EXCHANGE_TYPE_MEX' 時，才能指定 'WS_SERVICE_ENDPOINT_PROPERTY_ID' 識別碼 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX'。 |
The 'WS_SERVICE_ENDPOINT_PROPERTY_ID' id 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX' can only be specified when 'WS_SERVICE_ENDPOINT_ID' id 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_TYPE' is set to 'WS_METADATA_EXCHANGE_TYPE_MEX'. |
| 0x41D | 'WS_SERVICE_ENDPOINT_PROPERTY_ID' 識別碼 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX' 不能是長度為零的 WS_STRING。 |
The 'WS_SERVICE_ENDPOINT_PROPERTY_ID' id 'WS_SERVICE_ENDPOINT_PROPERTY_METADATA_EXCHANGE_URL_SUFFIX' cannot be a WS_STRING of length zero. |
| 0x41E | 當 'WS_CHANNEL_PROPERTY_ID' 識別碼 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE' 指定為 'WS_HTTP_PROXY_SETTING_MODE_NONE' 時，不能指定 'WS_CHANNEL_PROPERTY_ID' 識別碼 'WS_CHANNEL_PROPERTY_CUSTOM_HTTP_PROXY'。 |
The 'WS_CHANNEL_PROPERTY_ID' id 'WS_CHANNEL_PROPERTY_CUSTOM_HTTP_PROXY' cannot be specified when 'WS_CHANNEL_PROPERTY_ID' id 'WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE' is specified as 'WS_HTTP_PROXY_SETTING_MODE_NONE'. |
| 0x41F | 無法抓取自動 Proxy 設定。 |
Failed to retrieve automatic proxy settings. |
| 0x420 | 建立期間必須在 'WS_SERVICE_HOST' 上至少指定一個 'WS_SERVICE_ENDPOINT' 。 |
Must specify at least one 'WS_SERVICE_ENDPOINT' on 'WS_SERVICE_HOST' during creation. |
| 0x421 | 連入的 HTTP 要求包含使用者代理程式 '%1'，其中有不允許的使用者代程式子字串 '%2'。 |
The incoming HTTP request contained user agent '%1' which has the disallowed user agent sub-string '%2'. |
| 0x422 | 複製 %1 識別碼 '%2' 時，無法複製 'WS_DISALLOWED_USER_AGENT_LIST'。 |
Failed to clone 'WS_DISALLOWED_USER_AGENT_LIST' while cloning %1 id '%2'. |
| 0x423 | 如果 'subStrings' 是 NULL，則 'WS_DISALLOWED_USER_AGENT_LIST' 'subStringCount' 必須是零。 |
In 'WS_DISALLOWED_USER_AGENT_LIST' 'subStringCount' must be zero if 'subStrings' is NULL. |
| 0x424 | 'WS_URL' 結構的連接埠欄位不一致。 |
Port fields of the 'WS_URL' structure is not consistent. |
| 0x425 | 收到的 RequestSecurityToken 訊息格式錯誤。遺失名稱為 '%1' 且命名空間為 '%2' 的元素。 |
The RequestSecurityToken message received was not in the correct format. The element with name '%1' and namespace '%2' was missing. |
| 0x426 | 收到的 RequestSecurityToken 訊息格式錯誤。名稱為 '%1' 且命名空間為 '%2' 的元素不是預期的元素。 |
The RequestSecurityToken message received was not in the correct format. The element with name '%1' and namespace '%2' was not expected. |
| 0x427 | 收到的 RequestSecurityToken 訊息格式錯誤。指定的權杖類型是 '%1'，但需要的是 '%2'。 |
The RequestSecurityToken message received was not in the correct format. Token type '%1' was specified but '%2' was expected. |
| 0x428 | 收到的 RequestSecurityToken 訊息格式錯誤。指定的二進位密碼類型是 '%1'，但需要的是 '%2'。 |
The RequestSecurityToken message received was not in the correct format. Binary secret type '%1' was specified but '%2' was expected. |
| 0x429 | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。遺失名稱為 '%1' 且命名空間為 '%2' 的元素。 |
The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace '%2' was missing. |
| 0x42A | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。名稱為 '%1' 且命名空間為 '%2' 的元素不是預期的元素。 |
The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace '%2' was not expected. |
| 0x42B | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。指定的演算法是 '%1'，但需要的是 '%2'。 |
The RequestSecurityTokenResponse message received was not in the correct format. Algorithm '%1' was specified but '%2' was expected. |
| 0x42C | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。名稱為 '%1' 且命名空間為 '%2' 的元素出現一次以上。 |
The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace '%2' was present more than once. |
| 0x42D | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。辨識出名稱為 '%1' 且命名空間為 '%2' 的元素，但這樣的元素不應該出現在目前的設定中。 |
The RequestSecurityTokenResponse message received was not in the correct format. The element with name '%1' and namespace '%2' was recognized but not expected to be present in the current configuration. |
| 0x42E | 所傳回已簽發權杖的權杖類型不符合要求的權杖類型。 |
The token type of the issued token returned did not match the requested token type. |
| 0x42F | 安全性權杖參照上指定的權杖類型 '%1' 不符合同一個參照上指定的值類型 '%2'。 |
The token type '%1' specified on the security token reference did not match the value type '%2' that was specified on the same reference. |
| 0x430 | 安全性權杖參照上指定的權杖類型 '%1' 不符合預期值 '%2'。 |
The token type '%1' specified on the security token reference did not match the expected value '%2'. |
| 0x431 | 使用者名稱權杖包含無效或不支援的密碼類型。 |
The username token contains an invalid or unsupported password type. |
| 0x432 | 無法提供資料完整性，可能是因為資料損毀。 |
Unable to provide data integrity, possibly due to data corruption. |
| 0x433 | 無法提供資料機密性，可能是因為資料損毀。 |
Unable to provide data confidentiality, possibly due to data corruption. |
| 0x434 | 無法建立 Kerberos AP_REQ 驗證緩衝區。 |
Failed to create the Kerberos AP_REQ authentication buffer. |
| 0x435 | 無法確認用戶端的 Kerberos AP_REQ 驗證緩衝區。 |
Failed to verify the client's Kerberos AP_REQ authentication buffer. |
| 0x436 | 無法查詢 Kerberos APREQ 已驗證之登入工作階段的工作階段金鑰。 |
Failed to query the session key of the Kerberos APREQ authenticated logon session. |
| 0x437 | 指定的非同步狀態是 NULL。 |
The async state specified is NULL. |
| 0x438 | 指定的操作是 NULL。 |
The operation specified is NULL. |
| 0x439 | 原則替代未包含必要的簽署支援權杖。 |
The policy alternative did not contain an endorsing supporting token but one was required. |
| 0x43A | 原則替代未包含必要的已簽署支援權杖。 |
The policy alternative did not contain a signed supporting token but one was required. |
| 0x43B | 原則替代包含簽署支援權杖，但不需要有這種權杖。 |
The policy alternative contains an endorsing supporting token but none was required. |
| 0x43C | 原則替代包含已簽署的支援權杖，但不需要有這種權杖。 |
The policy alternative contains a signed supporting token but none was required. |
| 0x43D | 原則中指定的簽署支援權杖宣告 '%1' 數目與所需的計數 '%2 '不同。 |
The number of endorsing supporting token assertions '%1' specified in policy is different than required count '%2'. |
| 0x43E | 原則中指定的已簽署支援權杖宣告 '%1' 數目與所需的計數 '%2 '不同。 |
The number of signed supporting token assertions '%1' specified in policy is different than required count '%2'. |
| 0x43F | 在 'WS_DISALLOWED_USER_AGENT_LIST' 的欄位 'subStrings' 中，位於索引 '%1' 的 WS_STRING 是空的。 |
In 'WS_DISALLOWED_USER_AGENT_LIST' in field 'subStrings' WS_STRING at index '%1' is empty. |
| 0x440 | 在 'WS_DISALLOWED_USER_AGENT_LIST' 的欄位 'subStrings' 中，位於索引 '%1' 的 WS_STRING 是 NULL。 |
In 'WS_DISALLOWED_USER_AGENT_LIST' in field 'subStrings' WS_STRING at index '%1' is NULL. |
| 0x441 | WsutilHelper DLL 版本與 wsutil.exe 版本不相容。 |
WsutilHelper DLL version is incompatible with wsutil.exe. |
| 0x442 | 目前的執行緒正在模擬使用者權杖。伺服器通道不支援將執行緒權杖搭配 Windows 整合式驗證使用。 |
Current thread is impersonating a user token. Server channels do not support using thread tokens with Windows integrated authentication. |
| 0x443 | 停用 HTTP 要求的自動重新導向時發生錯誤。 |
There was an error disabling auto-redirection on the HTTP request. |
| 0x444 | 提供的 HTTP 重新導向回呼是 NULL。 |
The supplied HTTP redirection callback is NULL. |
| 0x445 | HTTP Proxy 無法連線到伺服器。 |
The HTTP proxy was not able to reach the server. |
| 0x446 | 不允許來自命名空間 '%2' 的原則延伸模組 '%1'，因為它可能會影響原則替代比對結果。 |
The policy extension '%1' from namespace '%2' is not allowed as it might affect policy alternative matching result. |
| 0x448 | 在安全通道收到不安全的錯誤。 |
An unsecured fault was received on a secure channel. |
| 0x449 | 伺服器傳回安全性錯誤: '提供了不支援的權杖'。 |
The server returned a security fault: 'An unsupported token was provided'. |
| 0x44A | 伺服器傳回安全性錯誤: '使用了不支援的簽章或加密演算法'。 |
The server returned a security fault: 'An unsupported signature or encryption algorithm was used'. |
| 0x44B | 伺服器傳回安全性錯誤: '處理 標頭時發現錯誤'。 |
The server returned a security fault: 'An error was discovered processing the header'. |
| 0x44C | 伺服器傳回安全性錯誤: '提供了無效的安全性權杖'。 |
The server returned a security fault: 'An invalid security token was provided'. |
| 0x44D | 伺服器傳回安全性錯誤: '無法驗證或授權安全性權杖'。 |
The server returned a security fault: 'The security token could not be authenticated or authorized'. |
| 0x44E | 伺服器傳回安全性錯誤: '簽章或解密無效'。 |
The server returned a security fault: 'The signature or decryption was invalid'. |
| 0x44F | 伺服器傳回安全性錯誤: '無法抓取參照的安全性權杖'。 |
The server returned a security fault: 'Referenced security token could not be retrieved'. |
| 0x450 | 伺服器傳回安全性錯誤: '訊息已到期'。 |
The server returned a security fault: 'The message has expired'. |
| 0x451 | 伺服器傳回安全對話錯誤: '要求的內容項目不足或不受支援'。 |
The server returned a secure conversation fault: 'The requested context elements are insufficient or unsupported'. |
| 0x452 | 伺服器傳回安全對話錯誤: '不支援與 SCT 關聯的所有值'。 |
The server returned a secure conversation fault: 'Not all of the values associated with the SCT are supported'. |
| 0x453 | 伺服器傳回安全對話錯誤: '指定的衍生來源不明'。 |
The server returned a secure conversation fault: 'The specified source for the derivation is unknown'. |
| 0x454 | 伺服器傳回安全對話錯誤: '提供的內容權杖已到期'。 |
The server returned a secure conversation fault: 'The provided context token has expired'. |
| 0x455 | 伺服器傳回安全對話錯誤: '無法更新指定的內容權杖'。 |
The server returned a secure conversation fault: 'The specified context token could not be renewed'. |
| 0x456 | 伺服器傳回定址失敗: '訊息資訊標頭無效，且無法處理訊息。有效性失敗的原因可能是結構性問題或語意問題，例如，目的地不是 URI 或從未發出之訊息識別碼的關係。'。 |
The server returned an addressing fault: 'A message information header is not valid and the message cannot be processed. The validity failure can be either structural or semantic, e.g. a destination that is not a URI or a relationship to a message id that was never issued.'. |
| 0x457 | 伺服器傳回定址錯誤: '要求的訊息資訊標頭 To、MessageID 或 Action 不存在。'。 |
The server returned an addressing fault: 'A required message information header, To, MessageID, or Action, is not present.'. |
| 0x458 | 伺服器傳回定址錯誤: '沒有路由可用來連線到 WS-Addressing To 所定義的目的地角色'。 |
The server returned an addressing fault: 'No route can be determined to reach the destination role defined by the WS-Addressing To.'. |
| 0x459 | 伺服器傳回定址錯誤: '接收器無法處理動作。'。 |
The server returned an addressing fault: 'The action cannot be processed at the receiver.'. |
| 0x45A | 伺服器傳回定址錯誤: '端點目前無法處理訊息。'。 |
The server returned an addressing fault: 'The endpoint is unable to process the message at this time.'. |
| 0x45B | 伺服器傳回定址錯誤: '代表訊息定址屬性的標頭無效，且無法處理訊息'。 |
The server returned an addressing fault: 'A header representing a Message Addressing Property is not valid and the message cannot be processed'. |
| 0x45C | 伺服器傳回定址錯誤: '代表訊息定址屬性的要求標頭不存在'。 |
The server returned an addressing fault: 'A required header representing a Message Addressing Property is not present'. |
| 0x45D | 伺服器傳回 SOAP 封套錯誤: '版本不符'。 |
The server returned a SOAP envelope fault: 'Version Mismatch'. |
| 0x45E | 伺服器傳回 SOAP 封套錯誤: '無法識別一或多個必要 SOAP 標頭區塊'。 |
The server returned a SOAP envelope fault: 'One or more mandatory SOAP header blocks not understood'. |
| 0x45F | 伺服器傳回信任錯誤: '要求無效或其格式不正確'。 |
The server returned a trust fault: 'The request was invalid or malformed'. |
| 0x460 | 伺服器傳回信任錯誤: '驗證失敗'。 |
The server returned a trust fault: 'Authentication failed'. |
| 0x461 | 伺服器傳回信任錯誤: '指定的要求失敗'。 |
The server returned a trust fault: 'The specified request failed'. |
| 0x462 | 伺服器傳回信任錯誤: '安全性權杖已被撤銷'。 |
The server returned a trust fault: 'Security token has been revoked'. |
| 0x463 | 伺服器傳回信任錯誤: 'Digest 元素不足'。 |
The server returned a trust fault: 'Insufficient Digest Elements'. |
| 0x464 | 伺服器傳回信任錯誤: '無法識別指定的 RequestSecurityToken。'。 |
The server returned a trust fault: 'The specified RequestSecurityToken is not understood.'. |
| 0x465 | 伺服器傳回信任錯誤: '要求資料不是最新的'。 |
The server returned a trust fault: 'The request data is out-of-date'. |
| 0x466 | 伺服器傳回信任錯誤: '要求的時間範圍無效或不受支援'。 |
The server returned a trust fault: 'The requested time range is invalid or unsupported'. |
| 0x467 | 伺服器傳回信任錯誤: '要求範圍無效或不受支援'。 |
The server returned a trust fault: 'The request scope is invalid or unsupported'. |
| 0x468 | 伺服器傳回信任錯誤: '可更新的安全性權杖已到期'。 |
The server returned a trust fault: 'A renewable security token has expired'. |
| 0x469 | 伺服器傳回信任錯誤: '要求的更新失敗'。 |
The server returned a trust fault: 'The requested renewal failed'. |
| 0x46A | 字串 '%1' 不是有效的 XML NCName。 |
The string '%1' is not a valid XML NCName. |
| 0x46B | 伺服器需要 HTTP 驗證配置 'basic'。 |
The server requires HTTP authentication scheme 'basic'. |
| 0x46C | 伺服器需要 HTTP 驗證配置 'NTLM'。 |
The server requires HTTP authentication scheme 'NTLM'. |
| 0x46D | 伺服器需要 HTTP 驗證配置 'digest'。 |
The server requires HTTP authentication scheme 'digest'. |
| 0x46E | 伺服器需要 HTTP 驗證配置 'negotiate'。 |
The server requires HTTP authentication scheme 'negotiate'. |
| 0x46F | Proxy 需要 HTTP 驗證配置 'basic'。 |
The proxy requires HTTP authentication scheme 'basic'. |
| 0x470 | Proxy 需要 HTTP 驗證配置 'NTLM'。 |
The proxy requires HTTP authentication scheme 'NTLM'. |
| 0x471 | Proxy 需要 HTTP 驗證配置 'digest'。 |
The proxy requires HTTP authentication scheme 'digest'. |
| 0x472 | Proxy 需要 HTTP 驗證配置 'negotiate'。 |
The proxy requires HTTP authentication scheme 'negotiate'. |
| 0x473 | 放棄期間主體無法序列化。 |
During abandon the body failed to serialize. |
| 0x474 | Proxy 失敗，因此已中止呼叫。 |
The proxy has faulted and as a result the call is being aborted. |
| 0x475 | 收到單向呼叫的訊息。 |
A message was received for a one way call. |
| 0x476 | 通道屬性 WS_CHANNEL_PROPERTY_HTTP_SERVER_SPN 無法使用。 |
The channel property WS_CHANNEL_PROPERTY_HTTP_SERVER_SPN is not available. |
| 0x477 | 通道屬性 WS_CHANNEL_PROPERTY_HTTP_PROXY_SPN 無法使用。 |
The channel property WS_CHANNEL_PROPERTY_HTTP_PROXY_SPN is not available. |
| 0x478 | 時間戳記的有效性範圍無效，它在建立前就已經到期。 |
The validity range of the timestamp was invalid. It expired before it was created. |
| 0x479 | 時間戳記的有效性範圍無效，它是在未來的時間建立。 |
The validity range of the timestamp was invalid. It was created in the future. |
| 0x47A | 時間戳記已到期。 |
The timestamp has expired. |
| 0x47B | 時間戳記的存在期間已超過允許的延遲時間上限。 |
The age of the timestamp exceeded the maximum allowed latency. |
| 0x47C | 伺服器回應中缺少 HTTP 內容類型標頭。 |
The HTTP content type header is missing in the server's response. |
| 0x47D | 提供的端點 URL '%1' 對於此操作而言無效。 |
The supplied endpoint URL '%1' is invalid for this operation. |
| 0x47E | 從自訂通道執行的 'WS_CHANNEL_PROPERTY_ENABLE_TIMEOUTS' 內容查詢傳回 TRUE。不停用所有逾時，就無法從服務模型使用自訂通道。 |
The 'WS_CHANNEL_PROPERTY_ENABLE_TIMEOUTS' property query from the custom channel returned TRUE. Custom channels cannot be used from Service Model without disabling all timeouts. |
| 0x47F | 目前接收的 HTTP 要求標頭大小為 %1 個位元組，超過 %2 個位元組的配額。 |
The size %1 bytes of the HTTP request headers being received exceeds the quota of %2 bytes. |
| 0x480 | 內容類型中不應該有動作字串 '%1'。 |
The action string '%1' was not expected in the content type. |
| 0x481 | 只有 Windows 7 和更新版本支援 WS_CHANNEL_PROPERTY_HTTP_SERVER_SPN。 |
WS_CHANNEL_PROPERTY_HTTP_SERVER_SPN is supported only on Windows 7 and later. |
| 0x482 | 只有 Windows 7 和更新版本支援 WS_CHANNEL_PROPERTY_HTTP_PROXY_SPN。 |
WS_CHANNEL_PROPERTY_HTTP_PROXY_SPN is supported only on Windows 7 and later. |
| 0x483 | 作業訊息選項 %1 無效。 |
The operation message option %1 is invalid. |
| 0x484 | WS_SERVICE_OPERATION_MESSAGE_NILLABLE_ELEMENT 不適用於 RPC 作業。 |
WS_SERVICE_OPERATION_MESSAGE_NILLABLE_ELEMENT is not applicable in RPC operation. |
| 0x485 | 無法連接提供的 Proxy。 |
The given proxy cannot be reached. |
| 0x486 | 呼叫內容識別碼為 '%1' 的 WsGetSecurityTokenProperty 時，'heap' 參數必須是 NULL。 |
When calling WsGetSecurityTokenProperty with property id '%1', the 'heap' parameter must be NULL. |
| 0x487 | 呼叫內容識別碼為 '%1' 的 WsGetSecurityTokenProperty 時，'heap' 參數不可以是 NULL。 |
When calling WsGetSecurityTokenProperty with property id '%1', the 'heap' parameter must not be NULL. |
| 0x488 | 權杖沒有對稱金鑰。 |
The token has no symmetric key. |
| 0x489 | 接收的 RequestSecurityTokenResponse 訊息格式錯誤。指定的金鑰類型是 '%1'，但應該是 '%2'。 |
The RequestSecurityTokenResponse message received was not in the correct format. Key type '%1' was specified but '%2' was expected. |
| 0x48A | 延伸的保護原則 '%1' 無效。 |
The extended protection policy '%1' is not valid. |
| 0x48B | 使用 WS_EXTENDED_PROTECTION_SCENARIO_TERMINATED_SSL 時，必須設定 WS_SECURITY_PROPERTY_SERVICE_IDENTITIES。 |
When using WS_EXTENDED_PROTECTION_SCENARIO_TERMINATED_SSL, WS_SECURITY_PROPERTY_SERVICE_IDENTITIES must be set. |
| 0x48C | 延伸的保護情況 '%1' 無效。 |
The extended protection scenario '%1' is not valid. |
| 0x48D | 無法在 HTTP 要求佇列上設定延伸的保護。 |
Unable to configure extended protection on HTTP request queue. |
| 0x48E | 安全性權杖中的延伸保護權杖不符合 SSL 連線的延伸保護權杖。 |
The extended protection token in the security token did not match the extended protection token of the SSL connection. |
| 0x48F | 收到的 SAML 權杖沒有證明金鑰。 |
The received SAML token has no proof key. |
| 0x490 | WS_SECURITY_PROPERTY_SERVICE_IDENTITIES 內容必須至少指定一個服務識別。 |
The WS_SECURITY_PROPERTY_SERVICE_IDENTITIES property must specify at least one service identity. |
| 0x491 | 已達到 HTTP 重試次數上限。一個要求最多可以重試 5 次。 |
The maximum number of HTTP retries has been exceeded. A request can be retried at most 5 times. |
| 0x492 | 無法查詢密碼編譯金鑰的大小。 |
Unable to query size of cryptographic key. |
| 0x493 | 除了簽章無效之外，無法確定其他任何的原因。 |
Unable to verify signature for reasons other than the signature being invalid. |
| 0x494 | 無法開啟安全性演算法提供者。 |
Unable to open security algorithm provider. |
| 0x495 | 無法查詢密碼編譯雜湊的大小。 |
Unable to query size of cryptographic hash. |
| 0x496 | 無法查詢密碼編譯雜湊。 |
Unable to query cryptographic hash. |
| 0x497 | 無法開啟加密編譯提供者。 |
Unable to open cryptographic provider. |
| 0x498 | 無法匯入密碼編譯金鑰。 |
Unable to import cryptographic key. |
| 0x499 | 無法設定密碼編譯雜湊。 |
Unable to configure cryptographic hash. |
| 0x49A | Internet Explorer Proxy 設定有格式錯誤的 Proxy 伺服器名稱。 |
The Internet Explorer proxy setting has a malformed proxy server name. |
| 0x49B | WS_SECURITY_BINDING_PROPERTY_CERT_FAILURES_TO_IGNORE 不支援 '%1'。其必須設為 WS_CERT_FAILURE 的一或多個值。 |
WS_SECURITY_BINDING_PROPERTY_CERT_FAILURES_TO_IGNORE does not support '%1'. It must be set to one or multiple values of WS_CERT_FAILURE. |
| 0x49C | 伺服器不支援 WS_SECURITY_BINDING_PROPERTY_CERT_FAILURES_TO_IGNORE。 |
WS_SECURITY_BINDING_PROPERTY_CERT_FAILURES_TO_IGNORE is not supported on the server. |
| 0x49D | 伺服器不支援 WS_SECURITY_BINDING_PROPERTY_DISABLE_CERT_REVOCATION_CHECK。 |
WS_SECURITY_BINDING_PROPERTY_DISABLE_CERT_REVOCATION_CHECK is not supported on the server. |
| 0x49E | 伺服器不支援 WS_SECURITY_BINDING_PROPERTY_DISALLOWED_SECURE_PROTOCOLS。 |
WS_SECURITY_BINDING_PROPERTY_DISALLOWED_SECURE_PROTOCOLS is not supported on the server. |
| 0x49F | 伺服器不支援 WS_SECURITY_BINDING_PROPERTY_CERTIFICATE_VALIDATION_CALLBACK_CONTEXT。 |
WS_SECURITY_BINDING_PROPERTY_CERTIFICATE_VALIDATION_CALLBACK_CONTEXT is not supported on the server. |
| 0x4A0 | 內容類型標頭中指定 utf-16 字元集，但訊息的編碼不是 utf-16。 |
utf-16 charset is specified in the content type header but message is not utf-16 encoded. |
| 0x4A1 | Content-Type 標頭 '%1' 中的動作不符合 start-info 標頭 '%2' 中的動作。 |
The action in Content-Type header '%1' does not match the action in start-info header '%2'. |
| 0x4A2 | 寫入具有 WS_TYPE '%1'、WS_TYPE_MAPPING '%2' 及 WS_WRITE_OPTION '%3' 的類型時發生序列化失敗。 |
Serialization failure occurred when writing a type with WS_TYPE '%1', WS_TYPE_MAPPING '%2' and WS_WRITE_OPTION '%3'. |
| 0x4A3 | 寫入具有 WS_TYPE '%1'、WS_FIELD_MAPPING '%2'、名稱 '%3' 及命名空間 '%4' 的欄位時發生序列化失敗。 |
Serialization failure occurred when writing a field with WS_TYPE '%1', WS_FIELD_MAPPING '%2', name '%3' and namespace '%4'. |
| 0x4A4 | 寫入具有 WS_WRITE_OPTION '%1'、名稱 '%2' 及命名空間 '%3' 的元素時發生序列化失敗。 |
Serialization failure occurred when writing an element with WS_WRITE_OPTION '%1', name '%2' and namespace '%3'. |
| 0x4A5 | 讀取具有 WS_TYPE '%1'、WS_TYPE_MAPPING '%2' 及 WS_READ_OPTION '%3' 的類型時發生序列化失敗。 |
Serialization failure occurred when reading a type with WS_TYPE '%1', WS_TYPE_MAPPING '%2' and WS_READ_OPTION '%3'. |
| 0x4A6 | 讀取具有 WS_READ_OPTION '%1'、名稱 '%2' 及命名空間 '%3' 的元素時發生序列化失敗。 |
Serialization failure occurred when reading an element with WS_READ_OPTION '%1', name '%2' and namespace '%3'. |
| 0x4A7 | 讀取具有 WS_TYPE '%1'、WS_FIELD_MAPPING '%2'、名稱 '%3' 及命名空間 '%4' 的欄位時發生序列化失敗。 |
Serialization failure occurred when reading a field with WS_TYPE '%1', WS_FIELD_MAPPING '%2', name '%3' and namespace '%4'. |
| 0x4A8 | 找不到預期要有的安全性標頭元素。 |
A security header element was expected but not found. |
| 0x4A9 | 發現未預期的安全性標頭元素。 |
An unexpected security header element was found. |
| 0x4AA | XML 讀取器屬性識別碼 '%1' 不能做為訊息屬性。 |
The XML reader property ID '%1' cannot be used as a message property. |
| 0x4AB | XML 寫入器屬性識別碼 '%1' 不能做為訊息屬性。 |
The XML writer property ID '%1' cannot be used as a message property. |
| 0x4AC | 收到的 RequestSecurityTokenResponse 訊息格式不正確。指定的 AppliesTo URL 是 '%1'，但應該是 '%2'。 |
The RequestSecurityTokenResponse message received was not in the correct format. AppliesTo URL '%1' was specified but '%2' was expected. |
| 0x4AD | 所收到使用 Kerberos AP_REQ 安全性權杖保護的訊息遺失了權杖資訊。 |
The received message secured using Kerberos AP_REQ security token is missing the token information. |
| 0x4AE | 無法加密不透明 Windows 認證。 |
Unable to encrypt opaque Windows credential. |
| 0x4AF | 無法解密不透明 Windows 認證。 |
Unable to decrypt opaque Windows credential. |
| 0x4B0 | 收到的 RequestSecurityTokenResponse 訊息格式錯誤。指定的 RequestType 是 '%1'，但應該是 '%2'。 |
The RequestSecurityTokenResponse message received was not in the correct format. RequestType '%1' was specified but '%2' was expected. |
| 0x4B1 | 對於陣列宣告，WS_FIELD_POINTER 只能用於 WS_STRUCT_TYPE 類型。 |
For array declaration, WS_FIELD_POINTER may by used only for WS_STRUCT_TYPE type. |
| 0x4B2 | 發現 NULL 值的陣列元素，但不能有 NULL (未指定 WS_FIELD_NILLABLE_ITEM 選項)。 |
NULL-valued array element found, but NULLs are not allowed (WS_FIELD_NILLABLE_ITEM option is not specified). |
| 0x4B3 | 指定之 WS_FAULT_DETAIL_DESCRIPTION 的 WS_ELEMENT_DESCRIPTION 需要名稱和命名空間。 |
The WS_ELEMENT_DESCRIPTION of the specified WS_FAULT_DETAIL_DESCRIPTION requires a name and namespace. |
| 0x4B4 | 無法配置記憶體來處理所有信任的簽發者憑證。 |
Unable to allocate memory to process all trusted issuer certificates. |
| 0x4B5 | 無法為 WS_CONTRACT_DESCRIPTION 結構中的 'operations' 欄位結構配置記憶體。 |
Unable to allocate memory for 'operations' field structures in WS_CONTRACT_DESCRIPTION structure. |
| 0x4B6 | 無法為 WS_SECURITY_DESCRIPTION 結構中的 'securityBindings' 欄位配置記憶體。 |
Unable to allocate memory for 'securityBindings' field in WS_SECURITY_DESCRIPTION structure. |
| 0x4B7 | 無法為 WS_SERVICE_METADATA 結構中的 'documents' 欄位配置記憶體。 |
Unable to allocate memory for 'documents' field in WS_SERVICE_METADATA structure. |
| 0x4B8 | 無法為 WS_DISALLOWED_USER_AGENT_SUBSTRINGS 結構中的 'subStrings' 欄位配置記憶體。 |
Unable to allocate memory for 'subStrings' field in WS_DISALLOWED_USER_AGENT_SUBSTRINGS structure. |
| 0x4B9 | 無法為 WS_METADATA_ENDPOINTS 結構中的 'endpoints' 欄位配置記憶體。 |
Unable to allocate memory for 'endpoints' field in WS_METADATA_ENDPOINTS structure. |
| 0x4BA | 無法為 WS_XML_DICTIONARY 結構中的 'strings' 欄位配置記憶體。 |
Unable to allocate memory for 'strings' field in WS_XML_DICTIONARY structure. |
| 0x4BB | 無法為 WS_XML_CANONICALIZATION_INCLUSIVE_PREFIXES 結構中的 'prefixes' 欄位配置記憶體。 |
Unable to allocate memory for 'prefixes' field in WS_XML_CANONICALIZATION_INCLUSIVE_PREFIXES structure. |
| 0x4BC | 無法複製 WS_CHANNEL_PROPERTY_HTTP_MESSAGE_MAPPING 屬性。 |
Unable to clone WS_CHANNEL_PROPERTY_HTTP_MESSAGE_MAPPING property. |
| 0x4BD | 無法為 WS_HTTP_MESSAGE_MAPPING 結構中的 'responseHeaderMappings' 欄位配置記憶體。 |
Unable to allocate memory for 'responseHeaderMappings' field in WS_HTTP_MESSAGE_MAPPING structure. |
| 0x4BE | 無法為 WS_FAULT 結構中的 'reasons' 欄位配置記憶體。 |
Unable to allocate memory for 'reasons' field in WS_FAULT structure. |
| 0x4BF | 無法為 WS_POLICY_CONSTRAINTS 結構中的 'policyExtensions' 欄位配置記憶體。 |
Unable to allocate memory for 'policyExtensions' field in WS_POLICY_CONSTRAINTS structure. |
| 0x4C0 | 無法為 WS_SERVICE_SECURITY_IDENTITIES 結構中的 'serviceIdentities' 欄位配置記憶體。 |
Unable to allocate memory for 'serviceIdentities' field in WS_SERVICE_SECURITY_IDENTITIES structure. |
| 0x4C1 | 無法為 WS_OPERATION_DESCRIPTION 結構中的 'parameterDescription' 欄位配置記憶體。 |
Unable to allocate memory for 'parameterDescription' field in WS_OPERATION_DESCRIPTION structure. |
| 0x4C2 | 無法為 WS_XML_STRING 結構中的 'bytes' 欄位配置記憶體。 |
Unable to allocate memory for 'bytes' field in WS_XML_STRING structure. |
| 0x4C3 | 具名管道 '%1' 未就緒。 |
The named pipe '%1' is not ready. |
| 0x4C4 | 找不到具名管道 '%1'。 |
The named pipe '%1' was not found. |
| 0x4C5 | 在具名管道傳送資料時發生錯誤。 |
There was an error sending data on the named pipe. |
| 0x4C6 | 從具名管道接收時發生錯誤。 |
There was an error receiving from the named pipe. |
| 0x4C7 | 無法建立具名管道。 |
Unable to create named pipe. |
| 0x4C8 | 無法建立檔案對應。 |
Unable to create file mapping. |
| 0x4C9 | 無法建立檔案的對應檢視。 |
Unable to create map view of file. |
| 0x4CA | 指定的具名管道已在使用中。 |
The specified named pipe is already in use. |
| 0x4CB | 接受具名管道時發生錯誤。 |
There was an error accepting a named pipe. |
| 0x4CC | 無法建立具名管道的安全性描述元。 |
Unable to create the security descriptor for a named pipe. |
| 0x4CD | 無法設定具名管道。 |
Unable to configure a named pipe. |
| 0x4CE | 無法檢查應用程式是否正在應用程式容器中執行。最後一個錯誤為 '%1'。 |
Unable to check if application is running in app container. The last error is '%1'. |
| 0x4CF | 在 AppContainer 中執行的處理程序不支援內容 '%1'。 |
The property '%1' is not supported in a process running in an AppContainer. |
| 0x4D0 | 在 AppContainer 中執行的處理程序不支援此 API。 |
The API is not supported in a process running in an AppContainer. |
| 0x4D1 | 正在傳送 HTTP 標頭驗證結構描述探查要求。 |
Sending HTTP header authentication schema probe request. |
| 0x4D2 | 收到對 HTTP 標頭驗證結構描述探查要求的回應。 |
Received response to the HTTP header authentication schema probe request. |
| 0x4D3 | URL: %3 上的端點數目已到達通道建立數目上限 (%4)。此事件在過去 %1 秒內發生過 %2 次。 |
Endpoint at URL: %3 has reached maximum number of created channels which is %4. This event was encountered %2 times during last %1 seconds. |
| 0x4D4 | 位於 URL: %3 之端點上的通道數目已到達訊息建立數目上限 (每個通道 %4 個)。此事件在過去 %1 秒內發生過 %2 次。 |
Channels at endpoint at URL: %3 have reached maximum number of created messages which is %4 per channel. This event was encountered %2 times during last %1 seconds. |
| 0x4D5 | 已使用動作: %1 呼叫 WsCall。 |
WsCall called with action: %1. |
| 0x4D6 | 含動作: %1 的 WsCall 失敗，錯誤: %2。 |
WsCall with action: %1 failed with error: %2. |
| 0x4D7 | 含動作: %1 的 WsCall 成功。 |
WsCall with action: %1 succeded. |
| 0x4D8 | 服務主機收到含有動作標頭: %1 的訊息。 |
Service host received a message with an action header: %1. |
| 0x4D9 | 服務主機收到不含動作的訊息。 |
Message without an action has been received by service host. |
| 0x4DA | 服務主機因為收到不正確的 HTTP 動詞而失敗，發生錯誤: %1。 |
Service host received bad HTTP verb and failed with error: %1. |
| 0x4DB | 服務主機因為呼叫者使用不正確的 HTTP 動詞而傳回錯誤。 |
Service host sent back an error because caller used bad HTTP verb. |
| 0x4DC | 服務主機因為發生錯誤: %1 而無法回應 GET 中繼資料要求。 |
Service host is unable to respond to the GET metadata request because of error: %1. |
| 0x4DD | 服務主機傳回中繼資料以回應 GET 要求。 |
Service host sent a metadata in response to the GET request. |
| 0x4DE | 分派含動作: %1 的服務主機呼叫失敗，發生錯誤: %2。 |
Service host call with action: %1 was dispatch and failed with error: %2. |
| 0x4DF | 分派含動作: %1 的服務主機呼叫成功。 |
Service host call with action: %1 was dispatched and succeeded. |
| 0x4E0 | 服務主機中繼資料呼叫分派失敗，發生錯誤: %1。 |
Service host metadata call dispatch failed with error: %1. |
| 0x4E1 | 服務主機中繼資料呼叫分派成功。 |
Service host metadata call dispatch succeeded. |
| 0x4E2 | 服務要求失敗，因為找不到要求的資源: %1。 |
Service request failed because requested resource could not be found: %1. |
| 0x4E3 | 服務要求失敗，因為找不到要求的資源。 |
Service request failed because requested resource could not be found. |
| 0x003D0000 | 正在以非同步方式完成函式呼叫。 |
The function call is completing asynchronously. |
| 0x003D0001 | 通道已經沒有可用的訊息。 |
There are no more messages available on the channel. |
| 0x10000001 | API |
API |
| 0x10000002 | 錯誤 |
Error |
| 0x10000003 | IO |
IO |
| 0x10000004 | 訊息 |
Message |
| 0x10000005 | BinaryMessage |
BinaryMessage |
| 0x3000000A | API 進入 |
API Enter |
| 0x3000000B | API ExitSyncSuccess |
API ExitSyncSuccess |
| 0x3000000C | API ExitSyncFailure |
API ExitSyncFailure |
| 0x3000000D | API 擱置 |
API Pending |
| 0x3000000E | API ExitAsyncSuccess |
API ExitAsyncSuccess |
| 0x3000000F | API ExitAsyncFailure |
API ExitAsyncFailure |
| 0x30000010 | IO 已開始 |
IO Started |
| 0x30000011 | IO 已完成 |
IO Completed |
| 0x30000012 | IO 已失敗 |
IO Failed |
| 0x30000014 | 傳送訊息 - 二進位 |
Sending Message - Binary |
| 0x30000015 | 接收訊息 - 二進位 |
Received Message - Binary |
| 0x30000016 | 傳送訊息 - 文字 |
Sending Message - Text |
| 0x30000017 | 接收訊息 - 文字 |
Received Message - Text |
| 0x30000018 | 傳送訊息開始 |
Sending Message Start |
| 0x30000019 | 傳送訊息停止 |
Sending Message Stop |
| 0x3000001A | 接收訊息開始 |
Received Message Start |
| 0x3000001B | 接收訊息停止 |
Received Message Stop |
| 0x3000001C | 正在傳送 HTTP 標頭 |
Sending HTTP headers |
| 0x3000001D | 正在接收 HTTP 標頭 |
Receiving HTTP headers |
| 0x3000001E | 追蹤 |
Trace |
| 0x50000004 | 資訊 |
Information |
| 0x50000005 | 詳細資訊 |
Verbose |
| 0x70000003 | IO 操作 |
IO Operations |
| 0x70000004 | 訊息交換 |
Message Exchange |
| 0x803D0000 | 輸入的資料不是預期的格式，或者不是預期的值。 |
The input data was not in the expected format or did not have the expected value. |
| 0x803D0001 | 因為先前的錯誤使物件處於錯誤狀態，所以無法完成操作。 |
The operation could not be completed because the object is in a faulted state due to a previous error. |
| 0x803D0002 | 因為操作會導致數字溢位，所以無法完成。 |
The operation could not be completed because it would lead to numeric overflow. |
| 0x803D0003 | 因為物件的目前狀態，所以不允許操作。 |
The operation is not allowed due to the current state of the object. |
| 0x803D0004 | 該操作已經中止。 |
The operation was aborted. |
| 0x803D0005 | 遠端端點拒絕存取。 |
Access was denied by the remote endpoint. |
| 0x803D0006 | 未在指定的時間內完成操作。 |
The operation did not complete within the time allotted. |
| 0x803D0007 | 操作已放棄。 |
The operation was abandoned. |
| 0x803D0008 | 超出配額。 |
A quota was exceeded. |
| 0x803D0009 | 不提供指定語言版本的資訊。 |
The information was not available in the specified language. |
| 0x803D000A | 對接收的資料進行安全性驗證失敗。 |
Security verification was not successful for the received data. |
| 0x803D000B | 位址已在使用中。 |
The address is already being used. |
| 0x803D000C | 位址對這種內容而言無效。 |
The address is not valid for this context. |
| 0x803D000D | 遠端端點不存在或找不到。 |
The remote endpoint does not exist or could not be located. |
| 0x803D000E | 這個位置的遠端端點目前不提供服務。 |
The remote endpoint is not currently in service at this location. |
| 0x803D000F | 遠端端點無法處理要求。 |
The remote endpoint could not process the request. |
| 0x803D0010 | 無法連線到遠端端點。 |
The remote endpoint was not reachable. |
| 0x803D0011 | 遠端端點不支援此項操作。 |
The operation was not supported by the remote endpoint. |
| 0x803D0012 | 由於遠端端點超載，無法處理要求。 |
The remote endpoint is unable to process the request due to being overloaded. |
| 0x803D0013 | 從遠端端點收到包含錯誤的訊息。 |
A message containing a fault was received from the remote endpoint. |
| 0x803D0014 | 已經終止與遠端端點的連線。 |
The connection with the remote endpoint was terminated. |
| 0x803D0015 | HTTP Proxy 伺服器無法處理要求。 |
The HTTP proxy server could not process the request. |
| 0x803D0016 | HTTP Proxy 伺服器拒絕存取。 |
Access was denied by the HTTP proxy server. |
| 0x803D0017 | 這個平台不提供要求的功能。 |
The requested feature is not available on this platform. |
| 0x803D0018 | HTTP Proxy 伺服器需要 HTTP 驗證配置 'basic'。 |
The HTTP proxy server requires HTTP authentication scheme 'basic'. |
| 0x803D0019 | HTTP Proxy 伺服器需要 HTTP 驗證配置 'digest'。 |
The HTTP proxy server requires HTTP authentication scheme 'digest'. |
| 0x803D001A | HTTP Proxy 伺服器需要 HTTP 驗證配置 'NTLM'。 |
The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
| 0x803D001B | HTTP Proxy 伺服器需要 HTTP 驗證配置 'negotiate'。 |
The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
| 0x803D001C | 遠端端點需要 HTTP 驗證配置 'basic'。 |
The remote endpoint requires HTTP authentication scheme 'basic'. |
| 0x803D001D | 遠端端點需要 HTTP 驗證配置 'digest'。 |
The remote endpoint requires HTTP authentication scheme 'digest'. |
| 0x803D001E | 遠端端點需要 HTTP 驗證配置 'NTLM'。 |
The remote endpoint requires HTTP authentication scheme 'NTLM'. |
| 0x803D001F | 遠端端點需要 HTTP 驗證配置 'negotiate'。 |
The remote endpoint requires HTTP authentication scheme 'negotiate'. |
| 0x803D0020 | 端點位址 URL 無效。 |
The endpoint address URL is invalid. |
| 0x803D0021 | Windows Web 服務架構發生無法辨識的錯誤。 |
Unrecognized error occurred in the Windows Web Services framework. |
| 0x803D0022 | 伺服器已拒絕安全性權杖，因為它已到期。 |
A security token was rejected by the server because it has expired. |
| 0x803D0023 | Windows Web 服務架構發生安全性作業失敗。 |
A security operation failed in the Windows Web Services framework. |
| 0x90000001 | Microsoft-Windows-WebServices |
Microsoft-Windows-WebServices |
| 0xB0000001 | 已經呼叫 %1 API。 |
%1 API is called. |
| 0xB0000002 | 已經傳回 %1 API。 |
%1 API returned. |
| 0xB0000003 | %2 的 %1 API 失敗 |
%1 API failed by %2 |
| 0xB0000004 | %1 API 待完成。 |
%1 API is pending completion. |
| 0xB0000005 | %1 API 已完成。 |
%1 API completed. |
| 0xB0000006 | %2 的 %1 API 無法完成 |
%1 API failed to complete by %2 |
| 0xB0000007 | 發生錯誤: %1 - %2 |
Error occurred: %1 - %2 |
| 0xB0000008 | %1 IO 操作已開始。 |
%1 IO operation started. |
| 0xB0000009 | %1 IO 操作已完成，已傳送 %2 個位元組。 |
%1 IO operation completed, %2 bytes transferred. |
| 0xB000000A | %1 IO 操作失敗: %2 |
%1 IO operation failed: %2 |
| 0xB000000B | 傳送訊息 - bin (id: %1): %n%3 |
Sending message - bin (id: %1): %n%3 |
| 0xB000000C | 接收訊息 - bin (id: %1): %n%3 |
Received message - bin (id: %1): %n%3 |
| 0xB000000D | 傳送訊息 (id: %1): %n%3 |
Sending message (id: %1): %n%3 |
| 0xB000000E | 接收訊息 (id: %1): %n%3 |
Received message (id: %1): %n%3 |
| 0xB000000F | 開始傳送訊息 (id: %1) |
Sending Message Start (id: %1) |
| 0xB0000010 | 停止傳送訊息 (id: %1) |
Sending Message Stop (id: %1) |
| 0xB0000011 | 開始接收訊息 (id: %1) |
Received Message Start (id: %1) |
| 0xB0000012 | 停止接收訊息 (id: %1) |
Received Message Stop (id: %1) |
| 0xB0000013 | 正在傳送下列 HTTP 標頭: %1 |
Sending following HTTP headers: %1 |
| 0xB0000014 | 正在接收下列 HTTP 標頭: %1 |
Receiving following HTTP headers: %1 |
| 0xB0000015 | 追蹤: %1 |
Trace: %1 |
| 0xD0000001 | WsStartReaderCanonicalization |
WsStartReaderCanonicalization |
| 0xD0000002 | WsEndReaderCanonicalization |
WsEndReaderCanonicalization |
| 0xD0000003 | WsStartWriterCanonicalization |
WsStartWriterCanonicalization |
| 0xD0000004 | WsEndWriterCanonicalization |
WsEndWriterCanonicalization |
| 0xD0000005 | WsCreateXmlBuffer |
WsCreateXmlBuffer |
| 0xD0000006 | WsRemoveNode |
WsRemoveNode |
| 0xD0000007 | WsCreateReader |
WsCreateReader |
| 0xD0000008 | WsSetInput |
WsSetInput |
| 0xD0000009 | WsSetInputToBuffer |
WsSetInputToBuffer |
| 0xD000000A | WsFreeReader |
WsFreeReader |
| 0xD000000B | WsGetReaderProperty |
WsGetReaderProperty |
| 0xD000000C | WsGetReaderNode |
WsGetReaderNode |
| 0xD000000D | WsFillReader |
WsFillReader |
| 0xD000000E | WsReadStartElement |
WsReadStartElement |
| 0xD000000F | WsReadToStartElement |
WsReadToStartElement |
| 0xD0000010 | WsReadStartAttribute |
WsReadStartAttribute |
| 0xD0000011 | WsReadEndAttribute |
WsReadEndAttribute |
| 0xD0000012 | WsReadNode |
WsReadNode |
| 0xD0000013 | WsSkipNode |
WsSkipNode |
| 0xD0000014 | WsReadEndElement |
WsReadEndElement |
| 0xD0000015 | WsFindAttribute |
WsFindAttribute |
| 0xD0000016 | WsReadValue |
WsReadValue |
| 0xD0000017 | WsReadChars |
WsReadChars |
| 0xD0000018 | WsReadCharsUtf8 |
WsReadCharsUtf8 |
| 0xD0000019 | WsReadBytes |
WsReadBytes |
| 0xD000001A | WsReadArray |
WsReadArray |
| 0xD000001B | WsGetReaderPosition |
WsGetReaderPosition |
| 0xD000001C | WsSetReaderPosition |
WsSetReaderPosition |
| 0xD000001D | WsMoveReader |
WsMoveReader |
| 0xD000001E | WsCreateWriter |
WsCreateWriter |
| 0xD000001F | WsFreeWriter |
WsFreeWriter |
| 0xD0000020 | WsSetOutput |
WsSetOutput |
| 0xD0000021 | WsSetOutputToBuffer |
WsSetOutputToBuffer |
| 0xD0000022 | WsGetWriterProperty |
WsGetWriterProperty |
| 0xD0000023 | WsFlushWriter |
WsFlushWriter |
| 0xD0000024 | WsWriteStartElement |
WsWriteStartElement |
| 0xD0000025 | WsWriteEndStartElement |
WsWriteEndStartElement |
| 0xD0000026 | WsWriteXmlnsAttribute |
WsWriteXmlnsAttribute |
| 0xD0000027 | WsWriteStartAttribute |
WsWriteStartAttribute |
| 0xD0000028 | WsWriteEndAttribute |
WsWriteEndAttribute |
| 0xD0000029 | WsWriteValue |
WsWriteValue |
| 0xD000002A | WsWriteXmlBuffer |
WsWriteXmlBuffer |
| 0xD000002B | WsReadXmlBuffer |
WsReadXmlBuffer |
| 0xD000002C | WsWriteXmlBufferToBytes |
WsWriteXmlBufferToBytes |
| 0xD000002D | WsReadXmlBufferFromBytes |
WsReadXmlBufferFromBytes |
| 0xD000002E | WsWriteArray |
WsWriteArray |
| 0xD000002F | WsWriteQualifiedName |
WsWriteQualifiedName |
| 0xD0000030 | WsWriteChars |
WsWriteChars |
| 0xD0000031 | WsWriteCharsUtf8 |
WsWriteCharsUtf8 |
| 0xD0000032 | WsWriteBytes |
WsWriteBytes |
| 0xD0000033 | WsPushBytes |
WsPushBytes |
| 0xD0000034 | WsPullBytes |
WsPullBytes |
| 0xD0000035 | WsWriteEndElement |
WsWriteEndElement |
| 0xD0000036 | WsWriteText |
WsWriteText |
| 0xD0000037 | WsWriteStartCData |
WsWriteStartCData |
| 0xD0000038 | WsWriteEndCData |
WsWriteEndCData |
| 0xD0000039 | WsWriteNode |
WsWriteNode |
| 0xD000003A | WsGetPrefixFromNamespace |
WsGetPrefixFromNamespace |
| 0xD000003B | WsGetWriterPosition |
WsGetWriterPosition |
| 0xD000003C | WsSetWriterPosition |
WsSetWriterPosition |
| 0xD000003D | WsMoveWriter |
WsMoveWriter |
| 0xD000003E | WsTrimXmlWhitespace |
WsTrimXmlWhitespace |
| 0xD000003F | WsVerifyXmlNCName |
WsVerifyXmlNCName |
| 0xD0000040 | WsXmlStringEquals |
WsXmlStringEquals |
| 0xD0000041 | WsGetNamespaceFromPrefix |
WsGetNamespaceFromPrefix |
| 0xD0000042 | WsReadQualifiedName |
WsReadQualifiedName |
| 0xD0000043 | WsGetXmlAttribute |
WsGetXmlAttribute |
| 0xD0000044 | WsCopyNode |
WsCopyNode |
| 0xD0000045 | WsAsyncExecute |
WsAsyncExecute |
| 0xD0000046 | WsCreateChannel |
WsCreateChannel |
| 0xD0000047 | WsOpenChannel |
WsOpenChannel |
| 0xD0000048 | WsSendMessage |
WsSendMessage |
| 0xD0000049 | WsReceiveMessage |
WsReceiveMessage |
| 0xD000004A | WsRequestReply |
WsRequestReply |
| 0xD000004B | WsSendReplyMessage |
WsSendReplyMessage |
| 0xD000004C | WsSendFaultMessageForError |
WsSendFaultMessageForError |
| 0xD000004D | WsGetChannelProperty |
WsGetChannelProperty |
| 0xD000004E | WsSetChannelProperty |
WsSetChannelProperty |
| 0xD000004F | WsWriteMessageStart |
WsWriteMessageStart |
| 0xD0000050 | WsWriteMessageEnd |
WsWriteMessageEnd |
| 0xD0000051 | WsReadMessageStart |
WsReadMessageStart |
| 0xD0000052 | WsReadMessageEnd |
WsReadMessageEnd |
| 0xD0000053 | WsCloseChannel |
WsCloseChannel |
| 0xD0000054 | WsAbortChannel |
WsAbortChannel |
| 0xD0000055 | WsFreeChannel |
WsFreeChannel |
| 0xD0000056 | WsResetChannel |
WsResetChannel |
| 0xD0000057 | WsAbandonMessage |
WsAbandonMessage |
| 0xD0000058 | WsShutdownSessionChannel |
WsShutdownSessionChannel |
| 0xD0000059 | WsGetOperationContextProperty |
WsGetOperationContextProperty |
| 0xD000005A | WsGetDictionary |
WsGetDictionary |
| 0xD000005B | WsReadEndpointAddressExtension |
WsReadEndpointAddressExtension |
| 0xD000005C | WsCreateError |
WsCreateError |
| 0xD000005D | WsAddErrorString |
WsAddErrorString |
| 0xD000005E | WsGetErrorString |
WsGetErrorString |
| 0xD000005F | WsCopyError |
WsCopyError |
| 0xD0000060 | WsGetErrorProperty |
WsGetErrorProperty |
| 0xD0000061 | WsSetErrorProperty |
WsSetErrorProperty |
| 0xD0000062 | WsResetError |
WsResetError |
| 0xD0000063 | WsFreeError |
WsFreeError |
| 0xD0000064 | WsGetFaultErrorProperty |
WsGetFaultErrorProperty |
| 0xD0000065 | WsSetFaultErrorProperty |
WsSetFaultErrorProperty |
| 0xD0000066 | WsCreateFaultFromError |
WsCreateFaultFromError |
| 0xD0000067 | WsSetFaultErrorDetail |
WsSetFaultErrorDetail |
| 0xD0000068 | WsGetFaultErrorDetail |
WsGetFaultErrorDetail |
| 0xD0000069 | WsCreateHeap |
WsCreateHeap |
| 0xD000006A | WsAlloc |
WsAlloc |
| 0xD000006B | WsGetHeapProperty |
WsGetHeapProperty |
| 0xD000006C | WsResetHeap |
WsResetHeap |
| 0xD000006D | WsFreeHeap |
WsFreeHeap |
| 0xD000006E | WsCreateListener |
WsCreateListener |
| 0xD000006F | WsOpenListener |
WsOpenListener |
| 0xD0000070 | WsAcceptChannel |
WsAcceptChannel |
| 0xD0000071 | WsCloseListener |
WsCloseListener |
| 0xD0000072 | WsAbortListener |
WsAbortListener |
| 0xD0000073 | WsResetListener |
WsResetListener |
| 0xD0000074 | WsFreeListener |
WsFreeListener |
| 0xD0000075 | WsGetListenerProperty |
WsGetListenerProperty |
| 0xD0000076 | WsSetListenerProperty |
WsSetListenerProperty |
| 0xD0000077 | WsCreateChannelForListener |
WsCreateChannelForListener |
| 0xD0000078 | WsCreateMessage |
WsCreateMessage |
| 0xD0000079 | WsCreateMessageForChannel |
WsCreateMessageForChannel |
| 0xD000007A | WsInitializeMessage |
WsInitializeMessage |
| 0xD000007B | WsResetMessage |
WsResetMessage |
| 0xD000007C | WsFreeMessage |
WsFreeMessage |
| 0xD000007D | WsGetHeaderAttributes |
WsGetHeaderAttributes |
| 0xD000007E | WsGetHeader |
WsGetHeader |
| 0xD000007F | WsGetCustomHeader |
WsGetCustomHeader |
| 0xD0000080 | WsRemoveHeader |
WsRemoveHeader |
| 0xD0000081 | WsSetHeader |
WsSetHeader |
| 0xD0000082 | WsRemoveCustomHeader |
WsRemoveCustomHeader |
| 0xD0000083 | WsAddCustomHeader |
WsAddCustomHeader |
| 0xD0000084 | WsAddMappedHeader |
WsAddMappedHeader |
| 0xD0000085 | WsRemoveMappedHeader |
WsRemoveMappedHeader |
| 0xD0000086 | WsGetMappedHeader |
WsGetMappedHeader |
| 0xD0000087 | WsWriteBody |
WsWriteBody |
| 0xD0000088 | WsReadBody |
WsReadBody |
| 0xD0000089 | WsWriteEnvelopeStart |
WsWriteEnvelopeStart |
| 0xD000008A | WsWriteEnvelopeEnd |
WsWriteEnvelopeEnd |
| 0xD000008B | WsReadEnvelopeStart |
WsReadEnvelopeStart |
| 0xD000008C | WsReadEnvelopeEnd |
WsReadEnvelopeEnd |
| 0xD000008D | WsGetMessageProperty |
WsGetMessageProperty |
| 0xD000008E | WsSetMessageProperty |
WsSetMessageProperty |
| 0xD000008F | WsAddressMessage |
WsAddressMessage |
| 0xD0000090 | WsCheckMustUnderstandHeaders |
WsCheckMustUnderstandHeaders |
| 0xD0000091 | WsMarkHeaderAsUnderstood |
WsMarkHeaderAsUnderstood |
| 0xD0000092 | WsFillBody |
WsFillBody |
| 0xD0000093 | WsFlushBody |
WsFlushBody |
| 0xD0000094 | WsRequestSecurityToken |
WsRequestSecurityToken |
| 0xD0000095 | WsGetSecurityTokenProperty |
WsGetSecurityTokenProperty |
| 0xD0000096 | WsCreateXmlSecurityToken |
WsCreateXmlSecurityToken |
| 0xD0000097 | WsFreeSecurityToken |
WsFreeSecurityToken |
| 0xD0000098 | WsRevokeSecurityContext |
WsRevokeSecurityContext |
| 0xD0000099 | WsGetSecurityContextProperty |
WsGetSecurityContextProperty |
| 0xD000009A | WsReadElement |
WsReadElement |
| 0xD000009B | WsReadAttribute |
WsReadAttribute |
| 0xD000009C | WsReadType |
WsReadType |
| 0xD000009D | WsWriteElement |
WsWriteElement |
| 0xD000009E | WsWriteAttribute |
WsWriteAttribute |
| 0xD000009F | WsWriteType |
WsWriteType |
| 0xD00000A0 | WsRegisterOperationForCancel |
WsRegisterOperationForCancel |
| 0xD00000A1 | WsGetServiceHostProperty |
WsGetServiceHostProperty |
| 0xD00000A2 | WsCreateServiceHost |
WsCreateServiceHost |
| 0xD00000A3 | WsOpenServiceHost |
WsOpenServiceHost |
| 0xD00000A4 | WsCloseServiceHost |
WsCloseServiceHost |
| 0xD00000A5 | WsAbortServiceHost |
WsAbortServiceHost |
| 0xD00000A6 | WsFreeServiceHost |
WsFreeServiceHost |
| 0xD00000A7 | WsResetServiceHost |
WsResetServiceHost |
| 0xD00000A8 | WsGetServiceProxyProperty |
WsGetServiceProxyProperty |
| 0xD00000A9 | WsCreateServiceProxy |
WsCreateServiceProxy |
| 0xD00000AA | WsOpenServiceProxy |
WsOpenServiceProxy |
| 0xD00000AB | WsCloseServiceProxy |
WsCloseServiceProxy |
| 0xD00000AC | WsAbortServiceProxy |
WsAbortServiceProxy |
| 0xD00000AD | WsFreeServiceProxy |
WsFreeServiceProxy |
| 0xD00000AE | WsResetServiceProxy |
WsResetServiceProxy |
| 0xD00000AF | WsAbandonCall |
WsAbandonCall |
| 0xD00000B0 | WsCall |
WsCall |
| 0xD00000B1 | WsDecodeUrl |
WsDecodeUrl |
| 0xD00000B2 | WsEncodeUrl |
WsEncodeUrl |
| 0xD00000B3 | WsCombineUrl |
WsCombineUrl |
| 0xD00000B4 | WsDateTimeToFileTime |
WsDateTimeToFileTime |
| 0xD00000B5 | WsFileTimeToDateTime |
WsFileTimeToDateTime |
| 0xD00000B6 | WsDumpMemory |
WsDumpMemory |
| 0xD00000B7 | WsSetAutoFail |
WsSetAutoFail |
| 0xD00000B8 | WsCreateMetadata |
WsCreateMetadata |
| 0xD00000B9 | WsReadMetadata |
WsReadMetadata |
| 0xD00000BA | WsFreeMetadata |
WsFreeMetadata |
| 0xD00000BB | WsResetMetadata |
WsResetMetadata |
| 0xD00000BC | WsGetMetadataProperty |
WsGetMetadataProperty |
| 0xD00000BD | WsGetMissingMetadataDocumentAddress |
WsGetMissingMetadataDocumentAddress |
| 0xD00000BE | WsGetMetadataEndpoints |
WsGetMetadataEndpoints |
| 0xD00000BF | WsMatchPolicyAlternative |
WsMatchPolicyAlternative |
| 0xD00000C0 | WsGetPolicyProperty |
WsGetPolicyProperty |
| 0xD00000C1 | WsGetPolicyAlternativeCount |
WsGetPolicyAlternativeCount |
| 0xD00000C2 | WsCreateServiceProxyFromTemplate |
WsCreateServiceProxyFromTemplate |
| 0xD00000C3 | WsCreateServiceEndpointFromTemplate |
WsCreateServiceEndpointFromTemplate |
| 0xD00000C4 | 傳送 |
Send |
| 0xD00000C5 | 接收 |
Receive |
| 0xD00000C6 | 接受 |
Accept |
| 0xD00000C7 | 連線 |
Connect |
| 0xD00000C8 | WaitForDisconnect |
WaitForDisconnect |