The Directory Synchronization may not function, and an error similar to the following appears in the DSA log file:
12/8/2008 12:58:42 PM (GMT-06:00) Common Error 0xe100002e. Scripting error: Source: Description: Line: Line number: 21 Char: 2
You may also notice a message indicating that an external add-in is being loaded:
12/8/2008 12:58:42 PM (GMT-06:00) Target Handlers Manager is loading the external add-in: [Add-in name], module: sth.dll
However, all synchronization jobs have been checked and no custom add-in is in use. How is this possible?
If a custom add-in is selected for a sync job, and that domain pair is then deleted without first removing this add-in, the DSA will continue to load it. This happens because the domain pair is still in ADAM, just marked as deleted.
To resolve this issue, the script must be manually removed from ADAM using ADAM ADSI Edit (or another LDAP tool).
Using ADAM ADSI Edit:
Quest does not provide support for problems that arise from improper modification of
objects using ADSI Edit.
The following statement about ADSI Edit was taken directly from Microsoft:
Warning: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version
3 client, and you incorrectly modify the attributes of Active Directory objects, you
can cause serious problems. These problems may require you to reinstall Microsoft
Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000
Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft
cannot guarantee that problems that occur if you incorrectly modify Active Directory
object attributes can be solved. Modify these attributes at your own risk.
1. Stop all synchronization jobs.
2. Open ADAM ADSI Edit, right-click the root of the tree and select "connect to". In the dialog that appears, specify the ADAM server and port, select "Distinguished Name (DN) or Naming context:", and entering cn=[qmm project name]. You may also need to enter credentials in this dialog if your currently logged in credentials do not have rights.
3. Right-click the new connection, select "New", and "Query".
4. Enter the following LDAP query:
5. Click OK
6. Expand the query, right-click the returned node(s), and click properties
7. Find the attribute "aelita-Amm-ScriptBody". It should equal "EMPTY_[GUID]". If it contains XML data, clear the attribute, then find another attribute that starts with "EMPTY_", and copy this value to "aelita-Amm-ScriptBody".
8. Click OK
Repeat steps 6-8 for each node returned by the query, then restart the synchronization jobs. The DSA should no longer load this add-in, and any script-related errors should disappear.