| File name: | scecli.dll.mui |
| Size: | 14848 byte |
| MD5: | f7ad11110cbef193f4bbc99961b2d625 |
| SHA1: | 4f4b1f17e37cc898bb87a3e0fd496dd2c0a4492e |
| SHA256: | 816be16cf3e30610b49383fe143fb15b1f4fc42b315e6f5872bb1c03c626fa3d |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Chinese (Simplified) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.
| id | Chinese (Simplified) | English |
|---|---|---|
| 7361 | 正在加密 %s | Securing %s |
| 7362 | 正在创建 %s | Creating %s |
| 7501 | 将安全配置复制到安全模板目录和修复目录的错误 %d。 | Error %d to copy security configuration to the security templates directory and the repair directory. |
| 7502 | 错误 %d 发生在将系统安全快点打印到 %s 的时候。详细信息，请参阅日志文件 %s。 | Error %d to snapshot system security to %s. See log file %s for detail info. |
| 7503 | 错误 %d 发生在加载 DLL %s 的时候。 | Error %d to load DLL %s. |
| 7504 | 错误 %d 发生在获取 %s 的过程地址的时候。 | Error %d to get procedure address of %s. |
| 7505 | 获取符号用户时的错误 0x%x。 | Error 0x%x to get token user. |
| 7506 | 由于上一个GPO 错误，GPO %s 没有被处理。 | GPO %s is not processed due to previous GPO error. |
| 7507 | 无法访问模板。错误代码 = %d。 %s。 |
Cannot access the template. Error code = %d. %s. |
| 7508 | GPO %s 中没有定义模板。 | No template is defined in GPO %s. |
| 7509 | 制作 %s 的本地副本。 | Make a local copy of %s. |
| 7510 | 处理 GP 模板 %s。 | Process GP template %s. |
| 7511 | 0x%x : %s 可以在 https://support.microsoft.com 找到此问题的高级帮助。请查询 "troubleshooting 1202 events"。 |
0x%x : %s Advanced help for this problem is available on https://support.microsoft.com. Query for "troubleshooting 1202 events". |
| 7512 | 定义的 EFS 策略: 长度是 %d。 |
EFS policy defined : Length is %d. |
| 7513 | 在这个层次上没有定义 EFS 策略 |
No EFS policy is defined at this level |
| 7514 | 将 EFS 策略保存到临时项的错误=%d。 |
Error=%d to save EFS policy to a temp key. |
| 7515 | LSA 中的现有 EFS 策略(长度=%d) |
Existing EFS policy in LSA (Length=%d) |
| 7516 | 状态=%d 设置 EFS 策略(长度 %d) |
Status=%d to set EFS policy (Length %d) |
| 7517 | EFS 策略没有改变 |
EFS policy is not changed |
| 7518 | 无法打开 LSA 以设置 EFS 策略。错误=%d |
Cannot open LSA to set EFS policy. Error=%d |
| 7519 | 在传播中查询合并的 EFS 策略时发生错误 %d。 |
Error %d to query merged EFS policy in this propagation. |
| 7520 | 获取 DS 根目录名称的错误 %d。 | Error %d to get the DS root name. |
| 7521 | 打开和绑定到 DS 的错误 %d。 | Error %d to open and bind to DS. |
| 7522 | 保存策略更改到本地 GPO 数据库时出错 %d。 | Error %d to save policy change in the local GPO database. |
| 7523 | 将策略更改通知发送到策略引擎时出现了错误 %d。 | Error %d to send policy change notification to policy engine. |
| 7524 | 默认组策略对象 %s 已成功创建。 | Default Group Policy Object %s is successfully created. |
| 7525 | 错误 %d 发生于将默认模板复制到 %s 时。 | Error %d to copy the default template to %s. |
| 7526 | 错误 %d 发生于创建目录 %s 时。 | Error %d to create directory %s. |
| 7527 | 内存不足，无法处理此命令。 | Not enough memory to process this command. |
| 7528 | 为默认 GPO 获取文件系统路径时出错 0x%x。 | Error 0x%x to get file system path for default GPO. |
| 7529 | 获取计算机的角色信息(域控制器、服务器、专业)时出错 %d。 | Error %d to get the role (DC, server, professional) of the machine. |
| 7530 | 错误 %d，在打开 GPO %s 时。 | Error %d to open GPO %s. |
| 7531 | 错误 %d，在从 GPO %s 读取策略时。 | Error %d to read policies from GPO %s. |
| 7532 | 在打开数据库时出现错误 %d。 | Error %d to open database. |
| 7533 | 在为另一个线程创建变量时出现错误 %d。 | Error %d to create arguments for second thread. |
| 7534 | 创建线程的错误 %d。 | Error %d to create a thread. |
| 7535 | 系统安全策略和用户权限的快照已被保存。 | Snapshot of system security policy and user rights are saved. |
| 7536 | 快照系统安全策略和用户权限的错误 %d。 | Error %d to snapshot system security policy and user rights. |
| 7537 | 错误 %d 出现在用选项 %x 删除默认设置时。 | Error %d to remove default settings with option %x. |
| 7538 | 全新安装系统的默认安全设置 | Out of box default security settings |
| 7539 | 为域控制器更新的默认安全设置 | Default security settings updated for domain controllers |
| 7540 | 安全配置服务器(services.exe 中)尚未就绪。这可能在系统重新启动重。策略将在下次产生时再试。 | Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation. |
| 7541 | 安装后，在第一次重新启动时处理策略筛选改动 | Process policy filter changes in the first reboot after setup |
| 7542 | 在安装中 LSA 策略经过更改。 | LSA policy is changed in setup. |
| 7543 | 在安装中 SAM 策略经过更改。 | SAM policy is changed in setup. |
| 7544 | 通知策略服务器。 | Notify policy server. |
| 7545 | 这不是最后的 GPO : 域策略在 DC 上被忽略。 | This is not the last GPO : domain policy is ignored on DC. |
| 7546 | 这不是最后的 GPO。 | This is not the last GPO. |
| 7547 | 这是最后的 GPO : 域策略在 DC 上被忽略。 | This is the last GPO : domain policy is ignored on DC. |
| 7548 | 这是最后的 GPO。 | this is the last GPO. |
| 7549 | 策略产生在 winlogon 阻塞线程中被启用。为慢速任务创建另一个线程。 | Policy propagation is invoked in winlogon blocking thread. Create another thread for slow task. |
| 7550 | 策略服务器没有就绪，重试次数 #%d。 | Policy server is not ready, retry count #%d. |
| 7551 | 正在应用安全策略 | Applying security policy |
| 7552 | 正在将安全策略应用到系统。 | Applying security policy to the system. |
| 7553 | 0x%x : %s 有关此问题的高级帮助可以在 https://support.microsoft.com 找到。查询 "troubleshooting 1202 events"。 当在一个或多个组策略对象(GPO)中的用户帐户不能解析为一个 SID 时发生错误 0x534。导致此错误的原因可能是在用户权限或一个 GPO 的受限制的组分支中引用的用户帐户键入错误或已被删除。要解析此事件，请联系域的管理员，执行下列操作: 1. 识别不能解析为一个 SID 的帐户: 在命令行中，键入: FIND /I "Cannot find" %%SYSTEMROOT%%\Security\Logs\winlogon.log 在 FIND 的输出中，"Cannot find" 后面的字符串就是有问题的帐户名。 示例: Cannot find JohnDough。 在这种情况下，用户名 "JohnDough" 的 SID 不能确定。这通常是因为帐户已经被删除，被重命名，或拼写错误(例如，"JohnDoe")。 2. 用 RSoP 来识别特定的用户权限，受限制的组，和饱含有问题帐户的源 GPO: a. 开始 - 运行 - RSoP.msc b. 查看“计算机配置\Windows 设置\安全设置\本地策略\用户权限分配”和“计算机配置\Windows 设置\安全设置\本地策略\受限制的组”的结果，查找用红色的 X 标记的错误。 c. 对于任何用红色的 X 标记的用户权限或受限制的组，包含有问题的策略的相应 GPO 在标题为“源 GPO”的列中列出。注意产生错误的特定用户权限，受限制的组和包含的源 GPO。 3. 从组策略中删除不能解析的帐户 a. 开始 - 运行 - MMC.EXE b. 从“文件”菜单选择“添加/删除管理单元...” c. 从“添加/删除管理单元”对话框选择“添加...” d. 在“添加独立管理单元”对话框中选择“组策略对象编辑器”，然后单击“添加” e. 在“选择组策略对象”对话框中，单击“浏览”按钮 f. 在“浏览组策略对象”对话框中，选择“全部”选项卡 g. 对于在步骤 2 中识别出的每一个源 GPO，更正在步骤 2 中用红色的 X 标出的特定用户权限或受限制的组。这些用户权限或受限制的组可以通过删除或更正到在步骤 1 中识别出的有问题帐户的引用来进行更正。 |
0x%x : %s Advanced help for this problem is available on https://support.microsoft.com. Query for "troubleshooting 1202 events". Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions: 1. Identify accounts that could not be resolved to a SID: From the command prompt, type: FIND /I "Cannot find" %%SYSTEMROOT%%\Security\Logs\winlogon.log The string following "Cannot find" in the FIND output identifies the problem account names. Example: Cannot find JohnDough. In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe"). 2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts: a. Start - Run - RSoP.msc b. Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X. c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors. 3. Remove unresolved accounts from Group Policy a. Start - Run - MMC.EXE b. From the File menu select "Add/Remove Snap-in..." c. From the "Add/Remove Snap-in" dialog box select "Add..." d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add" e. In the "Select Group Policy Object" dialog box click the "Browse" button. f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1. |
| 7554 | 在提升系统安全性时发生错误代码 %d。请查看 %windir%\security\logs\scedcpro.log 中的详细信息。 | Error code %d occurs when promoting system security. Please see detail in %windir%\security\logs\scedcpro.log. |
| 7555 | 打开一些安全数据库(例如 %s) 时发生错误。 | Error opening some security database(s) such as %s. |
| 7556 | 0x%x : %s 此问题的高级帮助可以在 https://support.microsoft.com 找到。请查询 "troubleshooting 1202 events"。 错误 0x5B4 通常是由于应用程序使用下级 API 更改策略，而策略被锁定。 |
0x%x : %s Advanced help for this problem is available on https://support.microsoft.com. Query for "troubleshooting 1202 events". Error 0x5B4 is likely caused because applications change policy using down level APIs and the policy store is locked. |
| 7581 | 无法为本地用户组添加经过验证的用户和交互。用户可以手动进行添加。 | Cannot add Authenticated User and Interactive to local Users group. User may add them manually. |
| 7582 | 重新配置文件安全的错误 %d。 | Error %d to reconfigure file security. |
| 7583 | 无法为本地高级用户组添加交互。用户可以手动进行添加。 | Cannot add Interactive to local Power Users group. User may add it manually. |
| 7584 | 不能删除 GP 缓存。 | Cannot delete GP cache. |
| 7585 | 在策略传播前没有权限设置。可以忽略。 | No privileges set before policy propagation. Okay to ignore. |
| 7586 | 错误 %d 打开缓存的 GPO %s | Error %d opening cached GPO %s |
| 7588 | 记录 RSOP 数据时的错误。错误代码 %d。信息 %s。 | Error in logging RSOP data. Error Code %d. Information %s. |
| 7589 | 不能创建 GP 缓存。 | Cannot create GP cache. |
| 7590 | ----RSOP 计划数据记录成功。成功代码 %d。 | ----RSOP planning data logged successfully. Success Code %d. |
| 7591 | RSOP 诊断信息。错误代码 %d - 用于实例 %s。 | RSOP diagnosis information. Error Code %d - for instance %s. |
| 7592 | RSOP 诊断信息。64 位或 32 位密钥。错误代码 %d - %s。 | RSOP diagnosis information. 64-bit or 32-bit key. Error Code %d - %s. |
| 7593 | 正在清空 RSOP 数据库。错误代码 %d | Emptying RSOP database. Error Code %d |
| 7594 | RSOP 日志信息。错误代码 %d - %s。 | RSOP logging information. Error Code %d - %s. |
| 7595 | %s 是一个 NTFS 卷。 | %s is a NTFS volume. |
| 7596 | 根驱动器 %s 不是一个固定卷。根安全性没有被更改。 | Root drive %s is not a fixed volume. Root security is not changed. |
| 7597 | 错误 %d，为 %s 查询卷信息。根安全性没有被更改。 | Error %d to query volume information for %s. Root security is not changed. |
| 7598 | 卷 %s 不是一个 NTFS 卷。根安全性没有被更改。 | Volume %s is not a NTFS volume. Root security is not changed. |
| 7599 | 错误 %d，转换安全描述符字符串 %s。根安全性没有被更改。 | Error %d to convert security descriptor string %s. Root security is not changed. |
| 7600 | 在安全描述符字符串 %s 中定义了无效的安全性信息。根安全性没有被更改。 | Invalid security information is defined in security descriptor string %s. Root security is not changed. |
| 7601 | 错误 %d，查询 %s 的安全性。 | Error %d to query security of %s. |
| 7602 | %s 的安全性没有被更改，因为它不是 Windows 的默认设置。当前安全性是 %s。 | Security for %s is not changed because it is not the default set by Windows. The current security is %s. |
| 7603 | 卷 %s 的默认安全性较弱。Windows 正在加强根安全性，开始于 %s。 | Volume %s has weak default security. Windows is strengthening the root security, starting at %s. |
| 7604 | 错误 %d，从新的安全描述符查询 DACL 指针。根安全性没有被更改。 | Error %d to query DACL pointer from the new security descriptor. Root security is not changed. |
| 7605 | SetNamedSecurityInfo 返回 %d 在 %s，为 %s 上的设置安全。 | SetNamedSecurityInfo returns %d at %s for setting security on %s. |
| 7606 | 错误 %d 将根安全描述符字符串 %s 写入 %windir%\security emplates\setup security.inf。 | Error %d to write root security descriptor string %s to %windir%\security emplates\setup security.inf. |
| 7607 | 错误 %d，发生于分析 %s 的根安全描述符时。 | Error %d analyzing root security descriptor at %s. |
| 7610 | 错误 %d 发送控制标志 %x 给服务器。 | Error %d to send control flag %x over to server. |
| 7611 | 错误 %d 在提升时模拟客户端令牌。 | Error %d impersonating client token during promotion. |
| 7612 | 错误 %d 在提升时回复到自己。 | Error %d reverting to self during promotion. |
| 7620 | 错误 0x%x 获得令牌系统。 | Error 0x%x to get token system. |
| 7621 | 错误 %d，发生在完成安全备份到 %s 时。 | Error %d to complete the security backup to %s. |
| 7622 | 注册表项值 | Registry Values |
| 7650 | 安全 | Security |
| 7651 | EFS 恢复 | EFS recovery |
| 8200 | 用户帐户控制: 管理员批准模式中管理员的提升权限提示的行为 | User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode |
| 8201 | 用户帐户控制: 标准用户的提升提示行为 | User Account Control: Behavior of the elevation prompt for standard users |
| 8202 | 用户帐户控制: 检测应用程序安装并提示提升 | User Account Control: Detect application installations and prompt for elevation |
| 8203 | 用户帐户控制: 以管理员批准模式运行所有管理员 | User Account Control: Run all administrators in Admin Approval Mode |
| 8204 | 用户帐户控制: 将文件和注册表写入错误虚拟化到每用户位置 | User Account Control: Virtualize file and registry write failures to per-user locations |
| 8205 | 用户帐户控制: 只提升签名并验证的可执行文件 | User Account Control: Only elevate executables that are signed and validated |
| 8206 | 用户帐户控制: 提示提升时切换到安全桌面 | User Account Control: Switch to the secure desktop when prompting for elevation |
| 8207 | 用户帐户控制: 用于内置管理员帐户的管理员批准模式 | User Account Control: Admin Approval Mode for the Built-in Administrator account |
| 8208 | 用户帐户控制: 仅提升安装在安全位置的 UIAccess 应用程序 | User Account Control: Only elevate UIAccess applications that are installed in secure locations |
| 8225 | 用户帐户控制: 允许 UIAccess 应用程序在不使用安全桌面的情况下提升权限 | User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop |
| 8251 | 在安全桌面上提示凭据 | Prompt for credentials on the secure desktop |
| 8252 | 在安全桌面上同意提示 | Prompt for consent on the secure desktop |
| 8253 | 不提示，直接提升 | Elevate without prompting |
| 8254 | 自动拒绝提升请求 | Automatically deny elevation requests |
| 8255 | 提示凭据 | Prompt for credentials |
| 8256 | 同意提示 | Prompt for consent |
| 8257 | 非 Windows 二进制文件的同意提示 | Prompt for consent for non-Windows binaries |
| 17573 | Users | Users |
| 17600 | 添加 %s 的错误。 | Error adding %s. |
| 17601 | 将 MemberOf 列表添加到组 %s 的错误。 | Error adding MemberOf list to group %s. |
| 17602 | 将“成员”列表添加到组 %s 的错误。 | Error adding Members list to group %s. |
| 17603 | 将 %s 添加到 %s 的错误。 | Error adding %s to %s. |
| 17604 | 构建对象的错误。 | Error build object. |
| 17605 | 为对象 %s 建立安全描述符的错误。 | Error building security descriptor for object %s. |
| 17606 | 找不到 %s 的数据类型。 | Cannot find data type for %s. |
| 17607 | 找不到关键字 %s。 | Cannot find keyword %s. |
| 17608 | 按 ID %d 找不到节。 | Cannot find section by ID %d. |
| 17609 | 获取 %s 的 LDAP 名称的错误。 | Error getting LDAP name of %s. |
| 17610 | 创建 %s 的错误。 | Error creating %s. |
| 17612 | 无效的模板路径 %s。 | Invalid template path %s. |
| 17613 | %s 不是有效特权。 | %s is not a valid privilege. |
| 17614 | 对象比分配的多(%d)。 | More objects than allocated (%d). |
| 17615 | 关键字 %s 不应该在节 %s 中。 | Keyword %s not expected in section %s. |
| 17616 | 对象 %s 每行必须有三个字符域。 | Object %s must have 3 fields each line. |
| 17617 | 打开 %s 的错误。 | Error opening %s. |
| 17618 | 按 ID %d 打开节的错误。 | Error opening section by ID %d. |
| 17619 | 处理对象 %s 的错误。 | Error process object %s. |
| 17620 | 查询 %s 的信息的错误。 | Error querying info of %s. |
| 17621 | 查询用户 %s 的特权指派的错误。 | Error querying privilege assignment for user %s. |
| 17622 | 查询 %s 数值的错误。 | Error querying value of %s. |
| 17623 | 注册表值 %s 必须每行有两个字符域。 | Registry value %s must have 2 fields each line. |
| 17624 | 在 %s 上设置安全性的错误。 | Error setting security on %s. |
| 17625 | 写入 %s 的信息的错误。 | Error writing info for %s. |
| 0x5DC | 安全配置被备份到 %1。 | Security configuration was backed up to %1. |
| 0x400006A4 | 副本域控制器正在被升级。不需要创建域策略对象。 | A replica domain controller is being promoted. No need to create domain policy object. |
| 0x400006A5 | %1 被注册来创建默认域组策略对象。 | %1 was registered to create default domain group policy objects. |
| 0x400006A6 | 由于域控制器上的帐户策略只能通过域级组策略对象来配置，GPO %1 中的域策略被忽略。 | Account policy in GPO %1,if any, was ignored because account policy on domain controllerscan only be configured through domain level group policy objects. |
| 0x400006A7 | 自上次传播起，没有对组策略对象进行更改。 | No change has been made to the group policy objects since last propagation. |
| 0x400006A8 | 组策略对象中的安全策略被成功应用。 | Security policy in the Group policy objects has been applied successfully. |
| 0x400006A9 | 处理组策略对象。 | Process group policy objects. |
| 0x400006AC | 在转换的驱动器 %1 上的安全性配置失败。请查看 %%windir%%\\security\\logs\\convert.log 以了解详细的错误。 | Security configuration on converted drive %1 failed.Please look at %%windir%%\\security\\logs\\convert.log for detailed errors. |
| 0x400006AD | 在转换的驱动器 %1 上的安全性配置成功。 | Security configuration on converted drive %1 succeeded. |
| 0x800004B0 | 无法将安全配置备份到安全模板目录。安全配置被备份到 %1。 | Security configuration cannot be backed up to security templates directory.Instead, it is backed up to %1. |
| 0x800004B1 | 无法创建默认域策略对象。%1 | Default domain policy object cannot be created.%1 |
| 0x800004B2 | 安全策略已传播，但有警告信息。%1 | Security policies were propagated with warning.%1 |
| 0x800004B3 | 计算机不应该是域控制器。策略的变化保存在本地数据库中。%1 | Machine was assumed as a non-domain controller. Policy changes were saved in local database.%1 |
| 0x800004B4 | 提升/降级域控制器遇到一个警告。%1 | Promoting/Demoting the domain controller encountered a warning.%1 |
| 0x800004B5 | 来自 LSA/SAM 的策略更改通知的策略处理被推迟，因为磁盘空间不足。%1 | Policy processing of notifications of policy change from LSA/SAM has been delayed because of low disk space.%1 |
| 0x800006AE | 根 SDDL 不能被备份到安全性模板目录。 | Root SDDL cannot be backed up to security templates directory. |
| 0x800006AF | JetTerm2() 无法干净关闭。某些 ESE 安全数据库可能不一致，无法任意移动。Scesrv 使用多个数据库，日志文件可以引用所有这些数据库。JetInit() 通过查找日志文件中指定的数据库位置，将恢复日志文件引用的所有数据库(如有必要)。如果在 JetTerm2() 指示的不干净关闭和恢复期间更改了该位置，将会出现此错误。将删除位于 %%windir%%\\security 的日志和检查点。 | JetTerm2() cannot shutdown cleanly. Some ESE security databases may not be consistent and cannot be moved anywhere. Scesrv uses multiple databases and the log files could be referring to all of them. JetInit() will recover (if needed) all databases which are referred by the log files by looking at the database location as specified in the log files. This error will be seen if that location changed between the unclean shutdown indicated by JetTerm2() and the recovery moment. The logs and checkpoint located at %%windir%%\\security should be deleted. |
| 0xC00003E8 | 安全配置没有备份。%1 | Security configuration was not backed up.%1 |
| 0xC00003E9 | 无法传播安全策略。%1 | Security policy cannot be propagated.%1 |
| 0xC00003EA | 无法创建默认组策略对象。%1 | Default group policy object cannot be created.%1 |
| 0xC00003EB | 来自 LSA/SAM 的策略更改通知被检索，但失败。%1 | Notification of policy change from LSA/SAM has been retried and failed.%1 |
| 0xC00003EC | 来自 LSA/SAM 的策略更改通知无法被添加到策略队列中。%1 | Notification of policy change from LSA/SAM failed to be added to policy queue.%1 |
| 0xC00003ED | 一些 JET 数据库损坏。运行 esentutl /g 来检查安全性数据库 %%windir%%\\security\\Database\\secedit.sdb 的完整性。如果损坏，先尝试在 %%windir%%\\security 目录中运行 esentutl /r 来进行软恢复。如果软恢复失败，尝试在 %%windir%%\\security\\Database\\secedit.sdb 上运行 esentutl /p。然后删除 %%windir%%\\security 中的日志文件。%1 | Some JET database is corrupt. Run esentutl /g to check the integrity of the security database %%windir%%\\security\\Database\\secedit.sdb. If it is corrupt, attempt a soft recovery first by running esentutl /r in the %%windir%%\\security directory. If soft recovery fails, attempt a repair with esentutl /p on %%windir%%\\security\\Database\\secedit.sdb. Then delete the log files in %%windir%%\\security.%1 |
| 0xC00003EE | 来自 LSA/SAM 的策略更改通知被处理而没有验证 PDC。此计算机上的旧安全策略可能被复制到其它 DC。%1 | Notification of policy change from LSA/SAM was processed without verifying PDC. Older security policy from this machine may be replicated out to other DCs.%1 |
| 0xC00003EF | 来自 LSA/SAM 的所有策略更改通知被策略引擎忽略，因为等待 PDC 同步超时。这可能是由于网络，Active Directory 或 FRS 复制问题造成的。%1 | All notification of policy changes from LSA/SAM were ignored by policy engine because it timed out to wait for PDC synchronization. This could be caused by network, Active Directory or FRS replication problems.%1 |
| 0xC00006AA | 在一个转换的驱动器上配置安全性时，一些线程参数无效。 | Some thread arguments are invalid when configuring security on a converted drive. |
| 0xC00006AB | 一个环境变量不可解析。 | An environment variable is unresolvable. |
| File Description: | Windows 安全配置编辑器客户端引擎 |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | scecli |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | scecli |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x804, 1200 |