Hi! According to the event logs you've sent us the error message:
"Error writing base64 data: APR does not understand this error code [500, #620019]" и "Provider encountered an error while streaming a REPORT response. [500, #0]" means that data transmission was interrupted by the client ahead of time for some reasons. The following error message means that the client has problems with the working copy: [[ Error writing base64 data: APR does not understand this error code [500, #620019] [client 172.16.200.123] A failure occurred while driving the update report editor [500, #620019] [client 172.16.200.123] Provider encountered an error while streaming a REPORT response. [500, #0] [client 172.16.200.123] ]] On Mon, Mar 2, 2009 at 6:20 PM, David Beahm <[email protected]> wrote: > Thanks for the feedback. Unfortunately, we set the relevant group to have > read/write to the root repository from the start. Generally this problem > has been quiet, but I saw the errors again last Friday (2/27). > > We are using TortoiseSVN 1.5.6, Build 14908 - 32 Bit , 2008/12/20 11:51:04. > (I know there are newer versions, but I want to limit the number of > variables). > > Building on your comment: Is there some sort of debug flag we could set for > more verbose logging? > > Best, > David > > > On Thu, Feb 26, 2009 at 11:03 AM, Sekar <[email protected]> wrote: >> >> After I noticed it with 1 user, i started getting complaints from >> several other developers working on separate repositories that they >> are also getting the same issue. The issue came ONLY when the >> developer was trying to update at the root level. They were able to >> update at an individual file level. I had not changed the access >> permissions in a while. The way I was able to get around it was to >> give the individual read access at the repository level and read-write >> at the branch level. Before, the individual had no access at the root >> level and read-write at the branches level (Tags & trunk were >> basically off limits). With this change, the error went away for >> everyone. Also the client used in all cases is TortoiseSVN >> >> I really like VisualSVN server and is a very convenient and quality >> product. Having said that, its integration with Windows authentication >> (using Active directory) is very fickle. I manage about 6 production >> repositories with numerous branches and have encountered errors in one >> repository/branch that doesn't occur for the same permissions in >> another repositories. The problems are exacerbated if I use Active >> directory groups or an individual is a member of multiple groups >> (Built in user & in AD group). There is no clear way to figure out >> from the error messages in the even viewer as to where the access >> privilege was derived to request access from the server. I guess >> better control of logging here would be very useful. I dont know of a >> way to control logging in the VisualSVN server. >> >> On Feb 25, 3:03 pm, VisualSVN Support <[email protected]> wrote: >> > Hi! >> > >> > >Same situation as above >> > >> > Could you please provide any details when does this error occur ? Does >> > it occur on commit? >> > >> > >> This happens for only 1 userid. >> > >> > Could you please check the difference in the access permissions for >> > this userid and others (both in Subversion and domain)? >> > >> > Please also could you check the Event Log and send us all information >> > related to VisualSVN Server? >> > >> > Thank you! >> > >> > >> > >> > On Wed, Feb 25, 2009 at 10:05 PM, Sekar <[email protected]> wrote: >> > >> > > Same issue. VisualSVN 1.6.3 on Windows XP. Just before this trio of >> > > error messages and exactly 1 second before this trio of error >> > > messages, this message is in the Event Viewer >> > >> > > Access denied: 'uid' OPTIONS reponame:/ >> > > [client 192.xxx.xxx.xxx] >> > >> > > This happens for only 1 userid. Same situation as above, Active >> > > Directory Authentication using domain accounts. I don't have any >> > > triggers. >> > >> > > Thanks >> > >> > > On Feb 23, 10:57 am, VisualSVN Support <[email protected]> wrote: >> > >> Hi! >> > >> > >> Please provide more information on the problem. >> > >> > >> Could we ask you to check the Event Log and send us all information >> > >> related to VisualSVN Server? >> > >> > >> Could you please send the detailed script of your actions? >> > >> > >> >We also see that the post-commit trigger is not firing. >> > >> > >> Did you have any problems before adding this post-commit trigger? >> > >> Please could you specify when did the problem appear? >> > >> > >> Thank you! >> > >> > >> On Mon, Feb 23, 2009 at 6:57 PM, dbeahm <[email protected]> wrote: >> > >> > >> > Running VisualSVN Server 1.6.3 on Windows Server 2003 SP2 >> > >> > >> > We are seeing the following event log entries: >> > >> > >> > Error writing base64 data: APR does not understand this error code >> > >> > [500, #620019] >> > >> > [client 172.16.200.123] >> > >> > A failure occurred while driving the update report editor [500, >> > >> > #620019] >> > >> > [client 172.16.200.123] >> > >> > Provider encountered an error while streaming a REPORT response. >> > >> > [500, #0] >> > >> > [client 172.16.200.123] >> > >> > >> > We also see that the post-commit trigger is not firing. Any >> > >> > suggestions? >> > >> > >> -- >> > >> Olga Dolidze >> > >> VisualSVN Support >> > >> > -- >> > Olga Dolidze >> > VisualSVN Support > > -- Olga Dolidze VisualSVN Support
