|
Home > Archive > IIS Server > June 2005 > Apps install to wrong directory
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Apps install to wrong directory
|
|
| Mike Swaim 2005-06-22, 5:57 pm |
| We have an existing Windows 2000 server hosting 2 web sites. The
directory structure is this:
default
| \
site1 site2
That way, when I install an applications, I can specify a directory
like "site1\foo" or "site2\bar" and everything works like a charm.
We have a new 2003 server to replace the old one. It wants to install
everything to site1. So if I try the trick above, I get
default\site1\site1\foo
which isn't what I want at all. Any idea how to fix this on the new
machine?
The msi files are bog standard files created by visual studio.
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| David Wang [Msft] 2005-06-23, 2:48 am |
| FYI: You are really asking a question about what your MSI installer is
doing, which is NOT an IIS issue at all. You need to obtain this information
from the support personnel of the MSI installer you are using. It is not
even an MSI issue because MSI has no code to configure IIS -- someone wrote
custom code to configure IIS in your MSI, and you need to obtain support
from that person.
I am really confused by your notation that there is a "default" parent to
"site 1" and "site 2" because there is no such thing in IIS. A "website" in
IIS would look like:
WebSites
| \
Site1 Site 2
There is no "default". My guess is that you are talking about Virtual
Servers like what Frontpage mentions or the many other misnomers floating
out there -- in which case what you call "site 1" is actually a virtual
directory underneath the "default" website (this is all in
IIS-terminology -- which is unfortunately different from FrontPage, Office,
OWA, etc)
If my guess is correct, you need to delete virtual directory "site 1" and
"site 2" from IIS, and tell the MSI to install at "site 1\foo".
If that doesn't work, then unfortunately, you will have to obtain support
for your MSI and figure out what is wrong. The issue really has nothing to
do with IIS.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mike Swaim" <mswaim@odin.mdacc.tmc.edu> wrote in message
news:%23tK86U3dFHA.3932@TK2MSFTNGP12.phx.gbl...
We have an existing Windows 2000 server hosting 2 web sites. The
directory structure is this:
default
| \
site1 site2
That way, when I install an applications, I can specify a directory
like "site1\foo" or "site2\bar" and everything works like a charm.
We have a new 2003 server to replace the old one. It wants to install
everything to site1. So if I try the trick above, I get
default\site1\site1\foo
which isn't what I want at all. Any idea how to fix this on the new
machine?
The msi files are bog standard files created by visual studio.
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| Wei-Dong XU [MSFT] 2005-06-23, 2:48 am |
| Hi Mike,
Gary Chang has replied your cross issue at platformsdk.MSI newsgroup.
From: v-garych@online.microsoft.com ("Gary Chang[MSFT]")
Date: Thu, 23 Jun 2005 07:08:07 GMT
Subject: RE: Apps install to wrong directory
Newsgroups: microsoft.public.platformsdk.msi
Please feel free to post any further question there. It is our pleasure to
be of any assistance.
Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Mike Swaim 2005-06-23, 6:00 pm |
| David Wang [Msft] wrote:
> I am really confused by your notation that there is a "default"
> parent to "site 1" and "site 2" because there is no such thing in
> IIS. A "website" in IIS would look like:
Go to your handy Windows server, start up Computer Management (Manage
my computer), go to IIS, and click on Web Sites. On the machines that
I've seen, unless it's removed, the first entry is "Default Web Site"
and it always has an ID of 1.
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| David Wang [Msft] 2005-06-24, 2:48 am |
| Actually, I do know what IIS configuration looks like in the UI, so thank
you for the reminder.
My concern is over terminology.
You were talking about two websites, "site 1" and "site 2", and you describe
them them as nested UNDER the "Default" Website.
I need to make sure that what you call "websites" is actually what IIS calls
"Virtual directories"... because it is not possible to nest what IIS
consideres a "website" within another "website". You can nest virtual
directories under each other, though.
In any case, you need to follow up for support from the provider of your MSI
CustomAction for IIS configuration. IIS does not provide anything for MSI,
MSI does not provide any CustomAction for IIS, so we are talking about
arbitrary IIS configuration code from Visual Studio and you need to obtain
support there.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mike Swaim" <mswaim@odin.mdacc.tmc.edu> wrote in message
news:Od7OBd$dFHA.2664@TK2MSFTNGP15.phx.gbl...
David Wang [Msft] wrote:
> I am really confused by your notation that there is a "default"
> parent to "site 1" and "site 2" because there is no such thing in
> IIS. A "website" in IIS would look like:
Go to your handy Windows server, start up Computer Management (Manage
my computer), go to IIS, and click on Web Sites. On the machines that
I've seen, unless it's removed, the first entry is "Default Web Site"
and it always has an ID of 1.
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| Mike Swaim 2005-06-24, 5:59 pm |
| David Wang [Msft] wrote:
> Actually, I do know what IIS configuration looks like in the UI, so
> You were talking about two websites, "site 1" and "site 2", and you
> describe them them as nested UNDER the "Default" Website.
The root directories for site1 and site2 are physical directories
under the "default" site.
> In any case, you need to follow up for support from the provider of
> your MSI CustomAction for IIS configuration. IIS does not provide
> anything for MSI, MSI does not provide any CustomAction for IIS, so
> we are talking about arbitrary IIS configuration code from Visual
> Studio and you need to obtain support there.
The provider is ... Microsoft. When we build web projects with Visual
Studio, and install them, the MSI file "knows" where the virtual root
is. In this case it consistently gets the wrong root. It's obviously
getting the the virtual directory from Windows/IIS. My question is how
does it know, and how can I change it? (And if you know of a better
forum for me to ask in, that'd be great. I've got another conversation
going in platformsdk.msi.)
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| David Wang [Msft] 2005-06-25, 8:47 pm |
| Ok, thanks for clarify that the directories are physical directories under
the default site. Are you sure that there is no metadata configured in IIS
such that it would think "site 1" is not a physical directory but instead a
virtual directory (which would change the "root" to not be "/" but rather
"/site1" -- which may result in that extra "site1" that is injected into
your situation).
I have a feeling that your "site1" is not a real physical directory but
rather a virtual directory. The difference is this -- a physical directory
provides no URL-to-physical mapping, while virtual directory provides a
mapping. This obviously affects how file paths resolve and can inject the
extra "site 1" into the resolved physical path depending on your
configuration.
This also corroborates with your other statement that things seem to want to
install into "site 1" by default instead of the root of the IIS "default"
website.
If this does not help, I can only tell you that the code in question is not
provided by either IIS nor MSI -- it is written by a team in Visual Studio
as a MSI CustomAction in conjunction with their MSI setup wizard tool.
You'll need to look for help there.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mike Swaim" <mswaim@odin.mdacc.tmc.edu> wrote in message
news:%23zP5xOMeFHA.2076@TK2MSFTNGP15.phx.gbl...
David Wang [Msft] wrote:
> Actually, I do know what IIS configuration looks like in the UI, so
> You were talking about two websites, "site 1" and "site 2", and you
> describe them them as nested UNDER the "Default" Website.
The root directories for site1 and site2 are physical directories
under the "default" site.
> In any case, you need to follow up for support from the provider of
> your MSI CustomAction for IIS configuration. IIS does not provide
> anything for MSI, MSI does not provide any CustomAction for IIS, so
> we are talking about arbitrary IIS configuration code from Visual
> Studio and you need to obtain support there.
The provider is ... Microsoft. When we build web projects with Visual
Studio, and install them, the MSI file "knows" where the virtual root
is. In this case it consistently gets the wrong root. It's obviously
getting the the virtual directory from Windows/IIS. My question is how
does it know, and how can I change it? (And if you know of a better
forum for me to ask in, that'd be great. I've got another conversation
going in platformsdk.msi.)
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| Mike Swaim 2005-06-27, 5:53 pm |
| David Wang [Msft] wrote:
> Ok, thanks for clarify that the directories are physical directories
> under the default site. Are you sure that there is no metadata
> configured in IIS such that it would think "site 1" is not a physical
> directory but instead a virtual directory (which would change the
> "root" to not be "/" but rather "/site1" -- which may result in that
> extra "site1" that is injected into your situation).
I have no idea how to tell.
> I have a feeling that your "site1" is not a real physical directory
> but rather a virtual directory.
This is quite possibly the case. Both site1 and site2 are root level
websites. They both have their own IP addresses, and site1's configured
for SSL. (Hopefully, be the end of next week, site 2 will also be
configured for SSL.)
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| Wei-Dong XU [MSFT] 2005-06-28, 2:53 am |
| Hi Mike,
Let's discuss this issue in MSI newsgroup. Since MSI has different site
searching policy in IIS5 & IIS6, this is really not one IIS issue.
Subject: Apps install to wrong directory
Newsgroups: microsoft.public.platformsdk.msi
Please feel free to let me know if you have any question at that thread. It
is our pleasure to be of any assistance.
Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Mike Swaim 2005-06-28, 5:54 pm |
| Wei-Dong XU [MSFT] wrote:
> Let's discuss this issue in MSI newsgroup. Since MSI has different
> site searching policy in IIS5 & IIS6, this is really not one IIS
> issue. Subject: Apps install to wrong directory
> Newsgroups: microsoft.public.platformsdk.msi
OK. I've already got a discussion going there with the same subject.
--
Mike Swaim swaim@hal-pc.org at home | Quote: "Boingie"^4 Y,W & D
MD Anderson Dept. of Biostatistics & Applied Mathematics
mpswaim@mdanderson.org or mswaim@odin.mdacc.tmc.edu at work
ICBM: 29.763N 95.363W|Disclaimer: Yeah, like I speak for MD Anderson.
| |
| Wei-Dong XU [MSFT] 2005-06-29, 2:48 am |
|
You are welcome! Please feel free to let me know if any question at that
thread. My pleasure to be of any assistance.
Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|