NICI Initialization failed: -1471, Exiting... when starting eDirectory (ndsd)
This document (7011966) is provided subject to the disclaimer at the end of this document.
NICI Initialization failed: -1471, Exiting...
NICI, or remove and then reinstall NICI.
When updating OES, start YaST/YaST2 | Software Management | Search for NICI | select nici or nici64 for 64 bit and select update | select Accept.
When forcing an update on OES, first check for the installed versions of nici, "zypper se nici". Then proceed to force install each required version for example:
zypper in --force nici
zypper in --force nici64
For StandAlone eDirectory use the rpm that was used to install or patch eDirectory. From a command line do:
rpm -Uvh --nodeps <nici rpm>
rpm -Uvh --nodeps nici64-2.7.6.rpm
NICI verification failure on start up.
This error was introduced with the FIPS 140 certified NICI and is present regardless of the certification level of NICI on non-NetWare platforms. Upon loading or being instantiated by a process, NICI runs a set of tests for module integrity as well as cryptographic process integrity. If one of these tests fail, NICI puts itself in an inoperable state and returns this error.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7011966
- Creation Date:15-MAR-13
- Modified Date:09-DEC-16
- NovellOpen Enterprise Server
Did this document solve your problem? Provide Feedback