I have IDM2(eDir driver) on eDir8.7.3 on NW6.5 for IDTREE
and IDM2(eDir driver) on eDir8.7.3 on NW6.5 for DMZTREE

I set eDir to eDir driver but they are not synch.(I create the same way as
previous one that they are synch.)

What should I do ? please help?

This is log message.

16:58:07 4355D5C0 Drvrs: Code(-9092) Unable to log message: {0}
16:58:07 4355D5C0 Drvrs: Code(-9090) Unable to resolve Persistent Log
object \IDTREE\oncbido\IDMDriver\ONCB DriverSet: {1}
16:58:38 483BB2E0 Drvrs: ID to DMZ eDirectory Driver PT:
DirXML Log Event -------------------
Driver: \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to DMZ eDirectory
Driver
Channel: Publisher
Status: Warning
Message: Lost connection to remote tree's Subscriber (the other side may
have been shut down)
16:58:38 483BB2E0 Drvrs: ID to DMZ eDirectory Driver PT:
DirXML Log Event -------------------
Driver: \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to DMZ eDirectory
Driver
Channel: Publisher
Status: Warning
Message: Lost connection to remote tree's Subscriber (the other side may
have been shut down)
17:13:18 4355D5C0 Drvrs: ENG ET:
DirXML Log Event -------------------
Status: Error
Message: Code(-9095) Unable to get state of DirXML Driver
\IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to DMZ eDirectory Driver:
novell.jclient.JCException: duplicateContext -670 ERR_INVALID_CONTEXT
at novell.jclient.JCContext.duplicateContext(Native Method)
at novell.jclient.JCContext.duplicate(JCContext.java: 655)
at com.novell.nds.dirxml.engine.MiscDS.getDriverState (MiscDS.java:96)
at
com.novell.nds.dirxml.engine.DriverEventMonitor$Dr iverStateHandler.handle
Event(DriverEventMonitor.java:261)
at com.novell.nds.events.EventNotification.processEve nt
(EventNotification.java:845)
at com.novell.nds.events.EventNotification.processEve nts(Native Method)
at com.novell.nds.events.EventNotification.access$500
(EventNotification.java:56)
at com.novell.nds.events.EventNotification$EventThrea d.run
(EventNotification.java:1149)
at java.lang.Thread.run(Thread.java:534)

17:13:18 4355D5C0 Drvrs: Code(-9092) Unable to log message: {0}
17:13:18 4355D5C0 Drvrs: Code(-9090) Unable to resolve Persistent Log
object \IDTREE\oncbido\IDMDriver\ONCB DriverSet: {1}
17:13:18 4355D5C0 Drvrs: ENG ET:
DirXML Log Event -------------------
Status: Error
Message: Code(-9084) Error in driver state change handler: invalid context (-
670)
17:13:18 4355D5C0 Drvrs: Code(-9092) Unable to log message: {0}
17:13:18 4355D5C0 Drvrs: Code(-9090) Unable to resolve Persistent Log
object \IDTREE\oncbido\IDMDriver\ONCB DriverSet: {1}
17:15:43 483BB2E0 Drvrs: ID to DMZ eDirectory Driver PT:
DirXML Log Event -------------------
Driver: \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to DMZ eDirectory
Driver
Channel: Publisher
Status: Warning
Message: Lost connection to remote tree's Subscriber (the other side may
have been shut down)
17:16:21 444DF580 Drvrs: ID to DMZ eDirectory Driver ST:
DirXML Log Event -------------------
Driver: \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to DMZ eDirectory
Driver
Channel: Subscriber
Status: Error
Message: Code(-9010) An exception occurred: novell.jclient.JCException:
duplicateContext -670 ERR_INVALID_CONTEXT
17:16:21 444DF580 Drvrs: Code(-9092) Unable to log message: {0}
17:16:21 444F6620 Drvrs: ID to ZEN eDirectory Driver ST:
DirXML Log Event -------------------
Driver: \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to ZEN eDirectory
Driver
Channel: Subscriber
Status: Error
Message: Code(-9010) An exception occurred: novell.jclient.JCException:
duplicateContext -670 ERR_INVALID_CONTEXT
17:16:21 444F6620 Drvrs: Code(-9092) Unable to log message: {0}
17:16:21 444F6620 Drvrs: Code(-9090) Unable to resolve Persistent Log
object \IDTREE\oncbido\IDMDriver\ONCB DriverSet\ID to ZEN eDirectory
Driver\Subscriber: {1}
17:16:21 444DF580 Drvrs: Code(-9090) Unable to resolve Persistent Log
object EID=33166: {1}

--------------------------------------------------------------------------------