We seem to have solved this by disabling and reenabling the sid cache (http://support.microsoft.com/kb/946358) and restarting the subversion service.
On May 28, 2:16 pm, Barry <dive...@gmail.com> wrote: > We have been using VisualSVN server since December 2008 and have since > upgraded to version 1.7. Last week we updated the SSL certificate, > and apparently starting yesterday we are experiencing "500 Internal > Server Error." I have tried various clients for connecting and have > received the error on all (command line, SmartSVN, and TortoiseSVN). > The client message comes in many flavors: > "REPORT of '<some_svn_repo_path>': 500 Internal Server Error (https:// > corp-svn01)" > "OPTIONS request failed on '<some_svn_repo_path>'" > "GET request failed for '<some_svn_repo_path>/<filename>': 500 > Internal Server Error (https://corp-svn01) REPORT request failed on '/ > svn/netspend/!svn/vcc/default'" > "PROPFIND of '<some_svn_repo_path>/<filename>': 500 Internal Server > Error (https://corp-svn01) REPORT request failed on '/svn/netspend/! > svn/vcc/default'" > > and the resulting entry in the event viewer on corp-svn01 appears to > allways be: > "LookupAccountSid() failed. > [client <my_ip>]" > > Any ideas what could be causing this issue?