You cannot log on to the domain, join a computer to the domain, or run the Active Directory Installation Wizard (Dcpromo.exe) in Windows Server 2003

Symptom 1

loadTOCNode(2, 'symptoms');When
you try to join a Windows Server 2003-based computer to a domain, the
operation may not be successful. Additionally, you receive the
following error message:

Back to the top

Symptom 2

loadTOCNode(2, 'symptoms');When
you try to remove Active Directory from a domain controller in a
Windows Server 2003-based computer in the same domain by using another
domain controller, you may receive the following error message:

Back to the top

Symptom 3

loadTOCNode(2, 'symptoms'); When you run the dcdiag.exe
command prompt utility on a Windows Server 2003-based computer, the
operation is unsuccessful. The following errors are logged:

Back to the top

This
problem occurs because the domain controller that is present in the
domain is not identifying itself as the domain controller. This
indicates that the Sysvol and the Netlogon folders are not shared. This
problem may occur when the policies and scripts that are stored in the
%Windows%Sysvol\Sysvol\DomainName folder are not available.

The policies and scripts may not be available in the following scenarios.

Back to the top

Scenario 1

loadTOCNode(2, 'cause'); The Policies and Scripts folders may be missing completely.

Back to the top

Scenario 2

loadTOCNode(2, 'cause'); The Policies and Scripts folders may be present in the Ntfrs_Preexisting folder.

Back to the top

Scenario 3

loadTOCNode(2, 'cause'); The Policies and Scripts folders are present. However, they are empty.

Back to the top

Warning
Serious problems might occur if you modify the registry incorrectly by
using Registry Editor or by using another method. These problems might
require that you reinstall the operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at
your own risk.
To resolve this problem, verify the following path for the Policies and Scripts folder:

Follow the steps, depending on the cause.

Back to the top

Resolution 1

loadTOCNode(2, 'resolution');

1.	If it is a single domain controller setup, create the Policies and Scripts folders manually.
2.	Start Registry Editor. Locate to the following subkey: HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Backup/Restore\Process at Startup
3.	Set the value of the BurFlags registry entry to D4. Note Before you change the registry, see the "More Information" section.
4.	Restart the Ntfrs service, and then wait until the Sysvol and the Netlogon folders are shared.
5.	Run the Dcgpofix command prompt utility. Note After you run this tool, all the default policies are implemented. The custom policies are not implemented. For more information about Dcgpofix utility, visit the following Microsoft TechNet Web site: http://technet.microsoft.com/en-us/library/cc739095.aspx ( http://technet.microsoft.com/en-us/library/cc739095.aspx)

Back to the top

Resolution 2

loadTOCNode(2, 'resolution');

1.	Copy the contents from Ntfrs_Preexisting folder to the %Windows%Sysvol\Sysvol\Domain Name folder.
2.	Start Registry Editor. Locate to the following subkey: HKLM\SYSTEM\CurrentControlSet\Services\Ntfrs\Parameters\Backup/Restore\Process at Startup .
3.	Set the value of the BurFlags registry entry to D4. Note Before you change the registry, see the "More Information" section.
4.	Restart the Ntfrs service, and then wait until the Sysvol and the Netlogon folders are shared.

Back to the top

Resolution 3

loadTOCNode(2, 'resolution');
For both single domain controller setup and multiple domain controller
environments, restore the Policies and Scripts folders from a valid
backup.

Back to the top

For more information about how to rebuild Sysvol tree, click the
following article number to view the article in the Microsoft Knowledge
Base:

You must be careful when you reinitialize the File
Replication Service (FRS) database by setting the value to D4 or D2. If
Distributed File System (DFS) is configured in the network, the
reinitializing of the database will differ, depending on the replica
sets.
For more information about BurFlag registry key, click the following
article number to view the article in the Microsoft Knowledge Base:

Back to the top