Novell Home

My Favorites

Close

Please to see your favorites.

DirXML driver won't start with KMO specified.

(Last modified: 29Aug2002)

This document (10074000) is provided subject to the disclaimer at the end of this document.

symptom

DirXML driver won't start with KMO specified.

Everytime the customer would add the DirXML Certificate to the authentication context, the driver would give a FATAL error and the driver would unload.

change

Customer had two trees using the NDS2NDS driver.  He followed the documentation for creating a single CA for two tree's a number of times.  The NW6 side worked fine with the CA.  The NW51 tree would not work with the KMO and they were positive that the cut and paste from the issued certificate was good.

cause

The KMO would even validate but there was still something wrong.  PKI on the NW51 server was broke after they had deleted and recreated the Security objects and CA. 

fix

Had them download and run PKIDIAG on both NW51 and NW6 servers and that fixed the problem.  The driver started up with no problems.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10074000
  • Solution ID: NOVL81919
  • Creation Date: 29Aug2002
  • Modified Date: 29Aug2002
    • NetIQeDirectory

Did this document solve your problem? Provide Feedback