I got it to work. The group I was trying to use was a distribution list and not a security group. Once the group was upgraded to a security group, I was able to commit as expected.
I'm not sure if its possible or not to check that attribute in code when a group is selected, but it would be nice to popup a warning if its a distribution list and not a secruity group. -Adam On Oct 29, 3:42 pm, "adam.c.main" <[EMAIL PROTECTED]> wrote: > I uninstalled VisualSVN Server and reinstalled it. During the > install, I let it install to the default locations and chose windows > authentication. The default locations (c:\Repositories and C:\Program > Files\VisualSVN Server) did not exist before installing. I created a > new repository adding the default structure. I changed the permissions > of Builtin\Users to read only for the root permissions. On my new > repository, I added an AD Group and gave it read/write access. > > On a different system, I was able to checkout the newly created > repository, which consisted of 3 folders (branches, trunk, and tags). > I created a new text file, entered in a line of text and tried to > commit it. It failed with "Server sent unexpected return value (403 > Forbidden) in response to MKACTIVITY". Without removing my group from > the permssions, I added my user specifically. I was able to commit > successfully. I removed my specific user, but not the AD group that > the user is in, and I am no longer able to commit (same 403 error). > Is there more configuration needed other than to select windows > authentication during the install? Does the VisualSVN service need to > run with special permissions? > > Any help at all would be appreciated. > > -Adam >
