Opened 16 years ago
Closed 15 years ago
#359 closed defect (wontfix)
IIS component configuration not guaranteed to succeed.
| Reported by: | jng | Owned by: | jng |
|---|---|---|---|
| Priority: | medium | Milestone: | |
| Component: | Installer | Version: | 1.2.0 |
| Severity: | minor | Keywords: | installer iis |
| Cc: | External ID: |
Description
I've been noticing with some recent installs of MapGuide Web Server Extensions on Windows Server 2003, that when I choose the IIS configuration, any or all of the following things can happen.
- IIS script maps won't register. (.php and .fcgi extensions)
- "mapviewerajax" virtual directory does not get created.
- "mapviewernet" virtual directory won't be configured as an application.
It is frustrating because I have to find out which aspect of the IIS configuration failed, and there is no way to tell.
Change History (7)
comment:1 by , 16 years ago
| Version: | → 1.2.0 |
|---|
comment:2 by , 16 years ago
| Severity: | major → minor |
|---|
comment:3 by , 16 years ago
comment:4 by , 15 years ago
| Component: | General → Installer |
|---|
comment:5 by , 15 years ago
I am curious to know if the new installer exhibits this same behaviour. My test runs so far on Win 2k3 return a 100% success rate on configuring IIS so far.
comment:6 by , 15 years ago
| Owner: | set to |
|---|
comment:7 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Closing as I cannot really reproduce this problem with the new installer
Note:
See TracTickets
for help on using tickets.
I've seen some weirdness in installation on IIS too.
For instance, I just installed the .Net installation (selecting PHP apis also during custom install) for IIS on w2k3. Installation went fine, but all of the virtual directories were configured for .Net 1.1 instead of 2.0.
I've been trying to find some time to write an NSIS installer for MapGuide OS... it's relatively simple to learn, but the initial script creation takes some time. It would be great if we could do this in an open way though. That way users that want things like web application pools, selection of the website to install to, what path to install to, etc could all scratch their own itches.