0x1F4C | 浏览器驱动程序已经在 %3 网络上收到来自 %2 计算机的选择数据包。数据为收到的数据包。 |
The browser driver has received an election packet from computer %2 on network %3. The data is the packet received. |
0x1F59 | 浏览器已从 %2 传输上的远程计算机 %1 中获得一份服务器列表。%n已读取的项目有 %3 个,共有 %4 个项目。 |
The browser has retrieved a list of servers from remote computer %1 on transport %2.%nThere were %3 entries read, and %4 total entries. |
0x1F5A | 浏览器已在 %2 传输上自远程计算机 %1 中获得一份域列表。%n已读取的项目有 %3 个,共有 %4 个项目。 |
The browser has retrieved a list of domains from remote computer %1 on transport %2.%nThere were %3 entries read, and %4 total entries. |
0x10000038 | 经典 |
Classic |
0x40000C1C | Microsoft TCP/IP 版本 6 驱动程序已启动。 |
The Microsoft TCP/IP version 6 driver was started. |
0x40001069 | 系统检测到网络适配器 %2 与网络连接,而且已启动一般操作。 |
The system detected that network adapter %2 was connected to the network,and has initiated normal operation. |
0x4000106A | 系统检测到网络适配器 %2 已断开网络连接,而且其网络配置已经释放。如果网络适配器没有断开,这可能表示适配器出现故障。请尝试更新网络适配器的驱动程序。 |
The system detected that network adapter %2 was disconnected from the networkand its network configuration has been released. If the network adapter wasnot disconnected, this may indicate that it has malfunctioned.Try updating the driver for the network adapter. |
0x4000106B | 系统检测到未安装 IPv4。这可能引起某些网络服务无法启动或出现故障。若要安装 IPv4,请使用 \"netsh interface ipv4 install\"。 |
The system detected that IPv4 is not installed. This may cause somenetworking services to fail to start, or to malfunction. To install IPv4, use\"netsh interface ipv4 install\". |
0x40001395 | %2 : 当前适配器的配置方式是接收空间小于最大的数据包规格。部分数据包可能会遗失。 |
%2 : The adapter is configured such that the receive space is smaller thanthe maximum packet size. Some packets may be lost. |
0x400013A6 | %2 : 网络适配器已成功地重新插入到环状网络中。 |
%2 : The network adapter has successfully reinserted into the ring. |
0x40001B7B | %1 服务成功发送一个 %2 控件。 |
The %1 service was successfully sent a %2 control. |
0x40001B7C | %1 服务处于 %2 状态。 |
The %1 service entered the %2 state. |
0x40001B80 | %1 服务的启动类型从 %2 更改为 %3。 |
The start type of the %1 service was changed from %2 to %3. |
0x40001B82 | %1 服务已成功发送 %2 控制。%n%n指定的原因为: %3 [%4]%n%n注释: %5 |
The %1 service was successfully sent a %2 control.%n%nThe reason specified was: %3 [%4]%n%nComment: %5 |
0x40001F4D | 浏览器驱动程序在 %2 网络上强制进行浏览器选举,因其无法在该网络上找到可检索备份列表的主浏览器。 |
The browser driver has forced an election on network %2 because it was unable to find a master browser to retrieve a backup list on that network. |
0x40001F4E | 浏览器驱动程序在 %2 网络上强制进行浏览器选举,因其无法在该网络上找到主浏览器。 |
The browser driver has forced an election on network %2 because it was unable to find a master browser for that network. |
0x40001F4F | 浏览器已经在网络 %1 上强制进行了浏览器选举,因为 Windows Server (或域主控服务器) 浏览器已经启动。 |
The browser has forced an election on network %1 because a Windows Server (or domain master) browser is started. |
0x40001F58 | 备份的浏览器服务器 %2 已经过时。请考虑将这台计算机升级。 |
The backup browser server %2 is out-of-date. Consider upgrading this computer. |
0x40001F5B | 域控制器上运行的浏览器未通过选举标准。通过选举标准的计算机是 %2,在传输 %3 上。%n数据包含了选举版本、选举标准、远程计算机过时标准以及关于当前计算机的相同信息。 |
The browser running on the Domain Controller has lost an election. The computer that won the election is %2, on the transport %3.%nThe data contains the election version, election criteria, and remote computer time up, and the same information forthe current computer. |
0x40001F5C | 此计算机上运行的浏览器已通过 %2 网络上浏览器的选举标准。本计算机为此域的成员,所以“域控制器”应成为主浏览器。 |
The browser running on this computer has won a browser election on network %2.This computer is a member of a domain, so the Domain Controller should become the masterbrowser. |
0x40001F5D | 浏览器驱动程序无法从注册表中初始化变量。 |
The browser driver was unable to initialize variables from the Registry. |
0x40001F5E | 浏览器驱动程序已放弃太多的邮件槽消息。 |
The browser driver has discarded too many mailslot messages. |
0x40001F5F | 浏览器驱动程序已放弃太多的 GetBrowserServerList 请求。 |
The browser driver has discarded too many GetBrowserServerList requests. |
0x40001F61 | 由于主浏览器已经停止,浏览器在 %1 网络上进行强制性的选举。 |
The browser has forced an election on network %1 because a master browser was stopped. |
0x40001F63 | 由于域控制器 (或服务器) 的角色有所更改,浏览器在 %1 网络上进行强制选举。 |
The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role. |
0x40002331 | %2 无法从网络适配器传送数据包。数据包丢失。 |
%2 could not transfer a packet from the network adapter. The packet was dropped. |
0x40002332 | %2 无法创建和远程计算机之间的链接。你的计算机在连接该远程计算机时已超出了容许的最大连接数。 |
%2 could not create a link to a remote computer. Your computer has exceeded the number of connections it can make to that remote computer. |
0x40002333 | %2 从收到远程计算机意外的数据包 %3。 |
%2 received an unexpected %3 packet from a remote computer. |
0x4000251D | 在 %2 上自动检测的默认帧类型已更改为 %3。如果无法检测到帧类型,则此类型是现在的默认值。 |
The default frame type for auto-detection on %2 was changed to %3.This type is now the default if no frame type can be detected. |
0x40002BC0 | 系统已注册的网络适配器,所用设置 :%n%n 适配器名 : %1%n 主机名 : %2%n 适配器特定的域后缀 : %3%n DNS 服务器列表 :%n %4%n 将更新送给服务器 : %5%n IP 地址 :%n %6 |
The system registered network adapter with settings :%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6 |
0x40002BC1 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR),所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 适配器相关的域后缀 : %3%n 主域后缀 : %4%n DNS 服务器列表 :%n %5%n 发送更新到服务器 : %6%n IP 地址 : %7 |
The system registered pointer (PTR) resource records (RRs) for networkadapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n Primary Domain Suffix : %4%n DNS server list :%n %5%n Sent update to server : %6%n IP Address : %7 |
0x40002BC2 | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR),所用设置为 :%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6 |
The system registered host (A or AAAA) resource records (RRs) for networkadapter%nwith settings :%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6 |
0x400030D5 | 已成功启动服务 |
Service started successfully |
0x400030D9 | 已为 %1 指派了新的卷 ID:%n%2%n%n分布式链接跟踪会使用这个卷 ID 自动修复文件链路,例如外壳快捷键和 OLE 链接,如果它们由于某种原因断开了的话。如果这个卷以前连到文件上的链接中断,这些文件可能不是自动修复。 |
A new volume ID has been assigned for %1:%n%2%n%nThis ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. If there previously were links to files on this volume that are broken, they might not be automatically repairable. |
0x400030DA | %1 的卷 ID 的所有权已成功获得。分布式链接跟踪会使用这个卷 ID 自动修复文件链路,例如外壳快捷键和 OLE 链接,如果它们由于某种原因断开了的话。 |
Ownership of the volume ID for %1: has been successfully claimed. This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. |
0x400030DB | %1卷 ID 已成功重置,由于它为 %2: 上的重复本。分布式链接跟踪会使用这个卷 ID 自动修复文件链路,例如外壳快捷键和 OLE 链接,如果它们由于某种原因断开了的话。 |
The volume ID for %1: has been reset, since it was a duplicate of that on %2:. This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. |
0x400034BD | 文件复制服务正在启动。 |
The File Replication Service is starting. |
0x400034BE | 文件复制服务正在停止。 |
The File Replication Service is stopping. |
0x400034BF | 文件复制服务已经停止。 |
The File Replication Service has stopped. |
0x400034CC | 文件复制服务不再阻止计算机 %1 成为域控制器。系统卷已成功初始化,而且 Netlogon 服务已经收到信息表明系统卷已经准备好共享为 SYSVOL。%n%n键入 \"net share\" 以检查 SYSVOL 共享。 |
The File Replication Service is no longer preventing the computer %1 frombecoming a domain controller. The system volume has been successfullyinitialized and the Netlogon service has been notified that the systemvolume is now ready to be shared as SYSVOL.%n%nType \"net share\" to check for the SYSVOL share. |
0x400034F1 | 文件复制服务成功地将此计算机添加到如下的副本集:%n \"%1\"%n%n与此事件相关的信息显示如下:%n计算机 DNS 名称是 \"%2\"%n副本集成员名称是 \"%3\"%n副本集根路径是 \"%4\"%n复制分段目录路径是 \"%5\"%n复制工作目录路径是 \"%6\" |
The File Replication Service successfully added this computer to the followingreplica set:%n \"%1\"%n%nInformation related to this event is shown below:%nComputer DNS name is \"%2\"%nReplica set member name is \"%3\"%nReplica set root path is \"%4\"%nReplica staging directory path is \"%5\"%nReplica working directory path is \"%6\" |
0x400034F2 | 文件复制服务成功地将下面的连接添加到副本集:%n \"%1\"%n%n %2%n %3%n %4%n %5%n %6%n %7%n %8%n %9%n%n在后面的事件日志消息中会显示更多的信息。 |
The File Replication Service successfully added the connections shown belowto the replica set:%n \"%1\"%n%n %2%n %3%n %4%n %5%n %6%n %7%n %8%n %9%n%nMore information may appear in subsequent event log messages. |
0x400037EE | Dfs 为“%2”接收到一个参考请求。返回编码在数据中。 |
Dfs received a referral request for \"%2\". The return code is in the data. |
0x40003840 | 路径“%2”不是一个 dfs 路径 |
The path \"%2\" is not a dfs path |
0x40003841 | Dfs 无法打开 Lan Redir |
Dfs was unable to open the Lan Redir |
0x40003842 | Dfs 无法打开一个接到服务器 %2 上的连接。返回的错误在记录数据中。 |
Dfs was unable to open a connection to server %2. The error returned is in the record data. |
0x40003843 | Dfs 无法从 %3 为“%2”获得一个参考。返回的错误在记录数据中。 |
Dfs was unable to obtain a referral for \"%2\" from %3. The error returned is in the record data. |
0x40003844 | Dfs 从 %3 为“%2”获得一个参考。 |
Dfs obtained a referral for \"%2\" from %3 |
0x40003845 | Dfs 达到了尝试“%2”解析的限制。 |
Dfs reached its limit of attempts of resolution of \"%2\". |
0x40003846 | Dfs 无法从 %2 获得特别的参考表。返回的错误在记录数据中。 |
Dfs was unable to obtain the special referral table from %2. The error returned is in the record data. |
0x40003847 | Dfs 打开 %2 通向 %3 失败。 返回的错误在记录数据中。 |
Dfs failed on open of %2 directed to %3. The error returned is in the record data. |
0x400038A4 | NetrDfsEnum 接收到一个枚举。返回的编码在记录数据中。 |
NetrDfsEnum received an enumeration. The return code is in the record data. |
0x400038A5 | NetrDfsEnumEx 接收到一个枚举。返回的编码在记录数据中。 |
NetrDfsEnumEx received an enumeration. The return code is in the record data. |
0x400038AC | DFS 重新建立了一个到 PDC 的连接以启动域 DFS 操作。 |
DFS re-established a connection to the PDC to initiate Domain DFS operations. |
0x400038C1 | DFS 已经连接到 %1 Active Directory。 |
DFS has connected to the %1 Active Directory. |
0x400038C3 | DFS 服务器完成了初始化。 |
DFS server has finished initializing. |
0x400038C4 | DFS 从一个错误中恢复,可以从 Active Directory 中读它的私有数据。根目录 %1 现在可以从 Active Directory 中读信息。 |
DFS has recovered from an error and is able to read its private data fromthe Active Directory. Root %1 is now able to read information from the Active Directory. |
0x400038C5 | DFS 已经完成了生成所有命名空间。 |
DFS has finished building all namespaces. |
0x400038C9 | DFS 正在对客户端要求一个更大的缓冲区以存储信任域的信息。某些 Win98 客户端可能不能访问 DFS 命名空间。 |
DFS is requesting the client for a larger buffer for trusted domain information. Some Win98 clients may not be able to access DFS namespaces. |
0x400038D2 | DFS 在目录 %2 下成功为目录 %1 创建了重分析点。之前该操作曾失败。 |
Dfs successfully created the reparse point for directory %1 under directory %2. This operation had previously failed. |
0x400038D5 | DFS 命名空间服务已成功初始化该域控制器上的受信任域信息。 |
The DFS Namespace service successfully initialized the trusted domain information on this domain controller. |
0x400038D7 | DFS 命名空间服务已成功初始化该域控制器上的跨林信任信息。 |
The DFS Namespace service successfully initialized cross forest trust information on this domain controller. |
0x400038D8 | DFS 命名空间服务已成功初始化以下命名空间:%1 |
The DFS Namespaces service has successfully initialized the following namespace: %1 |
0x400038DA | DFS 命名空间服务已成功初始化承载命名空间根目录的共享文件夹。共享文件夹为 %1 |
The DFS Namespaces service has successfully initialized the shared folder that hosts the namespace root. Shared folder: %1 |
0x40004074 | 计算机 QoS 策略成功地刷新。未检测到更改。 |
Computer QoS policies successfully refreshed. No changes detected. |
0x40004075 | 计算机 QoS 策略成功地刷新。检测到策略更改。 |
Computer QoS policies successfully refreshed. Policy changes detected. |
0x40004076 | 用户 QoS 策略成功地刷新。未检测到更改。 |
User QoS policies successfully refreshed. No changes detected. |
0x40004077 | 用户 QoS 策略成功地刷新。检测到策略更改。 |
User QoS policies successfully refreshed. Policy changes detected. |
0x40004078 | 入站 TCP 吞吐量级别的高级 QoS 设置已成功刷新。任何 QoS 策略均未指定设置值。将应用本地计算机默认值。 |
The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is not specified by any QoS policy. Local computer default will be applied. |
0x40004079 | 入站 TCP 吞吐量级别的高级 QoS 设置已成功刷新。设置值为 Level 0 (最小吞吐量)。 |
The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 0 (minimum throughput). |
0x4000407A | 入站 TCP 吞吐量级别的高级 QoS 设置已成功刷新。设置值为 Level 1。 |
The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 1. |
0x4000407B | 入站 TCP 吞吐量级别的高级 QoS 设置已成功刷新。设置值为 Level 2。 |
The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 2. |
0x4000407C | 入站 TCP 吞吐量级别的高级 QoS 设置已成功刷新。设置值为 Level 3 (最大吞吐量)。 |
The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 3 (maximum throughput). |
0x4000407D | DSCP 标记覆盖的高级 QoS 设置已成功刷新。设置值未由任何 QoS 策略指定。将应用本地计算机默认值。默认情况下,应用程序可以设置独立于 QoS 策略的 DSCP 值。 |
The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Setting value is not specified by any QoS policy. Local computer default will be applied. By default, applications can set DSCP values independently of QoS policies. |
0x4000407E | DSCP 标记覆盖的高级 QoS 设置已成功刷新。将忽略应用程序 DSCP 标记请求。仅 QoS 策略能够设置 DSCP 值。 |
The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Application DSCP marking requests will be ignored. Only QoS policies can set DSCP values. |
0x4000407F | DSCP 标记覆盖的高级 QoS 设置已成功刷新。应用程序可以设置独立于 QoS 策略的 DSCP 值。 |
The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Applications can set DSCP values independently of QoS policies. |
0x40004080 | 基于域或非域网络类别的 QoS 策略的选择性应用程序已在此计算机上禁用。QoS 策略将应用到所有网络接口。 |
Selective application of QoS policies based on domain or non-domain network category has been disabled on this machine.QoS policies will be applied to all network interfaces. |
0x40004081 | 在过去的 %1 小时 %2 分钟里,%3 HTTP.SYS 响应已让其应用程序请求的 QoS 与 URL QoS 策略冲突。 |
In the past %1 hour(s) and %2 minute(s), %3 HTTP.SYS responses have had their application requested QoS conflict with URL QoS policies. |
0x800007D9 | 服务器无法扩展表格,因为表格的规格已达上限。 |
The server could not expand a table because the table reached the maximum size. |
0x800007DC | 传输或接收数据时,服务器遇到网络错误。偶然出错在意料之中,但是大量错误则表明你的网络配置可能有错。错误状态码包含在返回的数据中(格式为 Words),它可能帮你找到问题。 |
While transmitting or receiving data, the server encountered a network error.Occasional errors are expected, but large amounts of these indicate a possibleerror in your network configuration. The error status code is contained withinthe returned data (formatted as Words) and may point you towards the problem. |
0x800007DD | %2 磁盘已满或几乎满载。你可能需要删除一些文件。 |
The %2 disk is at or near capacity. You may need to delete some files. |
0x800007E5 | 服务器无法在最近的 %3 秒内分配工作项目 %2 次。 |
The server was unable to allocate a work item %2 times in the last %3 seconds. |
0x800007E6 | 服务器无法在最近的 %3 秒内找到可用的连接 %2 次。这表明在网络流量中有一个峰值。如果这经常发生,你应该考虑增大最小自由连接的数目。要这样做,在注册表中更改LanmanServer 的 MinFreeConnections 和 MaxFreeConnections 的值。 |
The server was unable to find a free connection %2 times in the last %3 seconds. This indicates a spike innetwork traffic. If this is happening frequently, you should consider increasing the minimum number of freeconnections to add headroom. To do that, modify the MinFreeConnections and MaxFreeConnections for the LanmanServerin the registry. |
0x800007E7 | 服务器无法在最近的 %3 秒内找到可用的原始工作项目 %2 次。 |
The server was unable to find a free raw work item %2 times in the last %3 seconds. |
0x800007E8 | 服务器无法在最近的 %3 秒内次为 blocking I/O 分配资源 %2 次。 |
The server was unable to allocate resources for blocking I/O %2 times in the last %3 seconds. |
0x800007E9 | 服务器检测到来自客户端 %2 的拒绝服务攻击尝试,并已经中断连接。 |
The server has detected an attempted Denial-Of-Service attack from client %2, and has disconnected the connection. |
0x800007EA | 服务器检测到过多的拒绝服务攻击,并将停止对他们的记录。请注意,可能有人在积极地进攻你的机器。 |
The server has detected too many Denial-Of-Service attacks and will stop loggingevents for any more of them. Be advised it is likely someone is actively attackingyour machine. |
0x800007EB | 服务器检测到由消费完所有的工作项目引起的可能发生的拒绝服务攻击。有些连接已被中断以进行保护。如果情况不属实,请提高服务器 MaxWorkItems 或禁用 DoS 检测。此事件在 24 小时之内 不会再被记录。 |
The server has detected a potential Denial-of-Service attack caused by consuming all the work-items. Some connectionswere disconnected to protect against this. If this is not the case, please raise the MaxWorkItems for the server ordisable DoS detection. This event will not be logged again for 24 hours. |
0x800009C8 | 服务器无法与 %1 传输相绑定。 |
The server could not bind to the transport %1. |
0x800009CA | 服务器的注册表项 %2 中的数值 %1 无效,该数值被忽略。如果你想更改此值,将它更改为正确的类型,并在可接受的范围内,或者删除此值,使用默认值。此值可能由不使用正确边界的旧程序设置。 |
The value named %1 in the server's registry key %2 was not valid, and was ignored.If you want to change the value, change it to one that is the correct type and iswithin the acceptable range, or delete the value to use the default. This valuemight have been set up by an older program that did not use the correct boundaries. |
0x800009CB | 保存在注册表中的 %1 共享安全描述符无效。共享关系无法自动重建。 |
The security descriptor stored in the Registry for the share %1 was invalid. The share was not automatically recreated. |
0x800009CC | 服务器服务无法加载服务器驱动程序。 |
The server service was unable to load the server driver. |
0x800009CD | 服务器服务无法卸载服务器驱动程序。 |
The server service was unable to unload the server driver. |
0x800009CE | 服务器服务无法映射错误代码 %1。 |
The server service was unable to map error code %1. |
0x800009CF | 服务器服务无法重新创建 %1 共享关系,因为 %2 目录已不再存在。请运行 \"net share %1 /delete\" 来删除此共享,或重新创建目录 %2。 |
The server service was unable to recreate the share %1 because the directory %2 no longer exists. Please run \"net share %1 /delete\" to delete the share, or recreate the directory %2. |
0x800009D0 | 服务器服务无法将域名从 %1 更改成 %2。 |
The server service was unable to change the domain name from %1 to %2. |
0x800009D1 | 服务器服务无法注册到事务资源管理器。远程事务将不可用。 |
The server service was unable to register to the transaction resource manager. Remote transactions will be unavailable. |
0x80000BB9 | 重定向程序无法分配内存。 |
The redirector was unable to allocate memory. |
0x80000BBA | 重定向程序无法创建其设备。无法启动重定向程序。 |
The redirector could not create its device. The redirector could not be started. |
0x80000BBB | 重定向程序无法创建系统线程。 |
The redirector could not create a system thread. |
0x80000BBC | 重定向程序无法设置系统线程的优先级。 |
The redirector could not set the priority for a system thread. |
0x80000BBD | 重定向程序从 %2 收到格式不正确的响应。 |
The redirector received an incorrectly formatted response from %2. |
0x80000BBE | 重定向程序收到的 SMB 太短。 |
The redirector received an SMB that was too short. |
0x80000BBF | 重定向程序收到 %2 对于锁定请求的错误响应。 |
The redirector received an incorrect response from %2 to a lock request. |
0x80000BC1 | 重定向程序无法在 %2 服务器上解除部分文件的锁定。 |
The redirector failed to unlock part of a file on server %2. |
0x80000BC3 | 重定向程序无法在文件关闭后将数据写入 %2 服务器。 |
The redirector failed to write data to server %2 after the file was closed. |
0x80000BC4 | 连至 %2 的虚电路上产生意外的网络错误。 |
An unexpected network error has occurred on the virtual circuit to %2. |
0x80000BC5 | 重定向程序对于 %2 的请求已超时。 |
The redirector has timed out a request to %2. |
0x80000BC6 | 重定向程序自 %2 处收到了无效的 oplock 层。 |
The redirector received an invalid oplock level from %2. |
0x80000BC7 | 重定向程序用 0 取消了一个连接。 |
The redirector dereferenced a connection through zero. |
0x80000BC8 | 重定向程序用 0 取消了和服务器之间的关系。 |
The redirector dereferenced a server through zero. |
0x80000BC9 | 重定向程序用 0 取消了和分配 SMB 计数之间的关系。 |
The redirector dereferenced the allocated SMB count through zero. |
0x80000BCA | 重定向程序访问的共享级服务器可加密密码。不支持这种组合方式。 |
The redirector accessed a share-level server that indicates it encrypts passwords.This combination is not supported. |
0x80000BCB | 重定向程序无法决定连接类型。 |
The redirector failed to determine the connection type. |
0x80000BCD | 重定向程序无法分配多路复用表格项。这表示重定向程序的 MAXCMDS 参数无法满足用户的需要。 |
The redirector failed to allocate a multiplex table entry. This indicates thatthe MAXCMDS parameter to the redirector is insufficient for the users needs. |
0x80000BCE | 重定向程序无法为 oplock 中断分配缓冲区。 |
The redirector failed to allocate a buffer for an oplock break. |
0x80000BCF | 重定向程序无法映射请求的文件的性质 (NtCreateFile)。 |
The redirector failed to map the requested file disposition (for NtCreateFile). |
0x80000BD0 | 重定向程序正在为输入/输出请求数据包上下文分配额外的资源。导致此现象的原因,可能是因为重定向程序中产生了资源泄露的现象。 |
The redirector is allocating additional resources for input/output request packet contexts. This isprobably caused by a resource leak in the redirector. |
0x80000BD1 | 向 %2 远程服务器进行的 write-behind 操作失败。数据包含了请求写入的数量以及实际写入的数量。 |
A write-behind operation has failed to the remote server %2. The data contains the amount requested to write and the amount actually written. |
0x80000BD2 | 重定向程序无法创建工作者线程,因为能让重定向程序创建的配置工作线程限额已满。 |
The redirector was unable to create a worker thread because it has already created the maximum number of configured work threads. |
0x80000BD3 | 重定向程序无法在注册表中初始化变量。 |
The redirector was unable to initialize variables from the Registry. |
0x80000BD4 | %2 和当前工作站之间计算的时区偏差过大。数据在工作站和服务器之间指定了 100ns 个单位。请确定工作站和服务器上的日期时间是正确的。 |
The time zone bias calculated between %2 and the current workstation is toolarge. The data specifies the number of 100ns units between the workstationand server. Make sure that the time of day on the workstation and server arecorrect. |
0x80000BD5 | 重定向程序无法和主要传输上的 %2 服务器连接。数据中包含错误。 |
The redirector has failed to connect to the server %2 on the primary transport. The data contains the error. |
0x80000BD6 | 重定向程序无法更新 %2 服务器上文件的属性。数据中包含文件的名称。 |
The redirector was unable to update the file attributes on a file located on server %2.The data contains the name of the file. |
0x80000BD7 | 当应用程序关闭某个文件时,重定向程序无法在 %2 服务器上删除该指定文件。数据中包含文件的名称。 |
The redirector was unable to delete the file specified on server %2 when it was closed by the application.The data contains the name of the file. |
0x80000BD8 | 重定向程序未能把域 %2 注册到传输 %3 上,原因如下: %4。传输脱机。 |
The redirector was unable to register the domain %2 on to transport %3 for the following reason: %4. Transport has been taken offline. |
0x80000BD9 | 重定向程序未能注册传输 %3 的地址,原因如下: %4。传输脱机。 |
The redirector was unable to register the address for transport %3 for the following reason: %4. Transport has been taken offline. |
0x80000BDA | 重定向程序未能初始化安全上下文或查询上下文属性。 |
The redirector was unable to initialize security context or query context attributes. |
0x80000BDB | 重定向程序未能构建 SMB 标头。 |
The redirector was unable to build SMB header. |
0x80000BDC | 重定向器检测到一个安全签名不匹配。连接已被断开。 |
The redirector detected a security signature mismatch. The connection has been disconnected. |
0x80000FA1 | 无法分配一个 %2 字节的消息。 |
Unable to allocate a %2 byte message. |
0x80000FA2 | %2 消息分配在初始化时即告失败。 |
%2 message allocations have failed since initialization. |
0x80000FA3 | 无法分配 %2 字节的外部消息。 |
Unable to allocate a %2 byte external message. |
0x80000FA4 | %2 外部消息分配在初始化时即告失败。 |
%2 external message allocations have failed since initialization. |
0x8000105E | IP 无法启用 %2 网络适配器,以应用 DHCP 配置。如果启动了此网络适配器上的 DHCP,主界面可能无法适当地予以配置。此网络适配器上未以 DHCP 进行配置的界面不会受到影响。 |
IP was unable to initialize network adapter %2 for configuration by DHCP.If DHCP is enabled on this network adapter, the primary interface may not beconfigured properly. Interfaces on this network adapter not configured byDHCP will be unaffected. |
0x80001060 | 为 %3 网络适配器指定的默认网关地址 %2 无效。可能无法接上某些远程网络。 |
Invalid default gateway address %2 was specified for network adapter %3.Some remote networks may not be reachable as a result. |
0x80001065 | 为 %2 网络适配器指定的默认网关数量已超过最大上限。可能无法接上某些远程网络。 |
More than the maximum number of default gateways were specified fornetwork adapter %2. Some remote networks may not be reachable as a result. |
0x8000106C | 已达到自动配置的地址限制。在重新连接接口以后才将添加更多自动配置的地址。 |
Autoconfigured address limit has been reached. No further autoconfigured addresses will be added until the interface is reconnected. |
0x8000106D | 已达到自动配置的路由限制。在重新连接接口以后才将添加更多自动配置的路由。 |
Autoconfigured route limit has been reached. No further autoconfigured routes will be added until the interface is reconnected. |
0x80001082 | TCP/IP 已经达到并发 TCP 连接尝试次数的安全限制。 |
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. |
0x80001083 | TCP/IP 无法建立传出连接,因为选定的本地终结点最近用于连接到相同的远程终结点。当以高速率打开和关闭传出连接时,会导致所有可用的本地端口被使用,并迫使 TCP/IP 重新使用本地端口进行传出连接,此时通常会产生这种错误。为了最大限度地降低数据受到损坏的风险,在给定的本地终结点和给定的远程终结点之间的连续连接中,TCP/IP 标准需要等待一段最短的时间段。 |
TCP/IP failed to establish an outgoing connection because the selected local endpointwas recently used to connect to the same remote endpoint. This error typically occurswhen outgoing connections are opened and closed at a high rate, causing all availablelocal ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection.To minimize the risk of data corruption, the TCP/IP standard requires a minimum time periodto elapse between successive connections from a given local endpoint to a given remote endpoint. |
0x80001084 | TCP/IP 由于某个网络条件已选择限制缩放比例。这可能与网络设备问题有关,将导致吞吐量降低。 |
TCP/IP has chosen to restrict the scale factor due to a network condition. This could be related to a problem in a network device and will cause degraded throughput. |
0x80001085 | TCP/IP 已经检测到高内存使用率并中断部分连接以维持稳定。 |
TCP/IP has detected high memory utilization and has terminated some existing connections to maintain system stability. |
0x80001086 | 由于网络条件原因,TCP/IP 已选择限制拥塞窗口用于多个连接。这可能与 TCP 全局参数或补充配置中的问题有关,并且将导致吞吐量降低。 |
TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput. |
0x80001087 | 有关从全局 TCP 端口空间分配一个短端口号的请求失败,因为所有此类端口都在使用中。 |
A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use. |
0x800010A9 | 达到了挂起发送数据报囤积数。请增加注册表中 Tcpip\\Parameters\\DGMaxSendFree 的值。 |
Backlog of pending datagram sends reached. Please increase the value of Tcpip\\Parameters\\DGMaxSendFree in the registry. |
0x800010AA | 有关从全局 UDP 端口空间分配一个短端口号的请求失败,因为所有此类端口都在使用中。 |
A request to allocate an ephemeral port number from the global UDP port space has failed due to all such ports being in use. |
0x800010C2 | 无法在硬件地址为 %2 的网络适配器上设置多播地址列表(%3 %4 %5 %6)。 |
Multicast address list could not be set on the network adapter with hardware address %2 (%3 %4 %5 %6). |
0x800010C3 | 硬件地址为 %2 的网络适配器已指示数据包合并功能,但未指示对一个或多个必备接收筛选器功能的支持(%3 %4)。 |
The network adapter with hardware address %2 has indicated packet coalescing capabilitywithout indicating support for one or more prerequisite receive filter capabilities (%3 %4). |
0x800010C4 | 尝试在硬件地址为 %2 的网络适配器上设置数据包合并筛选器失败(%3 %4 %5)。 |
An attempt to set a packet coalescing filter on the network adapter with hardware address %2 has failed (%3 %4 %5). |
0x800010C5 | 硬件地址为 %2 的网络适配器上的 ARP 数据包合并筛选器未设置,因为当前向该适配器分配了多个 IPv4 地址。可以在仅有一个 IPv4 地址分配给此适配器时再设置 ARP 数据包合并筛选器(%3 %4)。 |
The ARP packet coalescing filter on the network adapter with hardware address %2 is not setsince more than one IPv4 address is currently assigned to the adapter. An ARP packet coalescingfilter may be set later when only one IPv4 address is assigned to this adapter (%3 %4). |
0x800010CE | 注册表中未配置备份 WINS 服务器地址。 |
The backup WINS server address is not configured in the registry. |
0x800010CF | 注册表中未配置主要 WINS 服务器地址。 |
The primary WINS server address is not configured in the registry. |
0x800010D0 | 注册表中备份 WINS 服务器地址的格式不正确。 |
The backup WINS server address is not formated correctly in the registry. |
0x800010D1 | 注册表中主要 WINS 服务器地址的格式不正确。 |
The primary WINS server address is not formatted correctly in the registry. |
0x800010D8 | 没有为本协议堆栈配置任何网络适配器。 |
There are no network adapters configured for this protocol stack. |
0x800010DC | 无法打开注册表来读取 WINS 服务器地址。 |
Unable to open the registry to read the WINS server addresses. |
0x800010DD | NetBIOS 名称领域内的某个组件长度超过 63 个字符。领域内的每个标签均不可超过 63 字节。 |
The Netbios Name Scope has a component longer than 63 characters. Each labelin the Scope cannot be longer than 63 bytes. |
0x800010DE | Netbios 名称领域太长。领域长度不得超过255 字节。 |
The Netbios Name Scope is too long. The scope cannot be longer than255 bytes. |
0x8000138F | %2 : 在操作进行中超时。 |
%2 : Timed out during an operation. |
0x80001396 | %2 : 由于网络适配器被禁用,驱动程序无法工作。 |
%2 : The driver cannot function because the network adapter is disabled. |
0x80001397 | %2 : 产生 I/O 端口冲突。 |
%2 : There is an I/O port conflict. |
0x80001398 | %2 : 产生 I/O 端口或 DMA 通道冲突。 |
%2 : There is an I/O port or DMA channel conflict. |
0x80001399 | %2 : 在 0x%3 地址处产生内存冲突。 |
%2 : There is a memory conflict at address 0x%3. |
0x8000139A | %2 : 中断 %3 包含中断冲突。 |
%2 : There is a interrupt conflict at Interrupt %3. |
0x8000139B | %2 : DMA %3 通道产生资源冲突。 |
%2 : There is a resource conflict at DMA channel %3. |
0x8000139D | %2 : 指定的注册表项目 MaxReceives 超出范围。请用默认值。 |
%2 : The specified registry entry MaxReceives is out of range. Using default value. |
0x8000139E | %2 : 指定的注册表项目 MaxTransmits 超出范围。请用默认值。 |
%2 : The specified registry entry MaxTransmits is out of range. Using default value |
0x8000139F | %2 : 指定的注册表项目 MaxFrameSize 超出范围。请用默认值。 |
%2 : The specified registry entry MaxFrameSize is out of range. Using default value. |
0x800013A0 | %2 : 指定的注册表项目 MaxInternalBufs 超出范围。请用默认值。 |
%2 : The specified registry entry MaxInternalBufs is out of range. Using default value. |
0x800013A1 | %2 : 指定的注册表项目 MaxMulticast 超出范围。请用默认值。 |
%2 : The specified registry entry MaxMulticast is out of range. Using default value. |
0x800013A2 | %2 : 指定的注册表项目 ProductId 超出范围。请用默认值。 |
%2 : The specified registry entry ProductId is out of range. Using default value. |
0x800013A3 | %2 : 发生 Token Ring Lobe Wire Fault。请检测电缆连接。网络适配器将继续尝试重新插入到环状网络中。 |
%2 : A Token Ring Lobe Wire Fault has occurred. Verify cable connections. The network adapter will continue to try to reinsert into the ring. |
0x800013A4 | %2 : 适配器检测到环状网络上的讯号丢失。适配器会继续尝试重新插入到环状网络中。 |
%2 : The adapter had detected a loss of signal on the ring. The adapterwill continue to try to reinsert back into the ring. |
0x800013A5 | %2: 适配器已接收到请求,要求退出环,适配器将继续尝试重新插入环中。 |
%2 : The adapter has received a request to deinsert from thering. The adapter will continue to try to reinsert back into the ring. |
0x800013A8 | %2 : 网络适配器在指定时间内未能重置,这可能是硬件故障导致的。网络适配器将继续尝试重置。 |
%2 : The network adapter failed to reset within a specified time, which could be caused by a hardware failure. The network adapter will continue to try to reset. |
0x800013A9 | %2 : 网络适配器检测到令牌环状网络电缆已经从网络适配器断开请重新连接电缆。 |
%2 : The network adapter has detected that the token ring cable is disconnected from the network adapter. Please reconnect the cable. |
0x800013AA | %2 : 网络适配器成功地完成了前次失败的复位。 |
%2 : The network adapter has successfully completed a previously failed reset. |
0x80001775 | 事件日志服务已启动。 |
The Event log service was started. |
0x80001776 | 事件日志服务已停止。 |
The Event log service was stopped. |
0x80001778 | 上一次系统的 %1 在 %2 上的关闭是意外的。 |
The previous system shutdown at %1 on %2 was unexpected. |
0x80001779 | Microsoft (R) Windows (R) %1 %2 %3 %4。 |
Microsoft (R) Windows (R) %1 %2 %3 %4. |
0x8000177B | 此机器的 NetBIOS 名称和 DNS 主机名从 %1 更改为 %2。 |
The NetBIOS name and DNS host name of this machine have been changed from %1 to %2. |
0x8000177C | 指定给此计算机的 DNS 域已经从 %1 更改为 %2。 |
The DNS domain assigned to this computer has been changed from %1 to %2. |
0x8000177D | 系统启动时间为 %5 秒。 |
The system uptime is %5 seconds. |
0x80001B7F | 在启动 %1 服务时连接到了一个不是由服务控制管理器启动的服务进程。服务控制管理器启动了进程 %2 和进程 %3。%n%n请注意如果此服务配置为在调试程序下启动,则此行为是正常的。 |
A service process other than the one launched by the Service Control Managerconnected when starting the %1 service. The Service Control Manager launchedprocess %2 and process %3 connected instead.%n%nNote that if this service is configured to start under a debugger, this behavioris expected. |
0x80001F44 | 当计算机成为主浏览器时,会送出一个请求以促使该计算机进行备份操作。 |
A request has been submitted to promote the computer to backup when it is already amaster browser. |
0x80001F45 | 浏览器收到了服务器的宣告,指明 %2 计算机为主浏览器。但是此计算机并非主浏览器。 |
The browser has received a server announcement indicating that the computer %2is a master browser, but this computer is not a master browser. |
0x80001F46 | 浏览器在 %4 传输上收到了远程计算机 %2 传给 %3 的无效数据报。数据为数据报。 |
The browser has received an illegal datagram from the remote computer %2 to name %3 on transport %4. The data is the datagram. |
0x80001F55 | 浏览器服务不能从在网络 %2 上的主浏览器 %1 上检索服务器列表。%n%n主浏览器: %1%n网络: %2%n%n此事件可能是由于暂时丢失网络连接造成的。如果此消息再次出现,请确认服务器仍然与网络连接。返回码在数据文本框中。 |
The browser service was unable to retrieve a list of servers from the browser master %1 on the network %2.%n%nBrowser master: %1%nNetwork: %2%n%nThis event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box. |
0x80001F56 | 浏览器服务不能从在网络 %2 上的主浏览器 %1 上检索域列表。%n%n主浏览器: %1%n网络: %2%n%n此事件可能是由于暂时失去网络连接。如果此消息再次出现,请确认服务器仍然连接到网络上。返回码在“数据”文本框中。 |
The browser service was unable to retrieve a list of domains from the browser master %1 on the network %2.%n%nBrowser master: %1%nNetwork: %2%n%nThis event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box. |
0x80001F57 | 浏览器服务的 %1 参数值不合法。 |
The value for the parameter %1 to the browser service was illegal. |
0x8000214D | 项 %1 中的名称太长: 名称 = %s。Sap 代理程序无法继续。 |
Name too long in key %1: Name = %s. The Sap Agent cannot continue. |
0x80002329 | 由于系统资源问题,%2 无法分配 %3 类型的资源。 |
%2 could not allocate a resource of type %3 due to system resource problems. |
0x8000232A | 由于 %4 的配置规格,%2 无法分配 %3 类型的资源。 |
%2 could not allocate a resource of type %3 due to its configured size of %4. |
0x8000232B | 由于 %4 的特殊配置限制,%2 无法分配 %3 类型的资源。 |
%2 could not allocate a resource of type %3 due to a specifically configured limit of %4. |
0x8000251E | SAP 宣告在 %2 上发送,后者配置为多网络,但是未配置内部网络。这可能会造成某些网络上的计算机无法找到广告服务 (advertised service) 的位置。 |
A SAP announcement was sent over %2 which is configured for multiplenetworks, but no internal network is configured. This may preventmachines on some networks from locating the advertised service. |
0x8000251F | %2 参数 %3 的数值无效。 |
The value for the %2 parameter %3 was illegal. |
0x80002B2A | DNS 客户端服务在重试多次后仍然不能联系任何DNS 服务器。在下面的 %3 秒内DNS 客户服务将不能使用网络以避免网络性能的出现问题。在此后它的行为将恢复正常。如果此问题持续存在,请检查你的 TCP/IP配置,特别是要有配置的首选(可以有一个可选的) DNS 服务器。如果此问题继续,请检查到 DNS 服务器的网络连接或与你的网络管理员联系。 |
The DNS Client service could not contact any DNS servers fora repeated number of attempts. For the next %3 seconds theDNS Client service will not use the network to avoid furthernetwork performance problems. It will resume its normal behaviorafter that. If this problem persists, verify your TCP/IPconfiguration, specifically check that you have a preferred(and possibly an alternate) DNS server configured. If the problemcontinues, verify network conditions to these DNS servers or contactyour network administrator. |
0x80002B2B | DNS 客户端服务在地址 %1 访问 DNS 服务器失败。它在 %2 秒内将不使用 DNS 服务器。 |
The DNS Client service failed to reach DNS server at address %1. It willnot use this DNS server for %2 seconds. |
0x80002B8E | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n此 DNS 注册失败的原因是因为在发送 DNS 更新到指定 DNS 服务器后超时。 这可能是因为名称更新的授权 DNS 服务器没有运行。%n%n 你可以手动重试此网络适配器的注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\" 来完成。如果问题依然存在,请与你的网络系统管理员联系,以验证网络状态。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS Server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because the DNS updaterequest timed out after being sent to the specified DNS Server. This isprobably because the authoritative DNS server for the name being updatedis not running.%n%n You can manually retry registration of the networkadapter and its settings by typing \"ipconfig /registerdns\" at the commandprompt. If problems still persist, contact your network systemsadministrator to verify network conditions. |
0x80002B8F | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n此 DNS 注册失败的原因是因为 DNS 服务器故障。这可能是由于一个区域复制,它为可用的区域锁定了 DNS 服务器,你的计算机需要此服务器来注册。%n%n(可用的区域通常应该与上面指出的网络适配器相关的域后缀相对应。) 你可以手动重试此网络适配器的注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\" 来完成。如果问题依然存在,请与你的网络系统管理员联系,以验证网络状态。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because of DNS server failure.This may be due to a zone transfer that has locked the DNS server for theapplicable zone that your computer needs to register itself with.%n%n(The applicable zone should typically correspond to the Adapter-specificDomain Suffix that was indicated above.) You can manually retry registrationof the network adapter and its settings by typing \"ipconfig /registerdns\"at the command prompt. If problems still persist, contact your networksystems administrator to verify network conditions. |
0x80002B90 | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n不能注册的原因可能是: (a) DNS 服务器不支持 DNS 动态更新协议,或 (b) 注册名称的主区域授权当前不接受动态更新。%n%n 要为此网络适配器使用特定的 DNS 名称添加或注册一个 DNS 主机 (A 或 AAAA) 资源记录,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason it could not register was because either: (a) the DNS serverdoes not support the DNS dynamic update protocol, or (b) the primary zoneauthoritative for the registering names does not currently accept dynamicupdates.%n%n To add or register a DNS host (A or AAAA) resource record using the specific DNS name for this adapter, contact your DNS server or networksystems administrator. |
0x80002B91 | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n不能注册的原因是因为 DNS 服务器拒绝动态更新请求。可能的原因如下:(a) 当前 DNS 更新策略不允许此计算机更新为此网络适配器配置的 DNS 域名,或 (b) 此 DNS 域名的授权 DNS 服务器不支持 DNS 动态更新协议。%n%n要为此网络适配器使用特定的 DNS 名称注册一个 DNS 主机 (A 或 AAAA) 资源记录,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason it could not register was because the DNS server refused thedynamic update request. This could happen for the following reasons:(a) current DNS update policies do not allow this computer to updatethe DNS domain name configured for this adapter, or (b) the authoritativeDNS server for this DNS domain name does not support the DNS dynamic updateprotocol.%n%nTo register a DNS host (A or AAAA) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systemsadministrator. |
0x80002B92 | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于与安全相关的问题,系统不能注册 DNS更新请求。可能的原因如下:(a)你的计算机要注册的 DNS 域名不能被更新,因为你的计算机没有正确的权限,或 (b) 可能与要更新的 DNS 服务器之间有协商有效凭据问题。%n%n你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not register the DNS update request because of asecurity related problem. This could happen for the following reasons:(a) the DNS domain name that your computer is trying to register couldnot be updated because your computer does not have the right permissions,or (b) there might have been a problem negotiating valid credentialswith the DNS server to update.%n%nYou can manually retry DNS registration of the network adapter and itssettings by typing \"ipconfig /registerdns\" at the command prompt. Ifproblems still persist, contact your DNS server or network systemsadministrator. See event details for specific error code information. |
0x80002B93 | 系统注册网络适配器失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%nDNS 更新请求不能被完成的原因是一个系统问题。你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the DNS update request could not be completed was becauseof a system problem. You can manually retry DNS registration of thenetwork adapter and its settings by typing \"ipconfig /registerdns\"at the command prompt. If problems still persist, contact your DNSserver or network systems administrator. See event details for specific error code information. |
0x80002B94 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于发送到指定 DNS 服务器的更新请求超时,系统不能注册这些 RR。这可能是由于此名称注册的授权 DNS 服务器没有在运行。%n%n 你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register pointer (PTR) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe reason that the system could not register these RRs was because theupdate request that was sent to the specified DNS server timed out. Thisis probably because the authoritative DNS server for the name beingregistered is not running.%n%n You can manually retry DNS registrationof the network adapter and its settings by typing \"ipconfig /registerdns\"at the command prompt. If problems still persist, contact your DNSserver or network systems administrator. See event details for specific error code information. |
0x80002B95 | 系统为网络适配器 %n 注册指针(PTR)资源记录(RR)失败,注册使用的设置为:%n%n 适配器名称 : %1%n 主机名称 : %2%n 特定于适配器的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n原因是 DNS 服务器故障。这可能是由于计算机需要更新的 DNS 服务器上的反向查找区域过忙或丢失。由于该现象不影响正常(向前)名称解析,因此在大多数情况下这是一个小问题。%n%n 如果计算机要求进行反向(地址到名称)解析,则你可以在命令提示符下键入 \"ipconfig /registerdns\" 手动重新尝试进行网络适配器的DNS 注册及其设置。如果问题仍然存在,请联系 DNS 服务器或网络系统管理员。有关特定的错误代码信息,请参阅事件详细信息。 |
The system failed to register pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe cause was DNS server failure. This may because the reverse lookupzone is busy or missing on the DNS server that your computer needs toupdate. In most cases, this is a minor problem because it does notaffect normal (forward) name resolution.%n%n If reverse (address-to-name)resolution is required for your computer, you can manually retry DNSregistration of the network adapter and its settings by typing \"ipconfig /registerdns\" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information. |
0x80002B96 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n系统不能注册这些 RR 的可能原因是(a) DNS 服务器不支持 DNS 动态更新协议,或 (b) 记录要注册到的授权区域不允许动态更新。%n%n要为此网络适配器使用特定 DNS 域名称注册 DNS 指针 (PTR) 资源记录,请与你的 DNS 服务器或网络管理员联系。 |
The system failed to register pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe reason that the system could not register these RRs was because(a) either the DNS server does not support the DNS dynamic updateprotocol, or (b) the authoritative zone where these records are tobe registered does not allow dynamic updates.%n%nTo register DNS pointer (PTR) resource records using the specificDNS domain name and IP addresses for this adapter, contact yourDNS server or network systems administrator. |
0x80002B97 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于 DNS 拒绝更新请求,系统不能注册这些 RR。可能的原因有 (a) 你的计算机不被允许更新网络适配器相关的 DNS域名,或 (b) 指定名称的 DNS 服务器授权不支持 DNS 动态更新协议。%n%n要为此网络适配器使用特定 DNS 域名称或 IP 地址注册DNS 指针 (PTR) 资源记录,请与你的 DNS 服务器或网络管理员联系。 |
The system failed to register pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe reason that the system could not register these RRs was becausethe DNS server refused the update request. The cause of this couldbe (a) your computer is not allowed to update the adapter-specified DNSdomain name, or (b) because the DNS server authoritative for the specifiedname does not support the DNS dynamic update protocol.%n%nTo register the DNS pointer (PTR) resource records using the specificDNS domain name and IP addresses for this adapter, contact your DNSserver or network systems administrator. |
0x80002B98 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于安全相关的问题,系统不能注册这些 RR。可能的原因有 (a) 你的计算机没有权限为此网络适配器注册和更新特定的DNS 域名称,或 (b) 在处理更新请求时,与DNS 服务器协商有效的凭据有问题。%n%n你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\" 来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe reason that the system could not register these RRs was becauseof a security related problem. The cause of this could be (a) yourcomputer does not have permissions to register and update the specificDNS domain name set for this adapter, or (b) there might have been aproblem negotiating valid credentials with the DNS server during theprocessing of the update request.%n%nYou can manually retry DNS registration of the network adapter andits settings by typing \"ipconfig /registerdns\" at the command prompt.If problems still persist, contact your DNS server or network systemsadministrator. |
0x80002B99 | 系统为网络适配器 %n 注册指针 (PTR) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于系统问题,系统不能在更新请求过程中注册这些 RR。你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe reason the system could not register these RRs during theupdate request was because of a system problem. You can manuallyretry DNS registration of the network adapter and its settings bytyping \"ipconfig /registerdns\" at the command prompt. If problemsstill persist, contact your DNS server or network systemsadministrator. See event details for specific error code information. |
0x80002B9A | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n系统不能注册这些 RR 的原因是发送到 DNS 服务器的更新请求超时。最有可能的原因是此名称要注册或更新的 DNS%n%n你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\" 来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register host (A or AAAA) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because theupdate request it sent to the DNS server timed out. The most likelycause of this is that the DNS server authoritative for the name itwas attempting to register or update is not running at this time.%n%nYou can manually retry DNS registration of the network adapter andits settings by typing \"ipconfig /registerdns\" at the command prompt.If problems still persist, contact your DNS server or network systemsadministrator. |
0x80002B9B | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于 DNS 服务器更新请求失败,系统不能注册这些 RR。最有可能的原因是处理此更新请求的授权 DNS 服务器在此区域有一个锁定,可能是因为区域复制正在进行。%n%n你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\" 来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register host (A or AAAA) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because theDNS server failed the update request. The most likely cause of thisis that the authoritative DNS server required to process this updaterequest has a lock in place on the zone, probably because a zonetransfer is in progress.%n%nYou can manually retry DNS registration of the network adapter andits settings by typing \"ipconfig /registerdns\" at the command prompt.If problems still persist, contact your DNS server or network systemsadministrator. |
0x80002B9C | 系统为网络适配器 %n 注册主机(A 或 AAAA)资源记录失败,注册使用的设置为:%n%n 适配器名称 : %1%n 主机名称 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%nDNS 服务器不支持 DNS 动态更新协议,或者指定 DNS 域名称的授权区域当前不接受动态更新。%n%n若要使用该适配器的特定的 DNS 域名和 IP 地址注册 DNS 主机(A 或 AAAA)资源记录,请联系DNS 服务器或网络系统管理员。 |
The system failed to register host (A or AAAA) resource records for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nEither the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates.%n%nTo register the DNS host (A or AAAA) resource records using the specificDNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
0x80002B9D | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n系统不能注册这些 RR 的原因是因为联系的 DNS 服务器拒绝更新请求。这可能的原因有 (a) 你没有被允许更新指定的 DNS 域名,或 (b) 此名称的 DNS 服务器授权不支持 DNS 动态更新协议。%n%n要为此网络适配器使用特定的 DNS 域名和 IP 地址注册 DNS 主机 (A 或 AAAA) 资源记录,请与你的 DNS 服务器或网络系统管理员联系。 |
The system failed to register host (A or AAAA) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because theDNS server contacted refused the update request. The reasons for thismight be (a) you are not allowed to update the specified DNS domain name,or (b) because the DNS server authoritative for this name does not supportthe DNS dynamic update protocol.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNSdomain name and IP addresses for this adapter, contact your DNS serveror network systems administrator. |
0x80002B9E | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于与安全相关的问题,系统不能注册这些 RR。可能的原因有 (a) 你的计算机没有权限为此网络适配器注册并更新指定的DNS 域名,或 (b) 可能在处理更新的过程中与 DNS 服务器协商有效凭据有问题。%n%n你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register host (A or AAAA) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because of asecurity related problem. The cause of this could be (a) your computerdoes not have permissions to register and update the specific DNS domainname set for this adapter, or (b) there might have been a problem negotiatingvalid credentials with the DNS server during the processing of the updaterequest.%n%nYou can manually retry DNS registration of the network adapter andits settings by typing \"ipconfig /registerdns\" at the command prompt.If problems still persist, contact your DNS server or network systemsadministrator. See event details for specific error code information. |
0x80002B9F | 系统为网络适配器 %n 注册主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于系统问题,系统不能在更新请求中注册这些 RR。你可以手动重试此网络适配器的 DNS 注册和设置,这可以通过在命令提示符下键入 \"ipconfig /registerdns\"来完成。 如果问题依然存在,请与你的 DNS 服务器或网络系统管理员联系。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to register host (A or AAAA) resource records (RRs) fornetwork adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs during theupdate request was because of a system problem. You can manuallyretry DNS registration of the network adapter and its settings bytyping \"ipconfig /registerdns\" at the command prompt. If problemsstill persist, contact your DNS server or network systemsadministrator. See event details for specific error code information. |
0x80002BAC | 系统更新和删除网络适配器注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n失败原因是由于发送更新请求到的 DNS 服务器超时。这最有可能的原因是区域的 DNS 服务器授权没有在运行或此时不能通过网络访问,而注册最初是在此区域上进行。 |
The system failed to update and remove registration for thenetwork adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the updaterequest to timed out. The most likely cause of this failure is that theDNS server authoritative for the zone where the registration was originallymade is either not running or unreachable through the network at this time. |
0x80002BAD | 系统更新和删除网络适配器注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n失败原因是由于发送更新到的 DNS 服务器处理更新请求失败。一个可能的原因是要求处理此更新的 DNS 服务器在区域中有一个锁定,可能是因为有一个区域复制正在进行。%n%n |
The system failed to update and remove registration for thenetwork adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the updateto failed the update request. A possible cause of this failure is thatthe DNS server required to process this update request has a lock in placeon the zone, probably because a zone transfer is in progress.%n%n |
0x80002BAE | 系统更新和删除网络适配器注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n失败原因是由于发送更新到的 DNS 服务器 (a) 可能不支持 DNS 动态更新协议,或 (b) 指定 DNS 域名称的授权区域当前不接受 DNS 动态更新。 |
The system failed to update and remove registration for the networkadapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the updateeither (a) does not support the DNS dynamic update protocol, or (b) theauthoritative zone for the specified DNS domain name does not currentlyaccept DNS dynamic updates. |
0x80002BAF | 系统更新和删除网络适配器注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n系统不能执行更新请求的原因是联系的 DNS 服务器拒绝更新请求。可能的原因有(a) 此计算机没有被允许更新指定的 DNS 域名称,或 (b) 要求更新的区域的 DNS 服务器授权不支持 DNS 动态更新协议。 |
The system failed to update and remove registration for the networkadapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was theDNS server contacted refused update request. The cause of this is(a) this computer is not allowed to update the specified DNS domainname, or (b) because the DNS server authoritative for the zone thatrequires updating does not support the DNS dynamic update protocol. |
0x80002BB0 | 系统更新和删除网络适配器注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于一个与安全相关的问题,系统不能执行更新请求。可能的原因有 (a) 你的计算机没有权限为此网络适配器注册并更新指定的 DNS 域名称设置,或 (b) 可能在处理更新的过程中与 DNS 服务器协商有效凭据有问题。%n%n有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove registration for the networkadapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was becauseof a security related problem. The cause of this could be (a) your computerdoes not have permissions to register and update the specific DNS domainname set for this adapter, or (b) there might have been a problem negotiatingvalid credentials with the DNS server during the processing of the updaterequest.%n%nSee event details for specific error code information. |
0x80002BB1 | 系统更新和删除网络适配器 DNS 注册失败,设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于系统问题,系统不能更新并删除DNS 注册。 有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove the DNS registration for thenetwork adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not update to remove this DNS registration because ofa system problem. See event details for specific error code information. |
0x80002BB2 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n系统不能删除这些 PTR RR,因为在等待来自DNS 的响应时,更新请求超时。这可能是因为要求更新的区域的 DNS 服务器授权没有在运行。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because the update requesttimed out while awaiting a response from the DNS server. This is probablybecause the DNS server authoritative for the zone that requires updateis not running. |
0x80002BB3 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n系统不能删除这些 PTR RR,因为 DNS 服务器处理更新请求失败。一个可能的原因是有一个区域复制正在进行,在授权为这些 RR 进行更新的 DNS 服务器上引起一个区域锁定。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because the DNS server failed theupdate request. A possible cause is that a zone transfer is in progress,causing a lock for the zone at the DNS server authorized to perform theupdates for these RRs. |
0x80002BB4 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n系统不能删除这些 PTR RR,因为 DNS 服务器不支持 DNS 动态更新协议,或包含这些 RR 的授权区域不接受动态更新。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because either the DNS serverdoes not support the DNS dynamic update protocol or the authoritative zonethat contains these RRs does not accept dynamic updates. |
0x80002BB5 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n系统不能删除这些 PTR RR,因为 DNS 服务器拒绝更新请求。可能的原因有 (a) 此计算机没有被允许更新由这些设置指定的 DNS 域名称,或(b) 授权对包含这些 RR 的区域进行更新的 DNS 服务器不支持 DNS 动态更新协议。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because the DNS server refused theupdate request. The cause of this might be (a) this computer is not allowedto update the specified DNS domain name specified by these settings, or(b) because the DNS server authorized to perform updates for the zone thatcontains these RRs does not support the DNS dynamic update protocol. |
0x80002BB6 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于一个与安全相关的问题,系统不能删除这些 PTR RR。可能的原因有 (a) 你的计算机没有权限删除或更新此网络适配器配置的特定的DNS 域名称或 IP 地址,或 (b) 可能在处理更新的过程中与 DNS 服务器协商有效凭据有问题。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because of a security relatedproblem. The cause of this could be that (a) your computer does not havepermissions to remove and update the specific DNS domain name or IP addressesconfigured for this adapter, or (b) there might have been a problem negotiatingvalid credentials with the DNS server during the processing of the updaterequest. See event details for specific error code information. |
0x80002BB7 | 系统为网络适配器 %n 更新和删除指针 (PTR) 资源记录 (RR)失败,所用设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 网络适配器相关的域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 : %6%n%n由于一个与安全相关的问题,系统不能删除这些 PTR RR。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove pointer (PTR) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because because of a systemproblem. See event details for specific error code information. |
0x80002BB8 | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n系统不能删除这些主机 (A 或 AAAA) RR,因为在等待来自 DNS 服务器的响应时,更新请求超时。这可能时因为这些 RR 需要更新的区域的 DNS 服务器授权当前没有在运行或不能通过网络访问。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably becausethe DNS server authoritative for the zone where these RRs need to be updatedis either not currently running or reachable on the network. |
0x80002BB9 | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n由于 DNS 服务器处理更新请求失败,系统不能删除这些主机 (A 或 AAAA) RR。一个可能的原因是有一个区域复制正在进行,在授权为这些 RR 进行更新的 DNS 服务器上引起一个区域锁定。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not remove these host (A or AAAA) RRs because the DNS serverfailed the update request. A possible cause is that a zone transfer is in progress,causing a lock for the zone at the DNS server authorized to perform theupdates for these RRs. |
0x80002BBA | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n失败的原始是发送更新到的 DNS 服务器 (a) 不支持 DNS 动态更新协议,或 (b) 在这些主机 (A 或 AAAA) RR 中指定的 DNS 域名称的授权区域当前不接受 DNS 动态更新。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the updateeither (a) does not support the DNS dynamic update protocol, or (b) theauthoritative zone for the DNS domain name specified in these host (A or AAAA)RRs does not currently accept DNS dynamic updates. |
0x80002BBB | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n删除这些记录的请求失败,因为 DNS 服务器拒绝更新请求。可能的原因有 (a) 此计算机没有被允许更新由这些设置指定的 DNS 域名称,或 (b) 授权执行包含这些 RR 的区域的更新的 DNS 服务器当前不支持 DNS 动态更新协议。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe request to remove these records failed because the DNS server refusedthe update request. The cause of this might be that either (a) thiscomputer is not allowed to update the DNS domain name specified by thesesettings, or (b) because the DNS server authorized to perform updates forthe zone that contains these RRs does not support the DNS dynamic updateprotocol. |
0x80002BBC | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n失败的原因是由于一个与安全相关的问题。可能的原因有 (a) 你的计算机没有权限删除和更新为此网络适配器配置的 DNS域名或 IP 地址,或 (b) 可能在处理更新请求的过程中与 DNS 服务器协商有效凭据有问题。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure was because of a security related problem.The cause of this could be that (a) your computer does not have permissionsto remove and update the specific DNS domain name or IP addressesconfigured for this adapter, or (b) there might have been a problemnegotiating valid credentials with the DNS server during the processing ofthe update request. See event details for specific error code information. |
0x80002BBD | 系统为网络适配器 %n 更新和删除主机 (A 或 AAAA) 资源记录 (RR) 失败,注册使用的设置为:%n%n 网络适配器名 : %1%n 主机名 : %2%n 主域后缀 : %3%n DNS 服务器列表 :%n %4%n 发送更新到服务器 : %5%n IP 地址 :%n %6%n%n更新请求失败的原因是由于系统问题。有关特定错误代码信息,请查看事件详细信息。 |
The system failed to update and remove host (A or AAAA) resource records (RRs)for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the update request failed was because of a system problem.See event details for specific error code information |
0x800030D8 | 已超出这台机器上的卷 ID 配额,因此无法创建新的卷 ID。如果由于某种原因断了,分布式链接跟踪通常使用这些卷 ID 自动修改文件链接,如外壳快捷键和 OLE 链接。 |
The Distributed Link Tracking volume ID quota on this machine has been exceeded. As a result, it is not possible to create new volume IDs. Distributed Link Tracking normally uses these volume IDs to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. |
0x800030DC | 该域上的分布式链接跟踪服务的移动表格配额已被超出。由于某种原因断了,分布式链接跟踪通常使用这些卷 ID 自动修复文件链路如在这些外壳快捷键和 OLE 链接。当超过这个配额时,可能无法自动修复这些断开的链接。 |
The move table quota for Distributed Link Tracking in this domain has been exceeded. This table is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. While this quota is exceeded, it may not be possible to automatically repair some such broken links. |
0x800034C4 | 文件复制服务无法启用复制: 从 %1 到 %2 为 %3 用 DNS 名称 %4。FRS 将继续重试。 %n 以下是你看到此警告的一些原因。%n%n [1] FRS 不能从此计算机正确解析此 DNS 名称 %4。%n [2] FRS 不在 %4 上运行。%n [3] Active Directory 里此副件的拓扑信息还没有复制到所有域控制器。%n%n 这个事件记录消息将每个连接出现一次。问题解决后,你将看到另一个事件记录消息,它表明连接被建立。 |
The File Replication Service is having trouble enabling replicationfrom %1 to %2 for %3 using the DNS name %4. FRS will keep retrying.%n Following are some of the reasons you would see this warning.%n%n [1] FRS can not correctly resolve the DNS name %4 from this computer.%n [2] FRS is not running on %4.%n [3] The topology information in the Active Directory for this replica has notyet replicated to all the Domain Controllers.%n%n This event log message will appear once per connection, After the problemis fixed you will see another event log message indicating that the connectionhas been established. |
0x800034C5 | 经过多次重试之后,文件复制服务为 %3 启动了从 %1 到 %2 服务。 |
The File Replication Service has enabled replication from %1 to %2 for %3after repeated retries. |
0x800034C8 | 文件复制服务在 %1 计算机上包含 %2 目录的驱动器中检测一个已启动的磁盘写缓存。当驱动器上的电源中断和关键更新丢失时,文件复制服务可能无法恢复。 |
The File Replication Service has detected an enabled disk write cacheon the drive containing the directory %2 on the computer %1.The File Replication Service might not recover when power to thedrive is interrupted and critical updates are lost. |
0x800034CA | 当用另一域控制器的数据初始化该系统卷然后共享为 SYSVOL 时,文件复制服务可能使计算机 %1 不能成为域控制器。%n%n键入“net share”检查 SYSVOL 共享。一旦 SYSVOL 出现,文件复制服务已停止使计算机不能成为域控制器。%n%n系统卷的初始化可能需要一些时间。时间的长短取决于系统卷中的数据量多少,其他域控制器是否可用,以及域控制器之间的复制间隔。 |
The File Replication Service may be preventing the computer %1 from becoming adomain controller while the system volume is being initialized with datafrom another domain controller and then shared as SYSVOL.%n%nType \"net share\" to check for the SYSVOL share. The File ReplicationService has stopped preventing the computer from becoming a domaincontroller once the SYSVOL share appears.%n%nThe initialization of the system volume can take some time.The time is dependent on the amount of data in the system volume,the availability of other domain controllers, and the replicationinterval between domain controllers. |
0x800034CB | 当初始化该系统卷然后共享为 SYSVOL 时,文件复制服务可能使计算机 %1 不能成为域控制器。%n%n键入 \"net share\" 检查 SYSVOL 共享。一旦 SYSVOL 出现,文件复制服务已停止使计算机不能成为域控制器。%n%n系统卷的初始化可能需要一些时间。时间的长短取决于系统卷中的数据量大小,以及域控制器之间的复制间隔。%n%n可通过键入 regedt32 并将 SysvolReady 设置为 1,然后重新启动 Netlogon 服务跳过系统卷的初始化。%n%n警告 - 不推荐你跳过系统卷初始化。应用程序可能会以意料不到的方式失败。%n%n可通过单击 HKEY_LOCAL_MACHINE然后单击System、CurrentControlSet、Services、Netlogon 和 Parameters 找到 SysvolReady 值。%n%n可通过键入 \"net stop netlogon\" 然后键入\"net start netlogon\" 重新启动 Netlogon服务。 |
The File Replication Service may be preventing the computer %1 from becoming adomain controller while the system volume is being initialized and thenshared as SYSVOL.%n%nType \"net share\" to check for the SYSVOL share. The File ReplicationService has stopped preventing the computer from becoming a domaincontroller once the SYSVOL share appears.%n%nThe initialization of the system volume can take some time.The time is dependent on the amount of data in the system volume.%n%nThe initialization of the system volume can be bypassed by first typingregedt32 and setting the value of SysvolReady to 1 and then restartingthe Netlogon service.%n%nWARNING - BYPASSING THE SYSTEM VOLUME INITIALIZATION IS NOT RECOMMENDED.Applications may fail in unexpected ways.%n%nThe value SysvolReady is located by clicking on HKEY_LOCAL_MACHINEand then clicking on System, CurrentControlSet, Services, Netlogon,and Parameters.%n%nThe Netlogon service can be restarted by typing \"net stop netlogon\"followed by \"net start netlogon\". |
0x800034CD | 文件复制服务不会检查对 API“%1”的访问。%n%n可通过运行 regedt32 为“%1”启动访问检查。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题为 HKEY_LOCAL_MACHINE 的窗口。双击 SYSTEM、CurrentControlSet、Services、NtFrs、Parameters、Access Checks、“%1”和“%2”。将字符串更改为 Enabled。%n%n权限可通过突出显示“%1”,然后单击工具栏选项“安全”然后“权限”来更改... |
The File Replication Service will not check access to the API \"%1\".%n%nAccess checks can be enabled for \"%1\" by running regedt32.%n%nClick on Start, Run, and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, Access Checks, \"%1\", and \"%2\".Change the string to Enabled.%n%nPermissions can be changed by highlighting \"%1\" and then clicking on thetoolbar option Security and then Permissions... |
0x800034CE | 文件复制服务不会授予用户“%3”对 API“%1”的访问。%n%n“%1”的权限可通过运行 regedt32 更改。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题为 HKEY_LOCAL_MACHINE 的窗口。双击 SYSTEM、CurrentControlSet、Services、NtFrs、Parameters、Access Checks 并突出显示“%1”。单击工具栏选项“安全”,然后单击“权限”...%n%n可为“%1”禁用访问检查。双击“%2”,然后将字符串更改为 Disabled。 |
The File Replication Service did not grant the user \"%3\" access to theAPI \"%1\".%n%nPermissions for \"%1\" can be changed by running regedt32.%n%nClick on Start, Run, and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, Access Checks, and highlight \"%1\".Click on the toolbar option Security and then Permissions...%n%nAccess checks can be disabled for \"%1\". Double click on \"%2\" andchange the string to Disabled. |
0x800034D0 | 文件复制服务将在 %1 中已存在的文件移动到 %2。%n%n文件复制服务可能在任何时候删除 %2 中的文件。可以通过将文件从 %2 中复制出来以保存文件。复制文件到 %1 可能会引起名称冲突,如果文件在其他复制伙伴中已经存在。%n%n在相同情况下,文件复制服务可能会将文件从 %2 复制到 %1,而不是从别的复制伙伴复制文件。%n%n可以通过在任何时候删除 %2 中的文件来回收硬盘空间。 |
The File Replication Service moved the preexisting files in %1 to %2.%n%nThe File Replication Service may delete the files in %2 at any time.Files can be saved from deletion by copying them out of %2. Copyingthe files into %1 may lead to name conflicts if the files already existon some other replicating partner.%n%nIn some cases, the File Replication Service may copy a filefrom %2 into %1 instead of replicating the file from some otherreplicating partner.%n%nSpace can be recovered at any time by deleting the files in %2. |
0x800034D2 | 由于临时区域已满,文件复制服务中止。如果临时空间有了的话或者如果临时空间限制增加后,复制将恢复使用。%n%n当前的临时空间限制为 %1 KB。%n%n若要更改临时空间限制,请运行regedt32。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题为 HKEY_LOCAL_MACHINE 的窗口。双击 SYSTEM、CurrentControlSet、Services、NtFrs、Parameters 和值\"Staging Space Limit in KB\"。 |
The File Replication Service paused because the staging area is full.Replication will resume if staging space becomes available or if thestaging space limit is increased.%n%nThe current value of the staging space limit is %1 KB.%n%nTo change the staging space limit, run regedt32.%n%nClick on Start, Run and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, and the value\"Staging Space Limit in KB\". |
0x800034D3 | 由于临时区域已满,文件复制服务中止。如果临时空间有了的话或者如果临时空间限制增加后,复制将恢复使用。%n%n当前的临时空间限制为 %1 KB,文件大小为 %2 KB。%n%n要更改临时空间限制,请运行regedt32。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题为 HKEY_LOCAL_MACHINE 的窗口。双击 SYSTEM、CurrentControlSet、Services、NtFrs、Parameters 和值“Staging Space Limit in KB”。 |
The File Replication Service paused because the size of a file exceeds thestaging space limit. Replication will resume only if the staging space limitis increased.%n%nThe staging space limit is %1 KB and the file size is %2 KB.%n%nTo change the staging space limit, run regedt32.%n%nClick on Start, Run and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, and the value\"Staging Space Limit in KB\". |
0x800034D5 | 文件复制服务无法为 %1 计算机找到 DNS 名称原因是不能从 \"%3\" 独特名称中读取 \"%2\" 属性。%n%n文件复制服务将使用 \"%1\" 名称直到计算机的 DNS 名称出现。 |
The File Replication Service cannot find the DNS name for the computer %1because the \"%2\" attribute could not be read from the distinguishedname \"%3\".%n%nThe File Replication Service will try using the name \"%1\" until thecomputer's DNS name appears. |
0x800034EB | 文件复制服务在注册表中检测到无效的参数值。%1。%n%n要求的注册表项名称是 \"%2\"。%n要求的值名称是 \"%3\"。%n要求的注册表数据类型是 %4。%n此参数的允许范围是 %5%n此参数值的数据单位是 %6。%n文件复制服务使用默认值 \"%7\"。%n%n要更改此参数,运行 regedt32。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题栏为 HKEY_LOCAL_MACHINE 的窗口。%n选择注册表项路径: \"%8\"%n双击值名称 -%n \"%9\"%n并更新其值。%n如果没有值名称,你可以在“编辑”菜单下选择“添加值”功能。键入与上面的值名称完全一样的值名称,使用上面的注册表数据类型。在输入值时,确认数据单位和范围正确。 |
The File Replication Service detected an invalid parameter value in theregistry. %1.%n%nThe expected registry key name is \"%2\".%nThe expected value name is \"%3\".%nThe expected registry data type is %4.%nThe allowed range for this parameter is %5%nThe data units for this parameter value are %6.%nThe File Replication Service is using a default value of \"%7\".%n%nTo change this parameter, run regedt32.%n%nClick on Start, Run and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE.%nClick down the key path: \"%8\"%nDouble click on the value name -%n \"%9\"%nand update the value.%nIf the value name is not present you may add it with the Add Value functionunder the Edit Menu item. Type the value name exactly as shown above using theabove registry data type. Make sure you observe the data units and allowed rangewhen entering the value. |
0x800034F8 | 文件复制服务正在将此计算机从副本集 \"%1\" 删除,以尝试从错误状态中恢复过来,%n 错误状态 = %2%n 下一轮询将在 %3 分钟内发生,此计算机将被重新添加入副本集。重新添加将引发副本集的整树同步。 |
The File Replication Service is deleting this computer from the replica set \"%1\" as an attempt torecover from the error state,%n Error status = %2%n At the next poll, which will occur in %3 minutes, this computer will be re-added to thereplica set. The re-addition will trigger a full tree sync for the replica set. |
0x800034FA | 以下是文件复制服务在为 FRS 副本集配置信息轮询域控制器 %1 时遇到的警告和错误提要。%n%n %2%n |
Following is the summary of warnings and errors encountered by File Replication Servicewhile polling the Domain Controller %1 for FRS replica set configuration information.%n%n %2%n |
0x80003714 | QoS [适配器 %2] : %n注册表里的 BestEffortLimit 值超出了 LinkSpeed。默认值采用 Unlimited BestEffort。 |
QoS [Adapter %2]:%nThe BestEffortLimit value set in the registry exceeds the LinkSpeed. Defaulting to Unlimited BestEffort. |
0x8000371D | Qos [适配器 %2]:%n BestEffortLimit 的注册表项目不能通过 WAN 链接支持。使用默认的无限制 BestEffort 模式。 |
QoS [Adapter %2]:%nThe registry entry for BestEffortLimit is not supported over WAN links. Defaulting to Unlimited BestEffort mode. |
0x8000371F | QoS [适配器 %2]:%n分配给流的总带宽超过了 NonBestEffortLimit。这是因为 LinkSpeed 减小,或者注册表项 NonBestEffortLimit 的更改。 |
QoS [Adapter %2]:%nTotal bandwidth allocated to flows exceeds the NonBestEffortLimit. This is because of a reduction in the LinkSpeed or because of a change to the NonBestEffortLimit registry key. |
0x800038BE | DFS 不能联系 %1 Active Directory。DFS 将使用缓存的数据。返回码在记录数据中。 |
DFS could not contact the %1 Active Directory. DFS will be using cached data. The return code is in the record data. |
0x800038C6 | DFS 根 %1 在初始化时失败。根将不可用。 |
DFS Root %1 failed during initialization. The root will not be available. |
0x800038C8 | DFS 不能将信任域的整个列表返回给客户端。信任域太多。 |
DFS is unable to return the entire list of trusted domains to the client. There are too many trusted domains. |
0x800038CA | DFS 无法将路径 %2 的根 %1 的所有匹配链接移动到新路径 %3 |
DFS was unable to move all matching links of root: %1 for path %2 to new path %3 |
0x800038CD | DFS 链接 %1 被错误标记为 DFS 根目录。DFS 命名空间在此服务器上是可操作的。如果此命名空间位于运行未安装 Service Pack 2 (SP2) 的 Windows Server 2003 的服务器上,或者如果该服务器正在运行 Windows 2000 Server,则该命名空间可能在那些服务器上不能完全起作用。有关更正此问题的详细信息,请参阅 Microsoft 知识库。 |
DFS link %1 was marked incorrectly as a DFS root. The DFS namespace is operational on this server. If this namespace is hosted on servers running Windows Server 2003 prior to Service Pack 2 (SP2), or if the server is running Windows 2000 Server, the namespace might not be fully functional on those servers.Please consult the Microsoft Knowledge Base for more information on correcting this issue. |
0x800038CE | 在 DFS 根目录 %2 的元数据中,DFS 元数据对象 %1 为空。DFS 命名空间在此服务器上是可操作的。如果此命名空间位于运行未安装 Service Pack 2 (SP2) 的 Windows Server 2003 的服务器上,或者如果该服务器正在运行 Windows 2000 Server,则该命名空间可能在那些服务器上不能完全起作用。有关更正此问题的详细信息,请参阅 Microsoft 知识库。 |
DFS metadata object %1 is empty in the metadata for DFS root %2. The DFS namespace is operational on this server. If this namespace is hosted on servers running Windows Server 2003 prior to Service Pack 2 (SP2), or if the server is running Windows 2000 Server, the namespace might not be fully functional on those servers.Please consult the Microsoft Knowledge Base for more information on correcting this issue. |
0x800038D9 | DFS 命名空间服务未能初始化承载命名空间根路径的共享文件夹。共享文件夹为:%1 |
The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: %1 |
0x800039D0 | Windows 不能为文件 %2 保存数据。数据已丢失。错误可能是由于你的计算机的硬件问题或网络连接失败造成的。请尝试将此文件保存到其他地方。 |
Windows was unable to save data for file %2. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. |
0x80003A35 | PUT 关闭文件 %1 失败。错误状态: %2。 |
PUT failed for file %1 on Close. ErrorStatus: %2. |
0x80003A36 | DELETE 关闭文件 %1 失败。错误状态: %2。 |
DELETE failed for file %1 on Close. ErrorStatus: %2. |
0x80003A37 | PROPPATCH 关闭文件 %1 失败。错误状态: %2。 |
PROPPATCH failed for file %1 on Close. ErrorStatus: %2. |
0x80003A38 | PROPPATCH 在 %1 上 SetFileInfo 失败。错误状态: %2。 |
PROPPATCH failed for file %1 on SetFileInfo. ErrorStatus: %2. |
0x80003E81 | 检测到一个 TDI 筛选器(%2)。该筛选器尚未通过 Microsoft 认证,可能会导致系统不稳定。 |
A TDI filter (%2) was detected. This filter has not been certified by Microsoft and may cause system instability. |
0x80003E82 | 关闭进程 %4 中本地端口号为 %3 的 %2 套接字所需的时间比预期的要长。在完成关闭操作之前,该本地端口号可能不可用。发生这种情况的原因通常是网络驱动程序行为失常。请确保已安装最新的 Windows 更新,以及任何第三方网络软件,包括 NIC 驱动程序、防火墙或其他安全产品。 |
Closing a %2 socket with local port number %3 in process %4 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products. |
0x800040D8 | EQOS: ***测试***,使用一个字符串 %2。 |
EQOS: ***Testing***, with one string %2. |
0x800040D9 | EQOS: ***正在测试***,有两个字符串,string1 是 %2,string2 是 %3。 |
EQOS: ***Testing***, with two strings, string1 is %2, string2 is %3. |
0x800040DA | 计算机 QoS 策略“%2”版本号无效。将不应用此策略。 |
A computer QoS policy \"%2\" has an invalid version number. This policy will not be applied. |
0x800040DB | 用户 QoS 策略“%2”版本号无效。将不应用此策略。 |
A user QoS policy \"%2\" has an invalid version number. This policy will not be applied. |
0x800040DC | 计算机 QoS 策略“%2”未指定 DSCP 值或调节率。将不应用此策略。 |
A computer QoS policy \"%2\" does not specify a DSCP value or throttle rate. This policy will not be applied. |
0x800040DD | 用户 QoS 策略“%2”未指定 DSCP 值或调节率。将不应用此策略。 |
A user QoS policy \"%2\" does not specify a DSCP value or throttle rate. This policy will not be applied. |
0x800040DE | 已超过计算机 QoS 策略的最大数目。将不应用计算机 QoS 策略“%2”和随后的计算机 QoS 策略。 |
Exceeded the maximum number of computer QoS policies. The computer QoS policy \"%2\" and subsequent computer QoS policies will not be applied. |
0x800040DF | 已超过用户 QoS 策略的最大数目。将不应用用户 QoS 策略“%2”和随后的用户 QoS 策略。 |
Exceeded the maximum number of user QoS policies. The user QoS policy \"%2\" and subsequent user QoS policies will not be applied. |
0x800040E0 | 计算机 QoS 策略“%2”可能与其他 QoS 策略冲突。有关在数据包发送时应用哪个策略的规则,请参阅文档。 |
A computer QoS policy \"%2\" potentially conflicts with other QoS policies. See documentation for rules about which policy will be applied at packet send time. |
0x800040E1 | 用户 QoS 策略“%2”可能与其他 QoS 策略冲突。有关在数据包发送时应用哪个策略的规则,请参阅文档。 |
A user QoS policy \"%2\" potentially conflicts with other QoS policies. See documentation for rules about which policy will be applied at packet send time. |
0x800040E2 | 由于无法处理应用程序路径,因此忽略计算机 QoS 策略“%2”。应用程序路径可能完全无效、或者驱动器号无效、或包含网络映射的驱动器号。 |
A computer QoS policy \"%2\" was ignored because the application path cannot be processed. The application path may be totally invalid, or has an invalid drive letter, or contains network-mapped drive letter. |
0x800040E3 | 由于无法处理应用程序路径,因此忽略用户 QoS 策略“%2”。应用程序路径可能完全无效、或者驱动器号无效、或包含网络映射的驱动器号。 |
A user QoS policy \"%2\" was ignored because the application path cannot be processed. The application path may be totally invalid, or has an invalid drive letter, or contains network-mapped drive letter. |
0x80004268 | 已达到 WinNat 会话限制。 |
WinNat session limit has been reached. |
0x90000001 | Microsoft-Windows-DfsSvc |
Microsoft-Windows-DfsSvc |
0x90000002 | System |
System |
0xC00007D0 | 服务器对于某项系统服务的调用在意外情况下宣告失败。 |
The server's call to a system service failed unexpectedly. |
0xC00007D1 | 由于可用资源不足,服务器无法运行操作。 |
The server was unable to perform an operation due to a shortage of available resources. |
0xC00007D2 | 服务器无法创建设备。服务器无法启动。 |
The server could not create its device. The server could not be started. |
0xC00007D3 | 服务器无法创建过程。服务器无法启动。 |
The server could not create a process. The server could not be started. |
0xC00007D4 | 服务器无法创建启动线程。服务器无法启动。 |
The server could not create a startup thread. The server could not be started. |
0xC00007D5 | 服务器收到一客户端的意外断开连接的请求。 |
The server received an unexpected disconnection from a client. |
0xC00007D6 | 服务器收到来自 %2 的请求,其格式不正确。 |
The server received an incorrectly formatted request from %2. |
0xC00007D7 | 服务器无法打开命名管道文件系统。远程命名管道被禁用。 |
The server could not open the named pipe file system. Remote named pipes are disabled. |
0xC00007DA | 服务器无法启动清除器线程。服务器无法启动。 |
The server could not start the scavenger thread. The server could not be started. |
0xC00007DB | 服务器的配置参数“irps4tacksize”太小,无法让服务器使用本地设备。请增加此参数的值。 |
The server's configuration parameter \"irpstacksize\" is too small for the server to use a local device. Please increase the value of this parameter. |
0xC00007E0 | 服务器无法分配虚拟内存。 |
The server was unable to allocate virtual memory. |
0xC00007E1 | 服务器无法通过系统非分页缓冲池来进行分配,因为服务器已达非分页缓冲池分配的配置极限。 |
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations. |
0xC00007E2 | 服务器无法通过系统分页缓冲池来进行分配,因为服务器已达分页缓冲池分配的配置极限。 |
The server was unable to allocate from the system paged pool because the server reached the configured limit for paged pool allocations. |
0xC00007E3 | 服务器无法通过系统非分页缓冲池来进行分配,因为缓冲池当前是空的。 |
The server was unable to allocate from the system nonpaged pool because the pool was empty. |
0xC00007E4 | 服务器无法通过系统分页缓冲池来进行分配,因为缓冲池当前是空的。 |
The server was unable to allocate from the system paged pool because the pool was empty. |
0xC00009C5 | 服务器的 %1 注册表项不存在。服务器无法启动。 |
The server's Registry key %1 was not present. The server could not start. |
0xC00009C6 | 服务器的 %1 注册表项不存在,且无法创建。服务器无法启动。 |
The server's Registry key %1 was not present and could not be created. The server could not start. |
0xC00009C7 | 服务器未与任何传输绑定。服务器无法启动。 |
The server did not bind to any transports. The server could not start. |
0xC00009C9 | 服务器无法与 %1 传输绑定,因为网络上的另一部计算机具有相同的名称。服务器无法启动。 |
The server could not bind to the transport %1 because another computer on the network has the same name. The server could not start. |
0xC0000FA0 | %2 |
%2 |
0xC0001004 | 无法创建 %2 设备对象。初始化失败。 |
Unable to create device object %2. Initialization failed. |
0xC0001005 | 无法分配需要的资源。初始化失败。 |
Unable to allocate required resources. Initialization failed. |
0xC0001059 | IP 所绑定的支持界面超过了最大上限。某些位于 %2 网络适配器上的界面无法初始化。 |
IP has been bound to more than the maximum number of supported interfaces.Some interfaces on network adapter %2 will not be initialized. |
0xC000105A | 没有为 %2 界面指定子网掩码。本界面和%3 网络适配器上所有的后续界面均无法初始化。 |
No subnet mask was specified for interface %2. This interface and allsubsequent interfaces on network adapter %3 cannot be initialized. |
0xC000105B | 为 %3 网络适配器指定的 %2 地址无效。本界面无法初始化。 |
An invalid address %2 was specified for network adapter %3. This interfacecannot be initialized. |
0xC000105C | 在网络适配器 %4 上为地址 %3 指定了无效的子网掩码 %2。无法初始化本界面。 |
An invalid subnet mask %2 was specified for address %3 on network adapter %4.This interface cannot be initialized. |
0xC000105D | IP 无法分配网络适配器 %2 在配置时所需要的一些资源。此网络适配器上部分的界面无法初始化。 |
IP could not allocate some resources required to configure network adapter %2.Some interfaces on this network adapter will not be initialized. |
0xC000105F | IP 无法打开网络适配器 %2 的注册表项。此网络适配器上的界面不会初始化。 |
IP could not open the registry key for network adapter %2.Interfaces on this network adapter will not be initialized. |
0xC0001061 | 无法读取 %2 网络适配器的配置 IP 地址。IP 界面不会在此网络适配器上初始化。 |
Unable to read the configured IP addresses for network adapter %2.IP interfaces will not be initialized on this network adapter. |
0xC0001062 | 无法读取网络适配器 %2 的配置子网掩码。IP 界面不会在此网络适配器上初始化。 |
Unable to read the configured subnet masks for network adapter %2.IP interfaces will not be initialized on this network adapter. |
0xC0001063 | IP 无法从注册表读取绑定。不会配置任何网络界面。 |
IP was unable to read its bindings from the registry. No network interfaceswere configured. |
0xC0001064 | IP 的初始化操作失败。 |
Initialization of IP failed. |
0xC0001066 | 系统检测到 IP 地址 %2和网络硬件地址 %3 发生地址冲突。本地界面已禁用。 |
The system detected an address conflict for IP address %2 with the systemhaving network hardware address %3. The local interface has been disabled. |
0xC0001067 | 系统检测到 IP 地址 %2和网络硬件地址 %3 发生地址冲突。此系统的网络操作可能会突然中断。 |
The system detected an address conflict for IP address %2 with the systemhaving network hardware address %3. Network operations on this system maybe disrupted as a result. |
0xC0001068 | 无法读取或写入网络适配器 %2 的 NTE 上下文列表。此网络适配器上的 IP 界面可能没有完全初始化。 |
Unable to read or write the NTE Context list for network adapter %2.IP interfaces on this network adapter may not be initialized completely. |
0xC0001081 | TCP/UDP 的初始化操作失败。 |
Initialization of TCP/UDP failed. |
0xC00010C6 | 尝试清除硬件地址为 %2 的网络适配器上的数据包合并筛选器失败(%3 %4 %5)。 |
An attempt to clear a packet coalescing filter on the network adapter with hardware address %2 has failed (%3 %4 %5). |
0xC00010CC | 无法创建驱动程序。 |
The driver could not be created. |
0xC00010CD | 无法打开注册表参数来读取配置信息。 |
Unable to open the Registry Parameters to read configuration information. |
0xC00010D2 | 无法配置 WINS 服务器地址。 |
Unable to configure the addresses of the WINS servers. |
0xC00010D3 | 初始化操作失败,因为传输拒绝打开起始地址。 |
Initialization failed because the transport refused to open initial addresses. |
0xC00010D4 | 初始化操作失败,因为传输拒绝打开初始连接。 |
Initialization failed because the transport refused to open initial connections. |
0xC00010D5 | 数据结构的初始化操作失败。 |
Data structure initialization failed. |
0xC00010D6 | 由于计时器无法启动,初始化操作失败。 |
Initialization failed because the timers could not be started. |
0xC00010D7 | 由于无法创建驱动程序设备,初始化失败。使用字符串“%2”识别初始化失败的接口。如果 NetBT 无法从全局唯一接口标识符(GUID)映射到 MAC 地址,则该接口表示已失败接口或 GUID 的 MAC 地址。如果 MAC 地址或 GUID 都不可用,字符串表示群集设备名称。 |
Initialization failed because the driver device could not be created.Use the string \"%2\" to identify the interface for which initializationfailed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. |
0xC00010D9 | 无法打开注册表链接 (Linkage) 来读取配置信息。 |
Unable to open the Registry Linkage to read configuration information. |
0xC00010DA | 无法自注册表中读取驱动程序对传输的绑定。 |
Unable to read the driver's bindings to the transport from the registry. |
0xC00010DB | 无法读取驱动程序的导出链接配置信息。 |
Unable to read the driver's exported linkage configuration information. |
0xC00010DF | 在 TCP 网络上检测出有重复名称。发送消息的计算机的 IP 地址在数据中。请在命令窗口中使用 nbtstat -n 来查看哪个名称冲突。 |
A duplicate name has been detected on the TCP network. The IP address ofthe computer that sent the message is in the data. Use nbtstat -n in acommand window to see which name is in the Conflict state. |
0xC00010E0 | 另一台计算机发送名称释放消息到这台计算机。可能是因为在 TCP 网络上检测出有重复名称。发送消息的节点的 IP 地址在数据中。请在命令窗口中使用 nbtstat -n 来查看那一个名称在冲突状态。 |
Another computer has sent a name release message to this computer, probablybecause a duplicate name has been detected on the TCP network. The IP addressof the node that sent the message is in the data. Use nbtstat -n in acommand window to see which name is in the Conflict state. |
0xC00010E1 | 名称 \"%2\" 不能注册到 IP 地址 %3 的界面上。具有 IP 地址 %4 的计算机不允许这个名称被此计算机占用。 |
The name \"%2\" could not be registered on the interface with IP address %3.The computer with the IP address %4 did not allow the name to be claimed bythis computer. |
0xC00010E2 | NetBT 没有处理请求,因为它在过去的一小时里遇到 OutOfResources 例外。 |
NetBT failed to process a request because it encountered OutOfResourcesexception(s) in the last 1 hour. |
0xC0001388 | %2 : 发生资源冲突,无法加载。 |
%2 : Has encountered a conflict in resources and could not load. |
0xC0001389 | %2 : 无法分配操作所需的资源。 |
%2 : Could not allocate the resources necessary for operation. |
0xC000138A | %2 : 系统确定网络适配器的运行方式不恰当。 |
%2 : Has determined that the network adapter is not functioning properly. |
0xC000138B | %2 : 找不到网络适配器。 |
%2 : Could not find a network adapter. |
0xC000138C | %2 : 无法和提供的中断号相连接。 |
%2 : Could not connect to the interrupt number supplied. |
0xC000138D | %2 : 遇到内部错误,宣告失败。 |
%2 : Has encountered an internal error and has failed. |
0xC000138E | %2 : 对本驱动程序而言,版本号错误。 |
%2 : The version number is incorrect for this driver. |
0xC0001390 | %2 : 遇到无效的网络地址。 |
%2 : Has encountered an invalid network address. |
0xC0001391 | %2 : 不支持所提供的配置。 |
%2 : Does not support the configuration supplied. |
0xC0001392 | %2 : 网络适配器将无效的数值返回驱动程序中。 |
%2 : The network adapter has returned an invalid value to the driver. |
0xC0001393 | %2 : 注册表中丢失某个需要的参数。 |
%2 : A required parameter is missing from the registry. |
0xC0001394 | %2 : I/O 基址与适配器上的跳线不符。 |
%2 : The I/O base address supplied does not match the jumpers on the adapter. |
0xC000139C | %2 : 下载文件无效。无法加载驱动程序。 |
%2 : The download file is invalid. The driver is unable to load. |
0xC00013A7 | %2: 网络适配器已检测到“适配器检查”,这是不可恢复的硬件或软件错误导致的。 |
%2 : The network adapter has detected an Adapter Check as a result of an unrecoverable hardware or software error. |
0xC00017D4 | 多处理器系统装入了单处理器驱动程序。不能装入此驱动程序。 |
A uniprocessor-specific driver was loaded on a multiprocessor system. The driver could not load. |
0xC0001B58 | 由于下列错误,%1 服务启动失败: %n%2 |
The %1 service failed to start due to the following error: %n%2 |
0xC0001B59 | 与 %1 服务相依的 %2 服务因下列错误而无法启动: %n%3 |
The %1 service depends on the %2 service which failed to start because of the following error: %n%3 |
0xC0001B5A | 与 %1 服务相依的组为 %2,该组中的组件均未启动。 |
The %1 service depends on the %2 group and no member of this group started. |
0xC0001B5B | %1 服务和下列不存在的服务存在相依的关系: %2 |
The %1 service depends on the following nonexistent service: %2 |
0xC0001B5D | %1 调用因下列错误而宣告失败: %n%2 |
The %1 call failed with the following error: %n%2 |
0xC0001B5E | 由于下列错误,%1 调用无法运行 %2: %n%3 |
The %1 call failed for %2 with the following error: %n%3 |
0xC0001B5F | 系统还原为最近一次的正确配置。系统正在重新启动.... |
The system reverted to its last known good configuration. The system is restarting.... |
0xC0001B60 | 帐户名内不能出现反斜线。 |
No backslash is in the account name. |
0xC0001B61 | 等待 %2 服务的连接超时(%1 毫秒)。 |
Timeout (%1 milliseconds) waiting for the %2 service to connect. |
0xC0001B62 | 等待 ReadFile 超时(%1 毫秒)。 |
Timeout (%1 milliseconds) waiting for ReadFile. |
0xC0001B63 | 等待来自 %2 服务的事务处理响应超时(%1 毫秒)。 |
Timeout (%1 milliseconds) waiting for a transaction response from the %2 service. |
0xC0001B64 | 事务处理返回的消息大小不正确。 |
Message returned in transaction has incorrect size. |
0xC0001B65 | 以当前密码登录的尝试因下列错误而宣告失败: %n%1 |
Logon attempt with current password failed with the following error: %n%1 |
0xC0001B66 | 以旧密码再次登录的尝试亦因下列错误而宣告失败: %n%1 |
Second logon attempt with old password also failed with the following error: %n%1 |
0xC0001B67 | 引导或系统启动驱动程序 (%1) 不得与服务有依赖关系。 |
Boot-start or system-start driver (%1) must not depend on a service. |
0xC0001B68 | %1 服务报告了无效的当前状态: %2。 |
The %1 service has reported an invalid current state %2. |
0xC0001B69 | 检测而得的循环依赖请求启动 %1。 |
Detected circular dependencies demand starting %1. |
0xC0001B6A | 检测而得的循环依赖自动启动服务。 |
Detected circular dependencies auto-starting services. |
0xC0001B6B | 循环依赖: %1 服务与组中某一稍后启动的服务有依赖关系。 |
Circular dependency: The %1 service depends on a service in a group which starts later. |
0xC0001B6C | 循环依赖: %1 服务与一个稍后启动的组有依赖关系。 |
Circular dependency: The %1 service depends on a group which starts later. |
0xC0001B6D | 因为 %1 服务启动失败,将会转换为最近一次的正确配置。 |
About to revert to the last known good configuration because the %1 service failed to start. |
0xC0001B6E | %1 服务在启动时挂起。 |
The %1 service hung on starting. |
0xC0001B6F | %1 服务因下列错误而停止: %n%2 |
The %1 service terminated with the following error: %n%2 |
0xC0001B70 | %1 服务因 %2 服务特定错误而停止。 |
The %1 service terminated with service-specific error %2. |
0xC0001B71 | 在系统启动时至少有一个服务或驱动程序产生错误。详细信息,请使用事件查看器查看事件日志。 |
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. |
0xC0001B72 | 下列引导或系统启动驱动程序无法加载: %1 |
The following boot-start or system-start driver(s) failed to load: %1 |
0xC0001B73 | Windows 无法依照配置的方式启动。改用先前的工作配置方式来启动。 |
Windows could not be started as configured. A previous working configuration was used instead. |
0xC0001B74 | %1 注册表项拒绝访问 SYSTEM 帐户程序,所以服务控制管理器取得注册表项的所有权。 |
The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key. |
0xC0001B75 | 服务控制管理器 %0 |
Service Control Manager %0 |
0xC0001B76 | %1 服务标记为交互服务。但是系统配置成不允许交互服务。这项服务可能无法正常操作。 |
The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. |
0xC0001B77 | %1 服务意外地终止,这种情况已经出现了 %2 次。以下的修正操作将在 %3 毫秒内运行: %5。 |
The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective action will be taken in %3 milliseconds: %5. |
0xC0001B78 | 在 %3 服务意外终止后,“服务控制管理器”试着进行修正操作(%2),但这个操作失败,错误是: %n%4 |
The Service Control Manager tried to take a corrective action (%2) after the unexpected termination of the %3 service, but this action failed with the following error: %n%4 |
0xC0001B79 | 服务控制程序没有成功初始化。安全配置服务器(scesrv.dll) 初始化失败,错误为 %1。系统正在重新启动... |
The Service Control Manager did not initialize successfully. The securityconfiguration server (scesrv.dll) failed to initialize with error %1. Thesystem is restarting... |
0xC0001B7A | 服务 %1 意外停止。这发生了 %2 次。 |
The %1 service terminated unexpectedly. It has done this %2 time(s). |
0xC0001B7D | 撤消 %1 服务的配置更改时,服务控制管理器遇到一个错误。此服务的 %2 当前处于无法预料的状态。如果不改正这个配置,你可能无法重新启动 %1 服务或将遇到其他错误。 要保证服务配置合理,请用 Microsoft 管理控制台 (MMC) 里的服务管理单元。 |
The Service Control Manager encountered an error undoing a configuration changeto the %1 service. The service's %2 is currently in an unpredictable state.If you do not correct this configuration, you may not be able to restart the %1service or may encounter other errors. To ensure that the service is configuredproperly, use the Services snap-in in Microsoft Management Console (MMC). |
0xC0001B7E | %1 服务未能用当前配置的密码以 %2 身份登录,因为以下错误:%n%3%n%n要保证服务配置合理,请用 Microsoft 管理控制台 (MMC) 里的服务管理单元。 |
The %1 service was unable to log on as %2 with the currently configuredpassword due to the following error: %n%3%n%nTo ensure that the service isconfigured properly, use the Services snap-in in Microsoft ManagementConsole (MMC). |
0xC0001B81 | %1 服务器无法用当前配置的密码以 %2 身份登录,错误原因如下:%n登录失败: 用户在没有被授予此计算机上的请求的登录类型。%n%n服务器: %1%n域和帐户: %2%n%n此服务器帐户没有足够的用户权限(“登录为服务”权限)。%n%n用户操作%n%n将“登录为服务”权限分配给此计算机上的服务帐户。你可以使用“本地安全设置”(Secpol.msc)来完成。如果此计算机是群集中的一个节点,请检查是否将该用户权限分配给群集中所有节点上的群集服务帐户。%n%n如果你已经将此用户权限分配给服务帐户,并且此用户权限显示为已经被删除,与该节点相关的组策略对象可能正在删除此权限。请与域管理员联系,弄清楚是否发生这种情况。 |
The %1 service was unable to log on as %2 with the currently configuredpassword due to the following error:%nLogon failure: the user has not been granted the requested logon type at thiscomputer.%n%nService: %1%nDomain and account: %2%n%nThis service account does not have the necessary user right \"Log on as a service.\"%n%nUser Action%n%nAssign \"Log on as a service\" to the service account on this computer. You canuse Local Security Settings (Secpol.msc) to do this. If this computer is anode in a cluster, check that this user right is assigned to the Clusterservice account on all nodes in the cluster.%n%nIf you have already assigned this user right to the service account, and theuser right appears to be removed, a Group Policy object associated with thisnode might be removing the right. Check with your domain administrator to findout if this is happening. |
0xC0001B83 | %1 服务在接收到预关闭控制后未正确关闭。 |
The %1 service did not shutdown properly after receiving a preshutdown control. |
0xC0001EDC | %1 命令标记为交互命令。但是系统配置成不允许运行交互命令。此命令可能无法正常运行。 |
The %1 command is marked as an interactive command. However, the system isconfigured to not allow interactive command execution. This command may notfunction properly. |
0xC0001EDD | %1 命令启动失败,错误原因如下: %n%2 |
The %1 command failed to start due to the following error: %n%2 |
0xC0001F43 | 主浏览器从计算机 %2上收到一个服务器宣告,认为它是传输 %3 上的域主浏览器。主浏览器已停止或一个主浏览器选举已开始。 |
The master browser has received a server announcement from the computer %2that believes that it is the master browser for the domain on transport %3.The master browser is stopping or an election is being forced. |
0xC0001F47 | 浏览器无法更新服务状态位。数据有错误。 |
The browser was unable to update the service status bits. The data is the error. |
0xC0001F48 | 浏览器无法更新其角色。数据有错误。 |
The browser was unable to update its role. The data is the error. |
0xC0001F49 | 浏览器无法自动升级为主浏览器。当前认为它是主浏览器的计算机是 %1。 |
The browser was unable to promote itself to master browser. The computer that currentlybelieves it is the master browser is %1. |
0xC0001F4A | 浏览器驱动程序无法将字符串转换成 Unicode 字符串。 |
The browser driver was unable to convert a character string to a unicode string. |
0xC0001F4B | 浏览器无法添加配置参数 %1。 |
The browser was unable to add the configuration parameter %1. |
0xC0001F50 | 浏览器驱动程序在 %4 传输上收到了太多从远程计算机 %2 传至名称 %3 的非法数据报。数据是数据报。在重置频率过期之前,不会再生成更多事件。 |
The browser driver has received too many illegal datagrams from the remote computer %2 to name %3 on transport %4. The data is the datagram.No more events will be generated until the reset frequency has expired. |
0xC0001F51 | 浏览器无法启动,因为 %1 相依服务处于无效的 %2 服务状态。状态 意义 1 服务停止%n 2 等待开始%n 3 停止等待%n 4 运行%n 5 继续等待%n 6 暂停等待%n 7 暂停%n |
The browser has failed to start because the dependent service %1 had invalid service status %2.Status Meaning 1 Service Stopped%n 2 Start Pending%n 3 Stop Pending%n 4 Running%n 5 Continue Pending%n 6 Pause Pending%n 7 Paused%n |
0xC0001F53 | 浏览器无法自动升级为主浏览器。浏览器仍将尝试自动升级为主浏览器,但是不会在“事件查看器”的事件日志中记录任何事件。 |
The browser was unable to promote itself to master browser. The browser will continueto attempt to promote itself to the master browser, but will no longer log any events in the event log in Event Viewer. |
0xC0001F54 | 浏览器无法自动升级为主浏览器。当前认为它是主浏览器的计算机不详。 |
The browser was unable to promote itself to master browser. The computer that currentlybelieves it is the master browser is unknown. |
0xC0001F60 | 浏览器服务已很多次无法在 %1 传输上捕获备份列表。备份浏览器已经停止。 |
The browser service has failed to retrieve the backup list too many times on transport %1.The backup browser is stopping. |
0xC0001F62 | 当浏览器不是主浏览器时,收到一个 GetBrowserServerList 请求。 |
The browser has received a GetBrowserServerList request when it is not the master browser. |
0xC0001F64 | 由于浏览器的 DirectHostBinding 参数有错,浏览器无法启动。 |
The browser has failed to start because of an error in the DirectHostBinding parameter to the browser. |
0xC0002134 | 没有注册表项 %1。无法启动 Sap 代理程序。 |
The Registry Key %1 was not present. The Sap Agent could not start. |
0xC0002135 | Winsock 启动程序失败。Sap 代理程序无法继续。 |
Winsock startup routine failed. The Sap Agent cannot continue. |
0xC0002136 | 主套接字创建调用的操作失败。Sap 代理程序无法继续。 |
Socket create call failed for main socket. The Sap Agent cannot continue. |
0xC0002137 | 无法在套接字上设置广播选项。Sap 代理程序无法继续。 |
Setting broadcast option on socket failed. The Sap Agent cannot continue. |
0xC0002138 | 无法绑定 SAP 套接字。Sap 代理程序无法继续。 |
Binding to SAP Socket failed. The Sap Agent cannot continue. |
0xC0002139 | 无法取得套接字的绑定地址。Sap 代理程序无法继续。 |
Getting bound address of socket failed. The Sap Agent cannot continue. |
0xC000213A | 无法设置 EXTENDED_ADDRESS 选项。Sap 代理程序无法继续。 |
Setting option EXTENDED_ADDRESS failed. The Sap Agent cannot continue. |
0xC000213B | 无法设置 NWLink BCASTINTADDR 选项。Sap 代理程序无法继续。 |
Setting NWLink option BCASTINTADDR failed. The Sap Agent cannot continue. |
0xC000213C | 包含卡片结构的内存分配方式有误。Sap 代理程序无法继续。 |
Error allocating memory to hold a card structure. The Sap Agent cannot continue. |
0xC000213D | 卡片枚举返回 0 张卡片。 |
Enumeration of cards returned 0 cards. |
0xC000213E | 创建线程计算事件的方式有误。Sap 代理程序无法继续。 |
Error creating thread counting event. The Sap Agent cannot continue. |
0xC000213F | 创建接收 semaphore 的方式有误。Sap 代理程序无法继续。 |
Error creating receive semaphore. The Sap Agent cannot continue. |
0xC0002140 | 创建发送事件的方式有误。Sap 代理程序无法继续。 |
Error creating send event. The Sap Agent cannot continue. |
0xC0002141 | 启动接收线程的方式有误。Sap 代理程序无法继续。 |
Error starting receive thread. The Sap Agent cannot continue. |
0xC0002142 | 启动工作者线程的方式有误。Sap 代理程序无法继续。 |
Error starting worker thread. The Sap Agent cannot continue. |
0xC0002143 | 分配数据库数组的方式有误。Sap 代理程序无法继续。 |
Error allocating database array. The Sap Agent cannot continue. |
0xC0002144 | 分配哈希表的方式有误。Sap 代理程序无法继续。 |
Error allocating hash table. The Sap Agent cannot continue. |
0xC0002145 | 启动 LPC 工作者线程的方式有误。Sap 代理程序无法继续。 |
Error starting LPC worker thread. The Sap Agent cannot continue. |
0xC0002146 | LPC 端口的创建方式有误。Sap 代理程序无法继续。 |
Error creating the LPC port. The Sap Agent cannot continue. |
0xC0002147 | LPC 线程事件的创建方式有误。Sap 代理程序无法继续。 |
Error creating the LPC thread event. The Sap Agent cannot continue. |
0xC0002148 | LPC 客户端结构的内存分配方式有误。Sap 代理程序无法继续。 |
Error allocating memory for an LPC Client structure. The Sap Agent cannot continue. |
0xC0002149 | 包含 LPC 工作者线程句柄的缓冲区分配方式有误。Sap 代理程序无法继续。 |
Error allocating buffer to hold LPC worker thread handles. The Sap Agent cannot continue. |
0xC000214A | 注册表中的 WANFilter 值必须为 0-2。Sap 代理程序无法继续。 |
The value for WANFilter in the registry must be 0-2. The Sap Agent cannot continue. |
0xC000214B | 卡片列表访问同步化事件创建错误。Sap 代理程序无法继续。 |
Error creating event for card list access synchronization. The Sap Agent cannot continue. |
0xC000214C | 数据库访问同步化事件创建错误。Sap 代理程序无法继续。 |
Error creating event for database access synchronization. The Sap Agent cannot continue. |
0xC000214E | WAN 控制 semaphore 创建方式错误。Sap 代理程序无法继续。 |
Error creating WAN control semaphore. The Sap Agent cannot continue. |
0xC000214F | WAN 套接字创建调用的操作失败。Sap 代理程序无法继续。 |
Socket create call failed for WAN socket. The Sap Agent cannot continue. |
0xC0002150 | 无法完成对 WAN 套接字 的绑定。Sap 代理程序无法继续。 |
Binding to WAN socket failed. The Sap Agent cannot continue. |
0xC0002151 | 启动 WAN 工作者线程方式有误。Sap 代理程序无法继续。 |
Error starting WAN worker thread. The Sap Agent cannot continue. |
0xC0002152 | 启动 WAN 检测线程方式有误。Sap 代理程序无法继续。 |
Error starting WAN check thread. The Sap Agent cannot continue. |
0xC0002153 | getsockopt IPX_MAX_ADAPTER_NUM 有错。数据为错误代码。Sap 代理程序无法继续。 |
Error on getsockopt IPX_MAX_ADAPTER_NUM. Data is the error code. The Sap Agent cannot continue. |
0xC0002154 | 包含 WAN 报告线程句柄的缓冲区分配错误。Sap 代理程序无法继续。 |
Error allocating buffer to hold WAN notify thread handles. The Sap Agent cannot continue. |
0xC0002155 | 创建 WAN 线程事件时出错。Sap 代理程序无法继续。 |
Error creating the WAN thread event. The Sap Agent cannot continue. |
0xC000232C | %2 无法向 NDIS 包装器注册自己。 |
%2 failed to register itself with the NDIS wrapper. |
0xC000232D | %2 绑定网络适配器 %3 失败。 |
%2 failed to bind to network adapter %3. |
0xC000232E | %2 找不到网络适配器 %3。 |
%2 could not find network adapter %3. |
0xC000232F | 在网络适配器 %4 上设置对象标识符 %3 时,%2 失败。 |
%2 failed while setting object identifier %3 on network adapter %4. |
0xC0002330 | 在网络适配器 %4 上查询对象标识符 %3 时,%2 失败。 |
%2 failed while querying object identifier %3 on network adapter %4. |
0xC0002520 | %2 配置为使用内部网络号码 %3。此网络号码和某个连到的网络有冲突。配置的内部网络号码将被忽略。 |
%2 was configured with an internal network number of %3. This networknumber conflicts with one of the attached networks. The configuredinternal network number will be ignored. |
0xC0002521 | %2 没有绑定到适配器 %3 上的配置帧类型。 |
%2 had no frame types configured for the binding to adapter %3. |
0xC0002522 | 因为无法创建驱动程序设备,所以 %2 无法初始化。 |
%2 failed to initialize because the driver device could not be created. |
0xC0002523 | %2 无法绑定到任何适配器。传输无法启动。 |
%2 could not bind to any adapters. The transport could not start. |
0xC0002710 | 无法启动 DCOM 服务器: %3。错误: %n“%%%2”%n 在启动该命令时发生: %n%1 |
Unable to start a DCOM Server: %3.The error:%n\"%%%2\"%nHappened while starting this command:%n%1 |
0xC0002711 | 无法启动 DCOM 服务器: %3 如 %4/%5。错误: %n“%%%2”%n在启动该命令时发生: %n%1 |
Unable to start a DCOM Server: %3 as %4/%5.The error:%n\"%%%2\"%nHappened while starting this command:%n%1 |
0xC0002712 | 启动 DCOM 服务器的访问被拒绝。服务器是: %n%1%n用户是 %2/%3, SID=%4. |
Access denied attempting to launch a DCOM Server.The server is:%n%1%nThe user is %2/%3, SID=%4. |
0xC0002713 | 利用 DefaultLaunchPermssion 启动 DCOM 服务器的访问被拒绝。服务器是: %n%1%n用户是 %2/%3, SID=%4. |
Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion.The server is:%n%1%nThe user is %2/%3, SID=%4. |
0xC0002714 | DCOM 遇到错误“%%%1”并且无法登录到 %2\\%3上以运行服务器:%n%4 |
DCOM got error \"%%%1\" and was unable to logon %2\\%3in order to run the server:%n%4 |
0xC0002715 | DCOM 遇到错误“%%%1”,试图以参数“%3”启动服务 %2 以运行服务器:%n%4 |
DCOM got error \"%%%1\" attempting to start the service %2 with arguments \"%3\"in order to run the server:%n%4 |
0xC0002716 | 试图激活服务器: %n%3 时,DCOM 从计算机 %2 得到错误“%%%1” |
DCOM got error \"%%%1\" from the computer %2 when attempting toactivate the server:%n%3 |
0xC0002717 | 当试图激活服务器: %n%2 时,DCOM 出现错误“%%%1”, |
DCOM got error \"%%%1\" when attempting toactivate the server:%n%2 |
0xC0002718 | 当试图用文件 %4 进入服务器: %n%3 时,DCOM 从计算机 %2 中得到错误“%%%1”。 |
DCOM got error \"%%%1\" from the computer %2 when attempting tothe server:%n%3 with file %4. |
0xC0002719 | DCOM 无法使用任何配置的协议与计算机 %1 通信。 |
DCOM was unable to communicate with the computer %1 using any of the configuredprotocols. |
0xC000271A | 服务器 %1 没有在限定的时间内用 DCOM 注册。 |
The server %1 did not register with DCOM within the required timeout. |
0xC000271B | 无法联系服务器 %1 以建立到客户端的连接 |
The server %1 could not be contacted to establish the connection to the client |
0xC000271C | 在 DCOM 中有一个声明失败。上下文如下:%1%2%3 |
There is an assertion failure in DCOM. Context follows:%1%2%3 |
0xC000271D | DCOM 服务器尝试在一个无效的结束点上侦听。Protseq: %1终结点: %2标志: %3 |
DCOM server attempted to listen on an invalid endpoint.Protseq: %1Endpoint: %2Flags: %3 |
0xC000271E | 激活 CLSID %1 失败,因为 COM+ 的远程激活被禁用。要启用此功能,请使用配置你的服务器向导,并选择“Web应用程序服务器”角色。 |
The activation for CLSID %1 failed because remote activations for COM+ are disabled.To enable this functionality use the Configure Your Server wizard and select the WebApplication Server role. |
0xC000272D | 等待服务 %2 停止时,CLSID %1 的激活已超时。 |
The activation of the CLSID %1 timed out waiting for the service %2 to stop. |
0xC000272E | 无法启动 COM 服务器进行调试:%3。在启动命令 %n%1 时发生错误 %n\"%%%2\"%n |
Unable to start a COM Server for debugging: %3.The error:%n\"%%%2\"%nHappened while starting this command:%n%1 |
0xC0002AF8 | 无法启动 DNS 客户端服务。无法加载 DLL %2,错误: %1。请从安装 CD 重新安装此 DLL。 |
Unable to start DNS Client Service.Failed to load DLL %2, Error: %1.Please reinstall this DLL from installation CD. |
0xC0002AF9 | 无法启动 DNS 客户端服务。在 DLL %2 中找不到 %3 项。请从安装 CD 重新安装此 DLL。有关特定错误代码信息,请查看事件详细信息。 |
Unable to start DNS Client service. Can not find entry %3 in DLL %2.Please reinstall this DLL from installation CD. See event details for specific error code information. |
0xC0002AFA | 无法启动 DNS 客户端服务。系统无法注册一个服务控制处理程序,可能是由于资源不足。请关闭所有未使用的应用程序或重新启动计算机。有关具体的错误代码信息,请查事件详细信息。 |
Unable to start the DNS Client service. The system could not register aservice control handler and could be out of resources. Close anyapplications not in use or reboot the computer. See event details for specific error code information. |
0xC0002AFB | 无法启动 DNS 客户端服务。系统无法为此服务创建终止事件,可能是由于资源不足。请关闭没有使用的应用程序或重新启动计算机。有关具体的错误代码信息,请查看事件详细信息。 |
Unable to start DNS Client service. The system couldnot create a termination event for this service andcould be out of resources. Close any applications notin use or reboot the computer. See event details for specific error code information. |
0xC0002AFC | 无法启动 DNS 客户端服务。无法为此服务启动远程过程调用(RPC)界面。若要更正此问题,你可以重新启动 RPC 和 DNS客户服务。为此,请在命令提示符处使用如下命令: (1) 键入 \"net start rpc\" 以启动 RPC 服务,(2)键入 \"net start dnscache\" 以启动 DNS 客户服务。有关具体的错误代码信息,请查看事件详细信息。 |
Unable to start DNS Client service. Could not start theRemote Procedure Call (RPC) interface for this service.To correct the problem, you may restart the RPC and DNSClient services. To do so, use the following commands at a commandprompt: (1) type \"net start rpc\" to start the RPC service, and (2)type \"net start dnscache\" to start the DNS Client service. See event details for specific error code information. |
0xC0002AFD | 无法启动 DNS 客户端服务。系统无法为此服务注册关机通知,可能是由于资源不足。请尝试关闭没有使用的应用程序或重新启动计算机。 |
Unable to start DNS Client service. The system could not registershutdown notification for this service and could be out of resources.Try closing any applications not in use or reboot the computer. |
0xC0002AFE | 无法启动 DNS 客户端服务。无法用服务控制管理器更新状态。若要更正此错误,你可以重新启动 RPC 和 DNS客户服务。 为此,请在命令提示符处使用如下命令: (1) 键入 \"net start rpc\" 以启动 RPC 服务,(2)键入 \"net start dnscache\" 以启动 DNS 客户端服务。有关具体的错误代码信息,请查看事件详细信息。 |
Unable to start DNS Client service. Could not update status withService Control Manager. To correct the problem, you may restartthe RPC and DNS Client services. To do so, use the following commandsat a command prompt: (1) type \"net start rpc\" to start the RPC service,and (2) type \"net start dnscache\" to start the DNS Client service. See event details for specific error code information. |
0xC0002AFF | 无法启动 DNS 客户端服务,因为系统分配内存失败。可能导致可用内存不足。请尝试关闭没有使用的所有应用程序或重新启动计算机。有关具体的错误代码信息,请查看事件错误信息。 |
Unable to start DNS Client service because the system failed to allocatememory and may be out of available memory. Try closing any applications notin use or reboot the computer. See event details for specific error code information. |
0xC00030D4 | 在“分布式链接跟踪”中出现内部错误。错误代码为 %1。 |
An internal error occured in Distributed Link Tracking. The error code was %1. |
0xC00030D6 | 服务未能启动。错误 = %1 |
Service failed to start. Error = %1 |
0xC00030D7 | 分布式链接跟踪日志在卷 %1 上被损坏: 已重新创建。由于某种原因断了,分布式链接跟踪通常使用这些卷 ID 这个日志是用于自动修改文件链接如在这些链路外壳快捷键和 OLE 链接。 |
The Distributed Link Tracking log was corrupt on volume %1: and has been re-created. This log is used to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. |
0xC00034BC | 文件复制服务 |
File Replication Service |
0xC00034C0 | 在清理之前,文件复制服务终止。 |
The File Replication Service stopped without cleaning up. |
0xC00034C1 | 在出现一个声明失败后,文件复制服务终止。 |
The File Replication Service has stopped after taking an assertion failure. |
0xC00034C2 | 文件复制服务的一致性检查%n (%3)%n(在 \"%1\" 在行 %2 上) 失败。%n%n文件复制服务将稍后自动重新启动。如果此问题持续出现,此事件日志的下一个项目描述了恢复过程。%n有关自动重新启动的详细信息,请在“我的电脑”上单击右键,然后单击管理、系统工具、服务、文件复制服务和故障恢复。 |
The File Replication Service failed a consistency check%n (%3)%nin \"%1\" at line %2.%n%nThe File Replication Service will restart automatically at a later time.If this problem persists a subsequent entry in this event log describes therecovery procedure.%nFor more information about the automatic restart right click onMy Computer and then click on Manage, System Tools, Services,File Replication Service, and Recovery. |
0xC00034C3 | 文件复制服务不能开始复制为 %3 目录在 %2 计算机上复制集 %1,因为卷 %4 的种类不是 NTFS 5.0 或更高版本。%n%n卷类可通过键入“chkdsk %4”找到。%n%n卷可通过键入“chkntfs /E %4” 更新到 NTFS 5.0 或更高版本。 |
The File Replication Service cannot start replica set %1 on computer %2for directory %3 because the type of volume %4 is not NTFS 5.0 or later.%n%nThe volume's type can be found by typing \"chkdsk %4\".%n%nThe volume can be upgraded to NTFS 5.0 or later by typing \"chkntfs /E %4\". |
0xC00034C6 | 在计算机 %1 上的文件复制服务无法与在 %2 计算机上的文件复制服务通信。%n%n验证计算机 %2 已启动并正在运行。%n%n在 %2 上键入 \"net start ntfrs\" 验证在 %2 上的文件复制服务正在运行。%n%n通过在 %2 上键入 \"ping %1\" 并且在 %1 上键入 \"ping %2\" 以验证%1 和 %2 之间的网络正在运行。如果 ping 成功,请重新尝试失败的操作。如果 ping 失败,则 DNS 服务器可能有问题,%n%nDNS 服务器负责向 IP 地址映射计算机名。\"ipconfig\" 和 \"nslookup\" 指令帮助 DNS 服务器诊断问题。%n%n键入 \"ipconfig /all\" 会列出计算机的 IP 地址和计算机的 DNS 服务器的地址。键入\"ping \"以验证有一台 DNS 服务器有效。%2 或 %1 的 DNS 映射可通过在 %1 和 %2 上键入 \"nslookup\" 然后键入 \"%2\" 然后键入 \"%1\"验证。确认检查在 %1 和 %2 上的 DNS 服务器;任何一台服务器上出现 DNS 问题都会影响正常的通信。%n%n某些 %1 和 %2 之间的问题可通过刷新DNS 解析程序缓存解决。键入 \"ipconfig /flushdns\"。%n%n某些 %1 和 %2 之间的问题可通过刷新IP 地址解决。键入 \"ipconfig /release\" 然后再键入\"ipconfig /renew\"。%n%n某些 %1 和 %2 之间的问题可通过重置计算机的 DNS 项解决。键入 \"net stop NetLogon\",然后再键入 \"net start NetLogon\"。%n%n某些 %1 和 %2 之间的问题可通过重新启动文件复制服务解决。键入 \"net stop ntfrs\",然后再键入 \"net start ntfrs\"。%n%n某些 %1 和 %2 之间的问题可通过关闭正在运行的应用程序之后重新启动 %1 和 %2 计算机解决,特别是 dcpromo。单击\"开始\"、\"关机\",选择\"重新启动\"并单击\"确定\"。%n%n其他网络和计算机问题超出这个事件日志消息的作用域。 |
The File Replication Service on the computer %1 cannot communicate withthe File Replication Service on the computer %2.%n%nVerify that the computer %2 is up and running.%n%nVerify that the File Replication Service is running on %2 bytyping \"net start ntfrs\" on %2.%n%nVerify that the network is functioning between %1 and %2 bytyping \"ping %1\" on %2 and \"ping %2\" on %1.If the pings succeed then retry the failed operation.If the pings fail then there may be problems with the DNS server.%n%nThe DNS server is responsible for mapping computer names to IP addresses.The commands \"ipconfig\" and \"nslookup\" help diagnose problems with theDNS server.%n%nTyping \"ipconfig /all\" will list the computer's IP address and the IPaddress of the computer's DNS servers. Type \"ping \"to verify that a DNS server is available. The DNS mapping for %2 or %1can be verified by typing \"nslookup\" and then typing \"%2\" and then \"%1\"on %1 and %2. Be sure to check out the DNS server on both %1 and %2;a DNS problem on either computer will prevent proper communication.%n%nSome network problems between %1 and %2 can be cleared up by flushingthe DNS Resolver Cache. Type \"ipconfig /flushdns\".%n%nSome network problems between %1 and %2 can be cleared up by renewingthe IP address. Type \"ipconfig /release\" followed by \"ipconfig /renew\".%n%nSome network problems between %1 and %2 can be cleared up by resettingthe computer's DNS entry. Type \"net stop NetLogon\" followed by\"net start NetLogon\".%n%nSome problems between %1 and %2 can be cleared up by restartingthe File Replication Service. Type \"net stop ntfrs\" followed by\"net start ntfrs\".%n%nSome problems between %1 and %2 can be cleared up by restartingthe computers %1 and %2 AFTER CLOSING RUNNING APPLIATIONS,especially dcpromo. Click on Start, Shutdown, select Restart, andclick on OK.%n%nOther network and computer problems are beyond the scope ofthis event log message. |
0xC00034C7 | 由于在包括 %2 的卷上没有空闲空间,在计算机 %1 上的文件复制服务已停止。%n%n可键入“dir %2”找到卷上的空闲空间。%n%n一旦在包括 %2 的卷上找到可用空间,可键入“net start ntfrs”马上重新启动文件复制服务。否则,文件复制服务稍后会自动重新启动。%n%n有关自动重新启动的详细信息,请右键单击“我的电脑”,然后单击“管理”、系统工具、服务、文件复制服务和故障恢复。%n%n关于在卷上管理空间的信息请键入 “copy /?”、“rename /?”、“del /?”、 “rmdir /?” 和 “dir /?”。 |
The File Replication Service is stopping on computer %1 because there is no freespace on the volume containing %2.%n%nThe available space on the volume can be found by typing\"dir %2\".%n%nOnce free space is made available on the volume containing %2,the File Replication Service can be restarted immediately by typing\"net start ntfrs\". Otherwise, the File Replication Service willrestart automatically at a later time.%n%nFor more information about the automatic restart right click onMy Computer and then click on Manage, System Tools, Services, FileReplication Service, and Recovery.%n%nFor more information about managing space on a volume type \"copy /?\",\"rename /?\", \"del /?\", \"rmdir /?\", and \"dir /?\". |
0xC00034C9 | 由于 %2 数据库损坏,在 %1 计算机上的文件复制服务已停止。%n%n可通过键入“esentutl /d %2 /l%3 /s%4”恢复数据库。%n%n数据库一旦成功恢复,可通过键入“net start ntfrs”重新启动文件复制服务。 |
The File Replication Service on computer %1 is stopping because thedatabase %2 is corrupted.%n%nThe database can be recovered by typing \"esentutl /d %2 /l%3 /s%4\".%n%nOnce the database has been successfully recovered theFile Replication Service can be restarted by typing \"net start ntfrs\". |
0xC00034CF | 文件复制服务不会授予一位未知用户对 API “%1” 的访问。%n%n可使用运行 regedt32 为“%1”禁用访问检查。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题为 HKEY_LOCAL_MACHINE 的窗口。双击 SYSTEM,CurrentControlSet、Services、NtFrs、Parameters、Access Checks、“%1”,和“%2”。将字符串更改为 Disabled。%n%n要更改权限,可选定“%1”,单击工具栏选项“安全”然后选择“权限...”。 |
The File Replication Service could not grant an unknown user access to theAPI \"%1\".%n%nAccess checks can be disabled for \"%1\" by running regedt32.%n%nClick on Start, Run, and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, Access Checks, \"%1\", and \"%2\".Change the string to Disabled.%n%nPermissions can be changed by highlighting \"%1\" and then clicking on thetoolbar option Security and then Permissions... |
0xC00034D1 | 在备份/还原应用程序完成之前,文件复制服务无法在 %1上启动复制。%n%n备份/还原应用程序设置了一个注册表项使 文件复制服务在删除注册表项之前或系统重新启动不能开始。%n%n备份/还原应用程序可能正在运行。继续之前请与你的本地管理员联系。%n%n可单击开始、关闭和选择重新启动来重新启动计算机。%n%n警告- 不推荐删除注册表项!应用程序可能会以意料不到的方式失败。%n%n可通过运行 regedt32 删除注册项。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击窗口式的 HKEY_LOCAL_MACHINE。双击 SYSTEM、CurrentControlSet、Services、NtFrs、Parameters、Backup/Restore、\"Stop NtFrs from Starting\"。在工具栏上,单击编辑并选择删除。小心! 删除“Stop NtFrs From Starting”之外的项可能造成意想不到的副作用。 |
The File Replication Service cannot enable replication on the comptuer %1until a backup/restore application completes.%n%nA backup/restore application has set a registry key thatprevents the File Replication Service from starting until the registrykey is deleted or the system is rebooted.%n%nThe backup/restore application may still be running. Check with yourlocal administrator before proceeding further.%n%nThe computer can be rebooted by clicking on Start, Shutdown, andselecting Restart.%n%nWARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED!Applications may fail in unexpected ways.%n%nThe registry key can be deleted by running regedt32.%n%nClick on Start, Run, and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,CurrentControlSet, Services, NtFrs, Parameters, Backup/Restore,\"Stop NtFrs from Starting\". On the toolbar, click on Edit and selectDelete. Be careful! Deleting a key other than \"Stop NtFrs From Starting\"can have unexpected sideeffects. |
0xC00034D4 | 由于无法创建一个通用唯一 ID (UUID),文件复制服务 在 %1计算机上停止。%n%nSDK 函数 UuidCreate() 返回错误 “%2”。%n%n问题可能是缺乏一个 Ethernet 地址、令派环地址或网络地址。缺乏一个网络地址意味着有一个不支持的网络适配器。%n%n文件复制服务将稍后自动重新启动。有关自动重新启动的详细信息,请右键单击“我的电脑”然后单击管理、系统工具、服务、文件复制服务和故障恢复。 |
The File Replication Service is stopping on the computer %1 becausea universally unique ID (UUID) cannot be created.%n%nThe SDK function UuidCreate() returned the error \"%2\".%n%nThe problem may be the lack of an Ethernet address,token ring address, or network address. The lack of a networkaddress implies an unsupported netcard.%n%nThe File Replication Service will restart automatically at a later time.For more information about the automatic restart right click onMy Computer and then click on Manage, System Tools, Services,File Replication Service, and Recovery. |
0xC00034D6 | 文件复制服务无法用 %2 计算机复制%1 原因是无法从已辨认的名称“%3”中决定该计算机的 SID。%n%n文件复制服务将稍后重试。 |
The File Replication Service cannot replicate %1 with the computer%2 because the computer's SID cannot be determined from the distinguishedname \"%3\".%n%nThe File Replication Service will retry later. |
0xC00034D7 | RPC 在对象 FileReplicaSet 的Open 函数上绑定失败。此对象的计数器数据将不可用。FileReplicaSet 对象 包含副本的性能计数器,副本集的文件将被文件复制服务所复制。 |
The RPC binding failed in the Open function of the FileReplicaSet Object. Thecounter data for this object will not be available. The FileReplicaSet objectcontains the performance counters of the Replica sets whose files are beingreplicated by the File Replication Service. |
0xC00034D8 | RPC 在对象 FileReplicaConn 的 Open 函数上绑定失败。此对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件的连接性能计数器。 |
The RPC binding failed in the Open function of the FileReplicaConn Object. Thecounter data for this object will not be available. The FileReplicaConn objectcontains the performance counters of the connections over which files are beingreplicated by the File Replication Service. |
0xC00034D9 | RPC 在对象 FileReplicaSet 的 Open 函数上调用失败。此对象的计数器数据无效。FileReplicaSet 对象 包含副本集的性能计数器,副本集的文件将被文件复制服务所复制。 |
The RPC call failed in the Open function of the FileReplicaSet Object. Thecounter data for this object will not be available. The FileReplicaSet objectcontains the performance counters of the Replica sets whose files are beingreplicated by the File Replication Service. |
0xC00034DA | RPC 调用 FileReplicaConn 对象的 Open 函数失败。此对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件的连接性能计数器。 |
The RPC call failed in the Open function of the FileReplicaConn Object. Thecounter data for this object will not be available. The FileReplicaConn objectcontains the performance counters of the connections over which files are beingreplicated by the File Replication Service. |
0xC00034DB | RPC 在 FileReplicaSet 对象的 Collect 函数上绑定失败。在绑定成功之前,此对象的计数器数据无效。FileReplicaSet 对象 包含 Replica Set 的性能计数器,副本集的文件将被文件复制服务所复制。 |
The RPC binding failed in the Collect function of the FileReplicaSet Object. Thecounter data for this object will not be available till the binding succeeds.The FileReplicaSet object contains the performance counters of the Replica setswhose files are being replicated by the File Replication Service. |
0xC00034DC | RPC 在 FileReplicaConn 对象的 Collect 函数上绑定失败。在绑定成功之前,此对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件的连接性能计数器。 |
The RPC binding failed in the Collect function of the FileReplicaConn Object.The counter data for this object will not be available till the bindingsucceeds. The FileReplicaConn object contains the performance counters of theconnections over which files are being replicated by the File ReplicationService. |
0xC00034DD | RPC 调用 FileReplicaSet 对象的 Collect 函数失败。在绑定成功之前,此对象的计数器数据无效。FileReplicaSet 对象包含 Replica Set 的性能计数器,Replica Set 的文件将被文件复制服务所复制。 |
The RPC call failed in the Collect function of the FileReplicaSet Object. Thecounter data for this object will not be available till the call succeeds. TheFileReplicaSet object contains the performance counters of the Replica setswhose files are being replicated by the File Replication Service. |
0xC00034DE | RPC 调用 FileReplicaConn 对象的Collect 函数失败。在绑定成功之前,此对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件的连接性能计数器。 |
The RPC call failed in the Collect function of the FileReplicaConn Object. Thecounter data for this object will not be available till the call succeeds. TheFileReplicaConn object contains the performance counters of the connections overwhich files are being replicated by the File Replication Service. |
0xC00034DF | 调用 FileReplicaSet 对象中的 Open 函数的 VirtualAlloc 失败。此对象的计数器数据无效。FileReplicaSet 对象包括用文件复制服务复制文件的复制设置的性能计数器。 |
The call to VirtualAlloc failed in the Open function of the FileReplicaSetObject. The counter data for this object will not be available. TheFileReplicaSet object contains the performance counters of the Replica setswhose files are being replicated by the File Replication Service. |
0xC00034E0 | 调用 FileReplicaConn 对象中的 Open 函数的 VirtualAlloc 失败。这个对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件连接性能计数器。 |
The call to VirtualAlloc failed in the Open function of the FileReplicaConnObject. The counter data for this object will not be available. TheFileReplicaConn object contains the performance counters of the connections overwhich files are being replicated by the File Replication Service. |
0xC00034E1 | 调用 FileReplicaSet 对象的 Open 函数的 Registry 失败。此对象的计数器数据无效。FileReplicaSet 对象包含 Replica Set的性能计数器,Replica Set 的文件将被文件复制服务所复制。 |
The call to the Registry failed in the Open function of the FileReplicaSetObject. The counter data for this object will not be available. TheFileReplicaSet object contains the performance counters of the Replica setswhose files are being replicated by the File Replication Service. |
0xC00034E2 | 调用 FileReplicaConn 对象的 Open 函数的 Registry 失败。此对象的计数器数据无效。FileReplicaConn 对象包括用文件复制服务复制文件的连接性能计数器。 |
The call to the Registry failed in the Open function of the FileReplicaConnObject. The counter data for this object will not be available. TheFileReplicaConn object contains the performance counters of the connections overwhich files are being replicated by the File Replication Service. |
0xC00034E3 | 文件复制服务不能复制 %1,因为复制目录的路径名不是一个现有的可访问的完全合格的本地目录。 |
The File Replication Service cannot replicate %1 because thepathname of the replicated directory is not the fully qualifiedpathname of an existing, accessible local directory. |
0xC00034E4 | 文件复制服务不能复制 %1,因为用户指定的分段目录:%n %2%n的路径名不是一个现有的可访问的合格的本地目录。 |
The File Replication Service cannot replicate %1 because the pathnameof the customer designated staging directory:%n %2%n is not the fully qualified pathname of an existing, accessible local directory. |
0xC00034E5 | 文件复制服务不能复制 %1,因为它与文件复制服务的登录路径名 %2 重叠。 |
The File Replication Service cannot replicate %1 because it overlapsthe File Replication Service's logging pathname %2. |
0xC00034E6 | 文件复制服务不能复制 %1,因为它与文件复制服务的工作目录 %2 重叠。 |
The File Replication Service cannot replicate %1 because it overlapsthe File Replication Service's working directory %2. |
0xC00034E7 | 文件复制服务不能复制 %1,因为它与分段目录 %2 重叠。 |
The File Replication Service cannot replicate %1 because it overlapsthe staging directory %2. |
0xC00034E8 | 文件复制服务不能复制 %1,因为它与复制目录 %2 重叠。 |
The File Replication Service cannot replicate %1 because it overlapsthe replicating directory %2. |
0xC00034E9 | 文件复制服务不能复制 %1,因为它与复制目录 %3 的分段目录 %2 重叠。 |
The File Replication Service cannot replicate %1 because it overlapsthe staging directory %2 of the replicating directory %3. |
0xC00034EA | 文件复制服务不能为复制准备根目录 %1。这可能是因为创建根目录或删除根目录以前存在的文件时出现问题。%n%n请检查指向根目录的路径存在而且可以访问。 |
The File Replication Service could not prepare the root directory%1 for replication. This is likely due to a problem creating theroot directory or a problem removing preexisting files in the rootdirectory.%n%nCheck that the path leading up to the root directory exists and isaccessible. |
0xC00034EC | 文件复制服务不能从它的伙伴计算机复制,因为时钟时间差别超过了正的或负的%1 分钟范围。%n%n到伙伴计算机的连接是:%n \"%2\"%n检查到的时间差别是: %3 分钟。%n%n注意: 如果此时间差别接近于 60 分钟的倍数,那么有可能此计算机或它的伙伴计算机的时区设置不对。请在两台计算机上检查时区和系统时间设置是否正确。%n%n如果需要,用于测试计算机时间一致性的默认值可以在计算机的注册表中更改。(注意: 不推荐使用。)%n%n要更改此参数,运行 regedt32。%n%n单击「开始」、“运行”,然后键入 regedt32。%n%n单击标题栏为 HKEY_LOCAL_MACHINE 的窗口。%n注册键路径为:%n \"System\\CurrentControlSet\\Services\\NtFrs\\Parameters\"%n双击%n \"Partner Clock Skew In Minutes\"%n并更新其值。%n%n如果没有值名称,你可以在“编辑”菜单下选用“添加值”。 使用注册表数据类型 REG_DWORD,并键入与上面的值完全一样的值。 |
The File Replication Service is unable to replicate with its partner computerbecause the difference in clock times is outside the range of plus or minus%1 minutes.%n%nThe connection to the partner computer is:%n \"%2\"%nThe detected time difference is: %3 minutes.%n%nNote: If this time difference is close to a multiple of 60 minutes then itis likely that either this computer or its partner computer was set to theincorrect time zone when the computer time was initially set. Check thatthe time zone and the system time are correctly set on both computers.%n%nIf necessary, the default value used to test for computer time consistencymay be changed in the registry on this computer. (Note: This is not recommended.)%n%nTo change this parameter, run regedt32.%n%nClick on Start, Run and type regedt32.%n%nClick on the window entitled HKEY_LOCAL_MACHINE.%nClick down the key path:%n \"System\\CurrentControlSet\\Services\\NtFrs\\Parameters\"%nDouble click on the value name%n \"Partner Clock Skew In Minutes\"%nand update the value.%n%nIf the value name is not present you may add it with the Add Value functionunder the Edit Menu item. Type the value name exactly as shown above using thethe registry data type REG_DWORD. |
0xC00034ED | 文件复制服务不能从伙伴计算机复制,因为与要复制的文件相关联的事件时间太远了。它比当前时间要大 %1 分钟。如果在文件创建或更新时伙伴计算机上的系统时间设置不正确,则有可能发生这种情况。为保持副本集的完整性,此文件今后不会被更新或传播。%n%n文件名为: \"%2\"%n到伙伴计算机的连接是:%n \"%3\"%n%n注意: 如果时间差别接近 60 分钟的倍数,那么有可能是在文件被创建或更新的伙伴计算机上,其最初设置计算机时间时的时区设置不正确。请检查在伙伴计算机上的时区和系统时间设置是否正确。 |
The File Replication Service is unable to replicate from a partner computerbecause the event time associated with the file to be replicated is too farinto the future. It is %1 minutes greater than the current time. This canhappen if the system time on the partner computer was set incorrectly whenthe file was created or updated. To preserve the integrity of the replicaset this file update will not be performed or propagated further.%n%nThe file name is: \"%2\"%nThe connection to the partner computer is:%n \"%3\"%n%nNote: If this time difference is close to a multiple of 60 minutes then itis likely that this file may have been created or updated on the partnercomputer while the computer was set to the incorrect time zone when itscomputer time was initially set. Check that the timezone and time arecorrectly set on the partner computer. |
0xC00034EE | 文件复制服务不能为副本集 %1 打开客户端指定的阶段目录。阶段目录使用的路径是,%n \"%2\"%n客户端为此副本集指定的根路径是:%n \"%3\"%n服务不能在此副本集上启动复制。要检查的可能错误是:%n -- 无效的阶段路径,%n -- 丢失的目录,%n -- 丢失的磁盘卷,%n -- 在不支持 ACL 的卷上的文件系统,%n -- 在有其他应用程序的阶段目录上的共享冲突。%n%n更正此错误,服务将稍后 自动重新启动复制。 |
The File Replication Service is unable to open the customer designatedstaging directory for replica set %1. The path used for the stagingdirectory is,%n \"%2\"%nThe customer designated root path for this replica set is:%n \"%3\"%nThe service is unable to start replication on this replica set. Among thepossible errors to check are:%n -- an invalid staging path,%n -- a missing directory,%n -- a missing disk volume,%n -- a file system on the volume that does not support ACLs,%n -- a sharing conflict on the staging directory with some other application.%n%nCorrect the problem and the service will attempt to restart replicationautomatically at a later time. |
0xC00034EF | 文件复制服务不能为副本集 %1 在客户指定的复制树目录下打开(或创建)安装前的目录。为此安装前的目录使用的路径是,%n \"%2\"%n客户为此副本集指定的根路径是:%n \"%3\"%n服务不能在此副本集上启动复制。要检查的可能错误是:%n -- 无效的根路径,%n -- 丢失的目录,%n -- 丢失的磁盘卷,%n -- 在不支持 NTFS 5.0 的卷上的文件系统,%n -- 在有其他应用程序的安装前的目录钟的共享冲突。%n%n更正此错误,服务将稍后 自动重新启动复制。 |
The File Replication Service is unable to open (or create) the pre-installdirectory under the customer designated replica tree directory forreplica set %1. The path used for the pre-installdirectory is,%n \"%2\"%nThe customer designated root path for this replica set is:%n \"%3\"%nThe service is unable to start replication on this replica set. Among thepossible errors to check are:%n -- an invalid root path,%n -- a missing directory,%n -- a missing disk volume,%n -- a file system on the volume that does not support NTFS 5.0%n -- a sharing conflict on the pre-install directory with some other application.%n%nCorrect the problem and the service will attempt to restart replicationautomatically at a later time. |
0xC00034F0 | 文件复制服务不能将此计算机添加到下列副本集:%n \"%1\"%n%n可能的原因很多,例如:%n -- 无效的根路径,%n -- 丢失的路径,%n -- 丢失的磁盘卷,%n -- 卷上的文件系统不支持 NTFS 5.0%n%n下面的信息可能有助于解决此问题:%n计算机 DNS 名称是 \"%2\"%n副本集成员名称是 \"%3\"%n副本集根路径是 \"%4\"%n复制分段目录路径是 \"%5\"%n复制工作目录路径是 \"%6\"%nWindows 错误状态码是 %7%nFRS 错误状态码是 %8%n%n其他事件日志消息可能也有助于解决此问题。纠正此问题,稍后服务会自动重新启动复制。 |
The File Replication Service is unable to add this computer to the followingreplica set:%n \"%1\"%n%nThis could be caused by a number of problems such as:%n -- an invalid root path,%n -- a missing directory,%n -- a missing disk volume,%n -- a file system on the volume that does not support NTFS 5.0%n%nThe information below may help to resolve the problem:%nComputer DNS name is \"%2\"%nReplica set member name is \"%3\"%nReplica set root path is \"%4\"%nReplica staging directory path is \"%5\"%nReplica working directory path is \"%6\"%nWindows error status code is %7%nFRS error status code is %8%n%nOther event log messages may also help determine the problem. Correct theproblem and the service will attempt to restart replication automatically ata later time. |
0xC00034F3 | 文件复制服务处于错误状态。文件将不能复制到或复制自计算机上的一个或多个副本集,直到执行了下面的恢复操作:%n%n 恢复步骤:%n%n [1] 如果你停止并重新启动 FRS 服务,错误状态可以自动清除。这可以通过在命令行窗口执行下列命令来完成:%n%n net stop ntfrs%n net start ntfrs%n%n如果清除问题失败,则执行如下操作。%n%n [2] 对于不主持任何 DFS 备用或启用了复制的副本集的 Active Directory 域控制器:%n%n如果域中至少有一个其他域控制器,则从备份还原此 DC 的\"系统状态\"(使用 ntbackup 或其他备份-还原工具),并使其成为非授权的。%n%n如果域中没有其他域控制器,则从备份还原此 DC 的\"系统状态\"(使用 ntbackup 或其他备份-还原工具),并选择\"高级\"选项,将 sysvols 标记为主要的。%n%n如果域中有其他域控制器,但是所有这些域控制器都有此事件日志消息,则将它们中间的一个还原为主要的(来自主要的数据文件将被复制到各处),其他的则作为非授权的。%n%n%n [3] 对于主持 DFS 备用或启用了复制的副本集的 Active Directory 域控制器:%n%n (3-a) 如果此 DC 上的 Dfs 备用没有任何其他的复制伙伴,则将 Dfs 共享中的文件复制到一个安全的位置。%n (3-b) 如果此服务器是域中唯一的 Active Directory 域控制器,则在执行 (3-c) 之前,确认服务器没有任何入站或出站连接到其他服务器,这些服务器以前是域的控制器,但是现在离线并且也将不再重新在线或没有降级就被重新安装。要删除连接,使用\"站点和服务\"管理单元,查找%n站点-站点名称-服务器-服务器名称-NTDS 设置-连接。%n (3-c) 从备份还原此 DC 的\"系统状态\"(使用 ntbackup 或其他备份-还原工具),并使其成为非授权的。%n (3-d) 在 sysvol 共享发布后,从上面的步骤 (3-a) 复制数据到原始位置。%n%n%n [4] 对其他 Windows 2000 服务器:%n%n (4-a) 如果此服务器主持的 DFS 备用或其他副本集没有任何其他复制伙伴,则将它的共享或副本复制集树根中的数据复制到一个安全位置。%n (4-b) net stop ntfrs%n (4-c) rd /s /q %1%n (4-d) net start ntfrs%n (4-e) 在安装了服务后(最好等待 5 分钟,以保证安全),将上面的步骤 (4-a) 中的数据复制到原始位置。%n%n注意: 如果此错误信息出现在一个特定副本集的所有成员的事件日志中,则只在其中的一个成员上执行上面的步骤 (4-a)和 (4-e)。 |
The File Replication Service is in an error state. Files will not replicateto or from one or all of the replica sets on his computer until thefollowing recovery steps are performed:%n%n Recovery Steps:%n%n [1] The error state may clear itself if you stop and restart the FRS service.This can be done by performing the following in a command window:%n%n net stop ntfrs%n net start ntfrs%n%nIf this fails to clear up the problem then proceed as follows.%n%n [2] For Active Directory Domain Controllers that DO NOT host any DFSalternates or other replica sets with replication enabled:%n%nIf there is at least one other Domain Controller in this domain thenrestore the \"system state\" of this DC from backup (using ntbackup or otherbackup-restore utility) and make it non-authoritative.%n%nIf there are NO other Domain Controllers in this domain then restorethe \"system state\" of this DC from backup (using ntbackup or otherbackup-restore utility) and choose the Advanced option which marksthe sysvols as primary.%n%nIf there are other Domain Controllers in this domain but ALL ofthem have this event log message then restore one of them as primary(data files from primary will replicate everywhere) and the others asnon-authoritative.%n%n%n [3] For Active Directory Domain Controllers that host DFS alternatesor other replica sets with replication enabled:%n%n (3-a) If the Dfs alternates on this DC do not have any other replicationpartners then copy the data under that Dfs share to a safe location.%n (3-b) If this server is the only Active Directory Domain Controller for thisdomain then, before going to (3-c), make sure this server does not have anyinbound or outbound connections to other servers that were formerly DomainControllers for this domain but are now off the net (and will never becoming back online) or have been fresh installed without being demoted.To delete connections use the Sites and Services snapin and look for%nSites-NAME_OF_SITE-Servers-NAME_OF_SERVER-NTDS Settings-CONNECTIONS.%n (3-c) Restore the \"system state\" of this DC from backup (using ntbackupor other backup-restore utility) and make it non-authoritative.%n (3-d) Copy the data from step (3-a) above to the original locationafter the sysvol share is published.%n%n%n [4] For other Windows 2000 servers:%n%n (4-a) If any of the DFS alternates or other replica sets hosted bythis server do not have any other replication partners then copy thedata under its share or replica tree root to a safe location.%n (4-b) net stop ntfrs%n (4-c) rd /s /q %1%n (4-d) net start ntfrs%n (4-e) Copy the data from step (4-a) above to the original location afterthe service has initialized (5 minutes is a safe waiting time).%n%nNote: If this error message is in the eventlog of all the members of aparticular replica set then perform steps (4-a) and (4-e) above on onlyone of the members. |
0xC00034F4 | 文件复制服务已经检测到尝试更改如下副本集的根路径:%n \"%1\"%n%n这是不允许的。要执行此操作,你必须从副本集中删除此成员,并用新的根路径重新添加此成员。%n%n可能这只是一个暂时问题,由于 Active Directory复制延迟,与更新 FRS 配置对象相关。如果文件复制在适当的等待时间以后还是不能进行(等待时间可以是几个小时,如果要求进行跨站点的 Active Directory复制),你必须从副本集中删除并重新添加此成员。%n%n与此事件相关的信息如下:%n计算机 DNS 名称为 \"%2\"%n副本集成员名称为 \"%3\"%n当前副本集根路径为 \"%4\"%n希望的新副本集根路径为 \"%5\"%n副本分段目录路径为 \"%6\" |
The File Replication Service has detected what appears to be an attemptto change the root path for the following replica set:%n \"%1\"%n%nThis is not allowed. To perform this operation you must remove this memberfrom the replica set and add the member back with the new root path.%n%nIt is possible that this is a transient error due to Active Directoryreplication delays associated with updating FRS configuration objects. Iffile replication does not take place after an appropriate waiting time,which could be several hours if cross site Active Directory replicationis required, you must delete and re-add this member to the replica set.%n%nInformation related to this event is shown below:%nComputer DNS name is \"%2\"%nReplica set member name is \"%3\"%nThe current Replica set root path is \"%4\"%nThe desired new Replica set root path is \"%5\"%nReplica staging directory path is \"%6\" |
0xC00034F5 | 文件复制服务在此计算机 \"%6\" 和计算机 \"%1\" 之间检测到一个重复的连接对象。%n这在如下副本集中检测到:%n \"%2\"%n%n这是不允许的。在重复的连接对象被删除之前,不会执行复制。%n%n这可能只是暂时现象,由于与更新 FRS 配置对象相关的 Active Directory复制延迟引起。如果在一段时间(如果要求跨站点的 Active Directory 复制,这可能要几个小时)后文件复制依然不能执行,你必须手动删除重复的连接对象,步骤如下:%n%n [1] 启动 “Active Directory 站点和服务”管理单元。%n [2] 单击 \"%3, %4, %5, %6, %7\"。%n [3] 在站点 \"%8\" 中从 \"%1\" 查找重复连接。%n [4] 删除所有连接,只留下一个。 |
The File Replication Service has detected a duplicate connection object betweenthis computer \"%6\" and a computer named \"%1\".%nThis was detected for the following replica set:%n \"%2\"%n%nThis is not allowed and replication will not occur between these twocomputers until the duplicate connection objects are removed.%n%nIt is possible that this is a transient error due to Active Directoryreplication delays associated with updating FRS configuration objects. Iffile replication does not take place after an appropriate waiting time,which could be several hours if cross site Active Directory replicationis required, you must manually delete the duplicate connection objects byfollowing the steps below:%n%n [1] Start the Active Directory Sites and Services Snapin.%n [2] Click on \"%3, %4, %5, %6, %7\".%n [3] Look for duplicate connections from \"%1\" in site \"%8\".%n [4] Delete all but one of the connections. |
0xC00034F6 | 文件复制服务在此计算机 \"%7\" 和计算机 \"%1\" 之间检测到一个重复的连接对象。%n这在如下副本集中检测到:%n \"%2\"%n%n这是不允许的。在重复的连接对象被删除之前,不会执行复制。%n%n这可能只是暂时现象,由于与更新 FRS 配置对象相关的 Active Directory复制延迟引起。如果在一段时间(如果要求跨站点的 Active Directory 复制,这可能要几个小时)后文件复制依然不能执行,你必须手动删除重复的连接对象,步骤如下:%n%n [1] 启动“Active Directory 用户和计算机”管理单元。%n [2] 单击“查看”按钮,“高级功能”,显示系统节点。%n [3] 单击 \"%3, %4, %5\"。%n [4] 在 \"%5\" 下你将会看到一个或多个 DFS 相关的副本集对象。在副本集\"%2\" 的子树下查找 FRS 成员对象 \"%6\"。%n [5] 在 \"%6\" 下从 \"%1\" 中查找重复连接。%n [6] 删除所有连接,只留下一个。 |
The File Replication Service has detected a duplicate connection object betweenthis computer \"%7\" and a computer named \"%1\".%nThis was detected for the following replica set:%n \"%2\"%n%nThis is not allowed and replication will not occur between these twocomputers until the duplicate connection objects are removed.%n%nIt is possible that this is a transient error due to Active Directoryreplication delays associated with updating FRS configuration objects. Iffile replication does not take place after an appropriate waiting time,which could be several hours if cross site Active Directory replicationis required, you must manually delete the duplicate connection objects byfollowing the steps below:%n%n [1] Start the Active Directory Users and Computers Snapin.%n [2] Click the view button and advanced features to display the system node.%n [3] Click on \"%3, %4, %5\".%n [4] Under \"%5\" you will see one or more DFS related replica set objects.Look for the FRS member object \"%6\" under the subtree for replica set \"%2\".%n [5] Under \"%6\" look for duplicate connections from \"%1\".%n [6] Delete all but one of the connections. |
0xC00034F7 | 文件复制服务检测到复制根路径从 \"%2\" 变成了 \"%3\"。如果这是有意做的,则需在新根路径下创建一个名为 NTFRS_CMD_FILE_MOVE_ROOT 的文件。%n在以下复制集检测到此更改%n \"%1\"%n%n更改复制根是一个由创建 NTFRS_CMD_FILE_MOVE_ROOT 文件引发的两部过程。%n%n [1] 第一次轮询将在 %4 分钟内执行,此计算机将被从复制集中删除。%n [2] 在紧接着删除的轮询里,此计算机将以新根路经被重新添加到复制集。此重新添加将引发复制集的整树同步。同步的结果是所有文件将在同一位置。这些文件可能被或没被从老位置删除,这要根据是否需要它们而定。 |
The File Replication Service has detected that the replica root path has changedfrom \"%2\" to \"%3\". If this is an intentional move then a file with the nameNTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.%nThis was detected for the following replica set:%n \"%1\"%n%nChanging the replica root path is a two step process which is triggered bythe creation of the NTFRS_CMD_FILE_MOVE_ROOT file.%n%n [1] At the first poll which will occur in %4 minutes this computer will bedeleted from the replica set.%n [2] At the poll following the deletion this computer will be re-added to thereplica set with the new root path. This re-addition will trigger a full treesync for the replica set. At the end of the sync all the files will be at the newlocation. The files may or may not be deleted from the old location depending on whetherthey are needed or not. |
0xC00034F9 | 文件复制服务检测到复制集 \"%1\" 在 JRNL_WRAP_ERROR。%n%n 复制集名称是 : \"%1\"%n 复制根目录是 : \"%2\"%n 复制根卷是 : \"%3\"%n当它尝试从 NTFS USN 日志中读取的记录找不到时,复制集达到 JRNL_WRAP_ERROR。这可能是由于下列原因之一造成。%n%n [1] 卷 \"%3\" 没有格式化。%n [2] 在卷 \"%3\" 上的 NTFS USN 日志被删除。%n [3]在卷 \"%3\" 上的 NTFS USN 日志被截断。Chkdsk 会截断日志,如果它在日志的结尾发现了损坏的项目。%n [4] 文件复制服务在此计算机上很久没有运行了。%n [5] 文件复制服务跟不上 \"%3\" 上的磁盘 IO 速度。%n%n 下面的恢复步骤将被执行以自动从此错误状态中恢复。%n [1] 第一次轮询将在 %4 分钟内执行,此计算机将从复制集中删除。%n [2] 在删除后的轮询中,此计算机会被重新添加到复制集中。此重新添加将会为此复制集触发一个树的完全同步。 |
The File Replication Service has detected that the replica set \"%1\" is in JRNL_WRAP_ERROR.%n%n Replica set name is : \"%1\"%n Replica root path is : \"%2\"%n Replica root volume is : \"%3\"%nA Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.This can occur because of one of the following reasons.%n%n [1] Volume \"%3\" has been formatted.%n [2] The NTFS USN journal on volume \"%3\" has been deleted.%n [3] The NTFS USN journal on volume \"%3\" has been truncated. Chkdsk can truncatethe journal if it finds corrupt entries at the end of the journal.%n [4] File Replication Service was not running on this computer for a long time.%n [5] File Replication Service could not keep up with the rate of Disk IO activity on \"%3\".%n%n Following recovery steps will be taken to automatically recover from this error state.%n [1] At the first poll which will occur in %4 minutes this computer will bedeleted from the replica set.%n [2] At the poll following the deletion this computer will be re-added to thereplica set. The re-addition will trigger a full tree sync for the replica set. |
0xC00036B0 | QoS: 数据包计划程序通过通用数据包分类器 (msgpc.sys) 注册失败。 |
QoS: The Packet Scheduler failed to register with the Generic Packet Classifier (msgpc.sys). |
0xC00036B1 | QoS: 数据包计划程序不能为初始化分配要求的资源。 |
QoS: The Packet Scheduler was unable to allocate required resources for initialization. |
0xC00036B2 | QoS: 数据包计划程序用 NDIS 注册为一个协议失败。 |
QoS: The Packet Scheduler failed to register as a protocol with NDIS. |
0xC00036B3 | Qos: 数据包计划程序未能作为小型端口用 NDIS 注册。 |
QoS: The Packet Scheduler failed to register as a miniport with NDIS. |
0xC0003715 | QoS [适配器 %2]:%n网络适配器驱动程序查询 OID_GEN_MAXIMUM_FRAME_SIZE 失败。 |
QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE. |
0xC0003716 | QoS [适配器 %2]:%n网络适配器驱动程序查询 OID_GEN_MAXIMUM_TOTAL_SIZE 失败。 |
QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE. |
0xC0003717 | QoS [适配器 %2]:%n网络适配器驱动程序查询 OID_GEN_LINK_SPEED 失败。 |
QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_LINK_SPEED. |
0xC0003718 | QoS [适配器 %2]:%n数据包计划程序绑定到网络适配器的小型端口驱动程序失败。 |
QoS [Adapter %2]:%nThe Packet Scheduler failed to bind to the network adapter's miniport driver. |
0xC0003719 | QoS [适配器 %2]:%n注册表中的键 UpperBindings 丢失。 |
QoS [Adapter %2]:%nThe UpperBindings key is missing from the registry. |
0xC000371A | QoS [适配器 %2]:%n数据包计划程序不能用 NDISWAN 调用管理器注册。 |
QoS [Adapter %2]:%nThe Packet Scheduler was unable to register with the NDISWAN Call Manager. |
0xC000371B | QoS [适配器 %2]:%n数据包计划程序不能用 NDIS 初始化虚拟小型端口。 |
QoS [Adapter %2]:%nThe Packet Scheduler could not initialize the virtual miniport with NDIS. |
0xC000371C | QoS [适配器 %2]:%n数据包计划程序不能从 NDIS 获取网络适配器的友好名称。 |
QoS [Adapter %2]:%nThe Packet Scheduler could not obtain the network adapter's friendly name from NDIS. |
0xC000371E | QoS [适配器 %2]:%n由于非分页缓冲池内存不足,不能初始化。 |
QoS [Adapter %2]:%nCould not initialize due to insufficient nonpaged pool memory. |
0xC0003720 | QoS [适配器 %2]:%n不能分配非分页缓冲池内存以保存网络地址。 |
QoS [Adapter %2]:%nCould not allocate non-paged pool memory for storing network addresses. |
0xC00037DC | 在服务器 %3 上找到一个额外的 ExitPoint %2 |
An extra ExitPoint %2 was found at server %3 |
0xC00037DD | ExitPoint %2 不在服务器 %3 上 |
The ExitPoint %2 was missing at server %3 |
0xC00037DE | 卷 %2 不在服务器 %3 上 |
The Volume %2 was missing at server %3 |
0xC00037DF | 在服务器 %3 上找到额外的卷 %2 |
The extra Volume %2 was found at server %3 |
0xC00037E0 | 成功地从服务器 %3 上删除c额外的 ExitPoint %2 |
The extra ExitPoint %2 was deleted successfully from the server %3 |
0xC00037E1 | 无法从服务器 %3 上删除额外的 ExitPoint %2 |
Unable to delete the extra ExitPoint %2 at the server %3 |
0xC00037E2 | 已成功地将丢失了的 ExitPoint %2 创建在服务器 %3 上 |
The missing ExitPoint %2 was created at the server %3 successfully |
0xC00037E3 | 无法在服务器 %3上创建丢失了的 ExitPoint %2 |
Unable to create the missing Exit Point %2 at the server %3 |
0xC00037E4 | 成功地在服务器 %3 上创建了丢失了的卷 %2 知识 |
Successfully created the missing volume %2 knowledge at the server %3 |
0xC00037E5 | 无法在服务器 %3 上创建丢失了的卷 %2 信息 |
Unable to create the missing Volume %2 info at server %3 |
0xC00037E6 | 从服务器 %3 上删除了额外的卷 %2 信息 |
The extra Volume %2 info was deleted at server %3 |
0xC00037E7 | 未从服务器 %3 上删除额外的卷 %2 信息 |
The extra Volume %2 info was not deleted at server %3 |
0xC00037E8 | 因为没有 DC %2,所以无法验证卷知识。 |
Since the DC %2 was unavailable could not verify volumes knowledge. |
0xC00037E9 | 检测出服务器 %3 上的卷 %2 知识不一致 |
Detected Knowledge inconsistency with the volume %2 at server %3 |
0xC00037EA | 本地前缀 %2 在远程服务器 %4 上以 %3 表示 |
The local Prefix %2 was represented as %3 at remote server %4 |
0xC00037EB | 远程前缀 %3 在远程服务器 %4 上更正成 %2 |
The remote Prefix %3 was corrected to %2 at remote server %4 |
0xC00037EC | 远程前缀 %3 在远程服务器 %4 上并未更正成 %2 |
The remote Prefix %3 was NOT corrected to %2 at remote server %4 |
0xC00037ED | 机器 %2 已没有与域连接。请将机器重新加入到这个域。 |
The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain. |
0xC00038A7 | Dfs 不能为目录 %2 中的目录 %1 创建重解析点。返回码在记录数据中。 |
Dfs could not create reparse point for directory %1 under directory %2. The return code is in the record data. |
0xC00038A8 | 映射到 %2 的共享 %1 不支持重解析点。请升级文件系统,然后再试一次。 |
Share %1 mapped to %2 does not support reparse points. Upgrade Filesystem and retry. |
0xC00038A9 | 映射到 %2 目录的共享 %1 与一个现有根重叠。将不会创建此 DFS 根。 |
Share %1 mapped to %2 directory overlaps an existing root. The DFS Root will not be created. |
0xC00038AD | 根 %1 错误太多。在此根上将不会记录更多的日志事件。 |
Root %1 has too many errors. No further eventlogs will be logged on this root. |
0xC00038AE | DFS 不能初始化 winsock 库。返回码在记录数据中。 |
DFS could not initialize winsock library. The return code is in the record data. |
0xC00038AF | DFS 不能初始化安全库。返回码在记录数据中。 |
DFS could not initialize security library. The return code is in the record data. |
0xC00038B0 | DFS 不能创建 DFS 支持线程。返回码在记录数据中。 |
DFS could not create DFS support thread. The return code is in the record data. |
0xC00038B1 | DFS 不能初始化 IP 站点缓存。返回码在记录数据中。 |
DFS could not initialize IP site cache. The return code is in the record data. |
0xC00038B2 | DFS 不能同步所有 DFS 根。返回码在记录数据中。 |
DFS could not synchronize all DFS roots. The return code is in the record data. |
0xC00038B3 | DFS 不能创建事件句柄。返回码在记录数据中。 |
DFS could not create event handle. The return code is in the record data. |
0xC00038B4 | DFS 不能获得要求的计算机信息。返回码在记录数据中。 |
DFS could not get required computer information. The return code is in the record data. |
0xC00038B5 | DFS 不能获得要求的群集信息。返回码在记录数据中。 |
DFS could not get required cluster information. The return code is in the record data. |
0xC00038B6 | DFS 不能获得要求的 DC 信息。返回码在记录数据中。 |
DFS could not get required DC information. The return code is in the record data. |
0xC00038B7 | DFS 不能初始化前缀表。返回码在记录数据中。 |
DFS could not initialize prefix table. The return code is in the record data. |
0xC00038B8 | DFS 不能初始化 DFS 命名空间。返回码在记录数据中。 |
DFS could not initialize DFS namespace.The return code is in the record data. |
0xC00038B9 | DFS 不能注册 DFS 命名空间。返回码在记录数据中。 |
DFS could not Register DFS Namespaces. The return code is in the record data. |
0xC00038BA | DFS 不能初始化用户/内核通信数据包。返回码在记录数据中。 |
DFS could not initialize User/kernel communication package. The return code is in the record data. |
0xC00038BB | DFS 不能联系任何 DC 以初始化域 DFS 操作。将定期重试此操作。 |
DFS could not contact any DC for Domain DFS operations. This operation will be retried periodically. |
0xC00038BC | DFS 不能初始化站点支持表。返回码在记录数据中。 |
DFS could not initialize site support table. The return code is in the record data. |
0xC00038C2 | DFS 不能从 Active Directory 访问它的私有数据。请手动检查网络是否连接好,安全访问,和/或在 Active Directory 中的DFS 信息的一致性。此错误在根 %1 上发生。 |
DFS could not access its private data from the Active Directory. Please manually checknetwork connectivity, security access, and/or consistency of DFS informationin the Active Directory. This error occurred on root %1. |
0xC00038C7 | 在 Standard Server 产品包中 DFS 不支持多重根。请清理根,或升级。 |
DFS does not support multiple roots on Standard server SKU. Please cleanup the roots or upgrade. |
0xC00038CB | DFS 无法重新同步根 %1 的这个根目标。这可能导致 DFS 命名空间的部分无法访问。请检查共享 %1 是否包含为 DFS 链接创建的所有链接目录。如果这个共享上存在阻止创建链接的目录,就可能发生这个错误。 |
DFS was unable to resynchronize this root target for root: %1. This may lead to inaccessability of portions of the DFS namespace. Please verify the share %1 has all the link directories created for the DFS links. This error may occur if there are directories on this share that may be preventing creation of links. |
0xC00038CC | 链接移动操作过程中,DFS 无法删除根 %1 的链接 %2。 |
DFS was unable to delete link: %2 for root: %1 during a link move operation. |
0xC00038CF | 以下分布式文件系统(DFS)文件夹的文件夹目标列表已损坏。DFS 文件夹: %1 |
The list of folder targets for the following Distributed File System (DFS) folder is corrupt. DFS folder: %1 |
0xC00038D0 | 已创建包含其他 DFS 文件夹并且具有文件夹目标的分布式文件系统(DFS)文件夹。如果不同命名空间服务器上的两个管理员大约同时创建冲突的文件夹结构,则可能会发生这种情况。命名空间: %1 DFS 文件夹 1: %2 DFS 文件夹 2: %3 |
A Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder 1: %2 DFS folder 2: %3 |
0xC00038D1 | 已创建包含其他 DFS 文件夹并且具有文件夹目标的分布式文件系统(DFS)文件夹。如果不同命名空间服务器上的两个管理员大约同时创建冲突的文件夹结构,则可能会发生这种情况。命名空间: %1 DFS 文件夹: %2 |
A Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder: %2 |
0xC00038D3 | 创建的分布式文件系统(DFS)文件夹具有冲突的描述。如果不同命名空间服务器上的两个管理员大约同时创建冲突的文件夹结构,则可能会发生这种情况。命名空间: %1 DFS 文件夹路径: %2 DFS 文件夹 1: %3 DFS 文件夹 2: %4 |
A Distributed File System (DFS) folder was created with conflicting descriptions. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder path: %2 DFS folder 1: %3 DFS folder 2: %4 |
0xC00038D4 | DFS 命名空间服务无法初始化该域控制器上的受信任域信息,但该服务将定期重试该操作。返回代码位于记录数据中。 |
The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically retry the operation. The return code is in the record data. |
0xC00038D6 | DFS 命名空间服务无法初始化该域控制器上的跨林信任信息,但该服务将定期重试该操作。返回代码位于记录数据中。 |
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data. |
0xC0003908 | 桥: 桥不能初始化,因为桥用 NDIS 作为协议注册失败。 |
Bridge: The bridge could not be initialized because the bridge failed to register as a protocol with NDIS. |
0xC0003909 | 桥: 桥不能初始化,因为桥的小型端口设备名称在注册表中找不到。 |
Bridge: The bridge could not be initialized because the bridge's miniport device name is missing from the registry. |
0xC000390A | 桥: 桥不能初始化,因为桥用 NDIS 作为小型端口注册失败。 |
Bridge: The bridge could not be initialized because the bridge failed to register as a miniport with NDIS. |
0xC000390B | 桥: 桥不能初始化,桥创建一个设备对象失败。 |
Bridge: The bridge could not be initialized because the bridge failed to create a device object. |
0xC000390C | 桥: 桥不能初始化,因为桥为它自身判断一个 MAC 地址失败。 |
Bridge: The bridge could not be initialized because the bridge failed to determine a MAC address for itself. |
0xC000390D | 桥: 桥未能创建虚拟小型端口。 |
Bridge: The bridge failed to create its virtual miniport. |
0xC000390E | 桥: 桥不能初始化它的虚拟小型端口,因为 Ethernet 不是以支持的媒体提供的。 |
Bridge: The bridge could not initialize its miniport because Ethernet was not offered as a supported medium. |
0xC000390F | 桥: 桥不能初始化,因为它没有创建系统线程。 |
Bridge: The bridge could not initialize because it failed to create a system thread. |
0xC0003910 | 桥: 桥不能初始化,因为它没有参考它的系统线程。 |
Bridge: The bridge could not initialize because it failed to reference its system thread. |
0xC0003911 | 桥: 桥不能初始化,因为它没有创建数据包池。 |
Bridge: The bridge could not initialize because it failed to create a packet pool. |
0xC0003912 | 桥: 桥不能初始化,因为它没有创建缓冲区池。 |
Bridge: The bridge could not initialize because it failed to create a buffer pool. |
0xC0003913 | 桥: 桥不能初始化,因为它没有分配内存。 |
Bridge: The bridge could not initialize because it failed to allocate memory. |
0xC000396C | 桥 [适配器 %2]:%n桥不能决定网络适配器的链接速度。此网络适配器将不被使用。 |
Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's link speed. The network adapter will not be used. |
0xC000396D | 桥 [适配器 %2]:%n桥不能决定网络适配器的 MAC 地址。此网络适配器将不被使用。 |
Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's MAC address. The network adapter will not be used. |
0xC000396E | 桥 [适配器 %2]:%n桥不能更改网络适配器的数据包筛选器。此网络适配器将不会正确工作。 |
Bridge [Adapter %2]:%nThe bridge could not modify the network adapter's packet filter. The network adapter will not function correctly. |
0xC000396F | 桥 [适配器 %2]:%n桥不能检索网络适配器的描述字符串。此网络适配器将不被使用。 |
Bridge [Adapter %2]:%nThe bridge could not retrieve the network adapter's description string. The network adapter will not be used. |
0xC0003970 | 桥 [适配器 %2]:%n桥未能绑定网络适配器。此网络适配器将不被使用。 |
Bridge [Adapter %2]:%nThe bridge failed to bind to the network adapter. The network adapter will not be used. |
0xC0003E80 | WSK 提供程序忽略了传递到 WSK 套接字创建请求的 OwningThread 参数。当需要在 TDI 传输提供程序上创建套接字时,则会发生这种情况,这是因为 TDI 筛选器驱动程序已安装,或者因为存在客户端指定的 TDI 映射,该 TDI 映射与套接字创建请求中指定的 AddressFamily、socketType 和协议相匹配。 |
WSK provider has ignored the OwningThread parameter passed to a WSK socket creation request. This happens when the socket needs to be created over a TDI transport provider either because a TDI filter driver is installed or because a client-specified TDI mapping exists that matches the AddressFamily, socketType, and Protocol specified in the socket creation request. |
0xC000413C | 计算机 QoS 策略未能刷新。错误代码: %2。 |
Computer QoS policies failed to refresh. Error code: %2. |
0xC000413D | 用户 QoS 策略未能刷新。错误代码: %2。 |
User QoS policies failed to refresh. Error code: %2. |
0xC000413E | QoS 无法打开计算机级别的 QoS 策略根键。错误代码: %2。 |
QoS failed to open the computer-level root key for QoS policies. Error code: %2. |
0xC000413F | QoS 无法打开用户级别的 QoS 策略的根键。错误代码: %2。 |
QoS failed to open the user-level root key for QoS policies. Error code: %2. |
0xC0004140 | 计算机 QoS 策略超过允许的最大名称长度。有问题的策略列在计算机级别的 QoS 策略根键之下,索引为 %2。 |
A computer QoS policy exceeds the maximum allowed name length. The offending policy is listed under the computer-level QoS policy root key, with index %2. |
0xC0004141 | 用户 QoS 策略超过允许的最大名称长度。有问题的策略列在用户级别的 QoS 策略根键之下,索引为 %2。 |
A user QoS policy exceeds the maximum allowed name length. The offending policy is listed under the user-level QoS policy root key, with index %2. |
0xC0004142 | 计算机 QoS 策略的名称长度为零。有问题的策略列在计算机级别的 QoS 策略根键之下,索引为 %2。 |
A computer QoS policy has a zero length name. The offending policy is listed under the computer-level QoS policy root key, with index %2. |
0xC0004143 | 用户 QoS 策略具有零长度名称。有问题的策略列在用户级别的 QoS 策略根键之下,索引为 %2。 |
A user QoS policy has a zero length name. The offending policy is listed under the user-level QoS policy root key, with index %2. |
0xC0004144 | QoS 无法打开计算机 QoS 策略的注册表子项。该策略列在计算机级别的 QoS 策略根键之下,索引为 %2。 |
QoS failed to open the registry subkey for a computer QoS policy. The policy is listed under the computer-level QoS policy root key, with index %2. |
0xC0004145 | QoS 无法打开用户 QoS 策略的注册表子项。该策略列在用户级别的 QoS 策略根键之下,索引为 %2。 |
QoS failed to open the registry subkey for a user QoS policy. The policy is listed under the user-level QoS policy root key, with index %2. |
0xC0004146 | QoS 无法读取或验证计算机 QoS 策略“%3”的“%2”字段。 |
QoS failed to read or validate the \"%2\" field for the computer QoS policy \"%3\". |
0xC0004147 | QoS 无法读取或验证用户 QoS 策略“%3”的“%2”字段。 |
QoS failed to read or validate the \"%2\" field for the user QoS policy \"%3\". |
0xC0004148 | QoS 无法读取或设置入站 TCP 吞吐量级别,错误代码:“%2”。 |
QoS failed to read or set inbound TCP throughput level, error code: \"%2\". |
0xC0004149 | QoS 无法读取或设置 DSCP 标记覆盖设置,错误代码:“%2”。 |
QoS failed to read or set the DSCP marking override setting, error code: \"%2\". |