| 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 | 属性 ID“%1”未被识别或不受支持。 |
The property ID '%1' was not recognized or supported. |
| 0x13 | 属性 ID“%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 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 | 服务器已返回 HTTP 状态代码“%1”以及文本“%2”。 |
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 | 方案 ID“%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 | 系统无法生成唯一的 ID。 |
The system was unable to generate a unique ID. |
| 0xA1 | 应答消息的“关联到”ID 值与请求消息的 ID 不匹配。 |
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 | 为侦听套接字获取 accept 函数时出错。 |
There was an error getting the accept function for the listen socket. |
| 0xC6 | 为套接字获取 connect 函数时出错。 |
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 | 在 URL 中用作主机名时，IPv6 地址“%1”必须包括在括号中。 |
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 为零。 |
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 | 运行时内存分配要求 %1 个字节，这超过了堆中提供的 %2 个字节限制。 |
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 | 该字符串包含嵌入式零。 |
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”包含字符值零，而此值在该上下文中是非法的。 |
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 | 日期时间格式“%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。如果分钟值和秒钟值均为零，则允许使用 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 位整数 %1 与 %2 相加，因为结果将超出不带符号 32 位整数的范围。 |
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 位整数 %1 与 %2 相乘，因为结果将超出不带符号 32 位整数的范围。 |
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 位整数 %1 与 %2 相加，因为结果将超出不带符号 64 位整数的范围。 |
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 位整数 %1 与 %2 相乘，因为结果将超出不带符号 64 位整数的范围。 |
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 | 不能将前缀“%1”绑定到命名空间“%2”，因为该前缀以 \"xml\" 开头。 |
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 | 不能将前缀“%1”绑定到命名空间“%3”，因为它已绑定到“%2”。 |
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 | 存在具有相同前缀“%1”的两个 xmlns 属性。 |
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，但不需要。 |
An start CDATA was found, but not expected. |
| 0x17D | 找到结尾 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)超出范围。在元素“%3”上只有 %2 个具有命名空间“%4”的属性。 |
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 字符串的 ID 无效。 |
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 的长度为零。 |
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 | 编码类型(%1)在 MTOM 编码中无效。 |
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 | 指定了 NULL 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 | 值“%1”不是 WS_ENUM_DESCRIPTION 中的有效值。 |
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 在 WSDL 文档中定义了多次。 |
The portType with name '%1' from namespace '%2' was defined more than once in the WSDL document. |
| 0x21C | 命名空间“%2”中名为“%1”的 portType 在所有的 WSDL 文档中都找不到。 |
The portType with name '%1' from namespace '%2' could not be found in any of the WSDL documents. |
| 0x21D | 命名空间“%2”中名为“%1”的消息在所有的 WSDL 文档中都找不到。 |
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 | 命名空间“%2”中名为“%1”的绑定在所有的 WSDL 文档中都找不到。 |
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 令牌，但是需要包含一个 kerberos 令牌。 |
The policy alternative did not contain a kerberos token but one was required. |
| 0x265 | 策略替代项不包含 X.509 令牌，但是需要包含一个 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 引用，但是系统不支持外部 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 | 策略替换选项指定的加密信息设置不是所需设置。 |
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 | 在通道上指定了默认的消息处理程序时，并发不能大于一。 |
When a default message handler on a channel is specified concurrency cannot be greater than one. |
| 0x280 | 非基于会话的通道不能具有一以上的并发。 |
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 | 无法设置套接字的保持活动状态设置。 |
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 | 当前服务代理状态“%1”不适用于所请求操作。 |
The current service proxy state '%1' was not appropriate for the requested operation. |
| 0x290 | 调用了 'WsAbortServiceProxy'，因此服务代理正在中止。 |
'WsAbortServiceProxy' was called, as a result Service Proxy is aborting. |
| 0x291 | 放弃了对服务代理的调用。 |
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 但长度无效。长度必须为二的倍数。 |
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 不支持将载荷密钥类型作为请求参数。 |
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 客户端连接限制不能为零。 |
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 | 对于指定的 HTTP 标头身份验证方案而言，为目标服务器指定的 WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL 无效。 |
The specified WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL for the target server is not valid for the specified HTTP header authentication scheme. |
| 0x307 | 对于指定的 HTTP 标头身份验证方案而言，为代理服务器指定的 WS_WINDOWS_INTEGRATED_AUTH_CREDENTIAL 无效。 |
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 | 安全加密信息模式“%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 | 请求的安全属性 ID“%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 | 参数描述的计数为 %1，而 WS_OPERATION_DESCRIPTION 上的 parameterDescription 为 NULL。 |
The count for parameter description is %1 while parameterDescription is NULL on WS_OPERATION_DESCRIPTION. |
| 0x33C | 参数计数为零，但 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 | 由于服务代理处于“%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 | 不支持指定的安全算法 ID“%1”。 |
The specified security algorithm id '%1' is not supported. |
| 0x37A | 为请求的操作指定的安全算法 ID“%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 | 类型参数的 Content-Type 标头应该为“%1”，但找到的是“%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”无效。其长度为零、大于 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 | 从 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 | 为输入 WS_MESSAGE_DESCRIPTION 的给定 WS_ELEMENT_DESCRIPTION 的给定 WS_STRUCT_DESCRIPTION 指定了 NULL WS_FIELD_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 | 为输出 WS_MESSAGE_DESCRIPTION 的给定 WS_ELEMENT_DESCRIPTION 的给定 WS_STRUCT_DESCRIPTION 指定了 NULL WS_FIELD_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 ID“%2”不可识别或不受支持。 |
The %1 id '%2' was not recognized or supported. |
| 0x3AE | 在属性列表中多次指定了 %1 ID“%2”。 |
The %1 id '%2' was specified more than once in the list of properties. |
| 0x3AF | 对于当前操作而言，%1 ID“%2”无效。 |
The %1 id '%2' is not valid for the current operation. |
| 0x3B0 | 为 %1 ID“%2”指定的缓冲区无效。它不应为 NULL。 |
The buffer specified for %1 id '%2' is invalid. It should not be NULL. |
| 0x3B1 | 为 %1 ID“%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 ID“%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 ID“%2”失败。 |
Failed to clone %1 id '%2'. |
| 0x3B4 | %1 数组为 NULL 或者数组的计数为零。 |
Either the %1 array is NULL or the count of the array is zero. |
| 0x3B5 | 为属性 ID“%1”指定的缓冲区无效。它不应为 NULL。 |
The buffer specified for property id '%1' is invalid. It should not be NULL. |
| 0x3B6 | 为属性 ID“%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 ID“%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 安全绑定不支持多路 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 | 当 WS_SERVICE_METADATA 中的 \"documents\" 字段本身指向 NULL 时，其计数为非零。 |
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\" 字段为零。 |
The 'count' field is zero while the 'documents' field in WS_SERVICE_METADATA is non NULL. |
| 0x3DF | 当 WS_SERVICE_METADATA 中的 \"serviceName\" 字段为非 NULL 时，\"count\" 字段为零。 |
The 'count' field is zero while the 'serviceName' field in WS_SERVICE_METADATA is non NULL. |
| 0x3E0 | 当 WS_SERVICE_METADATA 中的 \"serviceNs\" 字段为非 NULL 时，\"count\" 字段为零。 |
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 | 不支持指定的编码类型“%1”。 |
The specified encodingType '%1' is not supported. |
| 0x3F6 | MTOM 文档的字符集应该为“%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 代理设置。 |
Unable to retrieve IE proxy settings for the current user. |
| 0x3F9 | 无法配置用于 HTTP 请求的代理设置。 |
Unable to configure proxy settings for the HTTP request. |
| 0x3FA | 将通道属性 \"WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE\" 指定为 \"WS_HTTP_PROXY_SETTING_MODE_CUSTOM\" 时，必须指定通道属性 \"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 | 针对代理服务器的 HTTP 标头身份验证安全绑定不支持指定多个标头身份验证方案。 |
HTTP header authentication security binding against the proxy server does not support specifying multiple header authentication schemes. |
| 0x407 | 针对代理服务器的 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 ID“%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\" 指定的值必须为零。 |
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_HTTP_CHANNEL_BINDING\" 仅支持当前 \"WS_ENCODING\"。 |
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\" 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\" 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\" 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\" 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\" ID \"WS_CHANNEL_PROPERTY_HTTP_PROXY_SETTING_MODE\" 指定为 \"WS_HTTP_PROXY_SETTING_MODE_NONE\" 时，不能指定 \"WS_CHANNEL_PROPERTY_ID\" 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 | 检索自动代理设置失败。 |
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 ID“%2”时，克隆 \"WS_DISALLOWED_USER_AGENT_LIST\" 失败。 |
Failed to clone 'WS_DISALLOWED_USER_AGENT_LIST' while cloning %1 id '%2'. |
| 0x423 | 在 \"WS_DISALLOWED_USER_AGENT_LIST\" 中，如果 \"subStrings\" 为 NULL，则 \"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 代理无法连接服务器。 |
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，或者从未发出与消息 ID 的关系)”。 |
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 | 服务器返回了信任错误:“摘要元素不足”。 |
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 身份验证方案。 |
The server requires HTTP authentication scheme 'basic'. |
| 0x46C | 服务器需要 \"NTLM\" HTTP 身份验证方案。 |
The server requires HTTP authentication scheme 'NTLM'. |
| 0x46D | 服务器需要“摘要”HTTP 身份验证方案。 |
The server requires HTTP authentication scheme 'digest'. |
| 0x46E | 服务器需要“协商”HTTP 身份验证方案。 |
The server requires HTTP authentication scheme 'negotiate'. |
| 0x46F | 代理需要“基本”HTTP 身份验证方案。 |
The proxy requires HTTP authentication scheme 'basic'. |
| 0x470 | 代理需要 \"NTLM\" HTTP 身份验证方案。 |
The proxy requires HTTP authentication scheme 'NTLM'. |
| 0x471 | 代理需要“摘要”HTTP 身份验证方案。 |
The proxy requires HTTP authentication scheme 'digest'. |
| 0x472 | 代理需要“协商”HTTP 身份验证方案。 |
The proxy requires HTTP authentication scheme 'negotiate'. |
| 0x473 | 放弃期间，正文串行化失败。 |
During abandon the body failed to serialize. |
| 0x474 | 代理发生故障，因此即将中止调用。 |
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 | 无法连接给定的代理。 |
The given proxy cannot be reached. |
| 0x486 | 在使用属性 ID“%1”调用 WsGetSecurityTokenProperty 时，\"heap\" 参数必须为 NULL。 |
When calling WsGetSecurityTokenProperty with property id '%1', the 'heap' parameter must be NULL. |
| 0x487 | 在使用属性 ID“%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 代理设置的代理服务器名称格式不正确。 |
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 标头属性 ID“%1”不能用作消息属性。 |
The XML reader property ID '%1' cannot be used as a message property. |
| 0x4AB | XML 编写器属性 ID“%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 | 由于以下错误，服务主机无法响应 GET 元数据请求: %1。 |
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 代理服务器无法处理请求。 |
The HTTP proxy server could not process the request. |
| 0x803D0016 | 访问被 HTTP 代理服务器拒绝。 |
Access was denied by the HTTP proxy server. |
| 0x803D0017 | 请求的功能在此平台上不可用。 |
The requested feature is not available on this platform. |
| 0x803D0018 | HTTP 代理服务器需要“基本”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'basic'. |
| 0x803D0019 | HTTP 代理服务器需要“摘要式”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'digest'. |
| 0x803D001A | HTTP 代理服务器需要 \"NTLM\" HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
| 0x803D001B | HTTP 代理服务器需要“协商”HTTP 身份验证方案。 |
The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
| 0x803D001C | 远程终结点需要“基本”HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'basic'. |
| 0x803D001D | 远程终结点需要“摘要式”HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'digest'. |
| 0x803D001E | 远程终结点需要 \"NTLM\" HTTP 身份验证方案。 |
The remote endpoint requires HTTP authentication scheme 'NTLM'. |
| 0x803D001F | 远程终结点需要“协商”HTTP 身份验证方案。 |
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 | %1 API 因 %2 而失败 |
%1 API failed by %2 |
| 0xB0000004 | %1 API 尚未完成。 |
%1 API is pending completion. |
| 0xB0000005 | %1 API 已完成。 |
%1 API completed. |
| 0xB0000006 | %1 API 由于 %2 而未完成 |
%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 |