The Resource Has Been Modified Please Retrieve the Resource Again and Retry

The All-in-One WP Migration plugin communicates with your Box account and stores backups using the Box API. If there is a trouble communicating with your Box and the files in your business relationship, you may receive one of these errors.
Box cloud storage allocates a per-user quota to each user to distribute resources fairly. Yous may experience problems if yous have a large number of other applications or systems connected to your Box.

What can you practise about information technology?

Please see the listing of fault codes below for more information on each one:

Invalid Credentials
The All-in-I WordPress Migration Plugin is unable to connect to your Box. Please sign out of your Box account and sign back in to the Box Settings plugin on your WordPress Console.

The user does not have sufficient permissions for file
The All-in-One WP Migration Plugin is unable to access whatsoever files or folders on your Box. Please ensure that the file or folder you are attempting to access with the plugin is accessible via your Box account.
If this does not work, or if the file is on your Box drive, please sign out of your business relationship and sign back in to the Box Settings page of the plugin on your WordPress Console.

Cannot exist used inside the domain
The All-in-One WP Migration Plugin is unable to connect to your Box. If you're attempting to backup or drift your site while logged in on a corporate domain, brand certain you can admission your Box business relationship or contact the domain ambassador.

File not found
The All-in-One WP Migration Plugin is unable to access any files or folders in your Box account. Please double-bank check that the file exists and that you lot can admission information technology via your Box.

Backend Error
While processing the asking, an unexpected fault occurred with your Box storage. Delight attempt once more. Please sign out of your Box account and re-sign in to the Box Settings page of the plugin in your WordPress Console.

Bad Request
The All-in-Ane WP Migration Plugin is unable to connect to your Box account. Please sign out of your Box account and sign back in to the Box Settings of the plugin on your WordPress Panel.

User Rate Limit Exceeded
On your Box account, there accept been besides many API calls. After stopping drive sync and any other applications that connect to your Box and waiting five minutes, try once more.

Rate Limit Exceeded
On your Box account, at that place have been too many API calls. Later on stopping bulldoze sync and any other applications that connect to your Box and waiting 5 minutes, endeavor once more.

Sharing Rate Limit Exceeded
You have reached your Box account's sharing rate limit. This could be related to emails or documents that you lot are publicly sharing from your Box. When performing backups/migrations, avoid sending big volumes of emails. Remove permissions from publicly accessible files in your Box storage.

The user has not granted admission to the file
The All-in-One WP Migration Plugin is unable to access any files or folders on your Box. Please ensure that the file or folder you are attempting to access with the plugin is attainable via your Box account. If this does not piece of work, or if the file is already on your Box storage, please sign out of your account and sign dorsum in to the Box Settings page of the plugin on your WordPress Console.

Too Many Requests
There have been an excessive number of requests on your Box account. This could be related to documents you're publicly sharing from your Box storage or other applications that use your account.

Here is a consummate list of HTTP error codes:

*press control F to search this folio

Code: 400 'Bad Asking'
Unable to perform Box request

Code: 401 'Unauthorized'
The authorization token is not authorized. Authentication is required and has either failed or has yet to be provided.

Lawmaking: 402 'Payment Required'
You must pay for the product in society to proceed.

Code: 403 'Forbidden'
Forbidden access. The request was valid, simply the server is refusing activeness. The user might not have the necessary permissions for a resource, or may demand an account of some sort.

Code: 404 'Not Found'
Could not find the resources. Could not detect the requested resource merely it may be available in the future. Subsequent requests past the customer are permissible.

Lawmaking: 405 'Method Non Allowed'
Method not immune. The API functioning does non let the HTTP method.

Code: 406 'Not Acceptable'
The requested resource is capable of generating only content non adequate according to the Accept headers sent in the request.

Code: 407 'Proxy hallmark required'
Proxy hallmark required. The client must first authenticate themselves with the proxy.

Code: 408 'Asking Timed Out'
Request timed out. The server timed out waiting for the asking. The client did not produce a request within the time that the server was willing to await.  Echo the asking without modifications at whatsoever later time.

