Event IDs 1481, 1173, and 1203 are logged in the Directory Services log on a Windows Server 2003-based domain controller

After you install a Windows Server 2003-based domain controller into an existing domain, the following events are logged in the Directory Services event log on the Windows Server 2003-based domain controller:

Event ID: 1481

Event ID : 1481
Event Category : Internal Processing
Event Source : NTDS General
Type : Error
Date date
Time time
Computer ComputerName
Description: Internal error: The operation on the object failed.

Additional Data
Error value: 1 00002083: AtrErr: DSID-031510B7, #1: 0: 00002083: DSID-031510B7, problem 1006 (ATT_OR_VALUE_EXISTS), data 0, Att 90121 (printMediaReady)

Event ID: 1173

Event ID : 1173
Event Category : Internal Processing
Event Source : NTDS General
Type : Warning
Date date
Time time
Computer ComputerName
Description: Internal event: Active Directory has encountered the following exception and associated parameters.

Exception:
e0010002

Parameter:
2083

Additional Data

Error value:
8418

Internal ID:
31510b7

Event ID: 1203

Event ID : 1203
Event Category : Replication
Event Source : NTDS Replication
Type : Warning
Date date
Time time
Computer ComputerName
Description: The local domain controller could not replicate the following object from the source domain controller at the following network address because of an Active Directory schema mismatch.

Object:
CN=PRINTER1,CN=2000-PRINTSRV-01,OU=organizational-Unit,DC=corp,DC=contoso,DC=com

Network address:
f5f29b43-6b44-4cdc-b65d-84efe9510250._msdcs.contoso.com

Active Directory will attempt to synchronize the schema before attempting to synchronize the following directory partition.

Directory partition:
DC=corp,DC=contoso,DC=com

You may experience this issue if you install a Windows Server 2003-based domain controller into an existing domain that contains the following kinds of domain controllers:

• Windows Server 2008-based domain controllers
• Microsoft Windows 2000 Server Service Pack 4 (SP4)-based domain controllers

These events are logged during Active Directory Domain Services replication.

Also, the change is not replicated to the Windows Server 2003-based domain controller if you change the naming context of the objects that appear in these events on a Windows Server 2008-based domain controller or on a Windows 2000 SP4-based domain controller.

This issue occurs if Active Directory contains the following kind of third-party attribute:Windows 2000 SP4 and Windows Server 2008 accept UNICODE data that has the SYNTAX_UNICODE_TYPE attribute type. However, Windows Server 2003 does not accept this data type. Therefore, Windows Server 2003 does not replicate this kind of attribute data.

Note In the events that are displayed in the "Symptoms" section, the affected attribute is printMediaReady. This attribute is set on the PrintQueue class. This attribute is written by a third-party printer driver. You may experience this issue with other third-party attributes.

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

To resolve this problem, modify Active Directory to remove the affected attribute data. To do this, follow these steps.

Important There are no known Microsoft programs that write these types of entries in Active Directory. The following steps describe a general procedure to remove the third-party attribute data. If you remove this attribute data, the related third-party program may stop working. For more information about how to remove a particular third-party attribute from Active Directory, or for specific instructions about how to remove the settings, contact the program vendor.

Windows Server 2008

1. Start the ADSI Edit tool. To do this, click Start, click Run, type %systemroot%\system32\adsiedit.msc, and then click OK.
   
   Note The ADSI Edit tool is automatically installed when you install the Active Directory Domain Services role on a Windows Server 2008-based computer.
2. On the Action menu, click Connect to, and then click OK.
3. Locate the container for the object that is listed in the Description field of Event ID 1203. For example, locate the following object:
   CN=PRINTER1,CN=2000-PRINTSRV-01,OU=organizational-Unit,DC=corp,DC=contoso,DC=com
4. Right-click the object, and then click Properties.
5. On the Attribute Editor tab, click the attribute that is listed in Event ID 1481. For example, click printMediaReady.
6. Click Edit.
7. Select the entry, and then click Clear to remove it.
8. Click OK two times.
9. Exit the ADSI Edit tool.
10. Give sufficient time for the object deletion to replicate to all the Windows Server 2008-based domain controllers. These are the controllers that are configured to replicate with the Windows Server 2003-based domain controller on which you experience the problem.

Windows 2000 Server SP4

1. Start the ADSI Edit tool. To do this, click Start, click Run, type adsiedit.msc, and then click OK.
   
   Note ADSI Edit is included with the Windows 2000 Server Support Tools. To install the Windows 2000 Support Tools, double-click Setup in the Support\Tools folder on the Windows 2000 Server CD.
2. Locate the container for the object that is listed in the Description field of Event ID 1203. For example, locate the following object:
   CN=PRINTER1,CN=2000-PRINTSRV-01,OU=organizational-Unit,DC=corp,DC=contoso,DC=com
3. Right-click the object, and then click Properties.
4. In the ObjectName Properties dialog box, click Both in the Select which properties to view list.
5. In the Select a property to view list, click the attribute that is listed in Event ID 1481. For example, click printMediaReady.
6. Click Remove, and then click OK.
7. Exit the ADSI Edit tool.
8. Give sufficient time for the object deletion to replicate to all the Windows 2000 SP4-based domain controllers. These are the controllers that are configured to replicate with the Windows Server 2003-based domain controller on which you experience the problem.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.