We're using the IDM3 remote loader on several domain controllers. When
we get large bulk imports or even syncs between ADS and IDM after some
time the domain controller hangs. The MMC snap-in for active directory
administration gives a timeout, and the RPC service is down. Sometimes
the domain controller can be recovered by stopping the remote loader,
but usually it's necessary to reboot. Before the active directory goes
down, several trace messages of the remote loader state:

[08.05.2006 16:41:00.31] Drvrs : G3-7-AD-UKG PT:
DirXML Log Event -------------------
Driver: \GOESTERN\GWDG\GOESTERN DriverSet\G3-7-AD-UKG
Channel: Publisher
Status: Error
Message: Assocation does not resolve to an object in the application
[08.05.2006 16:41:00.53] Drvrs : G3-7-AD-UKG PT:
DirXML Log Event -------------------
Driver: \GOESTERN\GWDG\GOESTERN DriverSet\G3-7-AD-UKG
Channel: Publisher
Status: Error
Message: Code(-9024) Unable to read current state of
54145b9d4657ec4398f6b732e8819b21.

of course the GUID and the object mentioned exist in the directory. What
kind of interface is the ADDriver.dll using? ADSI? Can anyone confirm
same problems on a standard Windows 2003 SP1 Domain Controller using
stock Remote Loader of IDM3.

Thanks in advance,

Sebastian Rieger