Code: 409 'Conflict'
The conflict does not let the request to process.

Code: 410 'Gone'
Indicates that the resources requested is no longer bachelor and will not be bachelor over again. This should exist used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the futurity.

Code: 411 'Length Required'
Length required. The request did not specify the length of its content, which the requested resource requires.

Code: 412 'Precondition Failed'
The server does not meet one of the preconditions that the requester put on the request.

Lawmaking: 413 'Asking Entity Also Large'
Request entity too big. This error occurs when the size of the upload is more than the allowed maximum.

Lawmaking: 414 'Request-URI Too Long'
Request-URI too long. The URI provided was too long for the server to process.

Code: 415 'Unsupported Media Blazon'
Unsupported media type. The asking entity has a blazon which the server or resource does not support.

Code: 416 'Requested Range Not Satisfiable'
Requested range not satisfiable. The client has asked for a portion of the file, but the server cannot supply that portion.

Code: 417 'Expectation Failed'
Expectation failed. The server cannot see the requirements of the Expect request-header field.

Code: 500 'Internal Server Mistake'
Internal server error. This is a generic error message, which is given when you come across an unexpected status and no other specific message is suitable.

Code: 501 'Not Implemented'
Not implemented. The server either does not recognize the request method, or it lacks the ability to fulfil the request.

Code: 502 'Bad Gateway'
Bad gateway. The server was acting equally a gateway or a proxy and received an invalid response from the upstream server.

Code: 503 'Service Unavailable'
Unavailable. Please check Box API status page for information: https://condition.box.com/. The server is currently unavailable (because it is overloaded or downwards for maintenance). More often than not, this is a temporary country.

Code: 504 'Gateway Timeout'
The server was acting every bit a gateway or proxy and did not receive a timely response from the upstream server.

Code: 505 'HTTP Version Not Supported'
The server does not support the HTTP protocol version used in the request.

Here is a complete list of Box API errors:

*press control F to search this folio

Error: bad_digest
The specified Content-MD5 did non match what nosotros received. While uploading a file, a Content-MD5 header with the SHA-ane hash of the file can be supplied to ensure that the file is not corrupted in transit. The SHA-1 hash that was supplied in the request did not match what was received in the upload. Supply a valid SHA-1 hash of the uploaded file.

Error: bad_request
Required parameters supplied in the API request are either missing or invalid.

Error: cannot_make_collaborated_subfolder_private
Cannot move a collaborated subfolder to a private folder unless the new possessor is explicilty specified. Ready the owned past.id field in the request to the ID of the user receiving the content.

Fault: collaborations_not_available_on_root_folder
Root folder cannot be interact. Y'all cannot set collaborators on a user's root folder (folder ID 0). Use a dissimilar binder ID than the root folder.

Mistake: cyclical_folders_structure
Folder movement creates cyclical folder structure. The folder ID specified in the folder move would create a cyclical binder structure (due east.g. moving a folder to a sub-binder within itself). Change the folder ID for the folder motion asking.

Fault: folder_not_empty
Cannot delete as the folder is non empty. Delete all content from the folder earlier attempting to delete it.

Error: invalid_collaboration_item
Item blazon must be specified and set up to 'folder'.

Fault: invalid_grant
The authorization lawmaking supplied in the API request is issing or
no longer valid. Possible solutions are:
– Verify that the requests correctly adds the access token.
– If correctly gear up, the access token may have expired. Attempt to refresh the admission token or fetch a new one.

Error: invalid_grant
Electric current date time must be before the expiration date time listed in the 'exp' claim.
This error occurs when the Unix time on your local motorcar and the Box server are out of sync.
To prepare this fault, update the Unix fourth dimension on your machine to match the Unix time from this site, and then try the request once more.

Error: invalid_limit
Limit is non a valid number. Add a valid numeric value for the supplied limit value.

Error: invalid_offset
Offset is not a valid number. Add a valid numeric value for the supplied offset value.

