Google Drive Extension Error Codes

All-in-One WP Migration Google Drive Extension Error Codes Information

Please see below for more information on the error codes that the Google Drive extension API server may return:

Code: 400 ‘Bad Request’
Error by the user. This could indicate that a required field or parameter was not provided, that the value provided was invalid, or that the combination of provided fields was invalid.
This error may appear when attempting to add a duplicate parent to a Drive item. It can also appear when trying to add a parent, resulting in a directory graph cycle.

Code: 401 ‘Unauthorized’
Authorization header is invalid. You have an expired or invalid access token. Suggested action: Using the long-lived refresh token, refresh the access token.

Code: 402 ‘Payment Required’
You must pay for the product in order to proceed.

Code: 403 ‘Forbidden’
Access is prohibited. Although the request was valid, the server is refusing to act. The user may not have the required permissions for a resource or may require some kind of account.

Error: ‘Daily Limit Exceeded’
Your project has reached its Courtesy API limit. Suggested action: Request additional quota.

Error: ‘User Rate Limit Exceeded’
The per-user limit has been reached. This could be a limit from the Developer Console or a limit from the Drive backend.

Error: Rate Limit Exceeded
The user has reached the maximum request rate for the Google Drive API. The limit varies according to the type of request.

Error: Sharing Rate Limit Exceeded
The user has reached his or her sharing limit, which is frequently associated with an email limit.
Suggested actions:
– Avoid sending emails when sharing a large number of files.
– Consider a Service Account with authority delegation to impersonate the owner of each document to share if one user is making a lot of requests on behalf of many users in a G Suite domain.

Error: The user has not granted the app ‘App ID’ access to the file ‘File ID’
The requesting app is not on the ACL for the file. The user never explicitly opened the file with this Drive app.

Error: The user does not have sufficient permissions for file ‘File ID’
The app is attempting to modify a file that the user does not have write access to.
Suggested action: Inform the user that those permissions are necessary in order to update the file.

Error: App with id ‘App ID’ cannot be used within the authenticated user’s domain
The policy for the user’s domain prohibits your app from accessing Google Drive.
Suggested course of action: Inform the user that the domain does not permit your app to access Drive files.

Code: 404 ‘Not Found’
A file does not exist or the user does not have read access to it. Suggested course of action: Inform users that they lack read access to the file or that it does not exist. Inform them that they must seek permission from the file’s owner.

Code: 405 ‘Method Not Allowed’
The resource does not allow the HTTP method in the request.

Code: 406 ‘Not Acceptable’
This service does not support the format specified in the Accept header. The requested resource can only generate content that is not acceptable according to the Accept headers sent in the request.

Code: 407 ‘Proxy Authentication Required’
You need to authenticate via proxy. First, the client must authenticate with the proxy.

Code: 408 ‘Request Timeout’
The request has expired. The server timed out while awaiting the request. The client did not submit a request within the time frame that the server was willing to wait. At any time in the future, repeat the request without modification.

Code: 409 ‘Conflict’
The current state contradicts what the request anticipates. The conflict does not allow the request to process.

Code: 410 ‘Gone’
The requested resource is no longer available on the server.

Code: 411 ”Length Required’
The request requires a Content-Length based header.

Code: 412 ‘Precondition Failed’
The server did not meet one of the requester’s specific preconditions.

Code 413 ‘Request Entity Too Large’
The request size exceeds maximum limit.

Code 414 ‘Request-URI Too Long’
The Request-URI is too long. The server could not process the provided URI because it was too long.

Code: 415 ‘Unsupported Media Type’
The service does not support the content type of the request format.

Code: 416 ‘Requested Range Not Satisfiable’
The specified byte range is invalid or unavailable.

Code: 417 ‘Expectation Failed’
Expectation failed. The server cannot meet the requirements of the Expect request-header field.

Code: 429 ‘Too Many Requests’
The user has sent too many requests in a given amount of time.

