[cvsnt] Re: Error with 2.0.51a ends with "results may not be correct"
Fish
fish at fish-mail.com
Wed Aug 4 16:50:16 BST 2004
>>Thanks for the suggestion, but that can't be it, or at least there's some
>>other contributing factor, because the user group in question has full
>>control from the root of the repository on down.
>The error literally means a call to FindFirstFile in that directory
>returned access denied, so the permissions aren't what they appear to
>be. Do you have any 'deny' ACLs in there that could be stopping it?
>Your audit log will probably contain a failure provided you have
>auditing enabled.
>Try sharing the repository and letting one of the affected users
>attempt to browse it.
>>Are there any local security policy settings that must be in effect for
CVSNT
>>to function properly?
>Not really, just the defaults will do.
>Tony
There are no deny ACL settings, it's just full control for that group, the
local administrators group, and the local SYSTEM account from the root of the
repository on down. Auditing is also not enabled, so no additional info
there.
Any other ideas? Filesystem permissions on the repository itself seem to be
just fine.
Thanks,
Fish
More information about the cvsnt
mailing list