Error: invalid_request_parameters
Message: Invalid input parameters in request. Invalid parameters were sent in the API asking.

Error: invalid_status
You can change the status only if the collaboration is pending.

Fault: invalid_upload_session_id
The upload session ID provided in the URL is not a valid format. The session ID supplied when making a chunked upload API request was invalid. Use the same session ID from the session that was created.

Fault: item_name_invalid
Particular name invalid. Verify that the file's proper noun is valid. Box only supports file or folder names that are 255 characters or less. Does not support file names containing non-printable ascii, "/" or "\", names with leading or trailing spaces, and the special names "." and "..".

Error: item_name_too_long
Item proper name is too long. Reduce the item'southward proper noun'southward length. The maximum length of a file or folder proper noun in Box is 255 characters or less.

Error: password_reset_required
User needs to reset password. The user has not yet completed Box account setup steps.

Fault: requested_page_out_of_range
Requested representation page out of range. The range header supplied does not fit within the size of the specified item. Adjust the bounds to fit within the size of the item and try again.

Error: requested_preview_unavailable
Requested preview unavailable.

Fault: sync_item_move_failure
Cannot movement a synced particular. The item is set to be synced by the Box sync clients and cannot be moved.

Error: task_assignee_not_allowed
Assigner does not take sufficient privileges to assign task to assignee. The user who is attempting to assign the job does non have the appropriate permissions to do then. Adjust the user permissions to allow the assignment of tasks.

Mistake: terms_of_service_required
User must accept custom terms of service before taking activeness. The admin of your Box account has gear up custom terms of service and the user has non logged in to accept the terms even so. The user volition need to accept the terms of service, or the admin volition accept to disable them, in society to proceed.

Error: user_already_collaborator
User is already a collaborator. The user with whom yous want to interact on an item has already done then. This request is unnecessary.

Error: access_denied_insufficient_permissions
Access denied every bit there is bereft permission. This error is typically occurs when the necessary scopes for the API operation are not enabled.

Error: access_denied_item_locked
Access denied as the item is locked. Y'all are attempting to access a locked fitem without appropriate permissions to admission it. Unlock the item starting time, and so effort to access it again.

Error: access_from_location_blocked
You lot're attempting to log in to Box from a location that has not been approved by your admin. Delight talk to your admin to resolve this outcome.

Fault: file_size_limit_exceeded
File size exceeds the folder owner's file size limit.

Fault: forbidden
Client does not have permission to upload to this session. Only the user who initiated the upload session may upload to it.

Error: incorrect_shared_item_password
The shared item requires a password, just information technology was either incorrect or not supplied.

Mistake: storage_limit_exceeded
Account storage limit reached. The storage limit of the account has been reached. Either upgrade your account or permanently delete content to continue. Content that is simply moved to the trash will still count towards the account total until it is permanently deleted.

Error: user_email_confirmation_required
User needs to complete e-mail confirmation.

Error: not_found
Could not find the resource.

Fault: not_trashed
Did not trash detail. The item that y'all intend to permanently delete is not in the trash. Transport the particular to the trash first.

Fault: preview_cannot_be_generated
Cannot generate the preview. You are not able to generate a preview thumbnail for the specified file.

Error: trashed
Item is in the trash. The detail that you lot are trying to access is in the trash and unavailable for modification. Movement the item out of the trash and endeavour once again.

Error: disharmonize
A resource with this value already exists. This error may occur when the potential resource already exists. Bank check the extended fault bulletin in the response body for more details.

Error: item_name_in_use
Item with the same name already exists. This error occurs when a resources with the same proper name already exists. Ensure that the resource proper name beingness added / modified is unique.

Error: name_temporarily_reserved
Some other processing item is reserving the item name. Expect and then retry the request, or wait and check the parent folder to see if the proper noun is in use. Two duplicate requests have been submitted at the same time.

Error: operation_blocked_temporary
The operation blocked another ongoing operation. This error returns when trying to admission a folder that another folder performance blocks, such every bit a movement or copy. Try again at a later interval.