Code: 500 ‘Internal Server Error’
An unexpected error occurred while processing the request.

Code: 501 ‘Not Implemented’
Did not implement the requested feature.

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

Code: 503 ‘Service Unavailable’
The service is currently unavailable. You may resubmit the request after a brief delay. A Retry-After header may be present.

Code: 504 ‘Gateway Timeout’
The server was acting as a proxy or gateway and did not receive a timely response from the upstream server.

Code: 505 ‘HTTP Version Not Supported’
The server does not support the request’s use of HTTP protocol version.

Here is a complete list of cURL error codes:

All fine. Proceed as usual.

The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn’t use, it can be a misspelled protocol string or just a protocol libcurl has no code for.

Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn’t get done at init time.

The URL was not properly formatted.

A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function, you have to get a rebuilt libcurl.

Couldn’t resolve proxy. Could not resolve the given proxy host.

Couldn’t resolve host. Could not resolve the given remote host.

Failed to connect() to host or proxy.

The server sent data libcurl couldn’t parse. This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0.

We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.

After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates the return of an unexpected code.

During an active FTP session, while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.

FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code passes back.

An internal failure to lookup the host used for the new connection.

A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

Received an error when trying to set the transfer mode to binary or ASCII.

This was either a weird reply to a ‘RETR’ command or a zero byte transfer complete.

When sending custom “QUOTE” commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.

This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400.

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

Failed to start the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server’s explanation for this.

There was a problem reading a local file or an error returned by the read callback.

A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.

Operation timeout. The specified time-out period was reached according to the conditions.

The FTP PORT command returned an error. This mostly happens when you haven’t specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.

he FTP REST command returned an error. This should never happen if the server is sane.

The server does not support or accept range requests.

This is an odd error that mainly occurs due to internal confusion.

A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

The download could not be resumed because the specified offset was out of the file boundary.

A file is given with FILE:// couldn’t be opened. Most likely because the file path doesn’t identify an existing file. Did you check file permissions?

LDAP cannot bind. LDAP bind operation failed.

LDAP search failed.

Function not found. Could not find a required zlib function.

Aborted by callback. A callback returned “abort” to libcurl..

Internal error. A function was called with a bad parameter.

Interface error. Could not use a specific outgoing interface. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE.

Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns.

A telnet option string was Illegally formatted.

Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.

The specified crypto engine wasn’t found.

Failed to set the selected SSL crypto engine as default!

Failed sending network data.

Failure with receiving network data.

problem with the local client certificate.

Couldn’t use the specified cipher.

The remote server’s SSL certificate 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.

Unrecognized transfer encoding.

Invalid LDAP URL.

Maximum file size exceeded.

Requested FTP SSL level failed.

When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed.

Initiating the SSL Engine failed.

The remote server denied curl to login (Added in 7.13.1)

File not found on TFTP server.

Permission problem on TFTP server.

Out of disk space on the server.

Illegal TFTP operation.

Unknown TFTP transfer ID.

File already exists and will not be overwritten.

This error should never be returned by a properly functioning TFTP server.

Character conversion failed.

The caller must register conversion callbacks.

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

The resource referenced in the URL does not exist.

An unspecified error occurred during the SSH session.

Failed to shut down the SSL connection.

The socket is not ready for send/recv to wait till it’s ready and try again. This return code is only returned from curl_easy_recv and curl_easy_send (Added in 7.18.2)

Failed to load CRL file (Added in 7.19.0)

Issuer check failed (Added in 7.19.0)

The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST, a custom LIST command will be sent with PRET CMD before PASV as well. (Added in 7.20.0)

Mismatch of RTSP CSeq numbers.

Mismatch of RTSP Session Identifiers.

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

Chunk callback reported an error.

(For internal use only, will never be returned by libcurl) No connection available, the session will be queued. (added in 7.30.0)

Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY.

The status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS

Stream error in the HTTP/2 framing layer.

An API function was called from inside a callback.

An authentication function returned an error.

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

Leave A Comment?