Install Web Site to *:80 root path

[nvsoft]

Hi,

I'm creating an installation for a web server which has to be deployed on the server's root path (http://localhost/).
I also need to configure HTTPS access (https://localhost/) and many other settings.

From what I read in the forum, Advanced Installer does not support configuring the Default Web Site.
This conflicts with my requirements because on one hand, I cannot configure the Default Web Site and on the other, I cannot create a new Web Site and assign it to all IPs and port 80 (*:80) because then it conflicts with the existing Default Web Site and does not start automatically after installation.

One answer in this subject instructed to create a new Web Site, name it "Default Web Site" and configure its Error Policy to ask the user whether to overwrite the existing Web Site. This did not work for me. I could not name a new Web Site "Default Web Site" (error message saying one already exists). I created a public property, valued it "Default Web Site" and wrote the name of the property in my new Web Site's name but after installation nothing has changed in the original "Default Web Site".

So how can I create a new Web Site and bind it to the http://localhost & https://localhost without creating a conflict with the existing "Default Web Site".
And how can I direct the existing Default Web Site's physical path to my APPDIR and also bind it to HTTPS.

Thanks.

[mihai.petcu]

Hello,

Currently, overriding the default web site is a prohibited internal operation due to undesired behavior upon uninstall. I have discussed the issue with the development team and added an improvement on our TODO list. This improvement will be available in a future version.

Until then, if you urgently need a workaround, my colleague from the development team can provide a solution via e-mail. The solution will consist in a patch which will stop all web sites that conflict with the one you are installing, before it gets installed on the server. This way you can create another web site, with any given name or bindings( including the default web site's port - 80 ). Please contact us by e-mail to support at advancedinstaller dot com for more details.

Best,
Mihai

[CH_F]

I'm currently evaluating the trial version of Advanced Installer. It seems that it's a really good product, but unfortunatly I run in the same problem as described by the originally post. Is there a solution integrated now?

If I use the bindings of the default web site the default web site has stopped after installation and my new installed web site is running. But after a computer reboot the default web site is running and my web site has stopped because of the conflict using the same port and so on...

[Daniel]

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

A fix for this issue have been added since version 8.1 of Advanced Installer and should not reproducing if you are using our latest version (9.7) of Advanced Installer.

All the best,
Daniel

[CH_F]

Thank you for your fast response!

I'am using the latest version so I tried it on different machines.

The result is that it works on Windows XP SP 3, IIS 5.1. That means after a reboot the installed web site is still running and the default web site is still stopped.
But on Windows 7 Ultimate (32- and 64-Bit), IIS 7.5 it didn't work. After installation the installed web site is running, but after a reboot the default web site is running and the installed one has stopped.

[Daniel]

Hello,

I've tested your scenario and indeed this seems to be an Advanced Installer issue. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention.

All the best,
Daniel

[CH_F]

Thank you!

I found out that it happens also after calling iisreset.exe to stop/start the IIS. A reboot is therefore not needed to try out that behaviour.

The curious thing beside using Advanced Installer is, that when I stop the Default Web Site und start the installed one interactive by the IIS management console, the states are unmodified after reboot or calling iisreset.exe. So it's ok.
But if I use the IIS admin tool appcmd.exe to stop the Default Web Site and start the installed one, then the Default Web Page runs and the installed one has stopped after reboot or calling iisreset.exe. Strange...!?

Wating for a fix now...
Beside that it's a great product and great support!

[Daniel]

Hello,

A fix will be available in the next version of Advanced Installer.

All the best,
Daniel

[Daniel]

Hello,

This was fixed in version 9.8 of Advanced Installer released on December 20, 2012.

All the best,
Daniel

[CH_F]

Now it works! Thanks a lot...

[Daniel]

You're welcome. I'm glad you got this working.

All the best,
Daniel