
Bug
Number
Description Workaround
and Export tasks in the
Tasks).
• Using an absolute path to
import or export an LDIF file to
the remote machine (through
both the Configuration and the
Import and Export tasks in the
Tasks).
However, importing or exporting
the database to the remote
machine will fail if you supply a
relative path.
When importing or exporting
databases on a remote machine,
do not use relative paths for the
LDIF. Always supply the absolute
path or use the Browse button to
select a file.
426421 If both Password Sync and the Directory
Server Console are installed on the same
Windows machine, then the Directory Server
Console will load the Password
Syncnss3.dll, and will fail when it attempts
to open.
Do not install Password Sync
and the Windows version of the
Directory Server Console on the
same machine.
426439 When using the Console to install a CRL, if
the CRL is placed in the proper directory,
/etc/dirsrv/slapd-instance_name, the
Console returns an error that it cannot locate
the file.
Put the CRL in the Administration
Server directory,
/etc/dirsrv/admin-serv, and
the Console can locate the CRL
file automatically.
427321 If a Directory Server instance is migrated from
a previous version to Directory Server 8.0, the
nsslapd-saslpath is not migrated with the
dse.ldif on the new 8.0 instance, so that the
SASL libraries cannot be loaded. This
configuration attribute is properly created in
fresh Directory Server installations.
Use ldapmodify to edit the 8.0
dse.ldif file and add the
nsslapd-saslpath set in the
previous version.
Table 2. Known Issues in Directory Server 8.0
Red Hat Directory Server 8.0 Release Notes
14
Komentarze do niniejszej Instrukcji