Error: recent_similar_comment
A similar comment was recently made, and the API has flagged it as a potential duplicate. Verify that the comment was indeed made, or modify the comment content and endeavour again.

Error: user_login_already_used
User with the specified login already exists. A user with the same e-mail already exists. Either refer to the existing user or specify a different electronic mail.

Mistake: session_expired
The upload session associated with the given upload session ID has expired and can no longer be accessed.

Error: upload_failed
The upload session is in an unrecoverable failed state and cannot go along. This or other requests take resulted in the upload session reaching a bad state (eastward.g. parts overlapping).
Possible situations where this may ascend:
– You lot have exceeded  the maximum number of parts
– Y'all have uploaded overlapping parts

Fault: length_required
Requires a Content-Length header that was not provided.

Error: precondition_failed
Information technology is a modified resource. Please recollect the resource again and retry.

Fault: sync_state_precondition_failed
Information technology is a modified resource. Please remember the resource over again and retry.

Hither is a complete listing of cURL error codes:

CURLE_OK (0)
All fine. Proceed as usual.

CURLE_UNSUPPORTED_PROTOCOL (1)
The URL you passed to libcurl used a protocol that this libcurl does not support. The back up might be a compile-time pick that y'all didn't use, it can be a misspelled protocol cord or just a protocol libcurl has no code for.

CURLE_FAILED_INIT (ii)
Very early on initialization lawmaking failed. This is likely to be an internal fault or trouble, or a resource trouble where something fundamental couldn't go washed at init time.

CURLE_URL_MALFORMAT (3)
The URL was not properly formatted.

CURLE_NOT_BUILT_IN (4)
A requested characteristic, protocol or option was not found congenital-in in this libcurl due to a build-time conclusion. This means that a feature or pick was non enabled or explicitly disabled when libcurl was built and in order to get information technology to part you lot accept to get a rebuilt libcurl.

CURLE_COULDNT_RESOLVE_PROXY (5)
Couldn't resolve proxy. Could not resolve the given proxy host.

CURLE_COULDNT_RESOLVE_HOST (6)
Couldn't resolve host. Could not resolve the given remote host.

CURLE_COULDNT_CONNECT (seven)
Failed to connect() to host or proxy.

CURLE_FTP_WEIRD_SERVER_REPLY (8)
The server sent data libcurl couldn't parse. This mistake code is used for more than just FTP and is aliased every bit CURLE_WEIRD_SERVER_REPLY since 7.51.0.

CURLE_REMOTE_ACCESS_DENIED (nine)
Nosotros were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

CURLE_FTP_ACCEPT_FAILED (ten)
While waiting for the server to connect dorsum when an agile FTP session is used, an error code was sent over the command connexion or similar.

CURLE_FTP_WEIRD_PASS_REPLY (11)
Afterward having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected lawmaking was returned.

CURLE_FTP_ACCEPT_TIMEOUT (12)
During an agile FTP session, while waiting for the server to connect, theCURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

CURLE_FTP_WEIRD_PASV_REPLY (thirteen)
Libcurl failed to get a sensible result dorsum from the server every bit a response to either a PASV or a EPSV command. The server is flawed.

CURLE_FTP_WEIRD_227_FORMAT (14)
FTP servers return a 227-line as a response to a PASV control. If libcurl fails to parse that line, this return code passes back.

CURLE_FTP_CANT_GET_HOST (15)
An internal failure to lookup the host used for the new connection.

CURLE_HTTP2 (16)
A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, come across the fault buffer for details.

CURLE_FTP_COULDNT_SET_TYPE (17)
A trouble was detected in the HTTP2 framing layer. This is somewhat generic and tin can be 1 out of several issues, encounter the error buffer for details.

CURLE_PARTIAL_FILE (eighteen)
Received an mistake when trying to ready the transfer mode to binary or ASCII.

CURLE_FTP_COULDNT_RETR_FILE (19)
This was either a weird reply to a 'RETR' command or a nada byte transfer consummate.

