Troubleshooting Common Issues with CodeTwo FolderSync Addin
1. Installation fails or Add-in doesn’t appear in Outlook
- Possible causes: missing prerequisites, blocked by Outlook/Windows policies, corrupted installer.
- Fixes:
- Ensure Outlook version and bitness match the installer (32-bit vs 64-bit).
- Run installer as Administrator.
- Check Windows Event Viewer and Outlook’s Add-in Disabled Items (File → Options → Add-ins → Manage Disabled Items).
- Temporarily disable antivirus or application control that may block installation; re-enable after install.
- Repair Office installation (Control Panel → Programs → Microsoft Office → Change → Repair) if Outlook shows errors.
2. FolderSync Addin shows “Cannot connect” or sync fails
- Possible causes: network issues, authentication problems, firewall/port blocking, outdated add-in.
- Fixes:
- Confirm network connectivity to the target Exchange/Office 365 server; ping or test connection.
- Re-enter credentials and verify account permissions for shared folders.
- Ensure necessary ports (HTTPS/443) are open and proxy settings aren’t interfering.
- Update to the latest CodeTwo FolderSync Addin build.
- Check for OAuth token expiration if using modern auth; re-authenticate.
3. Changes in one mailbox don’t appear in the other
- Possible causes: sync schedule/settings, large items or attachments, folder mapping issues.
- Fixes:
- Verify sync rules and folder mappings in the add-in’s configuration.
- Force a manual sync from the add-in UI to test immediate replication.
- Check item size limits—split large attachments or enable attachments syncing if supported.
- Inspect synchronization logs for errors or skipped items (see log file location in add-in settings).
- Ensure both mailboxes have sufficient storage quota.
4. Duplicate items created after sync
- Possible causes: interrupted syncs, differing item IDs between systems, incorrect conflict handling.
- Fixes:
- Review conflict resolution settings; set consistent rules (e.g., newest wins).
- Clean up duplicates using Outlook’s built-in tools or third-party de-duplication utilities.
- Analyze logs to identify when duplicates were created and correlate with network interruptions.
- If duplicates persist, perform a full resync: disable sync, remove local sync metadata, then re-enable.
5. Permissions and access errors for shared folders
- Possible causes: insufficient mailbox delegation, incorrect sharing permissions, Exchange policy changes.
- Fixes:
- Confirm the user account used by FolderSync has Full Access and Send As permissions where required.
- Reapply sharing permissions in Exchange Admin Center or via PowerShell (Add-MailboxPermission).
- Check for recent Exchange or tenant changes that may affect shared mailbox access.
- Validate permissions by accessing the shared folder directly in Outlook.
6. Performance issues or high resource usage
- Possible causes: large folder trees, high sync frequency, limited client resources.
- Fixes:
- Limit scope: exclude nonessential folders from sync.
- Reduce sync frequency during peak hours.
- Ensure the client machine meets CPU/RAM requirements; close unnecessary apps.
- Check for add-in updates that include performance improvements.
7. Log locations and how to collect them for support
- Steps:
- Open FolderSync Addin settings → Diagnostics.
- Enable verbose logging if available and reproduce the issue.
- Note timestamps and affected mailboxes/folders.
- Compress log files and include a brief description when contacting CodeTwo support.
8. When to contact CodeTwo support
- Contact support if:
- Errors persist after trying the fixes above.
- Logs show internal add-in errors or exceptions.
- You need help interpreting logs or performing advanced diagnostics.
- Provide support with: Outlook version, Windows build, FolderSync Addin version, exact error messages, and collected logs.
Quick checklist (ordered)
- Verify Outlook/add-in compatibility and install as Admin.
- Confirm network, ports, and authentication.
- Check folder mappings, sync schedule, and storage quotas.
- Inspect logs and enable verbose logging if needed.
- Adjust permissions and conflict resolution settings.
- Contact CodeTwo support with logs and environment details.
If you want, I can convert this into a printable checklist, a troubleshooting flowchart, or a step-by-step script for collecting logs.
Leave a Reply