Export (0) Print
Expand All
2 out of 2 rated this helpful - Rate this topic

Troubleshooting schema

Updated: May 1, 2010

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting schema

What problem are you having?

Unable to modify or extend the schema.

Cause:  The schema operations master is not available. The domain controller that currently holds the schema master role is offline or network connectivity between you and the schema master is inoperable.

Solution:  Restore the availability of the schema master by fixing the network connectivity problem or by transferring or seizing the schema master role.

See also:  Diagnose Connections; Operations master roles; Responding to operations master failures; Transfer the schema master role; Seize the schema master role

Cause:  The user trying to modify the schema does not belong to the Schema Admins group.

Solution:  Add the correct user account to the Schema Admins group.

See also:  Add a member to the Schema Admins group

Cause:  There are syntax errors in the LDAP import format (LDIF) script.

Solution:  Debug and fix the LDIF script then try the modification again.

See also:  The Active Directory Programmer's Guide at the Microsoft Web site; Internet Engineering Task Force Web site

Cause:  The domain controller holding the schema master role is running Windows 2000 and has not been enabled for schema changes.

Solution:  Enable schema changes on the domain controller. For more information, see Enable schema changes on a schema master running Windows 2000.

See also:  Domain and forest functionality; Operations master roles; The Active Directory Programmer's Guide at the Microsoft Web site

Note

Unable to add attributes to a class.

Cause:  The attributes cannot be associated with a class because the schema cache has not been updated.

Solution:  Ensure that the schema cache is updated after an attribute is added before attempting to add the attribute to a class. For more information, see Reload the schema.

Cause:  You are attempting to define a class on a domain controller that is not the schema operations master and the new attribute has not replicated in.

Solution:  Always perform schema updates on the schema operations master.

See also:  Using the Windows Deployment and Resource Kits; Extending the schema; The Active Directory Programmer's Guide at the Microsoft Web site.

Unable to connect to a domain controller running Windows 2000 from the Active Directory Schema snap-in.

Cause:  You are trying to connect to a domain controller running Windows 2000 that does not have Service Pack 3 or later installed.

Solution:  Upgrade domain controllers running Windows 2000 to Service Pack 3 or later.

See also: Connecting to domain controllers running Windows 2000

Unable to find or run the Active Directory Schema snap-in.

Cause:  The Active Directory Schema snap-in has not been installed or registered.

Solution:  For instructions on installing and registering the Active Directory Schema snap-in, see Install the Active Directory Schema snap-in.

See also:  Managing Active Directory from MMC

Search for new and updated information. Or, your question does not match any of those listed above.

Cause:  You can find new and updated information on the Microsoft Web site.

Solution:  The Microsoft Web site contains the latest product support information. For information about where to look, see Using online resources.

For the latest Active Directory development information, see the Active Directory Programmer's Guide at the Microsoft Web site.

See also:  Managing Active Directory from MMC; Using the Windows Deployment and Resource Kits; Technical support options

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.