General discussion

Locked

NTDS SDPROP Internal Processing Error

By ninet4 ·
Windows 2003 Server Directory Service Log is completely spammed with the below error.

Event Type: Error
Event Source: NTDS SDPROP
Event Category: Internal Processing
Event I 2008
Date: 10/15/2004
Time: 3:21:11 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: EDC-DC2
Description:
Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected.

Object:
CN=Quality Engineering-12,CN=Microsoft Exchange System Objects,DC=everdream,DC=corp

Additional Data
Error value:
-1026 JET_errRecordTooBig, Record larger than maximum size
Internal I
20903d5

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Searching the normal channels (i.e this site, google, MS) turns up nothing or worse than nothing. No specific problems in AD are noticed as a result of this. Setup is 3 Domain Controllers all Win2K3 in Native mode. 1 clustered 2K3 Exchange Server. We have noticed some problems with SYSVOL security, specifically when creating or editing GPOs, though not all the time. Whether or not this is related is still unknown. Bottom line, information in specific regard to what is causing these errors is hard to come by. Help would be much appreciated.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to NTDS SDPROP Internal Proc ...

Run a metadata cleanup on the AD database.

Details here:

http://www.microsoft.com/resources/documentation/windowsserv/2003/standard/proddocs/en-us/sag_deldommetadata.asp

Collapse -

by ninet4 In reply to

This appeared to be to cleanup stale AD objects, specifically domains or DCs that were not properly deactivated from AD. This is not the case with my problem. I ran this utility and showed no rogue DCs.

Collapse -

Same issue

by khowlett In reply to

I am getting the same errors in my DC event logs since we set up our exchange cluster, since you have an exchange cluster too it seems likely that the answer could lie there?

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums