I just posted that we've been stumped here as well, but I found something that worked for us. My original problem was when using a saved username/password with the Tortoise gui, so I tried on the command line and manually specified my username/password (svn update -- username asdf --password asdf) and it worked. So, tried clearing the Tortoise saved login info, and it ended up working once I was prompted.
Sorry I can't provide a root cause, but hopefully this helps someone - Sam On Dec 15, 9:48 am, CGU75 <carl.gustafs...@gmail.com> wrote: > We have also problems with this. Some of our coworkers can not UPDATE. > The only solution we have come up with is to CHECKOUT the entire repos > again, which is not a good solution... > > I am also interested in a solution to this. Bugfix? > > Regards > Carl > > On 26 Nov, 20:32, teee...@gmail.com wrote: > > > I am getting the same error . Is this a known bug. > > I am using 1.5 .3 Version on SVN and When I try to commit to > > repository it throws Commit failed. > > Server sent Unexpected return value (403 Forbidden ) in respons to > > MKACTIVITY > > > Please provide a resolution. > > > On Nov 26, 7:19 am, ilan.ya...@gmail.com wrote: > > > > Hi all. > > > > I was trying to browse via repo-browser, and I got error message > > > when I wrote the URL:https://vm03.timetoknow.local:8443/svn > > > I got the error: "server sent unexpected return value (405 method not > > > allowed) in response to PROPFIND request for svn." > > > > So I tried to checkout files from the repository > > > I wrote the command: > > > svn cohttps://vm03.timetoknow.local:8443/svn/dev/LMS/branch/v2.3/2.3 > > > > And I got the following error: > > > svn: Server sent unexpected return value (403 Forbidden) in response > > > to OPTIONS > > > request for 'https://vm03.timetoknow.local:8443/svn/dev/LMS/branch/ > > > v2.3/2.3' > > > > I was working with SVN 1.4.5 without Apache, and then I moved the > > > folders to another server, installed the VisualSVN working with > > > Apache. I added the repository, so I can see it with the visualSVN, > > > and I can browse there but I can't work remotely. > > > > Why am I getting those errors ?