CURLE_QUOTE_ERROR (21)
When sending custom "QUOTE" commands to the remote server, 1 of the commands returned an error code that was 400 or college (for FTP) or otherwise indicated unsuccessful completion of the command.

CURLE_HTTP_RETURNED_ERROR (22)
This is returned ifCURLOPT_FAILONERROR is set TRUE and the HTTP server returns an fault code that is >= 400.

CURLE_WRITE_ERROR (23)
An fault occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.

CURLE_UPLOAD_FAILED (25)
Failed to start the upload. For FTP, the server typically denied the STOR control. The mistake buffer usually contains the server'due south explanation for this.

CURLE_READ_ERROR (26)
In that location was a trouble reading a local file or an error returned by the read callback.

CURLE_OUT_OF_MEMORY (27)
A memory allocation asking failed. This is serious badness and things are severely screwed upwardly if this e'er occurs.

CURLE_OPERATION_TIMEDOUT (28)
Operation timeout. The specified time-out period was reached according to the conditions.

CURLE_FTP_PORT_FAILED (thirty)
The FTP PORT control returned an fault. This by and large happens when y'all haven't specified a skilful enough address for libcurl to use. SeeCURLOPT_FTPPORT.

CURLE_FTP_COULDNT_USE_REST (31)
he FTP Remainder command returned an error. This should never happen if the server is sane.

CURLE_RANGE_ERROR (33)
The server does non support or accept range requests.

CURLE_HTTP_POST_ERROR (34)
This is an odd error that mainly occurs due to internal confusion.

CURLE_SSL_CONNECT_ERROR (35)
A trouble occurred somewhere in the SSL/TLS handshake. Yous actually desire the error buffer and read the message there every bit information technology pinpoints the problem slightly more. Could exist certificates (file formats, paths, permissions), passwords, and others.

CURLE_BAD_DOWNLOAD_RESUME (36)
The download could non exist resumed because the specified offset was out of the file boundary.

CURLE_FILE_COULDNT_READ_FILE (37)
A file is given with FILE:// couldn't exist opened. About likely because the file path doesn't identify an existing file. Did you check file permissions?

CURLE_LDAP_CANNOT_BIND (38)
LDAP cannot bind. LDAP bind operation failed.

CURLE_LDAP_SEARCH_FAILED (39)
LDAP search failed.

CURLE_FUNCTION_NOT_FOUND (41)
Function not constitute. Could not find a required zlib function.

CURLE_ABORTED_BY_CALLBACK (42)
Aborted by callback. A callback returned "abort" to libcurl..

CURLE_BAD_FUNCTION_ARGUMENT (43)
Internal error. A office was chosen with a bad parameter.

CURLE_INTERFACE_FAILED (45)
Interface error. Could not apply a specific approachable interface. Fix which interface to use for outgoing connections' source IP accost withCURLOPT_INTERFACE.

CURLE_TOO_MANY_REDIRECTS (47)
Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit withCURLOPT_MAXREDIRS.

CURLE_UNKNOWN_OPTION (48)
An pick passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the programme that uses libcurl. The error buffer might incorporate more specific information well-nigh which exact option it concerns.

CURLE_TELNET_OPTION_SYNTAX (49)
A telnet option string was Illegally formatted.

CURLE_GOT_NOTHING (52)
Zip was returned from the server, and under the circumstances, getting nothing is considered an fault.

CURLE_SSL_ENGINE_NOTFOUND (53)
The specified crypto engine wasn't found.

CURLE_SSL_ENGINE_SETFAILED (54)
Failed to set the selected SSL crypto engine as default!

CURLE_SEND_ERROR (55)
Failed sending network information.

CURLE_RECV_ERROR (56)
Failure with receiving network data.

CURLE_SSL_CERTPROBLEM (58)
Problem with the local client certificate.

CURLE_SSL_CIPHER (59)
Couldn't use the specified cipher.

CURLE_PEER_FAILED_VERIFICATION (threescore)
The remote server's SSL document or SSH md5 fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

