赞
踩
The following table provides a list of system error codes (errors 12000 to 15999). These values are defined in the WinError.h header file. They are returned by the GetLastError function when many functions fail. To retrieve the description text for the error in your application, use the FormatMessage function with the FORMAT_MESSAGE_FROM_SYSTEM flag.【下表列出了系统错误代码(错误12000到15999)。这些值在WinError.h头文件中定义。当许多函数失败时,GetLastError函数返回它们。要检索应用程序中错误的描述文本,请使用FormatMessage函数和FORMAT_MESSAGE_FROM_SYSTEM 标志。】
If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to http://support.microsoft.com.【如果正在安装或运行的应用程序遇到困难,请与客户支持联系以获取显示错误消息的软件。要获得对Microsoft产品的支持,请转到http://support.microsoft.com。】
ERROR_INTERNET_* (see Wininet.h) | 12000 - 12174 | Internet Error Codes【Internet错误代码】 |
ERROR_IPSEC_QM_POLICY_EXISTS | 13000 | The specified quick mode policy already exists.【指定的快速模式策略已存在。】 |
ERROR_IPSEC_QM_POLICY_NOT_FOUND | 13001 | The specified quick mode policy was not found.【找不到指定的快速模式策略。】 |
ERROR_IPSEC_QM_POLICY_IN_USE | 13002 | The specified quick mode policy is being used.【正在使用指定的快速模式策略。】 |
ERROR_IPSEC_MM_POLICY_EXISTS | 13003 | The specified main mode policy already exists.【指定的主模式策略已存在。】 |
ERROR_IPSEC_MM_POLICY_NOT_FOUND | 13004 | The specified main mode policy was not found【找不到指定的主模式策略】 |
ERROR_IPSEC_MM_POLICY_IN_USE | 13005 | The specified main mode policy is being used.【正在使用指定的主模式策略。】 |
ERROR_IPSEC_MM_FILTER_EXISTS | 13006 | The specified main mode filter already exists.【指定的主模式筛选器已存在。】 |
ERROR_IPSEC_MM_FILTER_NOT_FOUND | 13007 | The specified main mode filter was not found.【找不到指定的主模式筛选器。】 |
ERROR_IPSEC_TRANSPORT_FILTER_EXISTS | 13008 | The specified transport mode filter already exists.【指定的传输模式筛选器已存在。】 |
ERROR_IPSEC_TRANSPORT_FILTER_NOT_FOUND | 13009 | The specified transport mode filter does not exist.【指定的传输模式筛选器不存在。】 |
ERROR_IPSEC_MM_AUTH_EXISTS | 13010 | The specified main mode authentication list exists.【指定的主模式身份验证列表已存在。】 |
ERROR_IPSEC_MM_AUTH_NOT_FOUND | 13011 | The specified main mode authentication list was not found.【找不到指定的主模式身份验证列表。】 |
ERROR_IPSEC_MM_AUTH_IN_USE | 13012 | The specified main mode authentication list is being used.【正在使用指定的主模式身份验证列表。】 |
ERROR_IPSEC_DEFAULT_MM_POLICY_NOT_FOUND | 13013 | The specified default main mode policy was not found.【找不到指定的默认主模式策略。】 |
ERROR_IPSEC_DEFAULT_MM_AUTH_NOT_FOUND | 13014 | The specified default main mode authentication list was not found.【找不到指定的默认主模式身份验证列表。】 |
ERROR_IPSEC_DEFAULT_QM_POLICY_NOT_FOUND | 13015 | The specified default quick mode policy was not found.【找不到指定的默认快速模式策略。】 |
ERROR_IPSEC_TUNNEL_FILTER_EXISTS | 13016 | The specified tunnel mode filter exists.【指定的隧道模式筛选器存在。】 |
ERROR_IPSEC_TUNNEL_FILTER_NOT_FOUND | 13017 | The specified tunnel mode filter was not found.【找不到指定的隧道模式筛选器。】 |
ERROR_IPSEC_MM_FILTER_PENDING_DELETION | 13018 | The Main Mode filter is pending deletion.【主模式筛选器正在挂起删除。】 |
ERROR_IPSEC_TRANSPORT_FILTER_PENDING_DELETION | 13019 | The transport filter is pending deletion.【传输筛选器正在等待删除。】 |
ERROR_IPSEC_TUNNEL_FILTER_PENDING_DELETION | 13020 | The tunnel filter is pending deletion.【隧道筛选器正在等待删除。】 |
ERROR_IPSEC_MM_POLICY_PENDING_DELETION | 13021 | The Main Mode policy is pending deletion.【主模式策略正在挂起删除。】 |
ERROR_IPSEC_MM_AUTH_PENDING_DELETION | 13022 | The Main Mode authentication bundle is pending deletion.【主模式身份验证捆绑包正在挂起删除。】 |
ERROR_IPSEC_QM_POLICY_PENDING_DELETION | 13023 | The Quick Mode policy is pending deletion.【快速模式策略正在挂起删除。】 |
WARNING_IPSEC_MM_POLICY_PRUNED | 13024 | The Main Mode policy was successfully added, but some of the requested offers are not supported.【已成功添加主模式策略,但不支持某些请求的提供程序。】 |
WARNING_IPSEC_QM_POLICY_PRUNED | 13025 | The Quick Mode policy was successfully added, but some of the requested offers are not supported.【已成功添加快速模式策略,但不支持某些请求的提供。】 |
ERROR_IPSEC_IKE_NEG_STATUS_BEGIN | 13800 | ERROR_IPSEC_IKE_NEG_STATUS_BEGIN【错误\u IPSEC \u IKE \u NEG \u STATUS \u BEGIN】 |
ERROR_IPSEC_IKE_AUTH_FAIL | 13801 | IKE authentication credentials are unacceptable【IKE身份验证凭据不可接受】 |
ERROR_IPSEC_IKE_ATTRIB_FAIL | 13802 | IKE security attributes are unacceptable【IKE安全属性不可接受】 |
ERROR_IPSEC_IKE_NEGOTIATION_PENDING | 13803 | IKE Negotiation in progress【IKE协商进行中】 |
ERROR_IPSEC_IKE_GENERAL_PROCESSING_ERROR | 13804 | General processing error【一般处理错误】 |
ERROR_IPSEC_IKE_TIMED_OUT | 13805 | Negotiation timed out【协商超时】 |
ERROR_IPSEC_IKE_NO_CERT | 13806 | IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.【IKE找不到有效的计算机证书。有关在相应的证书存储中安装有效证书的信息,请与网络安全管理员联系。】 |
ERROR_IPSEC_IKE_SA_DELETED | 13807 | IKE SA deleted by peer before establishment completed【IKE SA在建立完成前被对等方删除】 |
ERROR_IPSEC_IKE_SA_REAPED | 13808 | IKE SA deleted before establishment completed【IKE SA在建立完成前删除】 |
ERROR_IPSEC_IKE_MM_ACQUIRE_DROP | 13809 | Negotiation request sat in Queue too long【协商请求在队列中的时间过长】 |
ERROR_IPSEC_IKE_QM_ACQUIRE_DROP | 13810 | Negotiation request sat in Queue too long【协商请求在队列中的时间过长】 |
ERROR_IPSEC_IKE_QUEUE_DROP_MM | 13811 | Negotiation request sat in Queue too long【协商请求在队列中的时间过长】 |
ERROR_IPSEC_IKE_QUEUE_DROP_NO_MM | 13812 | Negotiation request sat in Queue too long【协商请求在队列中的时间过长】 |
ERROR_IPSEC_IKE_DROP_NO_RESPONSE | 13813 | No response from peer【同行无回应】 |
ERROR_IPSEC_IKE_MM_DELAY_DROP | 13814 | Negotiation took too long【谈判时间太长了】 |
ERROR_IPSEC_IKE_QM_DELAY_DROP | 13815 | Negotiation took too long【谈判时间太长了】 |
ERROR_IPSEC_IKE_ERROR | 13816 | Unknown error occurred【发生未知错误】 |
ERROR_IPSEC_IKE_CRL_FAILED | 13817 | Certificate Revocation Check failed【证书吊销检查失败】 |
ERROR_IPSEC_IKE_INVALID_KEY_USAGE | 13818 | Invalid certificate key usage【证书密钥用法无效】 |
ERROR_IPSEC_IKE_INVALID_CERT_TYPE | 13819 | Invalid certificate type【无效的证书类型】 |
ERROR_IPSEC_IKE_NO_PRIVATE_KEY | 13820 | IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.【IKE协商失败,因为使用的计算机证书没有私钥。IPsec证书需要私钥。请与您的网络安全管理员联系,以替换为具有私钥的证书。】 |
ERROR_IPSEC_IKE_DH_FAIL | 13822 | Failure in Diffie-Hellman computation【Diffie-Hellman计算失败】 |
ERROR_IPSEC_IKE_INVALID_HEADER | 13824 | Invalid header【标头无效】 |
ERROR_IPSEC_IKE_NO_POLICY | 13825 | No policy configured【未配置策略】 |
ERROR_IPSEC_IKE_INVALID_SIGNATURE | 13826 | Failed to verify signature【验证签名失败】 |
ERROR_IPSEC_IKE_KERBEROS_ERROR | 13827 | Failed to authenticate using Kerberos【无法使用Kerberos进行身份验证】 |
ERROR_IPSEC_IKE_NO_PUBLIC_KEY | 13828 | Peer’s certificate did not have a public key【对等方的证书没有公钥】 |
ERROR_IPSEC_IKE_PROCESS_ERR | 13829 | Error processing error payload【处理错误负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_SA | 13830 | Error processing SA payload【处理SA负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_PROP | 13831 | Error processing Proposal payload【处理建议负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_TRANS | 13832 | Error processing Transform payload【处理转换负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_KE | 13833 | Error processing KE payload【处理KE负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_ID | 13834 | Error processing ID payload【处理ID负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_CERT | 13835 | Error processing Cert payload【处理证书负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_CERT_REQ | 13836 | Error processing Certificate Request payload【处理证书请求负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_HASH | 13837 | Error processing Hash payload【处理哈希负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_SIG | 13838 | Error processing Signature payload【处理签名负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_NONCE | 13839 | Error processing Nonce payload【处理Nonce负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_NOTIFY | 13840 | Error processing Notify payload【处理通知负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_DELETE | 13841 | Error processing Delete Payload【处理删除负载时出错】 |
ERROR_IPSEC_IKE_PROCESS_ERR_VENDOR | 13842 | Error processing VendorId payload【处理VendorId负载时出错】 |
ERROR_IPSEC_IKE_INVALID_PAYLOAD | 13843 | Invalid payload received【接收到无效负载】 |
ERROR_IPSEC_IKE_LOAD_SOFT_SA | 13844 | Soft SA loaded【软SA加载】 |
ERROR_IPSEC_IKE_SOFT_SA_TORN_DOWN | 13845 | Soft SA torn down【软SA拆卸】 |
ERROR_IPSEC_IKE_INVALID_COOKIE | 13846 | Invalid cookie received.【接收到无效的cookie。】 |
ERROR_IPSEC_IKE_NO_PEER_CERT | 13847 | Peer failed to send valid machine certificate【对等方未能发送有效的计算机证书】 |
ERROR_IPSEC_IKE_PEER_CRL_FAILED | 13848 | Certification Revocation check of peer’s certificate failed【对等方证书的证书吊销检查失败】 |
ERROR_IPSEC_IKE_POLICY_CHANGE | 13849 | New policy invalidated SAs formed with old policy【新政策使旧政策形成的社会保障体系失效】 |
ERROR_IPSEC_IKE_NO_MM_POLICY | 13850 | There is no available Main Mode IKE policy.【没有可用的主模式IKE策略。】 |
ERROR_IPSEC_IKE_NOTCBPRIV | 13851 | Failed to enabled TCB privilege.【未能启用TCB权限。】 |
ERROR_IPSEC_IKE_SECLOADFAIL | 13852 | Failed to load SECURITY.DLL.【加载失败安全.DLL.】 |
ERROR_IPSEC_IKE_FAILSSPINIT | 13853 | Failed to obtain security function table dispatch address from SSPI.【无法从SSPI获取安全函数表调度地址。】 |
ERROR_IPSEC_IKE_FAILQUERYSSP | 13854 | Failed to query Kerberos package to obtain max token size.【无法查询Kerberos包以获取最大令牌大小。】 |
ERROR_IPSEC_IKE_SRVACQFAIL | 13855 | Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.【无法获取ISAKMP/ERROR\u IPSEC\u IKE服务的Kerberos服务器凭据。Kerberos身份验证将不起作用。最可能的原因是缺乏域成员资格。如果您的计算机是工作组的成员,这是正常的。】 |
ERROR_IPSEC_IKE_SRVQUERYCRED | 13856 | Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).【无法确定ISAKMP/ERROR\u IPSEC\u IKE服务(QueryCredentialsAttributes)的SSPI主体名称。】 |
ERROR_IPSEC_IKE_GETSPIFAIL | 13857 | Failed to obtain new SPI for the inbound SA from Ipsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.【无法从Ipsec驱动程序获取入站SA的新SPI。最常见的原因是驱动程序没有正确的筛选器。检查策略以验证筛选器。】 |
ERROR_IPSEC_IKE_INVALID_FILTER | 13858 | Given filter is invalid【给定的筛选器无效】 |
ERROR_IPSEC_IKE_OUT_OF_MEMORY | 13859 | Memory allocation failed.【内存分配失败。】 |
ERROR_IPSEC_IKE_ADD_UPDATE_KEY_FAILED | 13860 | Failed to add Security Association to IPSec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.【未能将安全关联添加到IPSec驱动程序。最常见的原因是IKE协商花费了太长时间才完成。如果问题仍然存在,请降低故障机器上的负载。】 |
ERROR_IPSEC_IKE_INVALID_POLICY | 13861 | Invalid policy【无效的策略】 |
ERROR_IPSEC_IKE_UNKNOWN_DOI | 13862 | Invalid DOI【无效的DOI】 |
ERROR_IPSEC_IKE_INVALID_SITUATION | 13863 | Invalid situation【无效情况】 |
ERROR_IPSEC_IKE_DH_FAILURE | 13864 | Diffie-Hellman failure【迪菲-赫尔曼失败】 |
ERROR_IPSEC_IKE_INVALID_GROUP | 13865 | Invalid Diffie-Hellman group【Diffie-Hellman组无效】 |
ERROR_IPSEC_IKE_ENCRYPT | 13866 | Error encrypting payload【加密有效负载时出错】 |
ERROR_IPSEC_IKE_DECRYPT | 13867 | Error decrypting payload【解密负载时出错】 |
ERROR_IPSEC_IKE_POLICY_MATCH | 13868 | Policy match error【策略匹配错误】 |
ERROR_IPSEC_IKE_UNSUPPORTED_ID | 13869 | Unsupported ID【不支持的ID】 |
ERROR_IPSEC_IKE_INVALID_HASH | 13870 | Hash verification failed【哈希验证失败】 |
ERROR_IPSEC_IKE_INVALID_HASH_ALG | 13871 | Invalid hash algorithm【哈希算法无效】 |
ERROR_IPSEC_IKE_INVALID_HASH_SIZE | 13872 | Invalid hash size【哈希大小无效】 |
ERROR_IPSEC_IKE_INVALID_ENCRYPT_ALG | 13873 | Invalid encryption algorithm【加密算法无效】 |
ERROR_IPSEC_IKE_INVALID_AUTH_ALG | 13874 | Invalid authentication algorithm【无效的身份验证算法】 |
ERROR_IPSEC_IKE_INVALID_SIG | 13875 | Invalid certificate signature【无效的证书签名】 |
ERROR_IPSEC_IKE_LOAD_FAILED | 13876 | Load failed【加载失败】 |
ERROR_IPSEC_IKE_RPC_DELETE | 13877 | Deleted via RPC call【通过RPC调用删除】 |
ERROR_IPSEC_IKE_BENIGN_REINIT | 13878 | Temporary state created to perform reinit. This is not a real failure.【为执行reinit而创建的临时状态。这不是真正的失败。】 |
ERROR_IPSEC_IKE_INVALID_RESPONDER_LIFETIME_NOTIFY | 13879 | The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.【响应程序生存期通知中接收的生存期值低于Windows 2000配置的最小值。请修复对等计算机上的策略。】 |
ERROR_IPSEC_IKE_INVALID_CERT_KEYLEN | 13881 | Key length in certificate is too small for configured security requirements.【证书中的密钥长度太小,无法满足配置的安全要求。】 |
ERROR_IPSEC_IKE_MM_LIMIT | 13882 | Max number of established MM SAs to peer exceeded.【已超过对等机的最大已建立MM sa数。】 |
ERROR_IPSEC_IKE_NEGOTIATION_DISABLED | 13883 | IKE received a policy that disables negotiation.【IKE收到一个禁用协商的策略。】 |
ERROR_IPSEC_IKE_QM_LIMIT | 13884 | Reached maximum quick mode limit for the main mode. New main mode will be started.【已达到主模式的最大快速模式限制。将启动新的主模式。】 |
ERROR_IPSEC_IKE_MM_EXPIRED | 13885 | Main mode SA lifetime expired or peer sent a main mode delete.【主模式SA生存期已过期或对等方发送了主模式删除。】 |
ERROR_IPSEC_IKE_PEER_MM_ASSUMED_INVALID | 13886 | Main mode SA assumed to be invalid because peer stopped responding.【主模式SA假定无效,因为对等方停止响应。】 |
ERROR_IPSEC_IKE_CERT_CHAIN_POLICY_MISMATCH | 13887 | Certificate doesn’t chain to a trusted root in IPsec policy.【证书未链接到IPsec策略中的受信任根。】 |
ERROR_IPSEC_IKE_UNEXPECTED_MESSAGE_ID | 13888 | Received unexpected message ID.【收到意外消息ID。】 |
ERROR_IPSEC_IKE_INVALID_AUTH_PAYLOAD | 13889 | Received invalid authentication offers.【收到无效的身份验证提供。】 |
ERROR_IPSEC_IKE_DOS_COOKIE_SENT | 13890 | Sent DOS cookie notify to initiator.【已将DOS cookie通知发送给发起程序。】 |
ERROR_IPSEC_IKE_SHUTTING_DOWN | 13891 | IKE service is shutting down.【IKE服务正在关闭。】 |
ERROR_IPSEC_IKE_CGA_AUTH_FAILED | 13892 | Could not verify binding between CGA address and certificate.【无法验证CGA地址和证书之间的绑定。】 |
ERROR_IPSEC_IKE_PROCESS_ERR_NATOA | 13893 | Error processing NatOA payload.【处理NatOA负载时出错。】 |
ERROR_IPSEC_IKE_INVALID_MM_FOR_QM | 13894 | Parameters of the main mode are invalid for this quick mode.【主模式的参数对此快速模式无效。】 |
ERROR_IPSEC_IKE_QM_EXPIRED | 13895 | Quick mode SA was expired by IPsec driver.【快速模式SA已被IPsec驱动程序过期。】 |
ERROR_IPSEC_IKE_TOO_MANY_FILTERS | 13896 | Too many dynamically added IKEEXT filters were detected.【检测到太多动态添加的IKEEXT筛选器。】 |
ERROR_IPSEC_BAD_SPI | 13910 | The SPI in the packet does not match a valid IPsec SA.【数据包中的SPI与有效的IPsec SA不匹配。】 |
ERROR_IPSEC_SA_LIFETIME_EXPIRED | 13911 | Packet was received on an IPsec SA whose lifetime has expired.【在生存期已过期的IPsec SA上接收到数据包。】 |
ERROR_IPSEC_WRONG_SA | 13912 | Packet was received on an IPsec SA that doesn’t match the packet characteristics.【在与数据包特征不匹配的IPsec SA上接收到数据包。】 |
ERROR_IPSEC_REPLAY_CHECK_FAILED | 13913 | Packet sequence number replay check failed.【数据包序列号重播检查失败。】 |
ERROR_IPSEC_INVALID_PACKET | 13914 | IPsec header and/or trailer in the packet is invalid.【数据包中的IPsec标头和/或尾部无效。】 |
ERROR_IPSEC_INTEGRITY_CHECK_FAILED | 13915 | IPsec integrity check failed.【IPsec完整性检查失败。】 |
ERROR_IPSEC_CLEAR_TEXT_DROP | 13916 | IPsec dropped a clear text packet.【IPsec丢弃了一个明文包。】 |
ERROR_SXS_SECTION_NOT_FOUND | 14000 | The requested section was not present in the activation context.【激活上下文中不存在请求的节。】 |
ERROR_SXS_CANT_GEN_ACTCTX | 14001 | The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.【应用程序无法启动,因为其并排配置不正确。有关详细信息,请参阅应用程序事件日志。】 |
ERROR_SXS_INVALID_ACTCTXDATA_FORMAT | 14002 | The application binding data format is invalid.【应用程序绑定数据格式无效。】 |
ERROR_SXS_ASSEMBLY_NOT_FOUND | 14003 | The referenced assembly is not installed on your system.【系统上未安装引用的程序集。】 |
ERROR_SXS_MANIFEST_FORMAT_ERROR | 14004 | The manifest file does not begin with the required tag and format information.【清单文件不以所需的标记和格式信息开头。】 |
ERROR_SXS_MANIFEST_PARSE_ERROR | 14005 | The manifest file contains one or more syntax errors.【清单文件包含一个或多个语法错误。】 |
ERROR_SXS_ACTIVATION_CONTEXT_DISABLED | 14006 | The application attempted to activate a disabled activation context.【应用程序试图激活已禁用的激活上下文。】 |
ERROR_SXS_KEY_NOT_FOUND | 14007 | The requested lookup key was not found in any active activation context.【在任何活动激活上下文中都找不到请求的查找密钥。】 |
ERROR_SXS_VERSION_CONFLICT | 14008 | A component version required by the application conflicts with another component version already active.【应用程序所需的组件版本与另一个已激活的组件版本冲突。】 |
ERROR_SXS_WRONG_SECTION_TYPE | 14009 | The type requested activation context section does not match the query API used.【请求的类型激活上下文部分与使用的查询API不匹配。】 |
ERROR_SXS_THREAD_QUERIES_DISABLED | 14010 | Lack of system resources has required isolated activation to be disabled for the current thread of execution.【缺少系统资源要求对当前执行线程禁用独立激活。】 |
ERROR_SXS_PROCESS_DEFAULT_ALREADY_SET | 14011 | An attempt to set the process default activation context failed because the process default activation context was already set.【尝试设置进程默认激活上下文失败,因为已设置进程默认激活上下文。】 |
ERROR_SXS_UNKNOWN_ENCODING_GROUP | 14012 | The encoding group identifier specified is not recognized.【无法识别指定的编码组标识符。】 |
ERROR_SXS_UNKNOWN_ENCODING | 14013 | The encoding requested is not recognized.【无法识别请求的编码。】 |
ERROR_SXS_INVALID_XML_NAMESPACE_URI | 14014 | The manifest contains a reference to an invalid URI.【清单包含对无效URI的引用。】 |
ERROR_SXS_ROOT_MANIFEST_DEPENDENCY_NOT_INSTALLED | 14015 | The application manifest contains a reference to a dependent assembly which is not installed【应用程序清单包含对未安装的依赖程序集的引用】 |
ERROR_SXS_LEAF_MANIFEST_DEPENDENCY_NOT_INSTALLED | 14016 | The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed【应用程序使用的程序集的清单引用了未安装的依赖程序集】 |
ERROR_SXS_INVALID_ASSEMBLY_IDENTITY_ATTRIBUTE | 14017 | The manifest contains an attribute for the assembly identity which is not valid.【清单包含无效的程序集标识属性。】 |
ERROR_SXS_MANIFEST_MISSING_REQUIRED_DEFAULT_NAMESPACE | 14018 | The manifest is missing the required default namespace specification on the assembly element.【清单缺少程序集元素上所需的默认命名空间规范。】 |
ERROR_SXS_MANIFEST_INVALID_REQUIRED_DEFAULT_NAMESPACE | 14019 | The manifest has a default namespace specified on the assembly element but its value is not “urn:schemas-microsoft-com:asm.v1”.【清单具有在程序集元素上指定的默认命名空间,但其值不是“urn:microsoft com架构:asm.v1“。】 |
ERROR_SXS_PRIVATE_MANIFEST_CROSS_PATH_WITH_REPARSE_POINT | 14020 | The private manifest probed has crossed reparse-point-associated path【探测到的私有清单已越过与重分析点关联的路径】 |
ERROR_SXS_DUPLICATE_DLL_NAME | 14021 | Two or more components referenced directly or indirectly by the application manifest have files by the same name.【应用程序清单直接或间接引用的两个或多个组件具有相同名称的文件。】 |
ERROR_SXS_DUPLICATE_WINDOWCLASS_NAME | 14022 | Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.【应用程序清单直接或间接引用的两个或多个组件具有同名的窗口类。】 |
ERROR_SXS_DUPLICATE_CLSID | 14023 | Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.【应用程序清单直接或间接引用的两个或多个组件具有相同的COM服务器CLSID。】 |
ERROR_SXS_DUPLICATE_IID | 14024 | Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.【应用程序清单直接或间接引用的两个或多个组件具有相同COM接口IID的代理。】 |
ERROR_SXS_DUPLICATE_TLBID | 14025 | Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.【应用程序清单直接或间接引用的两个或多个组件具有相同的COM类型库TLBIDs。】 |
ERROR_SXS_DUPLICATE_PROGID | 14026 | Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.【应用程序清单直接或间接引用的两个或多个组件具有相同的COM ProgID。】 |
ERROR_SXS_DUPLICATE_ASSEMBLY_NAME | 14027 | Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.【应用程序清单直接或间接引用的两个或多个组件是同一组件的不同版本,这是不允许的。】 |
ERROR_SXS_FILE_HASH_MISMATCH | 14028 | A component’s file does not match the verification information present in the component manifest.【组件的文件与组件清单中的验证信息不匹配。】 |
ERROR_SXS_POLICY_PARSE_ERROR | 14029 | The policy manifest contains one or more syntax errors.【策略清单包含一个或多个语法错误。】 |
ERROR_SXS_XML_E_MISSINGQUOTE | 14030 | Manifest Parse Error : A string literal was expected, but no opening quote character was found.【清单分析错误:需要字符串文本,但找不到开头引号字符。】 |
ERROR_SXS_XML_E_COMMENTSYNTAX | 14031 | Manifest Parse Error : Incorrect syntax was used in a comment.【清单分析错误:注释中使用了不正确的语法。】 |
ERROR_SXS_XML_E_BADSTARTNAMECHAR | 14032 | Manifest Parse Error : A name was started with an invalid character.【清单分析错误:名称以无效字符开头。】 |
ERROR_SXS_XML_E_BADNAMECHAR | 14033 | Manifest Parse Error : A name contained an invalid character.【清单分析错误:名称包含无效字符。】 |
ERROR_SXS_XML_E_BADCHARINSTRING | 14034 | Manifest Parse Error : A string literal contained an invalid character.【清单分析错误:字符串文本包含无效字符。】 |
ERROR_SXS_XML_E_XMLDECLSYNTAX | 14035 | Manifest Parse Error : Invalid syntax for an xml declaration.【清单分析错误:xml声明的语法无效。】 |
ERROR_SXS_XML_E_BADCHARDATA | 14036 | Manifest Parse Error : An Invalid character was found in text content.【清单分析错误:在文本内容中发现无效字符。】 |
ERROR_SXS_XML_E_MISSINGWHITESPACE | 14037 | Manifest Parse Error : Required white space was missing.【清单分析错误:缺少所需的空白。】 |
ERROR_SXS_XML_E_EXPECTINGTAGEND | 14038 | Manifest Parse Error : The character ‘>’ was expected.【清单分析错误:应为字符“>”。】 |
ERROR_SXS_XML_E_MISSINGSEMICOLON | 14039 | Manifest Parse Error : A semi colon character was expected.【清单分析错误:应为分号字符。】 |
ERROR_SXS_XML_E_UNBALANCEDPAREN | 14040 | Manifest Parse Error : Unbalanced parentheses.【清单分析错误:括号不平衡。】 |
ERROR_SXS_XML_E_INTERNALERROR | 14041 | Manifest Parse Error : Internal error.【清单分析错误:内部错误。】 |
ERROR_SXS_XML_E_UNEXPECTED_WHITESPACE | 14042 | Manifest Parse Error : Whitespace is not allowed at this location.【清单分析错误:此位置不允许空白。】 |
ERROR_SXS_XML_E_INCOMPLETE_ENCODING | 14043 | Manifest Parse Error : End of file reached in invalid state for current encoding.【清单分析错误:当前编码处于无效状态时到达文件结尾。】 |
ERROR_SXS_XML_E_MISSING_PAREN | 14044 | Manifest Parse Error : Missing parenthesis.【清单分析错误:缺少括号。】 |
ERROR_SXS_XML_E_EXPECTINGCLOSEQUOTE | 14045 | Manifest Parse Error : A single or double closing quote character (’ or ") is missing.【清单分析错误:缺少单引号或双引号字符('或\“)。】 |
ERROR_SXS_XML_E_MULTIPLE_COLONS | 14046 | Manifest Parse Error : Multiple colons are not allowed in a name.【清单分析错误:名称中不允许有多个冒号。】 |
ERROR_SXS_XML_E_INVALID_DECIMAL | 14047 | Manifest Parse Error : Invalid character for decimal digit.【清单分析错误:十进制数字的字符无效。】 |
ERROR_SXS_XML_E_INVALID_HEXIDECIMAL | 14048 | Manifest Parse Error : Invalid character for hexadecimal digit.【清单分析错误:十六进制数字的字符无效。】 |
ERROR_SXS_XML_E_INVALID_UNICODE | 14049 | Manifest Parse Error : Invalid unicode character value for this platform.【清单分析错误:此平台的unicode字符值无效。】 |
ERROR_SXS_XML_E_WHITESPACEORQUESTIONMARK | 14050 | Manifest Parse Error : Expecting whitespace or ‘?’.【清单分析错误:应为空白或“?”。】 |
ERROR_SXS_XML_E_UNEXPECTEDENDTAG | 14051 | Manifest Parse Error : End tag was not expected at this location.【清单分析错误:此位置不应有结束标记。】 |
ERROR_SXS_XML_E_UNCLOSEDTAG | 14052 | Manifest Parse Error : The following tags were not closed: %1.【清单分析错误:以下标记未关闭:%1。】 |
ERROR_SXS_XML_E_DUPLICATEATTRIBUTE | 14053 | Manifest Parse Error : Duplicate attribute.【清单分析错误:属性重复。】 |
ERROR_SXS_XML_E_MULTIPLEROOTS | 14054 | Manifest Parse Error : Only one top level element is allowed in an XML document.【清单分析错误:XML文档中只允许一个顶级元素。】 |
ERROR_SXS_XML_E_INVALIDATROOTLEVEL | 14055 | Manifest Parse Error : Invalid at the top level of the document.【清单分析错误:文档顶层无效。】 |
ERROR_SXS_XML_E_BADXMLDECL | 14056 | Manifest Parse Error : Invalid xml declaration.【清单分析错误:xml声明无效。】 |
ERROR_SXS_XML_E_MISSINGROOT | 14057 | Manifest Parse Error : XML document must have a top level element.【清单分析错误:XML文档必须具有顶级元素。】 |
ERROR_SXS_XML_E_UNEXPECTEDEOF | 14058 | Manifest Parse Error : Unexpected end of file.【清单分析错误:意外的文件结尾。】 |
ERROR_SXS_XML_E_BADPEREFINSUBSET | 14059 | Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.【清单分析错误:参数实体不能在内部子集中的标记声明中使用。】 |
ERROR_SXS_XML_E_UNCLOSEDSTARTTAG | 14060 | Manifest Parse Error : Element was not closed.【清单分析错误:元素未关闭。】 |
ERROR_SXS_XML_E_UNCLOSEDENDTAG | 14061 | Manifest Parse Error : End element was missing the character ‘>’.【清单分析错误:结束元素缺少字符’>’。】 |
ERROR_SXS_XML_E_UNCLOSEDSTRING | 14062 | Manifest Parse Error : A string literal was not closed.【清单分析错误:字符串文本未关闭。】 |
ERROR_SXS_XML_E_UNCLOSEDCOMMENT | 14063 | Manifest Parse Error : A comment was not closed.【清单分析错误:注释未关闭。】 |
ERROR_SXS_XML_E_UNCLOSEDDECL | 14064 | Manifest Parse Error : A declaration was not closed.【清单分析错误:声明未关闭。】 |
ERROR_SXS_XML_E_UNCLOSEDCDATA | 14065 | Manifest Parse Error : A CDATA section was not closed.【清单分析错误:CDATA节未关闭。】 |
ERROR_SXS_XML_E_RESERVEDNAMESPACE | 14066 | Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string “xml”.【清单分析错误:命名空间前缀不允许以保留字符串“xml”开头。】 |
ERROR_SXS_XML_E_INVALIDENCODING | 14067 | Manifest Parse Error : System does not support the specified encoding.【清单分析错误:系统不支持指定的编码。】 |
ERROR_SXS_XML_E_INVALIDSWITCH | 14068 | Manifest Parse Error : Switch from current encoding to specified encoding not supported.【清单分析错误:不支持从当前编码切换到指定编码。】 |
ERROR_SXS_XML_E_BADXMLCASE | 14069 | Manifest Parse Error : The name ‘xml’ is reserved and must be lower case.【清单分析错误:名称“xml”是保留的,必须小写。】 |
ERROR_SXS_XML_E_INVALID_STANDALONE | 14070 | Manifest Parse Error : The standalone attribute must have the value ‘yes’ or ‘no’.【清单分析错误:独立属性的值必须为“yes”或“no”。】 |
ERROR_SXS_XML_E_UNEXPECTED_STANDALONE | 14071 | Manifest Parse Error : The standalone attribute cannot be used in external entities.【清单分析错误:独立属性不能在外部实体中使用。】 |
ERROR_SXS_XML_E_INVALID_VERSION | 14072 | Manifest Parse Error : Invalid version number.【清单分析错误:版本号无效。】 |
ERROR_SXS_XML_E_MISSINGEQUALS | 14073 | Manifest Parse Error : Missing equals sign between attribute and attribute value.【清单分析错误:属性和属性值之间缺少等号。】 |
ERROR_SXS_PROTECTION_RECOVERY_FAILED | 14074 | Assembly Protection Error : Unable to recover the specified assembly.【程序集保护错误:无法恢复指定的程序集。】 |
ERROR_SXS_PROTECTION_PUBLIC_KEY_TOO_SHORT | 14075 | Assembly Protection Error : The public key for an assembly was too short to be allowed.【程序集保护错误:程序集的公钥太短,不允许使用。】 |
ERROR_SXS_PROTECTION_CATALOG_NOT_VALID | 14076 | Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly’s manifest.【程序集保护错误:程序集的目录无效,或与程序集的清单不匹配。】 |
ERROR_SXS_UNTRANSLATABLE_HRESULT | 14077 | An HRESULT could not be translated to a corresponding Win32 error code.【无法将HRESULT转换为相应的Win32错误代码。】 |
ERROR_SXS_PROTECTION_CATALOG_FILE_MISSING | 14078 | Assembly Protection Error : The catalog for an assembly is missing.【程序集保护错误:缺少程序集的目录。】 |
ERROR_SXS_MISSING_ASSEMBLY_IDENTITY_ATTRIBUTE | 14079 | The supplied assembly identity is missing one or more attributes which must be present in this context.【提供的程序集标识缺少此上下文中必须存在的一个或多个属性。】 |
ERROR_SXS_INVALID_ASSEMBLY_IDENTITY_ATTRIBUTE_NAME | 14080 | The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.【提供的程序集标识具有一个或多个属性名称,这些属性名称包含XML名称中不允许的字符。】 |
ERROR_SXS_ASSEMBLY_MISSING | 14081 | The referenced assembly could not be found.【找不到引用的程序集。】 |
ERROR_SXS_CORRUPT_ACTIVATION_STACK | 14082 | The activation context activation stack for the running thread of execution is corrupt.【正在运行的执行线程的激活上下文激活堆栈已损坏。】 |
ERROR_SXS_CORRUPTION | 14083 | The application isolation metadata for this process or thread has become corrupt.【此进程或线程的应用程序隔离元数据已损坏。】 |
ERROR_SXS_EARLY_DEACTIVATION | 14084 | The activation context being deactivated is not the most recently activated one.【正在停用的激活上下文不是最近激活的上下文。】 |
ERROR_SXS_INVALID_DEACTIVATION | 14085 | The activation context being deactivated is not active for the current thread of execution.【正在停用的激活上下文对于当前执行线程不是活动的。】 |
ERROR_SXS_MULTIPLE_DEACTIVATION | 14086 | The activation context being deactivated has already been deactivated.【正在停用的激活上下文已停用。】 |
ERROR_SXS_PROCESS_TERMINATION_REQUESTED | 14087 | A component used by the isolation facility has requested to terminate the process.【隔离设施使用的组件已请求终止进程。】 |
ERROR_SXS_RELEASE_ACTIVATION_CONTEXT | 14088 | A kernel mode component is releasing a reference on an activation context.【内核模式组件正在释放激活上下文上的引用。】 |
ERROR_SXS_SYSTEM_DEFAULT_ACTIVATION_CONTEXT_EMPTY | 14089 | The activation context of system default assembly could not be generated.【无法生成系统默认程序集的激活上下文。】 |
ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE | 14090 | The value of an attribute in an identity is not within the legal range.【标识中属性的值不在合法范围内。】 |
ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME | 14091 | The name of an attribute in an identity is not within the legal range.【标识中属性的名称不在合法范围内。】 |
ERROR_SXS_IDENTITY_DUPLICATE_ATTRIBUTE | 14092 | An identity contains two definitions for the same attribute.【标识包含同一属性的两个定义。】 |
ERROR_SXS_IDENTITY_PARSE_ERROR | 14093 | The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.【标识字符串格式不正确。这可能是由于后面有逗号、两个以上未命名的属性、缺少属性名或缺少属性值。】 |
ERROR_MALFORMED_SUBSTITUTION_STRING | 14094 | A string containing localized substitutable content was malformed. Either a dollar sign ( ) w a s f o l l o w e d b y s o m e t h i n g o t h e r t h a n a l e f t p a r e n t h e s i s o r a n o t h e r d o l l a r s i g n o r a n s u b s t i t u t i o n ′ s r i g h t p a r e n t h e s i s w a s n o t f o u n d . 【 包 含 本 地 化 可 替 换 内 容 的 字 符 串 格 式 不 正 确 。 一 个 美 元 符 号 ( ) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.【包含本地化可替换内容的字符串格式不正确。一个美元符号( )wasfollowedbysomethingotherthanaleftparenthesisoranotherdollarsignoransubstitution′srightparenthesiswasnotfound.【包含本地化可替换内容的字符串格式不正确。一个美元符号()后面跟的不是左括号,或者找不到另一个美元符号或替换的右括号。】 |
ERROR_SXS_INCORRECT_PUBLIC_KEY_TOKEN | 14095 | The public key token does not correspond to the public key specified.【公钥令牌与指定的公钥不对应。】 |
ERROR_UNMAPPED_SUBSTITUTION_STRING | 14096 | A substitution string had no mapping.【替换字符串没有映射。】 |
ERROR_SXS_ASSEMBLY_NOT_LOCKED | 14097 | The component must be locked before making the request.【发出请求前必须锁定组件。】 |
ERROR_SXS_COMPONENT_STORE_CORRUPT | 14098 | The component store has been corrupted.【组件存储已损坏。】 |
ERROR_ADVANCED_INSTALLER_FAILED | 14099 | An advanced installer failed during setup or servicing.【高级安装程序在安装或维护期间失败。】 |
ERROR_XML_ENCODING_MISMATCH | 14100 | The character encoding in the XML declaration did not match the encoding used in the document.【XML声明中的字符编码与文档中使用的编码不匹配。】 |
ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT | 14101 | The identities of the manifests are identical but their contents are different.【清单的身份相同,但内容不同。】 |
ERROR_SXS_IDENTITIES_DIFFERENT | 14102 | The component identities are different.【组件标识不同。】 |
ERROR_SXS_ASSEMBLY_IS_NOT_A_DEPLOYMENT | 14103 | The assembly is not a deployment.【程序集不是部署。】 |
ERROR_SXS_FILE_NOT_PART_OF_ASSEMBLY | 14104 | The file is not a part of the assembly.【文件不是程序集的一部分。】 |
ERROR_SXS_MANIFEST_TOO_BIG | 14105 | The size of the manifest exceeds the maximum allowed.【清单的大小超过了允许的最大值。】 |
ERROR_SXS_SETTING_NOT_REGISTERED | 14106 | The setting is not registered.【设置未注册。】 |
ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE | 14107 | One or more required members of the transaction are not present.【事务的一个或多个必需成员不存在。】 |
ERROR_SMI_PRIMITIVE_INSTALLER_FAILED | 14108 | The SMI primitive installer failed during setup or servicing.【SMI原语安装程序在安装或维护期间失败。】 |
ERROR_GENERIC_COMMAND_FAILED | 14109 | A generic command executable returned a result that indicates failure.【通用命令可执行文件返回一个指示失败的结果。】 |
ERROR_SXS_FILE_HASH_MISSING | 14110 | A component is missing file verification information in its manifest.【组件的清单中缺少文件验证信息。】 |
ERROR_EVT_INVALID_CHANNEL_PATH | 15000 | The specified channel path is invalid.【指定的通道路径无效。】 |
ERROR_EVT_INVALID_QUERY | 15001 | The specified query is invalid.【指定的查询无效。】 |
ERROR_EVT_PUBLISHER_METADATA_NOT_FOUND | 15002 | The publisher metadata cannot be found in the resource.【在资源中找不到发布服务器元数据。】 |
ERROR_EVT_EVENT_TEMPLATE_NOT_FOUND | 15003 | The template for an event definition cannot be found in the resource (error = %1).【在资源中找不到事件定义的模板(错误=%1)。】 |
ERROR_EVT_INVALID_PUBLISHER_NAME | 15004 | The specified publisher name is invalid.【指定的发布服务器名称无效。】 |
ERROR_EVT_INVALID_EVENT_DATA | 15005 | The event data raised by the publisher is not compatible with the event template definition in the publisher’s manifest【发布服务器引发的事件数据与发布服务器清单中的事件模板定义不兼容】 |
ERROR_EVT_CHANNEL_NOT_FOUND | 15007 | The specified channel could not be found. Check channel configuration.【找不到指定的通道。检查通道配置。】 |
ERROR_EVT_MALFORMED_XML_TEXT | 15008 | The specified xml text was not well-formed. See Extended Error for more details.【指定的xml文本格式不正确。有关详细信息,请参阅扩展错误。】 |
ERROR_EVT_SUBSCRIPTION_TO_DIRECT_CHANNEL | 15009 | The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to.【调用者试图订阅不允许的直接频道。直接通道的事件直接转到日志文件,无法订阅。】 |
ERROR_EVT_CONFIGURATION_ERROR | 15010 | Configuration error.【配置错误。】 |
ERROR_EVT_QUERY_RESULT_STALE | 15011 | The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query.【查询结果过时/无效。这可能是由于在创建查询结果后清除或滚动日志造成的。用户应该通过释放查询结果对象并重新发出查询来处理此代码。】 |
ERROR_EVT_QUERY_RESULT_INVALID_POSITION | 15012 | Query result is currently at an invalid position.【查询结果当前位于无效位置。】 |
ERROR_EVT_NON_VALIDATING_MSXML | 15013 | Registered MSXML doesn’t support validation.【注册的MSXML不支持验证。】 |
ERROR_EVT_FILTER_ALREADYSCOPED | 15014 | An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation.【只有当表达式本身的计算结果是一个节点集并且还不是某个其他范围更改操作的一部分时,表达式才能后跟范围更改操作。】 |
ERROR_EVT_FILTER_NOTELTSET | 15015 | Can’t perform a step operation from a term that does not represent an element set.【无法从不表示元素集的项执行步进操作。】 |
ERROR_EVT_FILTER_INVARG | 15016 | Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants.【二进制运算符的左侧参数必须是属性、节点或变量,右侧参数必须是常量。】 |
ERROR_EVT_FILTER_INVTEST | 15017 | A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceding node set can be evaluated.【分步操作必须涉及节点测试,或者在谓词的情况下,可以根据代数表达式来测试前面节点集标识的节点集中的每个节点。】 |
ERROR_EVT_FILTER_INVTYPE | 15018 | This data type is currently unsupported.【当前不支持此数据类型。】 |
ERROR_EVT_FILTER_PARSEERR | 15019 | A syntax error occurred at position %1!d!【位置%1出现语法错误!d!】 |
ERROR_EVT_FILTER_UNSUPPORTEDOP | 15020 | This operator is unsupported by this implementation of the filter.【此筛选器实现不支持此运算符。】 |
ERROR_EVT_FILTER_UNEXPECTEDTOKEN | 15021 | The token encountered was unexpected.【遇到意外的令牌。】 |
ERROR_EVT_INVALID_OPERATION_OVER_ENABLED_DIRECT_CHANNEL | 15022 | The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation.【无法在启用的直接通道上执行请求的操作。在执行请求的操作之前,必须先禁用通道。】 |
ERROR_EVT_INVALID_CHANNEL_PROPERTY_VALUE | 15023 | Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can’t be updated or is not supported by this type of channel.【频道属性%1!s!包含无效值。值的类型无效、超出有效范围、无法更新或不受此类型通道的支持。】 |
ERROR_EVT_INVALID_PUBLISHER_PROPERTY_VALUE | 15024 | Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can’t be updated or is not supported by this type of publisher.【发布者属性%1!s!包含无效值。值的类型无效、超出有效范围、无法更新或此类型的发布服务器不支持该值。】 |
ERROR_EVT_CHANNEL_CANNOT_ACTIVATE | 15025 | The channel fails to activate.【通道无法激活。】 |
ERROR_EVT_FILTER_TOO_COMPLEX | 15026 | The xpath expression exceeded supported complexity. Please simplify it or split it into two or more simple expressions.【xpath表达式超出了支持的复杂性。请把它简化或分成两个或两个以上的简单表达式。】 |
ERROR_EVT_MESSAGE_NOT_FOUND | 15027 | The message resource is present but the message is not found in the string/message table.【消息资源存在,但在字符串/消息表中找不到该消息。】 |
ERROR_EVT_MESSAGE_ID_NOT_FOUND | 15028 | The message identifier for the desired message could not be found.【找不到所需消息的消息标识符。】 |
ERROR_EVT_UNRESOLVED_VALUE_INSERT | 15029 | The substitution string for insert index (%1) could not be found.【找不到插入索引(%1)的替换字符串。】 |
ERROR_EVT_UNRESOLVED_PARAMETER_INSERT | 15030 | The description string for parameter reference (%1) could not be found.【找不到参数引用(%1)的描述字符串。】 |
ERROR_EVT_MAX_INSERTS_REACHED | 15031 | The maximum number of replacements has been reached.【已达到最大替换数。】 |
ERROR_EVT_EVENT_DEFINITION_NOT_FOUND | 15032 | The event definition could not be found for the event identifier (%1).【找不到事件标识符(%1)的事件定义。】 |
ERROR_EVT_MESSAGE_LOCALE_NOT_FOUND | 15033 | The locale specific resource for the desired message is not present.【所需消息的区域设置特定资源不存在。】 |
ERROR_EVT_VERSION_TOO_OLD | 15034 | The resource is too old to be compatible.【资源太旧,无法兼容。】 |
ERROR_EVT_VERSION_TOO_NEW | 15035 | The resource is too new to be compatible.【资源太新,无法兼容。】 |
ERROR_EVT_CANNOT_OPEN_CHANNEL_OF_QUERY | 15036 | The channel at index %1!d! of the query cannot be opened.【索引%1处的频道!d!无法打开查询的。】 |
ERROR_EVT_PUBLISHER_DISABLED | 15037 | The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.【发布服务器已被禁用,其资源不可用。这通常发生在发布服务器正在卸载或升级的过程中。】 |
ERROR_EVT_FILTER_OUT_OF_RANGE | 15038 | Attempted to create a numeric type that is outside of its valid range.【试图创建超出其有效范围的数值类型。】 |
ERROR_EC_SUBSCRIPTION_CANNOT_ACTIVATE | 15080 | The subscription fails to activate.【订阅无法激活。】 |
ERROR_EC_LOG_DISABLED | 15081 | The log of the subscription is in disabled state, and cannot be used to forward events. The log must first be enabled before the subscription can be activated.【订阅的日志处于禁用状态,不能用于转发事件。必须先启用日志,然后才能激活订阅。】 |
ERROR_EC_CIRCULAR_FORWARDING | 15082 | When forwarding events from local machine to itself, the query of the subscription can’t contain target log of the subscription.【将事件从本地计算机转发到自身时,订阅的查询不能包含订阅的目标日志。】 |
ERROR_EC_CREDSTORE_FULL | 15083 | The credential store that is used to save credentials is full.【用于保存凭据的凭据存储已满。】 |
ERROR_EC_CRED_NOT_FOUND | 15084 | The credential used by this subscription can’t be found in credential store.【在凭据存储中找不到此订阅使用的凭据。】 |
ERROR_EC_NO_ACTIVE_CHANNEL | 15085 | No active channel is found for the query.【找不到查询的活动通道。】 |
ERROR_MUI_FILE_NOT_FOUND | 15100 | The resource loader failed to find MUI file.【资源加载器找不到MUI文件。】 |
ERROR_MUI_INVALID_FILE | 15101 | The resource loader failed to load MUI file because the file fail to pass validation.【资源加载器无法加载MUI文件,因为该文件无法通过验证。】 |
ERROR_MUI_INVALID_RC_CONFIG | 15102 | The RC Manifest is corrupted with garbage data or unsupported version or missing required item.【RC清单被垃圾数据、不支持的版本或缺少必需项损坏。】 |
ERROR_MUI_INVALID_LOCALE_NAME | 15103 | The RC Manifest has invalid culture name.【RC清单具有无效的区域性名称。】 |
ERROR_MUI_INVALID_ULTIMATEFALLBACK_NAME | 15104 | The RC Manifest has invalid ultimatefallback name.【RC清单具有无效的最终回退名称。】 |
ERROR_MUI_FILE_NOT_LOADED | 15105 | The resource loader cache doesn’t have loaded MUI entry.【资源加载器缓存没有加载MUI项。】 |
ERROR_RESOURCE_ENUM_USER_STOP | 15106 | User stop resource enumeration.【用户停止资源枚举。】 |
ERROR_MUI_INTLSETTINGS_UILANG_NOT_INSTALLED | 15107 | UI language installation failed.【UI语言安装失败。】 |
ERROR_MUI_INTLSETTINGS_INVALID_LOCALE_NAME | 15108 | Locale installation failed.【区域设置安装失败。】 |
ERROR_MCA_INVALID_CAPABILITIES_STRING | 15200 | The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.【监视器返回的DDC/CI功能字符串不符合访问总线3.0、DDC/CI 1.1或MCCS 2第1版规范。】 |
ERROR_MCA_INVALID_VCP_VERSION | 15201 | The monitor’s VCP Version (0xDF) VCP code returned an invalid version value.【监视器的VCP版本(0xDF)VCP代码返回了无效的版本值。】 |
ERROR_MCA_MONITOR_VIOLATES_MCCS_SPECIFICATION | 15202 | The monitor does not comply with the MCCS specification it claims to supports.【显示器不符合其声称支持的MCCS规范。】 |
ERROR_MCA_MCCS_VERSION_MISMATCH | 15203 | The MCCS version in a monitor’s mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.【当使用VCP版本(0xDF)VCP代码时,监视器的MCCS版本功能中的MCCS版本与监视器报告的MCCS版本不匹配。】 |
ERROR_MCA_UNSUPPORTED_MCCS_VERSION | 15204 | The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification, or the MCCS 2.0 Revision 1 specification.【监视器配置API仅适用于支持MCCS 1.0规范、MCCS 2.0规范或MCCS 2.0修订版1规范的监视器。】 |
ERROR_MCA_INTERNAL_ERROR | 15205 | An internal Monitor Configuration API error occurred.【发生内部监视器配置API错误。】 |
ERROR_MCA_INVALID_TECHNOLOGY_TYPE_RETURNED | 15206 | The monitor returned an invalid monitor technology type. CRT, Plasma, and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or the MCCS 2.0 Revision 1 specification.【监视器返回了无效的监视器技术类型。CRT、等离子和LCD(TFT)是显示器技术类型的示例。此错误表示监视器违反了MCCS 2.0或MCCS 2.0版本1规范。】 |
ERROR_MCA_UNSUPPORTED_COLOR_TEMPERATURE | 15207 | The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or the MCCS 2.0 Revision 1 specification.【SetMonitorColorTemperature的调用者指定了当前监视器不支持的色温。此错误表示监视器违反了MCCS 2.0或MCCS 2.0版本1规范。】 |
ERROR_AMBIGUOUS_SYSTEM_DEVICE | 15250 | The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.【无法识别请求的系统设备,因为多个不可区分的设备可能与识别条件匹配。】 |
ERROR_SYSTEM_DEVICE_NOT_FOUND | 15299 | The requested system device cannot be found.【找不到请求的系统设备。】 |
Copyright © 2003-2013 www.wpsshop.cn 版权所有,并保留所有权利。