4. Known Issues

4. Known Issues

The following are some of the most important known issues in Directory Server 7.1 SP6. When possible, supported workarounds are also described.

Bug Number Description Workaround
171140 Upgrading the Windows Sync service on the Windows server from version 7.1 to version 7.1 SP1 or higher (including 7.1 SP6) requires two things:
  • Rebooting the Windows machine.

  • Performing a full manual resynchronization. To manually synchronize Active Directory and Directory Server, open the Directory Server Console, and, in the Configuration tab, click the Replication folder, select the database, and the right-click on the synchronization agreement.

200799 The Directory Server Console allows the internal user SIE to authenticate to login. This account should be prohibited. Log into the Console only as the proper admin user, not the SIE user.
311851 SASL mapping entries are dynamically created and stored in the configuration file at the instance generation. The mapping entries are associated with the primary suffix. If a second root suffix is added and entries under the second suffix need to be mapped by SASL mapping, there are no mapping entries created for them. The original SASL mapping entries point to the first suffix. Manually create SASL mapping entries that are associated with the second suffix.
429631 If a Windows directory is synchronized with a virtual directory tree in Red Hat Directory Server, then the Red Hat Directory Server crashes when synchronization is initiated. Do not use virtual branch entries as the synchronization database.
Table 2. Known Issues in Directory Server 7.1 SP6