Windows Server TechCenter >
Windows Server Forums
>
Directory Services
>
NTDS Replication 1093 200d2 (proxyAddresses)
NTDS Replication 1093 200d2 (proxyAddresses)
- Hi there,
We have 7 domain in the same forest, all DCs are running Windows Server 2000 SP4. On 4 of the DCs we are seeing event NTDS replication 1093, indicating that an object couldn´t be updated as it exceeds the database size limit, always showing 200d2 (proxyAddresses) in the context of the warning. We are also running Exchange 2003. Can anyone help me determine the cause of the problem, or to find the property of the object causing the problem?
Thanks.
All Replies
- Hi Jonny
Does the event show the DN of the specific object? If so, you can browse to the object using ADSIEdit and look at the proxyAddresses attribute. It is likely that this object has exceeded the (approximately) 800 value limit for non-linked multi-valued attributes.
The proxyAddresses contains all of the Exchange email addresses associated with a recipient (e.g. SMTP, X.400, X.500, etc.). It is highly unusual for a single object to have more than 800 proxyAddresses, but could theoretically happen. For example, I have seen organisations that assign old SMTP addresses to a single user object when decommissioning mailboxes.
More info on the limit here:
http://technet.microsoft.com/en-us/library/cc772829(WS.10).aspx
Tony - Hi Tony,
Really appreciate the reply. Having a look at the object, it does indeed have a vast number of ProxyAddresses associated, nearly all starting with notes: then something like b5492/gsfadggadga/address@domain.com.
Right down at the bottom it has the more resonable looking ones like X400.... MS: dsfdsafads and CCMAIL: dsfasf
They had performed a migration from Lotus Notes to Exchange in the past.
Possibly this could appy in our situation: http://support.microsoft.com/default.aspx?scid=kb;EN-US;867474
I checked two of the offending accounts and neither had both First Name and Given Name specified in AD, we´d just have to check the other part in Notes.
Thanks,
John Hi there,
We have 7 domain in the same forest, all DCs are running Windows Server 2000 SP4. On 4 of the DCs we are seeing event NTDS replication 1093, indicating that an object couldn´t be updated as it exceeds the database size limit, always showing 200d2 (proxyAddresses) in the context of the warning. We are also running Exchange 2003. Can anyone help me determine the cause of the problem, or to find the property of the object causing the problem?
Thanks.
Hi
Can you please post the error that you're seing.
I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.- KB867474 certainly looks like it could explain the behaviour.
Tony - The error is:
The directory replication agent (DRA) could not apply changes to object DC=@,DC=xyz.example.com,CN=MicrosoftDNS,CN=System,DC=xyz,DC=example, DC=com (GUID 77d76064-f49e-4762-ba8c-324b6c518f11) because the incoming changes cause the object to exceed the database's record size limit. The incoming change to attribute 200d2 (proxyAddresses) will be backed out in an attempt to make the update fit. In addition to the change to the attribute not being applied locally, the current value of the attribute on this system will be sent out to all other systems to make that the definitive version. This has the effect of nullifying the change to the rest of the enterprise.
Cheers!! The error is:
I found a similar article that I'm not sure if still applies to your Windows 200 SP4, but the symptons are similar to yours except that thsi article is related to DNS:http://support.microsoft.com/default.aspx/kb/267855
The directory replication agent (DRA) could not apply changes to object DC=@,DC=xyz.example.com,CN=MicrosoftDNS,CN=System,DC=xyz,DC=example, DC=com (GUID 77d76064-f49e-4762-ba8c-324b6c518f11) because the incoming changes cause the object to exceed the database's record size limit. The incoming change to attribute 200d2 (proxyAddresses) will be backed out in an attempt to make the update fit. In addition to the change to the attribute not being applied locally, the current value of the attribute on this system will be sent out to all other systems to make that the definitive version. This has the effect of nullifying the change to the rest of the enterprise.
Cheers!!
I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
