Error -9010 while creating a user in eDirectory with IDM

  • 3963545
  • 28-Nov-2007
  • 26-Apr-2012


Novell Identity Manager 3.5
Novell Identity Manager 3.5.1


The error -9010 means that something went wrong in the underlying Java pieces of a driver, and it provides further information by adding a Java Stack right after the error message. To be able to properly identify if your problem is the one in this TID, you have to look at the first few lines of that Java Stack, and they need to match to the one bellow:

[11/28/07 10:00:13.333]:AnyDriver PT:Pumping XDS to eDirectory.

[11/28/07 10:00:13.334]:AnyDriver PT:Performing operation add for lab\users\testuser001.

[11/28/07 10:00:13.338]:AnyDriver PT:Adding entry lab\users\testuser001.

[11/28/07 10:00:13.338]:AnyDriver PT:Creating RDN testuser001 in context lab\users.

[11/28/07 10:00:13.346]:AnyDriver PT:

DirXML Log Event -------------------

Driver: \NTS-LAB076\lab\DriverSet\AnyDriver

Channel: Publisher

Object: testuser001 (lab\users\testuser001)

Status: Error

Message: Code(-9010) An exception occurred: java.lang.NullPointerException

at com.novell.nds.dirxml.engine.XmlInputProcessor$OperationProcessor.checkWriteManaged(

at com.novell.nds.dirxml.engine.XmlInputProcessor$AddProcessor.doJClientCall(

at com.novell.nds.dirxml.engine.XmlInputProcessor$OperationProcessor.makeCall(

at com.novell.nds.dirxml.engine.XmlInputProcessor$AddProcessor.process(

at com.novell.nds.dirxml.engine.XmlInputProcessor.processOperationElement(

at com.novell.nds.dirxml.engine.XmlInputProcessor.process(



The operation being sent (first XML block above the"Pumping XDS to eDirectory" in the trace) has one or more attributes that does not exist in the destination eDirectory server. The schema might not have been extended properly, or there might be a schema synchronization issue in your environment.
One way to check is to use iMonitor on the IDM server receiving the operation to verify that all attributes in the operation are present in the local server's schema. Upon finding which attributes are missing, you need to extend schema properly for those or in the case they are present on the tree but not on the IDM server (schema synchronization issue), do an eDirectory Health Check in your system and fix any issues found in the Health Check.
TID 3564075 has the procedures for an eDirectory Health Check