Lee:
If you only set the port (and do nothing with the IP & Host Header), I would
bet that there is another site using the same Port Number. I would think that
it has to be the case if other installers are working fine.
My advice: Check the sites in IIS (or have someone with the permissions do it).
You are looking for another site (active or disabled) that uses the same Port
Number (on the same IP). David Adams, MCSD MSN MessengerID: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Mon, 13 Aug 2007
09:33:49 -0700Subject: Re: [WiX-users] Wierd IIS issue with Wix
install/uninstall
Well, heres the kicker, I don’t set the HH or the IP ( I assume it’s the local
machine). The only thing I set is the port. L
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adamsSent:
Monday, August 13, 2007 9:09 AMTo: [EMAIL PROTECTED]: Re: [WiX-users] Wierd IIS
issue with Wix install/uninstall
I would suspect that it is something with that site. It is probably either a)
the IP address / Port / [Host Header, if used] has been changed; at which, the
installer would not be able to identify it in IIS or b) for whatever reason,
another site has been added that has the same IP address / Port / [Host Header]
combination & one of them is disabled. Under b), the search for the site
matching the criteria would return an array, but the function would always
return the 1st one (and possibly, not the right one) as the target of the
installer action. I'd make sure that the IP / Port / HH info is correct in the
installer defintion (wxs) and that there is not another web site on the server
that has matching info.David Adams, MCSD MSN MessengerID: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL
PROTECTED]: Mon, 13 Aug 2007 08:45:50 -0700Subject: Re: [WiX-users] Wierd IIS
issue with Wix install/uninstall
Hmm. I am wondering if it is the host header then, because this is just a
recent problem that’s shown up and the other 4 sites uninstall properly, it is
just this one package.
From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 3:38
PMTo: Pierson Lee (Volt); 'david adams'; [EMAIL PROTECTED]: RE: [WiX-users]
Wierd IIS issue with Wix install/uninstall
As I said, because it doesn’t remember the ID number. It’s trying to look up
which one to uninstall based on those three properties: IP, port, and host
header.
Another case where it gets confused is if you have another site with the same
properties which is disabled.
--
Mike Dimmick
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierson Lee
(Volt)Sent: 10 August 2007 23:31To: david adams; [EMAIL PROTECTED]: Re:
[WiX-users] Wierd IIS issue with Wix install/uninstall
I can see where this would be an issue of the IP address changing, but my issue
is with the w3svc ID number that gets assigned and why the MSI thinks it’s a
different number during uninstall then it was during the install portion.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adamsSent:
Friday, August 10, 2007 3:15 PMTo: [EMAIL PROTECTED]: Re: [WiX-users] Wierd IIS
issue with Wix install/uninstall
We overcome this issue by setting the install IP address to a property value.
The property value is set (for default purposes) within the WiX file; however,
we have added a custom dialog that allows the Install User to override the
property value with a User-input one. Whether the default value or a User-input
one is the actual IP address used, we persist the value to the machine registry
for use on uninstall. Note: This does introduce a risk if someone invalidates
the value in the registry, but we accept that risk for the benefit installing
to IP addresses that may be unknown at the time that the MSI is built.
<Property Id="WEBADDRESSIP_DEV" Value="10.1.20.84"> <RegistrySearch
Id="DevIpSearch" Root="HKLM" Key="SOFTWARE\Crawford\[APPREGKEY]\IpAddresses"
Name="Development" Type="raw" /></Property><Component
Id="CreateTemplateAppPool" Guid="0D9804CB-CEE4-4D2D-8B9B-A8455AC035E4">
<WebAppPool Id="TemplateAppPool" Identity="networkService" IdleTimeout="20"
MaxWorkerProcesses="1" Name="[APPPOOLNAME]" QueueLimit="4000"
RecycleMinutes="1740" /></Component><Component Id="CreateTemplateWebSiteDev"
Guid="54A19EA6-828D-45CA-9CB4-06E989E0CB66"> <WebSite
Id="TemplateWebSiteDev" AutoStart="no" ConnectionTimeout="120"
Description="[WEBSITEDESC]" Directory="INSTALLLOCATION" StartOnInstall="no"
DirProperties="VDirProperties"> <WebAddress Id="TemplateWebAddressDev"
IP="[WEBADDRESSIP_DEV]" Port="80" /> <WebApplication
Id="TemplateWebApplicationDev" AllowSessions="yes" Buffer="yes"
ClientDebugging="no" DefaultScript="VBScript" Name="[WEBAPPLICATIONNAME]"
ServerDebugging="no" SessionTimeout="20" WebAppPool="TemplateAppPool" />
</WebSite></Component><Component Id="CreateWebSiteDevKey"
Guid="A89D6667-C0F1-485C-9F2B-3A65F9676920"> <Registry Id="WebSiteDevKey"
Root="HKLM" Key="SOFTWARE\Crawford\[APPREGKEY]\IpAddresses" Name="Development"
Action="write" Type="string" Value="[WEBADDRESSIP_DEV]" /></Component>David
Adams, MCSD MSN MessengerID: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Fri, 10 Aug 2007
23:04:28 +0100Subject: Re: [WiX-users] Wierd IIS issue with Wix
install/uninstall
WiX only looks at the combination of IP address(es), port number, and Host
header. If any of those have been changed post-installation, the custom action
may either not uninstall or uninstall the wrong site.
The problem here is that IIS’s metabase schema does not offer anywhere for WiX
to put a cookie that the user cannot subsequently edit (there is a Comment
field but that’s user-editable). In theory, WiX should generate the site number
and store it elsewhere (e.g. in the registry), but the current WiX schema
doesn’t allow you to specify a registry path to store it in.
--
Mike Dimmick
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierson Lee
(Volt)Sent: 10 August 2007 21:27To: [EMAIL PROTECTED]: [WiX-users] Wierd IIS
issue with Wix install/uninstall
I am currently installing 4 sites packaged with WiX. I have it installing
app_pools, sites and the necessary files and file structures with each of these
4 on the same server. I noticed some weird behavior today, particularly in
uninstallation.
When I go to uninstall one of my sites, its not deleting the right metabase
path.
So for instance, I install SiteA, SiteB, SiteC, and SiteD. When installing they
are installed in W3SVC/2, 3, 4 and 5 respectively. (I don’t know why they are
always sequential starting at the lowest possible number, but that seems to be
a feature of WiX). When uninstalling SiteC (which was installed at W3SVC/4) it
is attempting to uninstall the metabase path at W3SVC/2.
I’ve caught it doing this a couple times now and I would like to know A) where
does it look to determine where the site was installed at and B) how to
fix/prevent this.
Thanks
See what you’re getting into…before you go there See it!
Messenger Café — open for fun 24/7. Hot games, cool activities served daily.
Visit now.
_________________________________________________________________
Messenger Café — open for fun 24/7. Hot games, cool activities served daily.
Visit now.
http://cafemessenger.com?ocid=TXT_TAGLM_AugWLtagline
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
