Error When Recovering M365 Items
Product version: 11.0.4
Last modified: 08 December 2025
Problem
The Microsoft 365 Recovery job fails.
Below are the common causes for Microsoft 365 recovery failures:
-
Issue because of free space in the temporary Java Transporter folder
-
EWS Error Quota Exceeded
-
Maximum number o network connections reached
Temporary Java Transporter Folder Free Space Problem
When attempting to recover Microsoft 365 items, an Internal error message is displayed.
Possible Cause
The Java Transporter temporary directory does not have free space on disk.
-
Java temp folder requires more than 5 GB free space for temporary files.
-
The disk itself should have >10 GB total available.
-
Default temp paths:
-
Windows: C:\Program Files\NAKIVO Backup & Replication\transporter\java\tmp
-
Linux: opt/nakivo/transporter/java/tmp
-
Solution
-
Ensure the Java Transporter temporary folder has at least 5 GB free space.
-
Ensure the system disk has at least 10 GB free.
-
If sufficient space exists but the issue remains, contact support.
Maximum Number of Network Connections Reached
When attempting to recover Microsoft 365 items, the following error message is displayed:
Maximum number of network connections reached on the system
Recovery fails because the operating system has exhausted network connection resources.
Possible Cause
The system has run out of:
-
Buffer space
-
Available ephemeral ports
-
Connection table slots
Solution
To resolve the problem do the following:
-
Increase the maximum number of ephemeral ports. Follow the official Microsoft guide.
-
Close unused connections. Ensure applications and scripts properly close connections when no longer needed.
-
Restart the system if needed. A restart can temporarily free up ports, but increasing limits and closing connections is the permanent fix.