Dirsync starts and then sooner or later it will fail with Common Error 0xe1000005. Internal DSA error entry in the log.
Log indicates it happens randomly and is not particular object related:
9/19/2008 9:54:19 AM (GMT-05:00) Common size: 28
9/19/2008 9:54:19 AM (GMT-05:00) Common class: group
9/19/2008 9:54:19 AM (GMT-05:00) Common integrity: NOT PARTIAL
9/19/2008 9:54:19 AM (GMT-05:00) Common type: DELETED(1)
9/19/2008 9:54:19 AM (GMT-05:00) Common Error 0xe1000005. Internal DSA error
9/19/2008 9:54:19 AM (GMT-05:00) Controller Abort transaction ...
9/19/2008 9:54:19 AM (GMT-05:00) Controller Transaction was aborted
Installing new DSA or modifying sync scope and including only one OU with one single user didn't help, it never finishes the Initial sync
Event Viewer for ADAM is the first place to check.
QMM console machine where ADAM was installed run out of space once. Admin freed up some space and everything seemed to work fine, but when analyzing ADAM in Event Viewer it is noticeable there was a space issue, there was 0 space, it could not write anymore and since then ADAM from time to time reports the local system account will not have rights to write, access denied, could not compact/defragment and different similar entries.
Stopping and starting ADAM was all what was needed in this particular situation, DSA immediately started to work properly.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy