Troubleshoot email issues

If you use Google Workspace Migration for HCL Notes (GWMHN), you might get some issues with migrating email messages. Use the information below to troubleshoot.

Email messages won't migrate

When you receive this issue, email messages don't migrate even though the feeder databases are created and calendar events and contacts have migrated. Migration profiles remain in the Active users view at the end of the migration cycle. Additionally, the email counts appear in the Pending column and there are no errors in the feeder logs.

Expand section  |  Collapse all & go to top

Step 1: Verify the issue

1. Open the user’s original mail file.
2. Open the Migration Status/Mail view.

   The issue is present if you have email in the Sent to Repository category and those messages haven't moved to the Migrated category in the Status view.

Step 2: Check the Domino server

The Domino Router task routes the message from the database to the feeder. Check whether the Router task is loaded on the migration server. If the router isn't loaded, in the Domino console, enter the load router command. After 24 hours, the messages that failed to route are tried again.

If the router is loaded:

1. Check the Domino console when the migration is running or open the migration server’s log (typically Log.nsf).
2. Find errors when GWMHN tries to route mail to the feeder.

   Errors, such as "Remote Server is not a known TCP/IP Host", usually indicate a name lookup problem.

3. Consult your HCL Notes documentation for information on resolving errors in the log.
4. If this resolves the issue, check the server’s mail.box files to make sure they aren't exceeding their storage limits. If they are:
   1. Release any dead mail or, if you think messages are duplicated, delete the mail.box files.

      Important: Make sure you haven't installed GWMHN on the production mail server. If you have, deleting mail.box files could remove messages that aren’t part of the migration.

   2. Restart the Domino server.

      When the server restarts, new files are created and messages are tried again.

5. If the issue isn't resolved, proceed to step 3.

Step 3: Check the logs and tasks

If the above steps don't resolve the problem:

1. Check the logs and tasks on the mail server for errors.
2. Make sure no rules are preventing mail from being routed from the mail server to the migration server.

Email count seems incorrect

Following a migration, you might notice the number of email messages in the source environment exceeds the number of messages migrated.

This discrepancy might be due to the difference between folders in Notes and labels in Gmail. In Notes, when you add a message to a folder, it's shown in both the current folder and the target folder. In Gmail, we add labels to a single message.

To verify all messages have been migrated, check the logs for any errors. For details, go to Export GWMHN logs.

If you think you’re missing some messages, check whether:

• The message, including attachments, is not bigger than 25 MB. You can’t migrate messages bigger than 25 MB. For details, go to Send attachments with your Gmail message.
• Gmail is not blocking an attachment to the message. Gmail blocks certain types of attachments, such as executable files. For details, go to File types blocked in Gmail.
• The message is in a folder or within a date range that’s part of the migration.

_{Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.}