Re: Setting up VisualSVN server - how to integrate to existing Apache

On Fri, 17 Nov 2017 17:38:20 +0300, Pavel Lyalyakin
<pavel.lyalyakin_at_visualsvn.com> wrote:

>> So my existing Apache 2.2.22 installation will remain as-is and the
>> one that comes with VisualSVN will be another service working on
>> another port?
>
>Yes.

Now back at home where I have a 180 day evaluation Windows Server
2016, on which there is no Apache running. So I tried to install
VisualSVN on this server instead.
But when I got to the "Inital Server Configuration" page I got an
error message when I hit Next saying that port 443 is occupied by
another service.
I believe that the culprit is the IIS server that is part of Windows
Server 2016, but I cannot confirm this nor can I prove it because
"netstat -abp tcp" does not show the owner of the port.
If I use the dropdown for "Server Port" the only alternative seems to
be 8443...

What will happen if I select this port instead?
Will I then have a non-standard SVN installation?

-- 
Bo Berglund
Developer in Sweden