The following tables list errors that can occur when calling various Mozilla APIs. Each error is listed by its name and an error code in parentheses. An error will typically be displayed on the error console, but can be captured using a try-catch block in JavaScript. These constants can be accessed through Components.results. For example, by using Components.results.NS_ERROR_NOT_INITIALIZED
General Errors
The following errors are general and can occur when using any component.
- NS_ERROR_NOT_INITIALIZED (0xC1F30001)
- An attempt was made to use a component or object which has not yet been initialized. These components usually provide an initialization method, often called
Init
, which must be called before other methods are used. - NS_ERROR_ALREADY_INITIALIZED (0xC1F30002)
- An attempt is made to initialize a component or object again which has already been initialized.
- NS_ERROR_NOT_IMPLEMENTED (0x80004001)
- This error is caused by methods which are not implemented. This could occur because the implementation has not yet been written, or because the component intentionally does not support the desired feature.
- NS_ERROR_NO_INTERFACE (0x80004002)
- An attempt was made to call QueryInterface to retrieve an interface which an object does not support.
- NS_ERROR_NULL_POINTER (0x80004003)
- An error occurred because a value was set to null when this was not expected.
- NS_ERROR_ABORT (0x80004004)
- This error indicates that an operation failed and the caller should abort whatever action is being performed. This typically will occur if an operation could not complete properly.
- NS_ERROR_FAILURE (0x80004005)
- This is the most general of all the errors and occurs for all errors for which a more specific error code does not apply.
- NS_ERROR_UNEXPECTED (0x8000FFFF)
- An operation did not complete due to a condition which was not expected. This error occurred rather than continuing.
- NS_ERROR_OUT_OF_MEMORY (0x8007000E)
- This error occurs when there is not enough memory available to carry out an operation, or an error occurred trying to allocate memory.
- NS_ERROR_ILLEGAL_VALUE (0x80070057)
- An argument supplied to a method was not valid, for instance a null value was supplied as an argument which does not allow null values, or a value was out of range.
- NS_ERROR_NO_AGGREGATION (0x80040110)
- NS_ERROR_NOT_AVAILABLE (0x80040111)
- An operation could not be completed because some other necessary component or resource was not available.
- NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)
- Returned when a service could not be found.
- NS_ERROR_FACTORY_REGISTER_AGAIN (0x80040155)
- This error is returned when registering a component and the registration should try registering again later.
- NS_ERROR_FACTORY_NOT_LOADED (0x800401f8)
- NS_ERROR_FACTORY_EXISTS (0xC1F30100)
- NS_ERROR_FACTORY_NO_SIGNATURE_SUPPORT (0xC1F30101)
- NS_ERROR_PROXY_INVALID_IN_PARAMETER (0x80010010)
- NS_ERROR_PROXY_INVALID_OUT_PARAMETER (0x80010011)
- NS_ERROR_CANNOT_CONVERT_DATA (0x80460001)
- NS_ERROR_OBJECT_IS_IMMUTABLE (0x80460002)
- NS_ERROR_LOSS_OF_SIGNIFICANT_DATA (0x80460003)
- NS_ERROR_ILLEGAL_DURING_SHUTDOWN (0x8046001E)
- Many operations cannot be performed once the application is being shutdown. This error will occur in this situation.
File Errors
The following table lists the errors that could occur when using files. While these errors can occur when using the file APIs, they can also occur with other components that use files.
- NS_ERROR_FILE_UNRECOGNIZED_PATH (0x80520001)
- This error occurs when an attempt is made to set a path that isn't valid for the platform. For example, if a character in the path is not valid for a filename. In addition, this error may occur when a relative path is supplied to a method that expects an absolute path and vice versa.
- NS_ERROR_FILE_UNRESOLVABLE_SYMLINK (0x80520002)
- An attempt was made to access a symbolic link to a file or directory which does not exist.
- NS_ERROR_FILE_EXECUTION_FAILED (0x80520003)
- An attempt to launch or execute a file failed because the file is not executable.
nsIFile.isExecutable()
may be used to check if a file is executable. - NS_ERROR_FILE_UNKNOWN_TYPE (0x80520004)
- An call was made to
nsIFile.create()
with an invalid type. Only NORMAL_FILE_TYPE and DIRECTORY_TYPE are allowed. - NS_ERROR_FILE_DESTINATION_NOT_DIR (0x80520005)
- An attempt was made to copy or move a file to a destination that is not a directory.
- NS_ERROR_FILE_TARGET_DOES_NOT_EXIST (0x80520006)
- An attempt was made to reference a file that does not exist for copy/move, checking its size, etc.
- NS_ERROR_FILE_COPY_OR_MOVE_FAILED (0x80520007)
- A call to
nsIFile.copyTo()
ornsIFile.moveTo()
failed. - NS_ERROR_FILE_ALREADY_EXISTS (0x80520008)
- An attempt was made to create a file that already exists.
- NS_ERROR_FILE_INVALID_PATH (0x80520009)
- This error occurs when an attempt is made to use a path that isn't valid for the platform.
- NS_ERROR_FILE_DISK_FULL (0x8052000A)
- This error will occur if attempting to write to a disk that is full.
- NS_ERROR_FILE_CORRUPTED (0x8052000B)
- Indicates that an attempt was made to open or access a file that has been corrupted, or that the format of a file is unknown. This error might occur if a previous attempt to write to the file had failed. This error may be returned by various components that use files to indicate that necessary files are not in an expected format.
- NS_ERROR_FILE_NOT_DIRECTORY (0x8052000C)
- This error will occur if an attempt was made to perform an operation on a file that is only valid for a directory. This error can be caused by the
directoryEntries
nsIFile.Attributes attribute. - NS_ERROR_FILE_IS_DIRECTORY (0x8052000D)
- This error will occur if an attempt was made to perform an operation on a directory that is only valid for files.
- NS_ERROR_FILE_IS_LOCKED (0x8052000E)
- This error indicates that a file cannot be accessed because it is locked, typically because the file is already being used by another application.
- NS_ERROR_FILE_TOO_BIG (0x8052000F)
- This error occurs when
nsIFile.createUnique()
cannot create a file with a unique filename. This indicates that too many files have been created already. - NS_ERROR_FILE_NO_DEVICE_SPACE (0x80520010)
- NS_ERROR_FILE_NAME_TOO_LONG (0x80520011)
- Indicates that a file name or path is larger than the platform can handle.
- NS_ERROR_FILE_NOT_FOUND (0x80520012)
- An attempt was made to access a file that does not exist. Use
nsIFile.exists()
to check if the file exists beforehand. - NS_ERROR_FILE_READ_ONLY (0x80520013)
- An attempt was made to create or write to a file or directory that is read only. This might happen if the file is not writable, the directory containing the file is not writable or the disk is write protected. Use
nsIFile.isWritable()
to check if the file can be written to. - NS_ERROR_FILE_DIR_NOT_EMPTY (0x80520014)
- When calling
nsIFile.remove()
on a directory and the 'recursive' argument to this method is false, this error will occur if the directory is not empty. - NS_ERROR_FILE_ACCESS_DENIED (0x80520015)
- An operation was not performed on a file because the file cannot be accessed, typically because the permissions set for the file do not allow the operation.
Stream Errors
- NS_BASE_STREAM_CLOSED (0x80470002)
- This error occurs when an operation is performed on a stream that has already been closed.
- NS_BASE_STREAM_OSERROR (0x80470003)
- This error occurs when an operating system error occurs. Currently, this error only occurs when a file stream is closed.
- NS_BASE_STREAM_ILLEGAL_ARGS (0x80470004)
- NS_BASE_STREAM_NO_CONVERTER (0x80470005)
- NS_BASE_STREAM_BAD_CONVERSION (0x80470006)
- This error occurs when the component
nsIStringBundleService
has been set with a badly encoded property file. Try using UTF-8 encoding instead. SeensIStringBundle
. - NS_BASE_STREAM_WOULD_BLOCK (0x80470007)
- This error occurs when an attempt is made to read from a non blocking stream yet there is not enough data available to read without waiting for more.
Document and Node Errors
The following errors can occur when using documents, nodes and elements.
- NS_ERROR_DOM_INDEX_SIZE_ERR (0x80530001)
- An attempt was made to adjust the value of a text node using an index that was out of range.
- NS_ERROR_DOM_DOMSTRING_SIZE_ERR (0x80530002)
- An attempt was made to create a string larger than is supported.
- NS_ERROR_DOM_HIERARCHY_REQUEST_ERR (0x80530003)
- A node was inserted into a location where it cannot go. For instance, a node cannot be inserted into a descendant of itself.
- NS_ERROR_DOM_WRONG_DOCUMENT_ERR (0x80530004)
- An operation was performed on a document involving a node that was created in a different document. The
document.importNode
method may need to be used to import the node into the document first. - NS_ERROR_DOM_INVALID_CHARACTER_ERR (0x80530005)
- An invalid character was used in a tag or attribute name.
- NS_ERROR_DOM_NO_DATA_ALLOWED_ERR (0x80530006)
- NS_ERROR_DOM_NO_MODIFICATION_ALLOWED_ERR (0x80530007)
- This error can occur when an attempt is made to modify an aspect of an object that cannot be changed.
- NS_ERROR_DOM_NOT_FOUND_ERR (0x80530008)
- A node was not found. For example, an attempt was made to use the
element.insertBefore
method to insert a node before one that is not a child. - NS_ERROR_DOM_NOT_SUPPORTED_ERR (0x80530009)
- The operation is not supported.
- NS_ERROR_DOM_INUSE_ATTRIBUTE_ERR (0x8053000A)
- NS_ERROR_DOM_INVALID_STATE_ERR (0x8053000B)
- An attempt was made to use an object which is no longer usable.
- NS_ERROR_DOM_SYNTAX_ERR (0x8053000C)
- An attribute value or property was set to an invalid value.
- NS_ERROR_DOM_INVALID_MODIFICATION_ERR (0x8053000D)
- An attempt was made to modify the type of the attribute.
- NS_ERROR_DOM_NAMESPACE_ERR (0x8053000E)
- A namespace was not valid. For instance, this error can occur when an invalid character was used in a namespace URI.
- NS_ERROR_DOM_INVALID_ACCESS_ERR (0x8053000F)
- A attempt was made to access a value that was not allowed.
- NS_ERROR_DOM_RANGE_BAD_BOUNDARYPOINTS_ERR (0x805C0001)
- The boundary points of a range are invalid.
- NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR (0x805C0002)
- The container of an boundary point of a range is being set to either a node of an invalid type or a node with an ancestor of an invalid type.
- NS_ERROR_DOM_VALIDATION_ERR (0x805300 16)
- NS_ERROR_DOM_TYPE_MISMATCH_ERR (0x805300 17)
- NS_ERROR_DOM_SVG_WRONG_TYPE_ERR (0x805F0000)
- NS_ERROR_DOM_SVG_INVALID_VALUE_ERR (0x805F0001)
- NS_ERROR_DOM_SVG_MATRIX_NOT_INVERTABLE (0x805F0002)
- A matrix could not be computed.
- NS_ERROR_DOM_INVALID_EXPRESSION_ERR (0x805B0033)
- NS_ERROR_DOM_TYPE_ERR (0x805B0034)
- NS_ERROR_DOM_SECURITY_ERR (0x805303E8)
- NS_ERROR_DOM_SECMAN_ERR (0x805303E9)
- NS_ERROR_DOM_WRONG_TYPE_ERR (0x805303EA)
- NS_ERROR_DOM_NOT_OBJECT_ERR (0x805303EB)
- NS_ERROR_DOM_NOT_XPC_OBJECT_ERR (0x805303EC)
- NS_ERROR_DOM_NOT_NUMBER_ERR (0x805303ED)
- NS_ERROR_DOM_NOT_BOOLEAN_ERR (0x805303EE)
- NS_ERROR_DOM_NOT_FUNCTION_ERR (0x805303EF)
- NS_ERROR_DOM_TOO_FEW_PARAMETERS_ERR (0x805303F0)
- NS_ERROR_DOM_BAD_DOCUMENT_DOMAIN (0x805303F1)
- NS_ERROR_DOM_PROP_ACCESS_DENIED (0x805303F2)
- NS_ERROR_DOM_XPCONNECT_ACCESS_DENIED (0x805303F3)
- NS_ERROR_DOM_BAD_URI (0x805303F4)
- NS_ERROR_DOM_RETVAL_UNDEFINED (0x805303F5)
- NS_ERROR_DOM_QUOTA_REACHED (0x805303F6)
- An attempt was made to add data into the local or global storage for a given domain that would exceed the amount allowed for that domain.
- NS_ERROR_DOM_FILE_NOT_FOUND_ERR (0x80650000)
- File was not found.
- NS_ERROR_DOM_FILE_NOT_READABLE_ERR (0x80650001)
- File could not be read.
Network Errors
The following errors can occur when creating connections over the network, or when reading or writing data.
NS_BINDING_FAILED
(0x804B0001)NS_BINDING_ABORTED
(0x804B0002)- The asynchronous request failed because it was aborted by some user action.
NS_BINDING_REDIRECTED
(0x804B0003)- The asynchronous request has been "redirected" to a different async request. (for example, an HTTP redirect occurred). This error code is used with load groups to notify the load group observer when a request in the load group is redirected to another request.
NS_BINDING_RETARGETED
(0x804B0004)- The asynchronous request has been "retargeted" to a different "handler." This error code is used with load groups to notify the load group observer when a request in the load group is removed from the load group and added to a different load group.
NS_ERROR_MALFORMED_URI
(0x804B000A)- The URI is malformed.
NS_ERROR_ALREADY_CONNECTED
(0x804B000B)- The connection is already established. XXX currently unused - consider removing.
NS_ERROR_NOT_CONNECTED
(0x804B000C)- The connection does not exist. XXX currently unused - consider removing.
NS_ERROR_CONNECTION_REFUSED
(0x804B000D)NS_ERROR_NET_TIMEOUT
(0x804B000E)NS_ERROR_IN_PROGRESS
(0x804B000F)- The requested action could not be completed while the object is busy. Implementations of
nsIChannel.asyncOpen()
will commonly return this error if the channel has already been opened (and has not yet been closed). NS_ERROR_OFFLINE
(0x804B0010)NS_ERROR_NO_CONTENT
(0x804B0011)- Returned from
nsIChannel.asyncOpen()
to indicate that OnDataAvailable will not be called because there is no content available. This is used by helper app style protocols (for example, mailto). NS_ERROR_UNKNOWN_PROTOCOL
(0x804B0012)- The URI scheme corresponds to an unknown protocol handler.
NS_ERROR_PORT_ACCESS_NOT_ALLOWED
(0x804B0013)NS_ERROR_NET_RESET
(0x804B0014)NS_ERROR_FTP_LOGIN
(0x804B0015)NS_ERROR_FTP_CWD
(0x804B0016)NS_ERROR_FTP_PASV
(0x804B0017)NS_ERROR_FTP_PWD
(0x804B0018)NS_ERROR_NOT_RESUMABLE
(0x804B0019)NS_ERROR_INVALID_CONTENT_ENCODING
(0x804B001B)- The content encoding of the source document was incorrect, for example returning a plain HTML document advertised as
Content-Encoding: gzip
NS_ERROR_FTP_LIST
(0x804B001C)NS_ERROR_UNKNOWN_HOST
(0x804B001E)NS_ERROR_REDIRECT_LOOP
(0x804B001F)NS_ERROR_ENTITY_CHANGED
(0x804B0020)NS_ERROR_UNKNOWN_PROXY_HOST
(0x804B002A)NS_ERROR_UNKNOWN_SOCKET_TYPE
(0x804B0033)NS_ERROR_SOCKET_CREATE_FAILED
(0x804B0034)NS_ERROR_CACHE_KEY_NOT_FOUND
(0x804B003D)NS_ERROR_CACHE_DATA_IS_STREAM
(0x804B003E)NS_ERROR_CACHE_DATA_IS_NOT_STREAM
(0x804B003F)NS_ERROR_CACHE_WAIT_FOR_VALIDATION
(0x804B0040)NS_ERROR_CACHE_ENTRY_DOOMED
(0x804B0041)NS_ERROR_CACHE_READ_ACCESS_DENIED
(0x804B0042)NS_ERROR_CACHE_WRITE_ACCESS_DENIED
(0x804B0043)NS_ERROR_CACHE_IN_USE
(0x804B0044)NS_ERROR_DOCUMENT_NOT_CACHED
(0x804B0046)NS_ERROR_NET_INTERRUPT
(0x804B0047)NS_ERROR_PROXY_CONNECTION_REFUSED
(0x804B0048)NS_ERROR_ALREADY_OPENED
(0x804B0049)- Returned from
nsIChannel.asyncOpen()
when trying to open the channel again (reopening is not supported). NS_ERROR_FIRST_HEADER_FIELD_COMPONENT_EMPTY
(0x804B0022)- While parsing for the first component of a header field using syntax such as that for Content-Disposition: or Content-Type:, the first component was found to be empty.
JavaScript Errors
These errors typically occur when interfacing between JavaScript and native code, or to XPCOM components.
- NS_ERROR_XPC_NOT_ENOUGH_ARGS (0x80570001)
- NS_ERROR_XPC_NEED_OUT_OBJECT (0x80570002)
- NS_ERROR_XPC_CANT_SET_OUT_VAL (0x80570003)
- NS_ERROR_XPC_NATIVE_RETURNED_FAILURE (0x80570004)
- NS_ERROR_XPC_CANT_GET_INTERFACE_INFO (0x80570005)
- NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO (0x80570006)
- NS_ERROR_XPC_CANT_GET_METHOD_INFO (0x80570007)
- NS_ERROR_XPC_UNEXPECTED (0x80570008)
- NS_ERROR_XPC_BAD_CONVERT_JS (0x80570009)
- NS_ERROR_XPC_BAD_CONVERT_NATIVE (0x8057000A)
- NS_ERROR_XPC_BAD_CONVERT_JS_NULL_REF (0x8057000B)
- NS_ERROR_XPC_BAD_OP_ON_WN_PROTO (0x8057000C)
- NS_ERROR_XPC_CANT_CONVERT_WN_TO_FUN (0x8057000D)
- NS_ERROR_XPC_CANT_DEFINE_PROP_ON_WN (0x8057000E)
- NS_ERROR_XPC_CANT_WATCH_WN_STATIC (0x8057000F)
- NS_ERROR_XPC_CANT_EXPORT_WN_STATIC (0x80570010)
- NS_ERROR_XPC_SCRIPTABLE_CALL_FAILED (0x80570011)
- NS_ERROR_XPC_SCRIPTABLE_CTOR_FAILED (0x80570012)
- NS_ERROR_XPC_CANT_CALL_WO_SCRIPTABLE (0x80570013)
- NS_ERROR_XPC_CANT_CTOR_WO_SCRIPTABLE (0x80570014)
- NS_ERROR_XPC_CI_RETURNED_FAILURE (0x80570015)
- NS_ERROR_XPC_GS_RETURNED_FAILURE (0x80570016)
- NS_ERROR_XPC_BAD_CID (0x80570017)
- NS_ERROR_XPC_BAD_IID (0x80570018)
- NS_ERROR_XPC_CANT_CREATE_WN (0x80570019)
- NS_ERROR_XPC_JS_THREW_EXCEPTION (0x8057001A)
- NS_ERROR_XPC_JS_THREW_NATIVE_OBJECT (0x8057001B)
- NS_ERROR_XPC_JS_THREW_JS_OBJECT (0x8057001C)
- NS_ERROR_XPC_JS_THREW_NULL (0x8057001D)
- NS_ERROR_XPC_JS_THREW_STRING (0x8057001E)
- NS_ERROR_XPC_JS_THREW_NUMBER (0x8057001F)
- NS_ERROR_XPC_JAVASCRIPT_ERROR (0x80570020)
- NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS (0x80570021)
- NS_ERROR_XPC_CANT_CONVERT_PRIMITIVE_TO_ARRAY (0x80570022)
- NS_ERROR_XPC_CANT_CONVERT_OBJECT_TO_ARRAY (0x80570023)
- NS_ERROR_XPC_NOT_ENOUGH_ELEMENTS_IN_ARRAY (0x80570024)
- NS_ERROR_XPC_CANT_GET_ARRAY_INFO (0x80570025)
- NS_ERROR_XPC_NOT_ENOUGH_CHARS_IN_STRING (0x80570026)
- NS_ERROR_XPC_SECURITY_MANAGER_VETO (0x80570027)
- NS_ERROR_XPC_INTERFACE_NOT_SCRIPTABLE (0x80570028)
- NS_ERROR_XPC_INTERFACE_NOT_FROM_NSISUPPORTS (0x80570029)
- NS_ERROR_XPC_CANT_GET_JSOBJECT_OF_DOM_OBJECT (0x8057002A)
- NS_ERROR_XPC_CANT_SET_READ_ONLY_CONSTANT (0x8057002B)
- NS_ERROR_XPC_CANT_SET_READ_ONLY_ATTRIBUTE (0x8057002C)
- NS_ERROR_XPC_CANT_SET_READ_ONLY_METHOD (0x8057002D)
- NS_ERROR_XPC_CANT_ADD_PROP_TO_WRAPPED_NATIVE (0x8057002E)
- NS_ERROR_XPC_CALL_TO_SCRIPTABLE_FAILED (0x8057002F)
- NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED (0x80570030)
- NS_ERROR_XPC_BAD_ID_STRING (0x80570031)
- NS_ERROR_XPC_BAD_INITIALIZER_NAME (0x80570032)
- NS_ERROR_XPC_HAS_BEEN_SHUTDOWN (0x80570033)
- NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN (0x80570034)
- NS_ERROR_XPC_BAD_CONVERT_JS_ZERO_ISNOT_NULL (0x80570035)
- NS_ERROR_XPC_COM_UNKNOWN (0x80570036)
- NS_ERROR_XPC_COM_ERROR (0x80570037)
- NS_ERROR_XPC_COM_INVALID_CLASS_ID (0x80570038)
- NS_ERROR_XPC_COM_CREATE_FAILED (0x80570039)
- NS_ERROR_XPC_IDISPATCH_NOT_ENABLED (0x8057003A)
XPath Errors
Errors that can occur when using XPath expressions.
- NS_ERROR_XPATH_PARSE_FAILURE (0x80600002)
- NS_ERROR_XPATH_UNKNOWN_FUNCTION (0x80600005)
- NS_ERROR_XPATH_BAD_ARGUMENT_COUNT (0x8060000D)
- NS_ERROR_XPATH_BAD_EXTENSION_FUNCTION (0x8060000E)
- NS_ERROR_XPATH_PAREN_EXPECTED (0x8060000F)
- NS_ERROR_XPATH_INVALID_AXIS (0x80600010)
- NS_ERROR_XPATH_NO_NODE_TYPE_TEST (0x80600011)
- NS_ERROR_XPATH_BRACKET_EXPECTED (0x80600012)
- NS_ERROR_XPATH_INVALID_VAR_NAME (0x80600013)
- NS_ERROR_XPATH_UNEXPECTED_END (0x80600014)
- NS_ERROR_XPATH_OPERATOR_EXPECTED (0x80600015)
- NS_ERROR_XPATH_UNCLOSED_LITERAL (0x80600016)
- NS_ERROR_XPATH_BAD_COLON (0x80600017)
- NS_ERROR_XPATH_BAD_BANG (0x80600018)
- NS_ERROR_XPATH_ILLEGAL_CHAR (0x80600019)
- NS_ERROR_XPATH_BINARY_EXPECTED (0x8060001A)
- NS_ERROR_XPATH_INVALID_EXPRESSION_EVALUATED (0x8060001C)
- NS_ERROR_XPATH_UNBALANCED_CURLY_BRACE (0x8060001D)
XSLT Errors
Errors that can occur when using XSLT.
- NS_ERROR_XSLT_PARSE_FAILURE (0x80600001)
- NS_ERROR_XSLT_ALREADY_SET (0x80600003)
- NS_ERROR_XSLT_EXECUTION_FAILURE (0x80600004)
- NS_ERROR_XSLT_BAD_RECURSION (0x80600006)
- NS_ERROR_XSLT_BAD_VALUE (0x80600007)
- NS_ERROR_XSLT_NODESET_EXPECTED (0x80600008)
- NS_ERROR_XSLT_ABORTED (0x80600009)
- NS_ERROR_XSLT_NETWORK_ERROR (0x8060000A)
- NS_ERROR_XSLT_WRONG_MIME_TYPE (0x8060000B)
- NS_ERROR_XSLT_LOAD_RECURSION (0x8060000C)
- NS_ERROR_XSLT_LOAD_BLOCKED_ERROR (0x8060001B)
- NS_ERROR_XSLT_BAD_NODE_NAME (0x8060001E)
- NS_ERROR_XSLT_VAR_ALREADY_SET (0x8060001F)
Miscellaneous Errors
Other errors that can occur.
- NS_ERROR_PLUGINS_PLUGINSNOTCHANGED (0x804C03E8)
- NS_ERROR_PLUGIN_DISABLED (0x804C03E9)
- NS_ERROR_UCONV_NOCONV (0x80500001)
- NS_ERROR_UDEC_ILLEGALINPUT (0x8050000E)
- NS_IMAGELIB_ERROR_FAILURE (0x80540005)
- NS_IMAGELIB_ERROR_NO_DECODER (0x80540006)
- NS_IMAGELIB_ERROR_NOT_FINISHED (0x80540007)
- NS_IMAGELIB_ERROR_LOAD_ABORTED (0x80540008)
- NS_ERROR_WONT_HANDLE_CONTENT (0x805D0001)
- MOZ_ERROR_STORAGE_ERROR (0x80630001)
- NS_ERROR_SCHEMAVALIDATOR_NO_SCHEMA_LOADED (0x80640001)
- NS_ERROR_SCHEMAVALIDATOR_NO_DOM_NODE_SPECIFIED (0x80640002)
- NS_ERROR_SCHEMAVALIDATOR_NO_TYPE_FOUND (0x80640003)
- NS_ERROR_SCHEMAVALIDATOR_TYPE_NOT_FOUND (0x80640004)
Note: there are other errors in these files:
gfx/public/nsIDeviceContext.h
base/public/nsNetError.h
parser/htmlparser/public/nsIParser.h
layout/base/nsLayoutErrors.h
profile/public/nsIProfileInternal.idl
security/manager/ssl/public/nsICMSMessageErrors.idl
directory/xpcom/base/public/nsILDAPErrors.idl
content/base/public/nsContentErrors.h
See also
- Mozilla Error Lookup lets you quickly look up the error name by its code in different formats.
- Components.results