b.Be sure a synch has been done. Look at the UI for step 5 of the configuration to see when the last replication was done. If there is no time given for the last replication then hit the “Sync Now” button. Even if a replication had been previously done it is possible the “Clear LDAP Cache” button may have been hit by mistake so “Synch Now” should still be run.
c.Even when the test for LDAP retrieval passes, there can occasionally be problems when a full replication is done. (The test itself does not put any addresses in the database, it just retrieves the first 5 addresses and displays them).
i.If you are using version 5.01.50 or greater open the Address Book Manager and check the area highlighted in figure 3 above. In this version of code and later the number of replicated LDAP addresses in the database will be displayed (this information is not shown in figure 3).
ii.If you are using a version of DSS earlier than 5.01.50 it will be necessary to use an external tool to look at the database and see if there are actually LDAP addresses in the database. SQL Server Management Studio Express (SSMSE) is a common tool. A version appropriate for the default DSS 5 database can be downloaded from: http://www.microsoft.com/en- us/download/details.aspx?id=7593. Installing SSMSE can be a little confusing, I find that a good set of instruction are here:
iii.If the test passes, but there are no LDAP addresses in the database, then there may be something wrong with the configuration. One issue that can occur on some systems (although we do not yet understand when or why) is when the advanced search options in step 3 of the configuration have the settings of
“Unlimited Addresses” and “Maximum Search Time” as shown in the screenshot below. If LDAP addresses are not getting to the DSS database, and if these are the current settings, change the Maximum LDAP Addresses setting to
“5,000 Addresses” and the Maximum Search Time setting to “5 minutes”. Then
Page 6 of 7 | white paper |