CURLE_BAD_CONTENT_ENCODING (61)
Unrecognized transfer encoding.

CURLE_LDAP_INVALID_URL (62)
Invalid LDAP URL.

CURLE_FILESIZE_EXCEEDED (63)
Maximum file size exceeded.

CURLE_USE_SSL_FAILED (64)
Requested FTP SSL level failed.

CURLE_SEND_FAIL_REWIND (65)
When doing a send functioning coil had to rewind the data to retransmit, but the rewinding operation failed.

CURLE_SSL_ENGINE_INITFAILED (66)
Initiating the SSL Engine failed.

CURLE_LOGIN_DENIED (67)
The remote server denied curl to login (Added in 7.13.i)

CURLE_TFTP_NOTFOUND (68)
File not found on TFTP server.

CURLE_TFTP_PERM (69)
Permission problem on TFTP server.

CURLE_REMOTE_DISK_FULL (70)
Out of deejay infinite on the server.

CURLE_TFTP_ILLEGAL (71)
Illegal TFTP operation.

CURLE_TFTP_UNKNOWNID (72)
Unknown TFTP transfer ID.

CURLE_REMOTE_FILE_EXISTS (73)
File already exists and volition not be overwritten.

CURLE_TFTP_NOSUCHUSER (74)
This fault should never exist returned by a properly functioning TFTP server.

CURLE_CONV_FAILED (75)
Grapheme conversion failed.

CURLE_CONV_REQD (76)
The caller must annals conversion callbacks.

CURLE_SSL_CACERT_BADFILE (77)
Problem with reading the SSL CA cert (path? access rights?)

CURLE_REMOTE_FILE_NOT_FOUND (78)
The resources referenced in the URL does not exist.

CURLE_SSH (79)
An unspecified error occurred during the SSH session.

CURLE_SSL_SHUTDOWN_FAILED (fourscore)
Failed to shut downwards the SSL connectedness.

CURLE_AGAIN (81)
The socket is non ready for send/recv to await till information technology'southward ready and try again. This return code is only returned fromcurl_easy_recv andcurl_easy_send (Added in 7.18.ii)

CURLE_SSL_CRL_BADFILE (82)
Failed to load CRL file (Added in 7.19.0)

CURLE_SSL_ISSUER_ERROR (83)
Issuer check failed (Added in vii.nineteen.0)

CURLE_FTP_PRET_FAILED (84)
The FTP server does non sympathize the PRET control at all or does non support the given argument. Be careful when usingCURLOPT_CUSTOMREQUEST, a custom LIST control will be sent with PRET CMD before PASV every bit well. (Added in vii.20.0)

CURLE_RTSP_CSEQ_ERROR (85)
Mismatch of RTSP CSeq numbers.

CURLE_RTSP_SESSION_ERROR (86)
Mismatch of RTSP Session Identifiers.

CURLE_FTP_BAD_FILE_LIST (87)
Unable to parse FTP file list (during FTP wildcard downloading).

CURLE_CHUNK_FAILED (88)
Clamper callback reported an error.

CURLE_NO_CONNECTION_AVAILABLE (89)
(For internal employ only, volition never be returned by libcurl) No connectedness available, the session volition be queued. (added in vii.30.0)

CURLE_SSL_PINNEDPUBKEYNOTMATCH (90)
Failed to friction match the pinned key specified withCURLOPT_PINNEDPUBLICKEY.

CURLE_SSL_INVALIDCERTSTATUS (91)
The status returned failure when asked withCURLOPT_SSL_VERIFYSTATUS

CURLE_HTTP2_STREAM (92)
Stream fault in the HTTP/ii framing layer.

CURLE_RECURSIVE_API_CALL (93)
An API function was chosen from inside a callback.

CURLE_AUTH_ERROR (94)
An authentication function returned an error.

CURLE_OBSOLETE*
These error codes will never return. They were used in an former libcurl version and are currently unused.

whitewhady1982.blogspot.com

Source: https://help.servmask.com/knowledgebase/box-error-codes/

Share this post