Hello Thomas, > We have VisualSVN 2.5 Server and TortoiseSvn 1.8. We use path based > authorization with Basic Authentication over Active Directory. > > I have one colleague who has write access to the entire project. > > On his Laptop, despite write access, he can’t commit to some branches (403). > Other branches Work fine. > > He can update and switch revisions on these branches. > > Doing the same commit operation with his credentials on my Laptop works > perfect. > > We ran out of Ideas. (Cleanup, Reset Save Data, update)
Show us server log events for successful commit and the one which fails. See "Where VisualSVN Server logs are stored": http://www.visualsvn.com/support/topic/00028/ -- With best regards, Pavel Lyalyakin VisualSVN Team
