Error: "Invalid API"

(Last modified: 18Nov2002)

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

fact

Novell eDirectory 8.7 for All Platforms

Novell eDirectory 8.6 for All Platforms

symptom

Error: "Invalid API"

cause

The administaration guide for eDirectory 8.7 (Table 4 entitled "DSREPAIR Versions" in the section "Updating the eDirectory Schema for Netware") states that if you are running NDS version 8.51 or later, you should copy the DSREPAIR.NLM from the PATCHES\DSREPAIR\NWNDS8\ directory and run the Post Netware 5 Schema Update option.  This statement is misleading in that DS 8.51 or later is for NDS 8 only.  It does not include eDirectory 8.5, eDirectory 8.6 or eDirectory 8.7.  (There is similar documentation in the "Updating the eDirectory Schema for Windows NT/2000" section.  This solution applies to that system as well.) The version of DSREPAIR.NLM that ships in the above directory is DSREPAIR for eDirectory 8.7.  Although this is not a necessary step if you are running eDirectory 8.6.x or higher, the operation itself should work.

fix

This should not be an issue.  If eDirectory 8.6.2 or higher is on the server in question, this step can safely be skipped.

This problem has been reported to development.

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742  - eDirectory 8.7 Readme Addendum

note

The error on the console screen will show as follows:
DSREPAIR INTERNAL INTERFACE: 99
DSREPAIR API INTERFACE: 101
DS API: 98

document

Document Title: Error: "Invalid API"
Document ID: 10076875
Solution ID: NOVL84123
Creation Date: 18Nov2002
Modified Date: 18Nov2002
Novell Product Class:Novell Directory Services

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.