Partager via

2.2.2.2.17.1 Error Codes

  • Article

This section specifies a selection of common errors that might require client action, and gives details of the client responses that are suggested. The server expects no specific responses from the client in reply to any specific error; however, there are no restrictions on the protocol server as to which errors can be generated at what time, or on the total set of errors which can be used. Therefore, the client is required to be prepared to handle any errors that are generated. If the client encounters an error it does not recognize or cannot interpret, preferably the client can handle this by outputting the error string (message) to the user. All errors from the server are paired with message strings.

Errors from the following table which are generated by few specific methods, or which suggest client action only in specific cases, will be referenced again in the Methods section of the document (3.1.5.3), as notes associated with the method that generates each error.

Error code

Message

0x0002000C

Write error on file 'value'.

This error can be generated in any case in which the protocol server fails to write a file.

Clients can provide users with the option to retry the operation or to retry with alternate choices in the case that a file cannot be written. If the file in question was being written to the client computer or to a path of the user's choosing, the client can present the user with a more specific response.<1>

0x00020019

Cannot rename 'value' to 'value': destination already exists.

This error can be generated in response to any attempt by the server to rename an object when an object with the chosen name already exists.

The client can provide an error message to the user, and can opt to re-attempt the operation specifying a different value for the destination name.

Methods: move document (section 3.1.5.3.9)

0x00040006

RPC syntax error: expected 'value' after 'value' but saw 'value' instead.

This represents a general syntax error; it can occur whenever the client makes an invalid request. Direct client action is not necessary, other than returning the error to the user; however, this error is noteworthy because it indicates an issue with the client request. Client implementations need to determine why incorrect syntax was provided.

0x0004000B

Client closed connection.

This error is generated in response to the server-client connection being closed unexpectedly on the client side. The client can opt to re-establish and retry whatever transaction was in progress. This error is also noteworthy for client implementations to determine why the connection was closed prematurely.

0x0004000C

The version of Windows SharePoint Services running on the server is more recent than the version of 'value' being used. A more recent version of 'value' is needed.

This error is returned in the case of unsuccessful version negotiation. (This topic is outlined in more detail in section 1.7.)

The client can opt to respond by blocking the attempted action that would follow version negotiation and/or by returning the error to the user directly.

If proper version negotiation occurs, this error is most commonly generated in the context of the server version method (section 3.1.5.3.14), but is not exclusive to that context. 

0x00090002

A file with the name 'value' already exists. It was last modified by 'value' on 'value'.

This error is generated when the server encounters an existing file that was not expected to be present. This error can also occur when "modified by" dates between files sharing the same name were expected to match.

The client can opt to provide this message to the user, or retry the operation with a different file name.

Methods: (move document, remove document (section 3.1.5.3.13), put document (section 3.1.5.3.11), and put documents (section 3.1.5.3.12))

0x00090005

The URL 'value' is invalid. It can refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current web.

This error can be generated when the client requests an invalid URL.

The client can return this message to the user or retry the operation with another URL.<2>

0x00090006

There is no file with URL 'value' in this web.

This error is generated when the client requests a URL that references no known file.

The client can return the error message to the user or retry with another URL. In some situations the client might decide to ignore the error.<3>

0x00090007

The folder that would hold URL 'value' does not exist on the server.

This error can occur either when a directory that the server expected to be present was not found, or when the client requested a folder that was not present.

The client can return the error to the user or retry with another URL. In some situations, the client might decide to ignore the error.<4>

0x0009000D

A folder with the name 'value' already exists.

This error can be generated when an attempt is made to create or rename a folder, and the target folder name already exists.

The client can return this error to the user, or retry the operation again with another folder name.

Methods: create url-directories (section 3.1.5.3.3), create url-directory (section 3.1.5.3.4)

0x0009000E

The file 'value' is checked out or locked for editing by 'value'.

This error is generated when a change (or another lock) is attempted on a file that is already locked.

The client can opt to provide the user with the full error in sharing scenarios.

Method: put document, put documents, checkout document (section 3.1.5.3.2)

0x0009000F

The file 'value' is not checked out.

This error is generated when an upload or check-in/unlock is attempted for an existing document that was not checked out.

The client can return the error message to the user.

Methods: put document, put documents, uncheckout document (section 3.1.5.3.15)

0x0009001E

Some files have been automatically checked out from the source control repository.

This error can be generated in rare cases during document check-in with specific server configuration in source control scenarios.

The client can return the error to the user.<5>

0x00090023

The folder 'value' does not exist. Create the folder and then retry the operation.

This error can be generated when an operation specifies a nonexistent folder name.

The client can return this error to the user, or can opt to prompt the user to retry with another value.

0x000E0002

The method is not recognized.

This error is generated when the server has received an invalid request from the client for a method that does not exist on the server.

No immediate client action has to be taken; this error suggests troubleshooting on the part of client implementations to determine which invalid request the client was generating.

0x0009003E

Only exclusive checkout for document 'value' is supported with SharePoint Designer–based locking.

This error is generated when the client requests shared locking, in the case that the lightweight source control model is enabled. 

The client can opt to display an error message to the user.

Methods: checkout document and get document (section 3.1.5.3.6)

0x001E0002

Access denied.

This is a generic access denied error. The server can generate this error, as opposed to returning a 401 NOT FOUND error, in cases where the server deliberately chooses not to allow the client to reauthenticate.

The client can show the user this error, but cannot attempt to reauthenticate, and cannot treat this as a 401 NOT FOUND error.