Share via

Event ID 1153 — Schema Operations

  • Article

Applies To: Windows Server 2008 R2

Schema operations include the following:

  • Updating the schema cache
  • Updating the schema index
  • Implementing schema modifications
  • Maintaining schema integrity

Event Details

Product: Windows Operating System
ID: 1153
Source: Microsoft-Windows-ActiveDirectory_DomainService
Version: 6.0
Symbolic Name: DIRLOG_SCHEMA_INVALID_SUPER
Message: Internal event: The following schema class has a superclass that is not valid.

Class identifier:
%1
Class name:
%2
Superclass identifier:
%3

Inheritance was ignored.

Resolve

Start a replication sync with all replication partners of the local directory service

You can use the following procedures to resolve this issue. After you complete each procedure, check Event Viewer to see if Event IDs 1142 or 1156 continue to be reported. If either of these events continue to be reported, try the next procedure.

  1. Start Active Directory replication.
  2. Restore the Active Directory database from backup media.

To perform these procedures, you must have membership in Domain Admins, or you must have been delegated the appropriate authority. Perform all steps on the computer that is logging the event to be resolved.

Start Active Directory replication

To start Active Directory replication:

  1. Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. At the command prompt, type **repadmin /syncall /user:**domain\user **/pw:**password, and then press ENTER. Substitute the appropriate domain name, user name, and password for domain, user, and password, respectively. The command output indicates whether synchronization started successfully.
  3. At the command prompt, type time /t, and then press ENTER. This command displays the time at the server on which you are working.
  4. Wait at least 15 minutes before proceeding to the next step.
  5. Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
  6. Expand Applications and Services Logs, and then click Directory Service. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  7. Look for events that occurred after you started replication with the repadmin command. Search for the following event identifiers: 1142, 1153, 1154, 1155, and 1156, which indicate that there is still an issue with the schema. To search for event 1142, click Find, type 1142, and then click Find Now. Use the same steps to search for the other event identifiers.
  8. If you do not find any additional events related to the issue, it is probably solved. Check back in one hour and search for the events again. If they do not appear, check back in 24 hours.
  9. If you do find additional events that are related to the issue, restore the Active Directory database on the affected domain controller from backup media.

Restore the Active Directory database from backup media

To restore the Active Directory database from backup media, you need the Directory Services Restore Mode password. If you do not know the Directory Services Restore Mode password, you can reset it by using the Ntdsutil tool and the steps in article 322672 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkID=95915).

To restore the Active Directory database from backup media:

  1. At a command prompt that you opened as administrator, type bcdedit /set safeboot dsrepair, and then press ENTER.
  2. Restart the domain controller.
  3. When the boot option menu appears, press F8 to start the domain controller in Directory Services Restore Mode. When the recovery options menu appears, select the option for Directory Services Restore Mode.
  4. At the Windows logon screen, click Switch User.
  5. Click Other User.
  6. Type .\administrator as the user name, type the Directory Services Restore Mode password for the server, and then press ENTER.
  7. Open a command prompt. To open a command prompt, click Start. In Start Search, type cmd, and then press ENTER.
  8. At the command prompt, type wbadmin get versions -backuptarget:targetDrive:, and then press ENTER. Substitute the location of the backup that you want to restore for targetDrive.
  9. Identify the version of the backup that you want to restore. You must enter this version exactly in the next step.
  10. Type **wbadmin start systemstaterecovery -version:**dateTime -backuptarget:targetDrive:-quiet, and then press ENTER. Substitute the version of the backup that you want to restore for dateTime and the volume that contains the backup for targetDrive.
  11. Open a command prompt, type bcdedit /deletevalue safeboot, and then press ENTER.
  12. After the recovery operation completes, restart the domain controller.

Note: There is no need to attempt an authoritative restore because the schema cannot be restored with an authoritative restore.

Verify

To verify that the schema is in a consistent state, complete the following procedures:

  1. Ensure that the domain controllers synchronize their directory data by starting Active Directory replication.
  2. Enable diagnostic logging for the schema.
  3. Update the schema cache.
  4. Verify that the schema was updated successfully by using Event Viewer.

To perform these procedures, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.

Start Active Directory replication

To start Active Directory replication:

  1. Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. Run the command **repadmin /syncall /user:**domain\user **/pw:**password. Substitute the appropriate domain name, user name, and password for domain, user, and password, respectively. The command output indicates whether synchronization started successfully.

Enable diagnostic logging for the schema

To verify a successful update of the schema, you can enable diagnostic logging for the schema. When you enable diagnostic logging, a schema update produces Event ID 1582 in the Directory Service log of Event Viewer. To enable diagnostic logging for the schema, you must edit the registry.

To enable diagnostic logging for the schema:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. Open Registry Editor. To open Registry Editor, click Start. In Start Search, type regedit, and then press ENTER. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics, in the left pane, right-click the 24 DS Schema value, and then click Modify.
  3. Type 1 or higher (up to 5) for Value data to enable diagnostic logging for the schema. The higher the value, the more information is reported to the Directory Service log. Click OK.

Update the schema cache

To update the schema cache:

  1. Create a file to force a schema cache update using Ldifde.exe. Create a new text file named SchemaUp (SchemaUp.txt, if you are viewing file extensions) in a folder location that is convenient for you to access.

  2. Copy the following five lines of text and paste them as the contents of the SchemaUp.txt file.

    dn:

    changetype: modify

    add: schemaUpdateNow

    schemaUpdateNow: 1

    -

  3. After you paste the text into the file, ensure that there are no line breaks (carriage returns) between each line of text. If there are, delete the empty lines. Ensure that you have a hyphen as the last line of text in the file.

  4. Save the file.

  5. Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start Menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  6. At the command prompt, type ldif -i -f SchemaUp.txt, and then press ENTER. If necessary, type the file path to the text file that you saved. For example, if you saved the file in the Documents folder of an account named Administrator, type ldifde -i -f "c:\users\administrator\documents\schemaUp.txt", and then press ENTER.

Verify that the schema cache was updated successfully by using Event Viewer

To verify that the schema cache was updated successfully by using Event Viewer:

  1. Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
  2. Expand Applications and Services Logs, and then click Directory Service.
  3. Look for Event ID 1582, which confirms that the schema cache was reloaded successfully. If you do not see the event, click Find, type 1582, and then click Find Now. Event 1582 confirms that the schema cache was updated.
  4. Confirm that there are no Critical, Error, or Warning events that are related to the schema that occurred after the schema cache update. To locate events that are related to the schema, click Find, type DS Schema, and then click Find Next.
  5. Continue to click the Find Next button and review each event until you have verified that there are no Critical, Error, or Warning events that occurred after the schema cache update.

When you confirm that the schema cache was updated, you may no longer need diagnostic logging for schema events. To disable diagnostic logging for schema events, use the Reg command to set the 24 DS Schema value to 0. To set the value of 24 DS Schema to 0, at a command prompt, type the following command, and then press ENTER:

Reg Add HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics /v "24 DS Schema" /t REG_DWORD /d 0

The number after /d indicates the value, in this case, the logging level. For example, to set the logging level to 1, change /d 0 to /d 1 in the previous command.

To learn more about the Reg command syntax and options, at a command prompt, type Reg /?, and then press ENTER.

Schema Operations

Active Directory