Thanks Blair. But when I install the msi directly instead using octopus I still get the same error.
Below error I found from the verbose logs WriteMetabaseChanges: Error 0x80070057: failed to create web application: /Root/ROMBSCALLBACK MSI (c) (A4:90) [22:41:07:112]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 26105. Failed to create web application. (-2147024809 /Root/ROMBSCALLBACK ) MSI (s) (14!7C) [22:41:12:080]: Product: ROMBSCallBack -- Error 26105. Failed to create web application. (-2147024809 /Root/ROMBSCALLBACK ). I created a new website and installed the same msi and it installed correctly. Not sure what is the difference between the old and new website. Any idea where exactly its going wrong. Thanks In Advance, Regards, Sandeep. -----Original Message----- From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-requ...@lists.sourceforge.net] Sent: Wednesday, September 16, 2009 2:13 PM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 40, Issue 68 Send WiX-users mailing list submissions to wix-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wix-users or, via email, send a message with subject or body 'help' to wix-users-requ...@lists.sourceforge.net You can reach the person managing the list at wix-users-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of WiX-users digest..." Today's Topics: 1. launching page localization (Lian Jiang) 2. launching page localization (DE?K JAHN, G?bor) 3. How to save project build output in Visual Studio? (Demyn Plantenberg) 4. Failed to create web application. (-2147024809) (Sandeep Kumar Bushnam (Wipro Ltd.)) 5. Re: Failed to create web application. (-2147024809) (Blair) 6. Re: launching page localization (Blair) 7. Re: Conditional installed based on REG_MULTI_SZ value (Dominique Louis) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Sep 2009 19:59:35 +0000 From: Lian Jiang <lji...@microsoft.com> Subject: [WiX-users] launching page localization To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Message-ID: <f569b1ee9bbff14ba7e1069a5ca9b2a50152f...@tk5ex14mbxc111.redmond.corp.microsoft.com> Content-Type: text/plain; charset="us-ascii" Hi, I localized all strings used in my installer UI. The installer is a MUI based msi which means the same MSI can work on different locale machines and shows the strings in the corresponding locale. All dialogs works fine except that the launching page (the verify first dialog showing something like "installation starts ...") shows strings incorrectly. For example, I saw it shows other language when running on an en-us machine and it shows English when running on other locales machine. The launching page shown in en-us locale machine is attached. Thanks for any clue. Thanks Lian ------------------------------ Message: 2 Date: Tue, 15 Sep 2009 22:22:04 +0200 From: "DE?K JAHN, G?bor" <d...@tramontana.co.hu> Subject: [WiX-users] launching page localization To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Message-ID: <200991522224.001...@pernix> Content-Type: text/plain; charset="iso-8859-2" On Tue, 15 Sep 2009 19:59:35 +0000, Lian Jiang wrote: Lian, You probably mean the very first small message about the installation launching. This is displayed by the Windows Installer, not your installer. So, no matter how fully you have localized yours, this message will display in the actual Windows system language your installer is running on. Bye, G?bor ------------------------------------------------------------------- DE?K JAHN, G?bor -- Budapest, Hungary E-mail: d...@tramontana.co.hu ------------------------------ Message: 3 Date: Tue, 15 Sep 2009 13:34:22 -0700 From: Demyn Plantenberg <de...@almaden.ibm.com> Subject: [WiX-users] How to save project build output in Visual Studio? To: wix-users <wix-users@lists.sourceforge.net> Message-ID: <of684d9bd1.a396ed84-on88257632.006fd108-88257632.00710...@us.ibm.com> Content-Type: text/plain; charset=US-ASCII We have a WiX project in our VS 2008 solution. I would like to save the project's build output to a file like BuildLog. Any ideas? Regards, Demyn ------------------------------ Message: 4 Date: Wed, 16 Sep 2009 05:57:19 +0000 From: "Sandeep Kumar Bushnam (Wipro Ltd.)" <v-san...@microsoft.com> Subject: [WiX-users] Failed to create web application. (-2147024809) To: "wix-users@lists.sourceforge.net" <wix-users@lists.sourceforge.net> Message-ID: <3828038621c0a3479f2fbf005eb39c59102b6...@tk5ex14mbxc103.redmond.corp.microsoft.com> Content-Type: text/plain; charset="us-ascii" Hi Team, My MSI creates a virtual directory under a default website and creates a new web application under existing App pool(this case DefaultAppPool). Which is working fine on windows 2003 OS. When I install the same MSI using Microsoft Octopus from Win7 onto windows 2003 server the installer throws below error. [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Failed to create web application. (-2147024809 /Root/ROMBSCALLBACK ) [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Error Code 1603: Fatal error during installation. (Exception from HRESULT: 0x80070643) [ERROR] Error occurred. Waiting for all active server executors to finish current task Any help is highly appreciated. Thanks, Sandeep. ------------------------------ Message: 5 Date: Wed, 16 Sep 2009 01:05:55 -0700 From: "Blair" <os...@live.com> Subject: Re: [WiX-users] Failed to create web application. (-2147024809) To: "'General discussion for Windows Installer XML toolset.'" <wix-users@lists.sourceforge.net> Message-ID: <bay122-ds7853aedac9b2fec2f7b9fcd...@phx.gbl> Content-Type: text/plain; charset="us-ascii" I'm pretty sure Octopus (being someone who has not actually used it) has an option to enable MSI logging. You received the generic "installation failed" error result. You will need to look at the MSI logging to determine the reason for the error. The "Failed to create web application" message has an error code of 0x80070057="The parameter is incorrect." It would be useful to know of the differences between the 2003 server targeted by Octopus and the one you tested directly, especially as regards any already existing web applications/contents of those applications in IIS. -----Original Message----- From: Sandeep Kumar Bushnam (Wipro Ltd.) [mailto:v-san...@microsoft.com] Sent: Tuesday, September 15, 2009 10:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Failed to create web application. (-2147024809) Hi Team, My MSI creates a virtual directory under a default website and creates a new web application under existing App pool(this case DefaultAppPool). Which is working fine on windows 2003 OS. When I install the same MSI using Microsoft Octopus from Win7 onto windows 2003 server the installer throws below error. [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Failed to create web application. (-2147024809 /Root/ROMBSCALLBACK ) [ERROR] ROMDVWEBV01 : Installers\ROMBSCallBack\ROMBSCallBack.msi: Error Code 1603: Fatal error during installation. (Exception from HRESULT: 0x80070643) [ERROR] Error occurred. Waiting for all active server executors to finish current task Any help is highly appreciated. Thanks, Sandeep. ---------------------------------------------------------------------------- -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------ Message: 6 Date: Tue, 15 Sep 2009 18:21:54 -0700 From: "Blair" <os...@live.com> Subject: Re: [WiX-users] launching page localization To: "'General discussion for Windows Installer XML toolset.'" <wix-users@lists.sourceforge.net> Message-ID: <bay122-ds392bdee8c42ee614f09abcd...@phx.gbl> Content-Type: text/plain; charset="us-ascii" The list server generally strips attachments. Before Windows Installer has finished parsing the MSI database file to determine what language it is in, it uses the user/system locale to show the first messages. One of the core wix-team members blogged about that (it seems like it was 3-4 years ago?) describing the process (I forget which one and I would have to research it to provide the link). Once it gets going, does it show the messages in the correct language? Or does it continue with the "wrong" language? -----Original Message----- From: Lian Jiang [mailto:lji...@microsoft.com] Sent: Tuesday, September 15, 2009 1:00 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] launching page localization Hi, I localized all strings used in my installer UI. The installer is a MUI based msi which means the same MSI can work on different locale machines and shows the strings in the corresponding locale. All dialogs works fine except that the launching page (the verify first dialog showing something like "installation starts ...") shows strings incorrectly. For example, I saw it shows other language when running on an en-us machine and it shows English when running on other locales machine. The launching page shown in en-us locale machine is attached. Thanks for any clue. Thanks Lian ------------------------------ Message: 7 Date: Wed, 16 Sep 2009 09:46:12 +0100 From: "Dominique Louis" <dominique.lo...@amxeurope.com> Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Message-ID: <488f6a8c5a9db84fbb082d732f1bbdef020bc...@exchange01.amxuk.local> Content-Type: text/plain; charset="us-ascii" I had never really thought about bootstrapping WI v4.5 with Installer. Does WiX 3.0 support <BootstrapperFile Include="Microsoft.Windows.Installer.4.5"> <ProductName>Windows Installer 4.5</ProductName> </BootstrapperFile> Or alternatively how can I check if v4.5 is installed so I can throw up an conditional message. Dominique. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 16:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In that case are you bootstrapping the Windows Installer 4.5 redistributable before your installer runs so all your users/customers will be able to successfully install your product or are you also testing it on 3.1 & 4.0 to make sure they don't have problems? According to the docs (http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm) before LaunchConditions should be fine but I would double check a verbose log just to make sure your RegistrySearch is populating the SQLSERVER Property before your CustomAction attempts to parse it. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 14:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value I'm using v4.5.6001.22159 if that is any help to anyone. Is putting my CustomAction before LaunchConditions the best place to run my vbs, or would there be another more appropriate place? Dominique. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 15 September 2009 10:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value No but you could attribute it to a bug in whichever version of Windows Installer you're using to test the MSI (v3.1 or v4.0 whether you're on XP/2k3 or Vista/2k8 respectively I'm guessing). People on this list really need to learn the difference between WiX & Windows Installer. They are *not* the same thing & should never be used interchangeably as if far too often the case. You'll have to write your own Custom Action to parse the registry value before you compare it as far as I know. Would be nice if there was some sort of Standard Custom Action in WiX for manipulating regex but then there's already plenty of features which existed in WiX v2.0 which we have to live without in WiX v3.0 so I wouldn't hold my breath. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 15 September 2009 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Hi Blair, Can we attribute this to a bug in WiX 3.0 then? If I need to write a work around, does WiX provide any parsing capabilities, or should I look at using VBScript or similar to get this working? Dominique. -----Original Message----- From: Blair [mailto:os...@live.com] Sent: 14 September 2009 17:34 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value In my tests using a simple installation package, it would appear that the conditional comparison routines for strings stop looking through the string at the first NUL character. Since REG_MULTI_SZ strings start with a NUL, then terminate each value with an additional NUL (remember that the conditional is evaluated AFTER the string is parsed replacing all "[whatever]" property references) means that the conditional syntax can't "see" any values after the first [~] value (which would include all values retrieved using RegistrySearch involving REG_MULTI_SZ strings. You can check for presence of the property, however. (If the property were truly empty, it would be removed). To see what I am talking about, compare these three lines from my log: AppSearch: Property: MYMULTIVALUE, Signature: MyMultiValue MSI (c) (38:98) [09:26:38:902]: PROPERTY CHANGE: Adding MYMULTIVALUE property. Its value is ''. Property(C): MYMULTIVALUE = [~]SysClass.Dll,StorageCoInstaller[~]WmiProp.dll,WmiPropCoInstaller[~] Those are the only references to that property in the entire debug verbose log. You would need some custom action to parse or otherwise "escape" the property values in the property before using the condition syntax to search them. -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: Monday, September 14, 2009 8:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value OK based on Pally's earlier post, it would seem that SQLSERVER><"MSSQLSERVER" or the property equivalent should work, but neither works for me. Do they work for anyone else? -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 14 September 2009 15:54 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Nope, Changing it to a Property does not work either. I'm guessing that changing it to a property just makes it the equivalent of writing SQLSERVER><"MSSQLSERVER" Which would be incorrect as well. Is the >< the correct conditional operator for what I'm trying to achieve? What is the difference between >< and <> if any? As I mentioned in my original post, some kind of website or official documentation showing exactly how each operator is used in a conditional situation would be really, really useful at this point. At the moment I feel like I'm walking through the woods, blind folded. Dominique. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 14 September 2009 14:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Have you tried using a Property with its value set to "MSSQLSERVER" as I first assumed you were doing? Even something as simple as <Property Id="MSSQLSERVER" Value="MSSQLSERVER" /> added to your first code fragment might cause this to work. Essentially your code is doing exactly what you're trying to achieve from how I understand it but a quirk of Windows Installer could be fooling both of us and the above might be the solution. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 14 September 2009 14:23 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value Hi Pally, Thanks for taking the time to answer my query. I should have mentioned that I had already tried putting quotes around MSSQLSERVER, but that does not work either. What I need is some kind of conditional code the does the equivalent of a "Does this SQLSERVER property *contain* MSSQLSERVER" Dominique. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 14 September 2009 13:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value <Condition Message="This application requires Microsoft SQL Server. Please install Microsoft SQL Server then run this installer again."> <![CDATA[Installed OR (SQLSERVER><MSSQLSERVER)]]> </Condition> That says to throw the condition 'If the Property SQLSERVER does not contain the Property MSSQLSERVER or the product is not already Installed' Try putting quotes around MSSQLSERVER if you want it to be a string rather than a Property. I may be wrong but that's how I understand it. See http://msdn.microsoft.com/en-us/library/aa368012.aspx Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 14 September 2009 12:48 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value MSSQLSERVER Is not a property, it is a literal string that should exist within the Registry. I'm essentially trying to check if 'MSSQLSERVER' exists within the multi-string SQLSERVER. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 14 September 2009 12:36 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional installed based on REG_MULTI_SZ value What is the property MSSQLSERVER set to? You appear to have omitted this from your code fragment. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Dominique Louis [mailto:dominique.lo...@amxeurope.com] Sent: 14 September 2009 11:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional installed based on REG_MULTI_SZ value Hi WiX gurus, I'm using the "supposed" standard way of detecting multiple SQLServer instances... <Property Id="SQLSERVER"> <RegistrySearch Id="SQLServer" Root="HKLM" Key="SOFTWARE\Microsoft\Microsoft SQL Server" Type="raw" Name="InstalledInstances"/> </Property> <Condition Message="This application requires Microsoft SQL Server. Please install Microsoft SQL Server then run this installer again."> <![CDATA[Installed OR (SQLSERVER><MSSQLSERVER)]]> </Condition> But the Condition... <![CDATA[Installed OR (SQLSERVER><MSSQLSERVER)]]> Does not evaluate correctly. For instance if the Property SQLSERVER only contains "[~]SQLEXPRESS[~]" ( according to the log ) It still allows the installation to proceed when it should not, so I'm not convinced that using the >< is the correct way to check if 1 value exists within a REG_MULTI_SZ variable. Can anyone enlighten me as to what I may be doing wrong. Also where can I find the correct documentation/list to find out what are the correct conditional operatives I can use within a Condition statement in WiX, preferably with examples. I Googled various sites, but nothing definitive or helpful. Thanks. Dominique. AMX ------------------------------------------------------------------------ ------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users AMX AMX UK Auster Road Clifton Moor York, North Yorkshire United Kingdom YO30 4GD +44 (0) 1904 343100 office +44 (0) 1904 343101 fax AMX South 6th Floor Salisbury House London Wall London United Kingdom EC2M 5QQ +44 (0) 2076 529450 office +44 (0) 8701 991661 fax AMX Belgium Boerenkrijglaan, 96a B-2260 Westerlo Belgium + 32 (0) 1454 2763 office + 32 (0) 1454 2766 fax ###################################################################### Attention: This e-mail message is privileged and confidential. If you are not the intended recipient please delete the message and notify the sender. Any views or opinions presented are solely those of the author. This email was scanned and cleared by NetIQ MailMarshal. ###################################################################### ------------------------------ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users End of WiX-users Digest, Vol 40, Issue 68 ***************************************** ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
