Thanks. Our server had been on Subversion 1.1.3, but I upgraded it to
Subversion 1.1.4 and repeated the test. The TortoiseSVN 1.1.3 clients
still get no error, but the TortoiseSVN 1.1.4 clients do get a 500
Internal Server Error when viewing the log, selecting a revision, and
double-clicking a modified file from the modified file list.
The Apache errors from the latest test using TortoiseSVN 1.1.4 clients
are:
[Thu Apr 07 08:10:59 2005] [error] [client 192.168.157.79] (20014)Error
string not specified yet: Can't open file 'C:\\SVNROOT/ort/format': The
system cannot find the path specified.
[Thu Apr 07 08:10:59 2005] [error] [client 192.168.157.79] Could not
fetch resource information. [500, #0]
[Thu Apr 07 08:10:59 2005] [error] [client 192.168.157.79] Could not
open the requested SVN filesystem [500, #720003]
[Thu Apr 07 08:10:59 2005] [error] [client 192.168.157.79] Could not
open
the requested SVN filesystem [500, #720003]
I checked the repository as you suggested with svnadmin verify, and it's
clean.
Arthur
-----Original Message-----
From: Molle Bestefich [mailto:molle.bestefich@gmail.com]
Sent: Thursday, April 07, 2005 7:43 AM
To: Arthur Penn
Subject: Re: [TSVN] TortoiseSVN 1.1.4 - PROPFIND 500 error
You wrote:
> Thanks for the note. There are some errors from my attempts that fall
> into two classes. However, I did revert back to TortoiseSVN 1.1.3 and
am
> no longer having the problems.
You'll "have to" upgrade some day..
> 1) Checksum mismatch problems.
>
> [Thu Apr 08 08:30:09 2004] [error] [client 192.168.157.70] Base
checksum
> mismatch on '/Path/Path/File.xsl':\n expected:
> d56b4d83facca722964639f360a32379\n actual:
> 76c89e00c7a303eee4589efddc8f6129\n [500, #200014]
> [Thu Apr 08 08:30:48 2004] [error] [client 192.168.157.70] Unable to
PUT
> new contents for
>
/svn/repo/!svn/wrk/4bee258e-ff1f-214e-b892-9d86b40eb89b/Path/Path/File.x
> sl. [403, #0]
> [Thu Apr 08 08:30:48 2004] [error] [client 192.168.157.70] Could not
> prepare to write the file [500, #200014]
TortoiseSVN 1.1.4 is using the new 1.1.4 version of the Subversion
libraries.
The bug might be in those. Or it could be that your repository is
corrupt, and that the upgrade of the client libraries to 1.1.4 has
triggered another codepath within the server which causes the above
error.
The above checksum mismatch error seems serious enough though.
Perhaps you should run "svnadmin verify" on your repository.
If it tells you that the repository is OK, you could report your
findings to the Subversion mailing list at dev@subversion.tigris.org.
They will actually know what the error messages mean ;-).
> 2) Non-existent revision issues.
>
> [Thu Apr 08 07:59:01 2004] [error] [client 192.168.157.70] Reference
to
> non-existent revision '223' in filesystem 'C:\\SVNROOT/repo/db' [500,
> #160006]
> [Thu Apr 08 07:59:04 2004] [error] [client 192.168.157.70] Could not
> fetch resource information. [500, #0]
Those two doesn't seem so serious..
> [Thu Apr 08 07:59:04 2004] [error] [client 192.168.157.70] Could not
> open a revision root. [500, #160006]
This one strikes me as odd, but not serious either..
> Any thoughts? Thanks!
Np. I'm not an expert though, so I'm mostly just guessing away.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 7 15:31:52 2005