We are seeing this, in a SOAP driver, every so often...

[01/08/13 06:52:39.845]:My-Objects :
DirXML Log Event -------------------
Status: Error
Message: Code(-9139) Unable to process DirXML sub-verb
DSVR_OPEN_DRIVER_ACTION because driver \STAGING-IDM\s
ervices\Staging Driver Set\MyApp MAD is not running.
[01/08/13 06:52:39.856]:WD-Objects :
DirXML Log Event -------------------
Status: Error
Message: Code(-9140) Error processing DirXML sub-verb
DSVR_OPEN_DRIVER_ACTION: com.novell.nds.dhutil.DSErr:
-333 (0xfffffffffffffeb3)
at
com.novell.nds.dirxml.engine.verb.OpenDriverAction .remoteOpenDriverAction(OpenDriverAction.java:223)
at
com.novell.nds.dirxml.engine.verb.OpenDriverAction .processSubVerb(OpenDriverAction.java:165)
at
com.novell.nds.dirxml.engine.verb.DirXMLVerbs$SetV erbHandler.processVerb(DirXMLVerbs.java:585)
at
com.novell.nds.dhutil.VerbProcessor$HandlerThread. run(VerbProcessor.java:507)
at java.lang.Thread.run(Unknown Source)


333 is an eDir, No connection error.

Newer IDM (4.x something), dunno if 100% patched or not. But anyone
ever seen this sort of thing?

Almost like an attempt to open the MyApp MAD driver is getting
incorrectly targeted at the SOAP driver? Odd.