Login fails during a migration to NetWare 6

(Last modified: 15Feb2003)

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

fact

Novell NetWare 6.0

Novell eDirectory 8.6 (10110.20)

Novell Directory Services 7

Novell Directory Services 6

symptom

Error: "618 -618 0xFFFFFD96 = ERR_INCONSISTENT_DATABASE"

Error: "PKI.NLM could not create an NDS context. (-663)"

Errors appear on the server Console Screen

change

Migration from NetWare 4.x/5.x to NetWare 6

cause

The server being upgraded to NetWare 6 has previously been upgraded from NDS 6.xx or NDS 7.xx. When upgrading from these versions, there was a defect in the original DIBMIG.NLM that shipped with NDS 8 which converted the data incorrectly. The DIBMIG.NLM that ships with eDirectory 8.6.1 (or NW 6) does NOT have this problem. The data that was converted incorrectly was not used until NetWare 6 (eDirectory 8.6 / 10110.20) For this reason, the bad data was not exposed until upgrading to NetWare 6.

NOTE: A -663 error in PKI.NLM will ALWAYS occur if NDS gets an error opening. The -663 error simply says the database is inaccessbile. The key to this problem would be the -618 error in DS.NLM in conjuction with the -663 error in PKI.NLM.

fix

This issue has been resolved with the release of eDirectory 8.6.2. This release can be found at http://download.novell.com under the eDirectory category.

For additional information on eDirectory 8.6, please see the following solution. TID #10066455 - eDirectory 8.6 Readme Addendum

document

Document Title:	Login fails during a migration to NetWare 6
Document ID:	10066043
Solution ID:	NOVL63480
Creation Date:	13Nov2001
Modified Date:	15Feb2003
Novell Product Class:	NetWare 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.