Errors & Exceptions Reference

    The standardized error codes returned by the Couchbase Node.js SDK, from cloud connection to sub-document.

    Shared Error Definitions


    Raised when a request cannot be completed until the user-defined timeout fires.

    Note, this is a base class for AmbiguousTimeout and UnambiguousTimeout.


    Raised when a request is cancelled and cannot be resolved in a non-ambiguous way. Most likely the request is in-flight on the socket and the socket gets closed.


    Raised when it is unambiguously determined that the error was caused because of invalid arguments from the user. Usually only thrown directly when doing request arg validation on KV and sub-doc. Also commonly used as a parent class for many service-specific exceptions (see below).


    Raised when it can be determined from the config unambiguously that a given service is not available. I.e. no query node in the config, or a memcached bucket is accessed and views or n1ql queries should be performed.


    Raised when:

    • Query: Error range 5xxx.

    • Analytics: Error range 25xxx.

    • KV: error code ERR_INTERNAL (0x84).

    • Search: HTTP 500.


    Raised when:

    • Query: Error range 10xxx.

    • Analytics: Error range 20xxx.

    • View: HTTP status 401.

    • KV: error code ERR_ACCESS (0x24), ERR_AUTH_ERROR (0x20), AUTH_STALE (0x1f).

    • Search: HTTP status 401, 403.


    Raised when:

    • Analytics: Errors: 23000, 23003.

    • KV: Error code ERR_TMPFAIL (0x86), ERR_BUSY (0x85) ERR_OUT_OF_MEMORY (0x82), ERR_NOT_INITIALIZED (0x25).


    Raised when:


    Raised when:

    • KV: ERR_EXISTS (0x02) when replace or remove with CAS.

    • Query: code 12009.


    Raised when a request is made but the current bucket is not found.


    Raised when a request is made but the current collection (including scope) is not found.


    Raised when:

    • KV: 0x81 (unknown command), 0x83 (not supported).


    Raised when a timeout occurs and we aren’t sure if the underlying operation has completed. This normally occurs because we sent the request to the server successfully, but timed out waiting for the response. Note that idempotent operations should never return this, as they do not have ambiguity.


    Raised when a timeout occurs and we are confident that the operation could not have succeeded. This normally would occur because we received confident failures from the server, or never managed to successfully dispatch the operation.


    Raised when a feature which is not available was used.


    Raised when a management API attempts to target a scope which does not exist.


    Raised when:

    • Query:

    • Analytics: rised when 24047 raised.

    • Search: Http status code 400 AND text contains "index not found".


    • Query: Raised when

      • Code 5000 AND message contains Index .+ already exist

      • Code 4300 AND message contains index .+ already exist

    • Analytics: Raised when 24048 raised.


    Raised when encoding of a user object failed while trying to write it to the cluster.


    Raised when decoding of the data into the user object failed.

    KeyValue Error Definitions


    Raised when:

    • KV: Code 0x01. The document requested was not found on the server.


    Raised when in getAnyReplica, the getAllReplicas returns an empty stream because all the individual errors are dropped (i.e. all returned a DocumentNotFound).


    Raised when:

    • KV: Code 0x09. The document requested was locked.


    Raised when:

    • KV: Code 0x03. The value that was sent was too large to store (typically > 20MB).


    Raised when:

    • KV: Code 0x02. An operation which relies on the document not existing fails because the document existed.


    Raised when:

    • KV: Code 0xa0. The specified durability level is invalid.


    Raised when:

    • KV: Code 0xa1. The specified durability requirements are not currently possible (for example, there are an insufficient number of replicas online).


    Raised when:

    • KV: Code 0xa3.

      • A sync-write has not completed in the specified time and has an ambiguous result - it may have succeeded or failed, but the final result is not yet known.

      • A SEQNO OBSERVE operation is performed and the vbucket UUID changes during polling.


    Raised when:

    • KV: Code 0xa2. A durable write is attempted against a key which already has a pending durable write.


    Raised when:

    • KV: Code 0xa4. The server is currently working to synchronize all replicas for previously performed durable operations (typically occurs after a rebalance).


    Raised when:

    • KV: Code 0xc0. The path provided for a sub-document operation was not found.


    Raised when:

    • KV: Code 0xc1. The path provided for a sub-document operation did not match the actual structure of the document.


    Raised when:

    • KV: Code 0xc2. The path provided for a sub-document operation was not syntactically correct.


    Raised when:

    • KV: Code 0xc3. The path provided for a sub-document operation is too long, or contains too many independent components.


    Raised when:

    • KV: Code 0xc4. The document contains too many levels to parse.


    Raised when:

    • KV: Code 0xca. The value provided, if inserted into the document, would cause the document to become too deep for the server to accept.


    Raised when:

    • KV: Code 0xc5. The value provided for a sub-document operation would invalidate the JSON structure of the document if inserted as requested.


    Raised when:

    • KV: Code 0xc6. A Sub-Document operation is performed on a non-JSON document.


    Raised when:

    • KV: Code 0xc7. The existing number is outside the valid range for arithmetic operations.


    Raised when:

    • KV: Code 0xc8. The delta value specified for an operation is too large.


    Raised when:

    • KV: Code 0xc9. A sub-document operation which relies on a path not existing encountered a path which exists.


    Raised when:

    • KV: Code 0xd0. A macro was used which the server did not understand.


    Raised when:

    • KV: Code 0xcf. A Sub-Document operation attempts to access multiple xattrs in one operation.


    Raised when:

    • KV: Code 0xd1. A sub-document operation attempts to access a virtual attribute.


    Raised when:

    • KV: Code 0xd2. A Sub-Document operation attempts to modify a virtual attribute.


    Raised when:

    • KV: Code 0x24. The user does not have permission to access the attribute. Occurs when the user attempts to read or write a system attribute (name starts with underscore) but does not have the SystemXattrRead / SystemXattrWrite permission.

    Query Error Definitions


    • Query: Raised when code range 4xxx other than those explicitly covered.


    • Query: Raised when code range 12xxx and 14xxx raised (other than 12004 and 12016).


    Analytics Error Definitions


    Raised when error range 24xxx (excluded are specific codes in the errors below).


    Raised when error code 23007.


    Raised when error codes 24044, 24045, 24025.


    Raised when error code 24034.


    Raised when 24040.


    Raised when 24039.


    Raised when 24006.

    Search Error Definition

    There are no specific errors for Search; see the Shared Error Definitions section for errors that apply to Search.

    View Error Definitions


    Raised when Http status code 404 — reason or error contains “not_found”.


    Raised on the Management APIs only when:

    • Getting a design document;

    • Dropping a design document;

    • And the server returns 404.

    Management API Error Definitions


    Raised from the collection management API.


    Raised from the collection management API.


    Raised from the user management API.


    Raised from the user management API.


    Raised from the bucket management API.


    Raised from the user management API.


    Raised from the bucket management API.

    Field-Level Encryption Error Definitions

    Note, in SDK 3.0, Field Level Encryption is only available as a Developer Preview with the Java SDK.


    Generic cryptography failure. Inherits from CouchbaseException. Parent Type for all other Field-Level Encryption errors.


    Raised by CryptoManager.encrypt() when encryption fails for any reason. Should have one of the other Field-Level Encryption errors as a cause.


    Raised by CryptoManager.decrypt() when decryption fails for any reason. Should have one of the other Field-Level Encryption errors as a cause.


    Raised when a crypto operation fails because a required key is missing.


    Raised by an encrypter or decrypter when the key does not meet expectations (for example, if the key is the wrong size).


    Raised when a message cannot be decrypted because there is no decrypter registered for the algorithm.


    Raised when a message cannot be encrypted because there is no encrypter registered under the requested alias.


    Raised when decryption fails due to malformed input, integrity check failure, etc.

    Connecting to Cloud

    Although the SDK and client application should be located in the same LAN-like environment (or cloud availability zone), and this is the only network configuration supported, we recognise that this set-up may not be possible during development. In particular, you may be developing against Couchbase Capella from a laptop in a small or home office, where DNS-SRV may cause problems.

    In order for your application to connect to your cloud, Capella creates a special kind of DNS record, called a Service record, or DNS-SRV record. DNS SRV records are widely supported and used frequently in systems like XMPP, and Kubernetes services. Occasionally, some DNS providers can run into issues with large DNS SRV records. This can manifest as a host not found issue. The actual problem is (a typically older) DNS server that cannot handle large responses which converts the error to host not found. This has frequently been observed when working from home with a service provider router that embeds a caching DNS Server.

    Below is a list of log messages that you may see if you hit DNS SRV issues. These examples have been created in the circumstance that the SRV record is too long for the DNS provider to handle, and are included here so that they are findable by search, and you can then go to our cloud connection troubleshooting page.

    couchnode:lcb:info (instance @ ../deps/lcb/src/ DNS SRV lookup failed: LCB_ERR_UNKNOWN_HOST (1049). Ignore this if not relying on DNS SRV records +0ms
    Couldn’t look up
    couchnode:lcb:error (connection @ ../deps/lcb/src/lcbio/ <> (SOCK=23609f0e7a32db36) Couldn't look up (nodename nor servname provided, or not known) [EAI=8] +0ms
    Failed to establish connection
    couchnode:lcb:error (connection @ ../deps/lcb/src/lcbio/ <> (SOCK=23609f0e7a32db36) Failed to establish connection: LCB_ERR_UNKNOWN_HOST (1049), os errno=0 +0ms
    couchnode:lcb:debug (lcbio_mgr @ ../deps/lcb/src/lcbio/ <> (HE=0x102b11cd0) Received result for I=0x102b13d30,C=0x0; E=0x419 +0ms
    Could not get configuration
    couchnode:lcb:error (cccp @ ../deps/lcb/src/bucketconfig/ <NOHOST:NOPORT> (CTX=0x0,) Could not get configuration: LCB_ERR_UNKNOWN_HOST (1049) +0ms

    Further Reading