Error -288 opening the Schema Mapping rule in Console One.
(Last modified: 05Dec2002)
This document (10076207) is provided subject to the disclaimer at the end of this document.
symptom
Error -288 opening the Schema Mapping rule in Console One.
In DSTRACE, DirXML could not get the application schema from Active Directory.
fact
Novell DirXML 1.1
Windows 2000 Active Directory
Novell Remote Loader for Active Directory
change
A test bed was setup using two Dell Laptops, one with NW6, and one with w2K. Everything installed and was running fine with one exception. When attempting to open the schema mapping rule with ConsoleOne, it displayed a -288 error. We could successfully create and modify users with no problem on both sides: eDir or AD. We were also running the remote loader on the w2k server with client 4.83e using the May version of the addriver.dll. Attempting to read schema from the Schema Mapping Rule on the AD Driver... We consistently received the message on the NW6 trace screen as follows: "Message= com.novell.nds.dirxml.remote.connectionClosedException: No Document received"
"DirXML Driver Initialization Error!"
Waiting 2 minutes for the Java thread to time out results in:
"Unable to bind DirXML Driver<\Big_Tree\Novell\Dal\dirXMLdriverSet\ADDriver>.DirXML Driver Worker Thread Unable to bind driver, exiting.
cause
There is a bug in the remote loader wither it may not handle large schema documents correctly.
fix
DirXML 1.1a has the fix for this.
document
Document Title: | Error -288 opening the Schema Mapping rule in Console One. |
Document ID: | 10076207 |
Solution ID: | NOVL83572 |
Creation Date: | 29Oct2002 |
Modified Date: | 05Dec2002 |
Novell Product Class: | Novell eDirectory |
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.