Event ID: 1016
Source: NTDS General
Type: Error
Description: The schema could not be loaded, and the directory updates could not be made. Stop and restart this Windows Domain Controller and try again
According to the Microsoft article "Event ID 1016 — Schema Operations", this event may be recorded when there certain conditions such as low memory or schema corruption. The article contains information on how to correct these type of problems.
Message: AD_TERM could not be initialized because the schema could not be loaded.
User Action
Restart the directory service and try this task again. If this error continues to occur, restore the directory service from backup media.
Solution:
Add memory or correct schema corruption
Event IDs 1016, 1135, 1140, 1141, 1208, and 1315 indicate there may be a low memory condition or schema corruption. Determining whether the issue is related to low memory is the least intrusive operation. Therefore, first determine if low memory is the cause of the issue.
To determine how much memory is available, click Start. In Start Search, type winver, and then press ENTER. The physical memory appears at the bottom of the dialog box. Click OK.
You can check memory usage in Task Manager. To check memory usage, click Start. In Start Search, type taskmgr, and then press ENTER. Click Performance.
You can also check virtual memory usage. To check virtual memory usage, click Start. In Start Search, type sysdm.cpl, click Advanced, and in Virtual memory click Change.
In Total paging file size for all drives, compare the numbers from Recommended with the numbers from Currently allocated. If the numbers are the same, the server may be running low on virtual memory.
You can resolve memory issues by adding more physical memory or reducing the number of applications that are running on the computer. If the memory is operating within normal parameters, the server may have a corrupt schema. If you are unsure about the type of memory or the maximum physical memory capacity of the server, visit the manufacturer's web site or contact their support number for further information.
If the available memory is not low, then there is likely schema corruption. Perform the following procedures on the domain controller reporting the issue. After each procedure, check Event Viewer to see if this event continues to be reported. If the event continues to be reported, try the next procedure in the list.
Enable diagnostic logging for the schema.
Update the schema cache.
Restart the directory service.
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.
Enable diagnostic logging for the schema
To verify a successful update of the schema, you can enable diagnostic logging for the schema. When diagnostic logging is enabled, 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.
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.
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.
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:
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.
Copy the following five lines of text, and then paste them as the contents of the SchemaUp.txt file.
dn:
changetype: modify
add: schemaUpdateNow
schemaUpdateNow: 1
-
After you paste the text to the file, ensure that there are no line breaks (carriage returns) between each line of text. If there are line breaks, delete the empty lines. Ensure that you have a hyphen as the last line of text in the file.
Save the file.
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.
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.
Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
Expand Applications and Services Logs, and then click Directory Service.
Look for Event ID 1582, which confirms that the schema cache was reloaded successfully. If you do not see this event, click Find, type 1582, and then click Find Now. Event ID 1582 confirms that the schema cache was updated.
Confirm that there are no Critical, Error, or Warning events related to the schema after the schema cache update. To locate events that are related to the schema, click Find, type DS Schema, and then click Find Next.
Continue to click Find Next and review each event until you have verified that there are no Critical, Error, or Warning events that occured after the schema cache update.
Note: When you confirm that the schema cache was updated, you can set the 24 DS Schema value to 0 if you no longer need diagnostic logging for schema events. You can use the Reg command to modify the 24 DS Schema registry value. For example, 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, of 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.
Restart the directory service
To restart the directory service:
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.
At the command prompt, type net stop ntds & net start ntds, and then press ENTER.
If the event continues to appear in Event Viewer, restart the domain controller, and then check Event Viewer again.
You may have to increase virtual memory or physical memory.
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 instructions in article 322672 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=95915).
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 (http://go.microsoft.com/fwlink/?LinkID=95915).
To restore the Active Directory database from backup media:
At a command prompt that you opened as administrator, type bcdedit /set safeboot dsrepair, and then press ENTER.
Restart the domain controller.
At the Windows logon screen, click Switch User.
Click Other User.
Type .\administrator as the user name, type the Directory Services Restore Mode password for the server, and then press ENTER.
Click Start. In Start Search, type cmd, and then press ENTER.
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.
Identify the version of the backup that you want to restore. You must enter this version exactly in the next step.
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.
Open a command prompt, type bcdedit /deletevalue safeboot, and then press ENTER.
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 by using an authoritative restore.
Verification :
Source: NTDS General
Type: Error
Description: The schema could not be loaded, and the directory updates could not be made. Stop and restart this Windows Domain Controller and try again
According to the Microsoft article "Event ID 1016 — Schema Operations", this event may be recorded when there certain conditions such as low memory or schema corruption. The article contains information on how to correct these type of problems.
Message: AD_TERM could not be initialized because the schema could not be loaded.
User Action
Restart the directory service and try this task again. If this error continues to occur, restore the directory service from backup media.
Solution:
Add memory or correct schema corruption
Event IDs 1016, 1135, 1140, 1141, 1208, and 1315 indicate there may be a low memory condition or schema corruption. Determining whether the issue is related to low memory is the least intrusive operation. Therefore, first determine if low memory is the cause of the issue.
To determine how much memory is available, click Start. In Start Search, type winver, and then press ENTER. The physical memory appears at the bottom of the dialog box. Click OK.
You can check memory usage in Task Manager. To check memory usage, click Start. In Start Search, type taskmgr, and then press ENTER. Click Performance.
You can also check virtual memory usage. To check virtual memory usage, click Start. In Start Search, type sysdm.cpl, click Advanced, and in Virtual memory click Change.
In Total paging file size for all drives, compare the numbers from Recommended with the numbers from Currently allocated. If the numbers are the same, the server may be running low on virtual memory.
You can resolve memory issues by adding more physical memory or reducing the number of applications that are running on the computer. If the memory is operating within normal parameters, the server may have a corrupt schema. If you are unsure about the type of memory or the maximum physical memory capacity of the server, visit the manufacturer's web site or contact their support number for further information.
If the available memory is not low, then there is likely schema corruption. Perform the following procedures on the domain controller reporting the issue. After each procedure, check Event Viewer to see if this event continues to be reported. If the event continues to be reported, try the next procedure in the list.
Enable diagnostic logging for the schema.
Update the schema cache.
Restart the directory service.
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.
Enable diagnostic logging for the schema
To verify a successful update of the schema, you can enable diagnostic logging for the schema. When diagnostic logging is enabled, 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.
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.
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.
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:
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.
Copy the following five lines of text, and then paste them as the contents of the SchemaUp.txt file.
dn:
changetype: modify
add: schemaUpdateNow
schemaUpdateNow: 1
-
After you paste the text to the file, ensure that there are no line breaks (carriage returns) between each line of text. If there are line breaks, delete the empty lines. Ensure that you have a hyphen as the last line of text in the file.
Save the file.
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.
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.
Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
Expand Applications and Services Logs, and then click Directory Service.
Look for Event ID 1582, which confirms that the schema cache was reloaded successfully. If you do not see this event, click Find, type 1582, and then click Find Now. Event ID 1582 confirms that the schema cache was updated.
Confirm that there are no Critical, Error, or Warning events related to the schema after the schema cache update. To locate events that are related to the schema, click Find, type DS Schema, and then click Find Next.
Continue to click Find Next and review each event until you have verified that there are no Critical, Error, or Warning events that occured after the schema cache update.
Note: When you confirm that the schema cache was updated, you can set the 24 DS Schema value to 0 if you no longer need diagnostic logging for schema events. You can use the Reg command to modify the 24 DS Schema registry value. For example, 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, of 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.
Restart the directory service
To restart the directory service:
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.
At the command prompt, type net stop ntds & net start ntds, and then press ENTER.
If the event continues to appear in Event Viewer, restart the domain controller, and then check Event Viewer again.
You may have to increase virtual memory or physical memory.
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 instructions in article 322672 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=95915).
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 (http://go.microsoft.com/fwlink/?LinkID=95915).
To restore the Active Directory database from backup media:
At a command prompt that you opened as administrator, type bcdedit /set safeboot dsrepair, and then press ENTER.
Restart the domain controller.
At the Windows logon screen, click Switch User.
Click Other User.
Type .\administrator as the user name, type the Directory Services Restore Mode password for the server, and then press ENTER.
Click Start. In Start Search, type cmd, and then press ENTER.
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.
Identify the version of the backup that you want to restore. You must enter this version exactly in the next step.
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.
Open a command prompt, type bcdedit /deletevalue safeboot, and then press ENTER.
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 by using an authoritative restore.
Verification :
To verify that the schema is in a consistent state, complete the following procedures:
Ensure that the domain controllers synchronize their directory data by starting Active Directory replication.
Enable diagnostic logging for the schema.
Update the schema cache.
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:
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.
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.
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.
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.
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:
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.
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
-
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.
Save the file.
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.
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:
Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
Expand Applications and Services Logs, and then click Directory Service.
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.
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.
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.
Ensure that the domain controllers synchronize their directory data by starting Active Directory replication.
Enable diagnostic logging for the schema.
Update the schema cache.
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:
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.
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.
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.
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.
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:
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.
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
-
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.
Save the file.
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.
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:
Open Event Viewer. To open Event Viewer, click Start. In Start Search, type eventvwr.msc, and then press ENTER.
Expand Applications and Services Logs, and then click Directory Service.
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.
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.
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.
Posts
