To resolve this issue, check for socket errors in the tmuDump.txt located in SMID install path>\...\AU_Data/AU_Log/TmuDump.txt.

When socket errors have been resolved but you still encounter the issue, do the following:

1. If you have several Domino servers, try to delete the replication conflicts in smency.nsf.

   1. Open the smd update database from the source server.
   2. Perform the Delete replication conflicts action.
   3. Reproduce the issue.

2. Recreate the smency.nsf file.

   1. Copy a new smency.ntf file to your server and replace the old one. The new smency.nsf file is available in the SMID installation package, or from a running SMID server.

   2. Create a new smency.nsf database from the template, smency.ntf. To do this:

      1. Go to File > Database > New and specify the New Database Name and Location.
      2. Select the Domino server.
      3. Set "smd\smency.nsf" as the File name.
      4. Set "ScanMail Update Database" as the Title.
      5. Specify Template for New Database then select Domino server. Select Show advanced templates > ScanMail Update Database.
      6. Click OK.
      7. When prompted “Replace existing SERVER_NAME smd\smency.nsf?”, answer “Yes”.