Have seen and posted this before but no solution so far:

When stopping edir (or when ndsd crashes on my SLES9 IDM server) sometimes the RL service on Win2k3 that runs the AD driver also stops. Restarting edir of course does not restart the Windows service, so that driver does not continue working automatically. Here's how the RL trace looks like in that case:

DirXML: [05/15/08 14:40:01.14]: ADDriver: object changes complete
DirXML: [05/15/08 14:41:01.14]: ADDriver: Publisher Poll
DirXML: [05/15/08 14:41:01.14]: ADDriver: get object changes - 0x0000
DirXML: [05/15/08 14:41:01.14]: ADDriver: object changes complete
DirXML: [05/15/08 14:42:01.14]: ADDriver: Publisher Poll
DirXML: [05/15/08 14:42:01.14]: ADDriver: get object changes - 0x0000
DirXML: [05/15/08 14:42:01.14]: ADDriver: object changes complete
DirXML: [05/15/08 14:43:01.14]: ADDriver: Publisher Poll
DirXML: [05/15/08 14:43:01.14]: ADDriver: get object changes - 0x0000
DirXML: [05/15/08 14:43:01.14]: ADDriver: object changes complete
DirXML: [05/15/08 14:43:58.07]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Connection Receiver
Level = warning
Message = SSL protocol-violating EOF found or I/O error:
DirXML: [05/15/08 14:43:58.07]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = error
Message = Connection was broken
DirXML: [05/15/08 14:43:58.07]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = fatal
Message = Connection was broken
DirXML: [05/15/08 14:43:58.16]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = error
Message = SSL protocol failure: error:140D00CF:SSL routines:SSL_writerotocol is shutdown
DirXML: [05/15/08 14:43:58.18]: Loader: Stopping driver
DirXML: [05/15/08 14:43:58.19]: ADDriver: Driver::destroy
DirXML: [05/15/08 14:43:58.19]: ADDriver: driver destroy without publisher start
DirXML: [05/15/08 14:43:58.24]: ADDriver: Driver::~Driver()
DirXML: [05/15/08 14:43:58.39]: Loader: Waiting for DirXML to connect on 'TCP server socket, port 8090, address localhost, using SSL'...

From the trace it looks like the RL service would be waiting for a reconnect now, but in fact it stopped a few seconds later. Windows event log has the following:


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 15.05.2008
Time: 14:44:03
User: N/A
Computer: HAMBURGAD03
Description:
The DirXML Loader: C:\Program Files\Novell\RemoteLoader\ADDriver.dll command: 8000 service terminated unexpectedly. It has done this 1 time(s).


Anyone else seeing this? Any known workaround or solution to the issue?

Many Thanks, Lothar