Common Error Solutions
Posted by
@MultCloud December 31, 2024
Posted by
@MultCloud December 31, 2024
Migrate files across different cloud drives without manually downloading and re-uploading.
Sync two clouds or directories in two different cloud drives via one-way or two-way sync.
Backup one cloud data to another cloud for an extra protection and easy recovery.
MultCloud facilitates data transfers between cloud drives, but occasional transfer failures may occur. Below is a list of common errors and their solutions for different cloud drives.
If you don’t see your error listed or the suggested solutions don’t resolve the issue, please contact our support team for further assistance.
Tip: Use Ctrl+F to open the search box and quickly locate the related cloud drive or corresponding error message.
Read timed out
Connect timed out
Connection reset
Connection pool shut down
Connection has been shut down
Connection closed prematurely
Socket closed
Stream closed
Remote host terminated the handshake
Error writing request body to server
These errors typically stem from network instability, servers configuration issues, or resource availability constraints. Common Causes:
Slow Network Connection: The network between the MultCloud transfer servers and the Cloud Drive servers may be slow, often due to the geographical distance between the servers.
Busy Servers: Either the MultCloud servers or the Cloud Drive servers may be experiencing high traffic, leading to delayed responses or interrupted connections.
Solution: Wait for a short period and then retry the transfer.
Solution: You may not have full access permissions to the file. Please check and adjust the permissions on Adrive:
1. Log in to your Adrive account.
2. Right-click on the file and select "Properties."
3. Ensure "Permissions" is set to "Full Access." If not, change it.
4. Return to MultCloud and try the copy process again.
Solution: This error message indicates that the file size you are trying to upload exceeds the maximum file size limit set by the owner of that folder in Box for Business.
In general, the maximum file size limit for uploading to Box Business varies depending on the account type of Box for Business. Please refer to here to learn the limit.
In this situation, you might need to upgrade your Box for Business plan. Or, please consider transferring these files to other cloud storage.
Solution: This error message indicates that requests are being sent to Box for Business too frequently, exceeding the rate limit set by the system. Simply put, too many requests were sent to your box for business in a short period of time.
Reason for Rate Limiting: Box sets rate limits to protect its server resources from problems caused by a single user generating too much traffic.
In this situation, please wait a period of time to retry so that the box recalculates the number of requests. Typically, you will need to wait anywhere from a few minutes to several minutes. The exact wait time depends on your Box account settings and current box server load.
Solution: Please verify that the file name is valid. Typically, Box only supports file or folder names of 255 characters or less; or if the file name contains non-printable characters (/, \, <, >, :, `).
In this situation, you need to modify the file name, and then transfer again.
Solution: This is Dropbox’s rate limit. The rate limit can be triggered when a large number of requests are sent to the Dropbox API in a short period of time; or when multiple threads or instances write to the same folder or file at the same time. The rate limit of the Dropbox API is not a fixed value, but varies according to different factors.
In this situation, you need to wait for a while, then run the task again.
Note: Retrying may also trigger the rate limit again if there is a large amount of data. In this case, you can only retry multiple times, and each retry will transfer part of the file.
Solution: The source file/folder names are not supported in Dropbox and therefore cannot be saved to Dropbox. Typically, Dropbox file/folder name restrictions:
1. Do not use special characters in file names (only @ # $ % ^ & are supported).
2. Do not use the following characters in file or folder names: / \ : * ? “ < > . | and emoticons.
3. Do not add spaces to the end of file or folder names, for example, “Panda .png”.
4. The file or folder path should not exceed 260 characters.
For more details, please refer to here.
In this situation, you need to change the file or folder name and try again.
Solution: There is not enough free space in target Dropbox. Please free more space for target dropbox, and run task again.
Solution: Server internal error! Please try again:
1. If you’re using Copy or Copy to feature, please click Detailed inside the "Progress" message box in the lower right corner of this page. Then choose Unfinished, click to View and click Retry.
2. If you’re using Transfer function, please click Menu of this task, then View Logs, click to view and then click Retry.
Solution: The file may don’t exist or cannot be accessed. Please try following methods to fix:
*Please make sure the file exists in the source. Click Menu of this task, click View Logs and click to view. Open Error Files window and click file path to jump to the source file location;
*Please try to download this file. If it can be downloaded, please try steps below to do another transfer: click Menu of this task, click View Logs, click to view and then click Retry;
Solution: The file may not exist. Please make sure the file exists in the source. Click Menu of this task, click View Logs and click to view. Open Error Files window and click file path to jump to the source file location.
Solution: Please check if there’s a same file name in the target path. If yes, please rename the source file and try to transfer again.
Solution:
Evernote's API will limit the number of times MultCloud can make requests to each Evernote user in an hour. For example: Evernote is integrated into MultCloud, and then a series of Evernote API requests (containing requests for download, list, upload, delete, etc.) are made to the user's Evernote account via MultCloud. If these API requests exceed the rate limit set by Evernote within an hour, any subsequent API requests within that time will cause the Evernote API to throw the rate error RATE_LIMIT_REACHED. And, this error will come with the rateLimitDuration parameter. The value of this parameter indicates the amount of time (in seconds) that must elapse before the user and API key combination will allow another API request. For more details, please refer to here.
In this case, you need to wait for the specified time of the rateLimitDuration before trying again.
Solution: The largest file that can be stored in the note directory is 50MB in size. Check if the source file to be transferred is larger than 50MB.
Solution: Cannot rename or delete the notes content files(.ENML).
Solution: This is a Flickr storage limit.
1. You can only transfer pictures or videos to Flickr.
2. Folders can only be transferred to the "Albums" directory and there can not be subdirectories under the "Albums" directory.
3. Files can only be transferred to the "My Photostream" or "Albums" directory you create.
If you need to transfer some folders to Flickr, and these folders only include pictures or video files, no subfolders, you can use the Cloud Sync feature to sync these folders to Flick\Albums.
Solution: This is a Flickr cloud drive limitation: the Flickr platform requires you to upload at least one photo before you can create an album.
When your Flickr is a brand new account, and there are no photos stored in it yet. Then when you use MultCloud to transfer or synchronize a folder to the “Albums” directory of this flickr, because you have to create the folder first and then transfer the photos, there are no photos in the flickr at this time, it will report this error when you create the folder. (If there are photos in Flickr, MultCloud will copy a photo to the folder when creating the folder.)
In this situation, please upload a photo to Flickr manually on the official site, then transfer the source folders to the “Albums” directory. Or, please use the sync function to sync the photos to the “My Photostream” directory.
Solution: Flickr supports saving pictures and video files only, so please make sure what you transferred are all pictures and video files.
Note:
1. Please make sure that you have read/write permissions before file operations. Otherwise, MultCloud may be unable to transfer files into your FTP.
2. Please make sure that there is enough space for your operations. We are temporarily unable to identify its size.
3. The failure might be caused by the access permission of files, the firewall of FTP, the FTP setting, and so on. Please check if you can download these files to computers by MultCloud. If these files can be downloaded, none of the mentioned factors is the cause. Please send an email to us for further support.
Solution: The IP address of the MultCloud Server is restricted by the FTP Server’s firewall and cannot be connected, please add the IP section(209.126.103.1/19) to the white list of your FTP firewall.
Solution: Increase the maximum number of connections of your FTP server, please set the connect value to a larger value on the FTP Server.
Solution: Increase the maximum number of available users, please set the connect value to a larger value on the FTP Server.
Solution: Probably because there is not enough permission with folder operations, may also because the folder does not exist, and it may also because the folder name is garbled.
*Please find the folder in the FTP Server. If it exists, please check the file’s permission and make sure authorized for all operations. If the file name is garbled, please modify the code and try again; Steps to modify the code:
1. Select the FTP that the file exists, right-click it, and select "Edit";
2. Click "Advanced";
3. Modify the character editing code;
4. Save the changes.
Solution:
*There may not be enough permission with folder operations, please check the file’s permission and make sure authorized to all operations and try again.
*Please remove the FTP from MultCloud, then re-add it and try again.
Solution: There may not be enough permission with folder operations, please check the file’s permission and make sure authorized for all operations, and try again.
Solution:
*The failure might be caused by the access permission of the file, the firewall of FTP, the FTP setting, and so on;
*Please check if you can download these files to computers by MultCloud. If these files can be downloaded, none of the mentioned factors is the cause. Please send an email to us for further support.
When transferring/syncing data from other clouds to Dropbox/Dropbox Business, some files transfer failed with errors:
Solution: This is a Google Photos limitation: the size of the uploaded photo file exceeds the maximum limit allowed by the Google Photos API. The error message clearly states that uploaded photos cannot exceed 209715200 bytes (this number is not fixed), which is about 200MB.
Solution: This error is due to the API call quota limit for Google Photos being reached. This quota limit is to prevent a single user from overusing Google's server resources.
Usually, this is due to sending too many requests in a short period of time (transferring too many files at once) reaching the Google API request quota for a single user. However, Goole does not publicize the number of request quota limits for a single user.
For this error, one can only try to retry the task after some time. Or you can try to contact Google support to request a temporary quota increase to your account.
Solution: Google Photos only stores images, videos and other media files. If you transfer other type files to Google Photos, you will get the error.
Solution: This is a Flickr storage limit.
1. The "Photos" directory can only store images, videos and other media files, but not directories.
2. The "Albums" directory can only store album directories, but not media files.
So, you can create the sync task from Other Cloud\...\XXX to Google Photos\Albums. XXX is the folder that includes subfolders, and every subfolder only include photos and media files. So, it will sync these subfolders to Google Photos\Albums as albums folders.
Or, you can sync from Other Cloud\...\XXX to Google Photos\Photos. XXX is the folder that directly includes photos and media files. not have subfolders.
Solution: This error is due to a large number of requests (uploads, downloads, shares, etc.) being initiated to Google in a short period of time, reaching the maximum number of quota per user for the Google API. Typically, Google contains request and storage limits for a single user:
A maximum of 12,000 requests per minute per user to Google.
A maximum of 750GB of data can be uploaded or copied per user per day; the maximum upload size of a single file is 5TB, but only the first file over 5TB can be uploaded successfully.
In this situation, you can only retry the task on the next day. Usually, google resets this request quota in the early hours of the day (US Pacific Time).
Solution: This error is due to exceeding the number of queries per minute that the Google API allows for the project (MultCloud).
In this situation, you can only try to retry the task after some time.
Note: The number of requests to the project MultCloud is the number of requests that includes all users using Google through MultCloud at the same time.
Solution: The Google API does not allow third parties (such as MultCloud) to download these files. Google does not publish the size and type of files that are restricted for download, MultCloud only gets this error returned by the google api on the actual request.
In this situation, MultCloud can’t help you transfer these files with the errors. You might need to manually download and upload the files via the cloud official site.
Solution: The target Google Drive does not have enough space to save files. You need to make more free space on Google Drive, then run your transfer task again.
Solution: This error is due to the fact that Google's API doesn't provide permission for MultCloud to delete/download/create this file/folder. Please check that you are able to delete/download/create this file/folder on Google's website.
Note:
1. Please make sure that you have read/write permissions before file operations, otherwise, MultCloud may be unable to transfer files into your HiDrive.
2. Please make sure that there is enough space for your operations. We are temporarily unable to identify its size.
Solution:
1. It is possibly because the HiDrive account has not set read permission for the file.
Visit the HiDrive official site, and log in with your HiDrive account. Navigate to "Settings" -> "Account management" -> "Account settings" -> "Read and write access", check "Read-only access to the shared folder("public")" and "Write access to the shared folder("public"). Then go back to Multcloud and refresh the page to try again.
2. It is possibly because MultCloud authentication credentials are expired. Follow the steps below to re-add HiDrive and try again please:
Right-click on the HiDrive and select Remove; click Add Clouds -> select HiDrive -> enter account and password -> click ADD HiDrive Account.
Solution:
1. These 3 folders, HiDrive’s root directory, "user" folder and ".hidrive" folder in the "users" account folder, are not allowed to create files or upload files. You can go to the "Public" folder or the corresponding account folder in "users" to create new files or upload files.
2. It is possibly because the HiDrive account has not set read permission for the file. Visit the HiDrive official site, and log in with your HiDrive account. Navigate to "Settings" -> "Account management" -> "Account settings" -> "Read and write access", check "Read-only access to the shared folder("public") "and "Write access to the shared folder("public"). Then go back to Multcloud and refresh the page to try again.
3. It is possibly because MultCloud authentication credentials are expired. Follow the steps below to re-add HiDrive and try again please: Right-click on the HiDrive and select Remove; click Add Clouds -> select HiDrive -> enter account and password -> click ADD HiDrive Account.
Solution: It is possibly because the HiDrive account has not set read permission for the file. Visit the HiDrive official site, and log in with your HiDrive account. Navigate to "Settings" -> "Account management" -> "Account settings" -> "Read and write access", check "Read-only access to the shared folder("public")" and "Write access to the shared folder("public"). Then go back to Multcloud and refresh the page to try again.
Solution: The possible reasons for this error:
Concurrency Conflict: The MultCloud app and iCloud client may try to operate on the same synchronization area at the same time, resulting in a conflict.
Network issues: Network instability or latency may cause requests to fail.
iCloud service issues: The iCloud service itself may be temporarily down.
Since errors are usually temporary, you can try re-adding iCloud/iCloud Photos to MultCloud and re-transfer.
Solution: iCloud does not allow file names longer than 250 characters. So to the point where the filename of the file you are transferring to iCloud exceeds 250 characters will return this error. Please try to change the shortened file name and transfer it again.
Solution: This error is because the iCloud Photos feature is not enabled on your Apple account. Please make sure you're signed in to your iCloud account on your device or on the web, and check that the "Photos" option is turned on in your iCloud settings:
1. On your iPhone, iPad, or Mac, find and open the Settings app on your device.
2. In the Settings app, tap on your Apple ID, usually at the top of the screen.
3. Once you've tapped your Apple ID, find and tap “iCloud.
4. In the iCloud settings, find “Photos” and tap on it. In the “Photos” section, you'll see an on/off switch, so turn it on.
Once turned on, the photos on your device will be automatically uploaded to iCloud and you will be able to view and access them on other devices.
Solution: iCloud Photos only supports storing “jfif”, “pjpeg”, “jpeg”, “pjp”, “jpg”, “heic” file types.
Solution: Too many requests for iCloud Photo caused a timeout, please wait a while and retry.
Note: If the amount of data is relatively large, you may need to retry multiple times. Each retry will transfer part of the file.
Solution: Make sure if the file to be transferred is an empty file, namely file size is 0KB, because MeidaFile does not support empty file transferring.
Solution: Make sure the folder name of the folder to be transferred does not include the following special characters: # % * : < > ? / \ |, because MediaFire does not support these characters as file name or folder name. Rename the source file and try again, please.
Solution: MediaFire needs to know the file size before saving it. When processing the file, the real file size has to be the same as the predicted. Otherwise, it will fail. You can use another cloud drive to transfer the file, please try the following steps:
1. Transfer the file to another cloud drive;
2. Transfer that file from another cloud drive to MediaFire.
Solution: For this error, please clear your browser cache and try the transfer again.
Solution: This is a Mega-specific error code that indicates that you have exceeded the limit of command weights initiated within a certain period of time.
About command weights: Each operation performed on Mega, such as uploading a file or creating a folder, has a specific weight. There is a limit to the total number of command weights you can execute in a certain period of time.
You may have tried to upload too many files or folders in a short period of time; or you may have uploaded a very large file and reached Mega's command weight.
In this situation, please wait a while and retry.
Note: If the amount of data is relatively large, you may need to retry multiple times. Each retry will transfer part of the file.
Solution: This is a specific error code given by Mega indicating that your upload request could not be processed due to a temporary server issue or network congestion. This may be because Mega's servers are under high load at this time, causing temporary congestion; or temporary network instability or high latency may be preventing the request from reaching Mega's servers; or a temporary error.
In this situation, please wait a while and retry.
Solution: A temporary network error caused the download of the file to fail. Please try again.
Solution: Mega limits the bandwidth of free Mega accounts. When the traffic transferred from Mega reaches the bandwidth limit, an error occurs. You can wait a few hours and then retransmit. Or upgrade your Mega account to VIP.
Solution: Access to the requested resource is denied. It is possible that the user's Onedrive account does not have sufficient permissions.
Reasons for this may include:
Your account may not have been granted permission to access the resource (read, write, or download).
If the resource is shared with you by someone else, the person who shared it may have restricted your level of access, such as not allowing downloads.
If you belong to a group, the permissions of that group may affect your access.
You can log in to the same account on the OneDrive official website to check if you can access the resource.
Solution: OneDrive does not support file names containing special characters: “*: < >? / \ | as well as ending with a period or starting with a period are not supported. And, leading and trailing spaces in file or folder names are also not allowed.
Please modify the file name and retransfer.
Solution: In Microsoft 365, the total decoded file path (including the file name) for OneDrive Business, and SharePoint cannot exceed 400 characters. This limit applies to the combined lengths of folder paths and file names in their decoded form.
For example, when transferring a file to OneDrive for Business or SharePoint, if the combined length of the source and destination paths exceeds 400 characters, the transfer will fail.
To resolve this issue, shorten either the source or destination path, or rename the file/folder to reduce the total character count before retrying the transfer.
Solution: MultCloud currently doesn’t support transferring OneNote files.
Solution: The file or folder you are looking for is no longer in its original location, or you do not have permission to access it. Reasons for this may include:
File deleted: The file may have been accidentally or intentionally deleted by you or someone else with permission.
File moved: The file may have been moved to another location in OneDrive or even to another cloud drive.
Insufficient permissions: You may not have permission to view the file. This may be due to a change in sharing settings or access permissions.
Please log in to the OneDrive website to check if the file exists or you don't have permission to access it.
Solution: This is the OneDrive quota limit:
Subscription Plans: Different subscription plans for OneDrive offer different storage space and upload limits.
Network conditions: Network speed and stability can affect upload speeds and concurrent task limits.
File types: Different types of files (such as images, videos, documents, etc.) may have different upload limits.
Quota recovery time depends on the API's restriction policy; Microsoft does not publicize a definitive recovery time, but the restriction is usually lifted automatically between a few minutes and a few hours. It is recommended to wait a while before attempting to re-run the task.
Solution: Too many requests were initiated in a short period of time, reaching the OneDrive for Business API call frequency limit.
The duration of the limit depends on the limiting policy of the API; Microsoft does not publicize a clear recovery time, but the limit is usually lifted automatically between a few minutes and a few hours. Users are advised to wait a while before attempting to re-run the task.
Solution: OneDrive for Business account configuration issue, please see here:
Solution: This error message indicates that the OneDrive for Business API was unable to find the user's MySite.This could be due to several reasons:
User does not have a MySite: The user may not have a MySite associated with their OneDrive for Business account. This may be because they are a guest user, or their account has been deleted or disabled.
Incorrect user ID: The user ID provided in the API request may be incorrect or invalid.
Insufficient API permissions: Your application may not have the necessary permissions to access the user's MySite.
Please see here to configure permission.
Solution: SugarSync does not allow you to create files or folders in the root directory. Choose a subdirectory or other directories, please.
Google Drive
Google Workspace
OneDrive
OneDrive for Business
SharePoint
Dropbox
Dropbox Business
MEGA
Google Photos
iCloud Photos
FTP
box
box for Business
pCloud
Baidu
Flickr
HiDrive
Yandex
NAS
WebDAV
MediaFire
WEB.DE
Evernote
Amazon S3
Wasabi
Cubby
ownCloud
MySQL
Egnyte
Putio
ADrive
SugarSync
Backblaze
CloudMe
MyDrive
Cubby