Troubleshooting

• Exchange Directory names used in the Placement policy are case-sensitive.
• If Exchange and eDirectory^TM are running on the same machine, you must disable the eDirectory LDAP server or change the port assignment from port 389.
• If you encounter syntax errors in XML, use the Web browser required by Nsure^TM Identity Manager to verify the syntax.
• The authentication credentials you specify should be for an NT account/domain that has rights to the Exchange Directory.
• CN and Object-Class should not be in the filter.
• If there is an invalid attribute in the filter (for example, one for which Schema Mapping is not defined), the following happens:
  • At each polling loop, the Publisher fails to synchronize the class that contains the invalid attribute, and gives an error indicating an unsupported attribute.
  • The driver is still able to start.
  • The Subscriber channel still functions correctly unless the invalid attribute is referenced. A task that references an invalid attribute gives an error and is not successful.

  The sample driver configuration supports the standard attributes in Exchange, so this issue could occur only for custom attributes you have added in Exchange.

• The DirXML^® Driver for Exchange supports the following classes:
  • Distribution List
  • Remote
  • Mailbox