scecli.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x5dc78.11011Security configuration was backed up to %1.
0x400006a478.11011A replica domain controller is being promoted. No need to create domain policy object.
0x400006a578.11011%1 was registered to create default domain group policy objects.
0x400006a678.11011Account policy in GPO %1,if any, was ignored because account policy on domain controllers can only be configured through domain level group policy objects.
0x400006a778.11011No change has been made to the group policy objects since last propagation.
0x400006a878.11011Security policy in the Group policy objects has been applied successfully.
0x400006a978.11011Process group policy objects.
0x400006ac78.11011Security configuration on converted drive %1 failed. Please look at %windir%\security\logs\convert.log for detailed errors.
0x400006ad78.11011Security configuration on converted drive %1 succeeded.
0x800004b078.11011Security configuration cannot be backed up to security templates directory. Instead, it is backed up to %1.
0x800004b178.11011Default domain policy object cannot be created. %1
0x800004b278.11011Security policies were propagated with warning. %1
0x800004b378.11011Machine was assumed as a non-domain controller. Policy changes were saved in local database. %1
0x800004b478.11011Promoting/Demoting the domain controller encountered a warning. %1
0x800004b578.11011Policy processing of notifications of policy change from LSA/SAM has been delayed because of low disk space. %1
0x800006ae78.11011Root SDDL cannot be backed up to security templates directory.
0x800006af78.11011JetTerm2() 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.
0xc00003e878.11011Security configuration was not backed up. %1
0xc00003e978.11011Security policy cannot be propagated. %1
0xc00003ea78.11011Default group policy object cannot be created. %1
0xc00003eb78.11011Notification of policy change from LSA/SAM has been retried and failed. %1
0xc00003ec78.11011Notification of policy change from LSA/SAM failed to be added to policy queue. %1
0xc00003ed78.11011Some 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
0xc00003ee78.11011Notification 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
0xc00003ef78.11011All 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
0xc00006aa78.11011Some thread arguments are invalid when configuring security on a converted drive.
0xc00006ab78.11011An environment variable is unresolvable.
27 entries