Couchbase Server Windows Install Failing when Specifying Port other than 8091

When the Windows Couchbase Server install sees that Port 8091 is in use, it prompts the user for another port. This is not working as expected, and upon install completion, the console page does not come up for http://localhost:9090/index.html (or whatever port is specified). In looking at a Windows port monitor, nothing is showing on Port 9090, even after restarting the Couchbase service. This configuration may be needed by customers if they have another service already running on Port 8091. If this other service is stopped, then the Couchbase Console does indeed come up, but only on Port 8091 (even if another port is specified during setup).

Running the following command after installation to reconfigure the Couchbase server from port 8091 to port 9090 and then restarting the Windows Service does allow it to work on another port, but is not an ideal customer experience.

couchbase-cli.exe cluster-init -c localhost:8091 -u Administrator -p <admin password> --cluster-init-port=9090

Steps to Reproduce:

• Configure a Windows system with IIS on Port 8091, for example, prior to Couchbase install.
• Run the Couchbase installer, and note the install dialog popup, prompting for a different port
• Enter 9090 as the port
• Complete the setup
• Note that the Console does not launch after setup on Port 9090, says "cannot connect"
• Note that after stopping IIS, the console does start, but does so on Port 8091

Expected Behavior: The Couchbase Console should launch on the specified port upon completion of setup.