I had the same issue. The fix was pretty simple, actually. I have a
public ssl that I use for my website and wanted to use it for
VisualSVN Server. I located an article that describes converting
a .pfx to a pem file (http://blog.scottlowe.org/2006/06/24/converting-
ssl-certificates-with-openssl/). Following the instructions produced
a file a new pem file. After stopping the VisualSVN Server service
and renaming the server.pem to server.pem.original I renamed my newly
converted .pem file to server.pem and copied it into the conf folder.
After starting up the service everything worked well. One thing to
note was that the initial server mmc screen displays a different name
than the certificate's common name until you manually change it in the
mmc config window.
