Release Summary › Known Issues › Known Issues Affecting All Operating Systems

Known Issues Affecting All Operating Systems

Issues with DXmanager

DXmanager contains the following minor issues:

• The configuration dialog box may flicker when moving the mouse or entering data, when connected to DXmanager over a latent connection
• There is currently no field validation performed against IP addresses. Care must be taken to ensure these items are syntactically correct otherwise features relying on them will not function as expected.
• A log-in after a timed-out session is sometimes rejected with a “Resource Temporarily Unavailable” error. A subsequent log-in will work fine.
• If an edit session times out, a user may be blocked from selecting nodes on the Map view to edit. If this occurs, the current configuration can be edited by going into Configuration -> Edit version and selecting the most recently saved version.

Cryptic Error Message Using the DXdumpdb -i Option

When you use the DXdumpdb tool, you have to include all naming attributes in the –i option. If any naming attribute is missing, the operation fails and the following message appears:

Entry has no attributes

Note: For more information about the -i option, see DXdumpdb Tool—Export Data from a Datastore to an LDIF File

Action Required After DXmanager Upgrade

After you upgrade DXmanager, you must restart all Internet Explorer sessions running DXmanager before you can see the new functionality.

In addition, if you switch back and forth between different versions of DXmanager on the same computer, you must clear the Java cache each time you go back to the older version. For more information about how to clear the Java cache, see the Administration Guide.

IE7 Maintains DXmanager Session After Tab is Closed

In Internet Explorer 7, if you have logged in to DXmanager, closing the tab does not terminate the session. This means that if you re-open the tab, or open a new tab to the same address, the browser continues the session without requiring you to log in again. This can present a security risk.

To work around this issue, log out of DXmanager before you close the tab, or close the browser, not just the tab.

DXmanager Only Allows One DXadmind Port and Password

DXmanager can store only one port number and password for the DXadmind processes on every computer.

This means that during installation, you should set the same values for these on each host.

After installation, when you are using DXmanager to set up the directory backbone, you will specify the DXadmind port and password that you set during the installation.

DXmanager May Incorrectly Show a Stopped or Started DSA as Initializing

After deploying a new configuration, DXmanager may incorrectly show a DSA as initializing, when the DSA is, in fact, stopped or running.

To update the state of the DSA and correct the display, do the following:

1. Right click on the DSA icon.
2. If the Start DSA and Stop DSA options are available, click one of these.

   If these options are not available, restart CA Directory Webserver.

   This will change the DSA to the selected state, and the display will be correct.

DXmanager Chart Issues

The following DXmanager chart issues exist:

• DXmanager charts are not updated if none of the DSAs being charted are running.
• DXmanager charts do not display correct information after you deploy a new configuration.

To work around this issue, re-request the chart. To do this, navigate to a configuration page and then back to the main tabbed page for charts on the dashboard. Alternatively, clear then redefine a chart request for the charts tab.

DXmanager Does Not Validate All Data Entry Fields

If you deploy a configuration with invalid settings, DXserver will not start. Take care when entering configuration values.

DXmanager Drop-down Menus Show Unexpected Behavior

Some second level drop-down menus display the options you can select at a random location on the screen. To work around this, select the second level tabs directly.

No Monitoring in a Pure IPv6 Environment

Monitoring in a pure IPv6 environment does not work. This means that DXmanager does not provide:

• Statistics (for example, graphs)
• Status of running DSAs updated in real time
• Error messages from the DSA (for example: why a DSA could not start, data files filling up, and so on).

Note: Monitoring does work in an IPv4 or IPv4/IPv6 hybrid environment.

Cannot Start DSA after Upgrade from CA Directory 8.1

The following settings are no longer valid. Remove them from your configuration:

set limit-list = true|false;
set limit-search = true|false;
set eis-count-attr = dxentrycount;