Can update_option store compressed data


Error messages

Cannot copy / move 'XXX' to 'YYY': The specified file was not found.

This error usually appears when updating the working copy. The reason for the error is either:

  • There are two different files in the repository where the file name only differs in upper / lower case. This may not work on Windows because Windows sees these two files as just one. It is very likely that one of these files was added incorrectly. Find out which it is and delete this file with the repository browser.
  • There is a file in the repository with a file name which is not allowed under Windows. For example "con", "lpr", "com", etc. are not allowed as file names under Windows because these names are used for devices. And of course file names cannot use characters like "/ \ * ?: |" and contain some other special characters.

Yes, we also know that the error message is not very helpful in this case. But the error message is generated by the Subversion library and TortoiseSVN cannot change it on its own.

Cannot move 'XXX' to 'YYY': The file or folder is damaged or unreadable.

This error message usually appears during an update or when transferring a working copy and is mainly found on Windows 7. This error occurs when another process has a file open while Subversion is trying to move or modify the file. This other process can be a virus scanner, for example. Configure this so that the working copies are not continuously examined by the virus scanner.

Note: An error in Windows7 can also be the cause of this error message. The error has been corrected with Service Pack 1 for Windows7.

Cannot open file 'XXX': The process cannot access the file because the file is open in another process.

Users who receive this error usually report that this error only occurs randomly during a mostly larger transmission.

The most likely reason for this error is an incorrectly configured virus scanner, which examines the files which Subversion creates for the transfer for too long and therefore keeps the file open. Try to deactivate the virus scanner or at least configure it so that it leaves the working copies and TortoiseSVN alone.

The client is too old to work with the working copy 'XXX'.

This error occurs when you are using an SVN client which is a higher version than the client you are using now.

The reason for this is that Subversion clients automatically update the working copy to newer versions with the first command executed on the working copy. Once a working copy has been updated to newer versions in this way, older Subversion clients can no longer access it.

The only way to fix this problem is to update all SVN clients you are using to the same version (the version of the SVN library the client is using). Or you may need to check out the working copy again.

Cannot write to standard output

TortoisePlink uses the standard Plink code, but is created as a window application so that the command line window does not appear with every connection. However, this means that Plink cannot display error messages without a command line window. If this occurs, this meaningless error message appears instead.

Therefore in this case you should not use TortoisePlink first, but the right Plink tool. The correct error messages are then displayed and you can then set up and configure the server correctly. As soon as the connection with Plink works correctly, you can use TortoisePlink again.

400 Bad Request

REPORT request failed on '...' REPORT of '...': 400 Bad Request (http: // ...)

This error occurs when a firewall or proxy server blocks the DAV requests. Unfortunately, this is the case with most firewalls / proxy servers in the standard setting. You must configure the firewall or proxy server in such a way that DAV requests are allowed through without change. Some virus scanners also block such DAV requests.

Another way to avoid this error is to use SSL, so https: // instead of http: // to use for the connection to the repository.

403 Forbidden

PROPFIND request failed: 403 Forbidden

The most likely cause of this error is that you specified the path to the parent directory instead of the path to the repository itself. Try appending the name of the repository to the URL. The URL must also have a slash at the end after the name of the repository.

For more detailed information about this error, please refer to the Apache error log.

405 HTTP Method Not Allowed

PROPFIND Request Failed - Error 405 HTTP Method Not Allowed

This error occurs in different variations. You will see this error when:

  • PROPFIND Request Failed You forgot to put a '/' slash at the end of the url.
  • PROPFIND Request Failed You are trying to access the repository, but a proxy server between TortoiseSVN and the repository does not let DAV requests through. With a web browser, however, you can access the repository without problems, only with TortoiseSVN or other SVN clients you get this error. You have to configure your firewall / proxy server so that DAV requests are allowed through. Or use https: // instead of http: // - most firewalls or proxy servers cannot block encrypted data and therefore allow DAV-Request it https: // through.
    Another possibility for this error is a virus scanner on your computer, which also blocks DAV requests.
  • Lock Request Failed You tried to lock a file in your working copy that no longer exists in the repository. Update your working copy.

More detailed information on such errors can be found in the error log of your Apache server.