System information

Known Issues and Limitations
Page 16 of 3 2Directory Server 5. 22004Q 2 •Release Notes
2.
Click Edit and modify the suffix in the User directory subtree field.
3.
Click OK to save the change.
Error message with migrateInstance5 (#4529552)
When running the
migrateInstance5
script with error logging disabled, a message is displayed
indicating that the migration procedure is attempting to restart the server while the server is
already running.
If error logging is disabled, you can ignore this error message.
If this message appears when error logging is enabled, consult the error log for more information.
User enters into a loop if an incorrect password is entered during command-line installation (#4885580)
Workaround
When prompted for the password again, type “<“ to return to the previous input item, and then
press return to keep the previous choice. When the password is requested again, enter the correct
password.
Running the pkgrm command does not remove all the Directory Server distribution packages
(#4911028)
Installation failure occurs if the administration domain of the remote directory being used to configure
Directory Server does not exactly match the administration domain in the setup procedure. (#4931503)
Workaround
During installation use the exact same administration domain as defined in the remote
configuration directory.
The startconsole command may fail to start certain servers if the user running the command does not
have write access to the ServerRoot directory (#5008600)
To access certain servers Server Console may have to download JAR files into the ServerRoot
directory. If the user running the
startconsole
command does not have write access to the
ServerRoot directory, the console will refuse to open the servers in question.
Workaround
Either run the
startconsole
command as the user who owns the ServerRoot directory or install and
configure the server packages on the host running Server Console.