
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2011 11:41 PM
After a server reboot, IIS wouldn't start since IIS Express was using the binding.
Please fix for release.
Please fix for release.
Labels:
- Labels:
-
Archive
7 REPLIES 7

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2011 08:35 AM
We were able to reproduce the problem.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2011 10:27 PM
lansweeper is on 443, IIS Express I don't know since it's installed by the beta installer. Anyway, there seems to be a misconfiguration in there.
I see that in IISExpress..config:
<sites>
<site name="Lansweeper" id="1" serverAutoStart="true">
<application path="/" applicationPool="Clr2ClassicAppPool">
<virtualDirectory path="/" physicalPath="C:\Program Files\Lansweeper\website" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:80:" />
</bindings>
</site>
I see that in IISExpress..config:
<sites>
<site name="Lansweeper" id="1" serverAutoStart="true">
<application path="/" applicationPool="Clr2ClassicAppPool">
<virtualDirectory path="/" physicalPath="C:\Program Files\Lansweeper\website" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:80:" />
</bindings>
</site>

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2011 12:12 PM
physh wrote:
lansweeper is on 443, IIS Express I don't know since it's installed by the beta installer. Anyway, there seems to be a misconfiguration in there.
I see that in IISExpress..config:
<sites>
<site name="Lansweeper" id="1" serverAutoStart="true">
<application path="/" applicationPool="Clr2ClassicAppPool">
<virtualDirectory path="/" physicalPath="C:\Program Files\Lansweeper\website" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:80:" />
</bindings>
</site>
IIS express is only installed if you used the "lansweeper build-in webserver" before.
Maybe you had both installed on the machine?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2011 04:58 PM
Lansweeper wrote:
IIS express is only installed if you used the "lansweeper build-in webserver" before.
Maybe you had both installed on the machine?
I can tell you when I installed the beta, it installed IIS Express as well, and I never used the built-in webserver on this box. It has always used "True" IIS.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2011 05:13 PM
dteague wrote:
I can tell you when I installed the beta, it installed IIS Express as well, and I never used the built-in webserver on this box. It has always used "True" IIS.
Did you do an upgrade of the existing installation or a new installation?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2011 08:44 PM
Lansweeper wrote:
Did you do an upgrade of the existing installation or a new installation?
Did an upgrade. I was working with someone because the beta install was crashing when looking for SQL servers.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-23-2011 08:47 AM
Are they both bound to the same port?
What was the exact error you got?
When you install with IIS express you can choose a free port.
What was the exact error you got?
When you install with IIS express you can choose a free port.
