[WiX-users] DiskCost dialog is not being udated
I have a PathEdit control where user could enter installation location. I realized that hitting Disk Space button, which brings up DiskCost dialog does not show the cost updated based on user input. DiskCost dialog uses VolumeCostList control to show the cost. After playing around I realized that SetTargetPath makes VolumeCostList control aware of the install location change, and updates accordingly: Publish Event=SetTargetPath Value=TARGETDIR![CDATA[1]]/Publish Is there a better way of doing this, so that VolumeCostList shows correct info? _ Put your friends on the big screen with Windows Vista® + Windows Live™. http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_012008- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSI returns 1606 Could not access location
Thank you for the clarification! From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL PROTECTED]: Fri, 2 Nov 2007 07:26:39 -0700Subject: RE: [WiX-users] MSI returns 1606 Could not access location All I'm saying is that if you remove the location that the software is installed to, it is unreasonable to uninstall, repair, reinstall, or perform any other operation since the location the software has been installed to no longer exists. What do you want Windows Installer to do differently? It has no chance to even confirm that the directories were removed since the volume they reside on is no longer accessible. This is expected behavior from WI, and is By Design. Nothing wix can do to change it. Either restore the volume or get MsiZap. From: Davut Karabay [EMAIL PROTECTED]: Friday, November 02, 2007 12:47 AMTo: Blair Murri; Rob MenschingCc: [EMAIL PROTECTED]: RE: [WiX-users] MSI returns 1606 Could not access location Are you saying that TARGETDIR should not be set to \\wmiscratch\scratch\davut\DaRT? But that's where software was installed right?. Installer should be setting it internally. My problem is; if the share become unavailable then there seems to be no way out. Can't uninstall or repair, or install on top of existing. From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL PROTECTED]: Thu, 1 Nov 2007 14:50:41 -0700Subject: RE: [WiX-users] MSI returns 1606 Could not access location MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'. This line seems to me to be the primary reason. TARGETDIR is the location where the software has been installed. It seems to me that it can’t erase it out of the network share if the network share doesn’t exist. The MSDN docs say that KB886549 can also produce 1606 errors (http://support.microsoft.com/kb/886549/en-us). But, instead I think it is something wrong in your directory table and/or passed in command-line values. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 2:28 PMTo: Rob MenschingCc: [EMAIL PROTECTED]: Re: [WiX-users] MSI returns 1606 Could not access location Hi Rob - Thank you for your reply. Do you mean I require network share to exist during uninstall (in the WIX code)? Isn't that a requirement by MSI which I don't have control over? Here is the log. I couldn't understand anything useful other than error code. ...Id start 13:48:25: CostFinalize.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2205 2: 3: MsiAssembly MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'.MSI (c) (4C:38) [13:48:25:825]: PROPERTY CHANGE: Adding enUS property. Its value is '\\wmiscratch\scratch\davut\DaRT\en-us'.MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Patch MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Condition MSI (c) (4C:38) [13:48:25:840]: PROPERTY CHANGE: Adding MSDARTShortCuts property. Its value is 'C:\Users\Davut\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Diagnostics and Recovery Toolset\'.MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1314 2: \\wmiscratch\scratch\davut\DaRT MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:31:637]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:31:652]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:32:909]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut
Re: [WiX-users] MSI returns 1606 Could not access location
Are you saying that TARGETDIR should not be set to \\wmiscratch\scratch\davut\DaRT? But that's where software was installed right?. Installer should be setting it internally. My problem is; if the share become unavailable then there seems to be no way out. Can't uninstall or repair, or install on top of existing. From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL PROTECTED]: Thu, 1 Nov 2007 14:50:41 -0700Subject: RE: [WiX-users] MSI returns 1606 Could not access location MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'. This line seems to me to be the primary reason. TARGETDIR is the location where the software has been installed. It seems to me that it can’t erase it out of the network share if the network share doesn’t exist. The MSDN docs say that KB886549 can also produce 1606 errors (http://support.microsoft.com/kb/886549/en-us). But, instead I think it is something wrong in your directory table and/or passed in command-line values. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 2:28 PMTo: Rob MenschingCc: [EMAIL PROTECTED]: Re: [WiX-users] MSI returns 1606 Could not access location Hi Rob - Thank you for your reply. Do you mean I require network share to exist during uninstall (in the WIX code)? Isn't that a requirement by MSI which I don't have control over? Here is the log. I couldn't understand anything useful other than error code. ...Id start 13:48:25: CostFinalize.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2205 2: 3: MsiAssembly MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'.MSI (c) (4C:38) [13:48:25:825]: PROPERTY CHANGE: Adding enUS property. Its value is '\\wmiscratch\scratch\davut\DaRT\en-us'.MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Patch MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Condition MSI (c) (4C:38) [13:48:25:840]: PROPERTY CHANGE: Adding MSDARTShortCuts property. Its value is 'C:\Users\Davut\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Diagnostics and Recovery Toolset\'.MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1314 2: \\wmiscratch\scratch\davut\DaRT MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:31:637]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:31:652]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:32:909]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.Id ended 13:48:32: CostFinalize. Return value 3Thanks,Davut Date: Wed, 31 Oct 2007 11:35:43 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MSI returns 1606 Could not access location This happens if your MSI requires the original source media for some reason during uninstall. Usually, it's some coding error that causes this problem. Look in the verbose log file and see what is causing the source prompt. Davut Karabay wrote: Hi, I run my insaller (e.g. msiexec /i XYZ.msi). Select a network path to install (e.g. \\somecomputer\someshare\installdir). Product is installed with success. Now delete the network path. Run the installer again. It returns 1606 saying that could not access the network location. Installer is stuck. Can't uninstall or repair. Is this by design? Can I handle it differently? Thanks, Davut
[WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Hi, When I run the new version of installer, it invokes the installed old version. I don't want that happen. I want the new version installed anyway. How can I break the link between the new and the old? I changed Product ID GUID but it didn't help. Using Launch Conditions do not help because old version is invoked. Here I am not asking msiexec /fv. My users will likely run the installer by double clicking. Thanks,Davut _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews- 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
Re: [WiX-users] MSI returns 1606 Could not access location
Hi Rob - Thank you for your reply. Do you mean I require network share to exist during uninstall (in the WIX code)? Isn't that a requirement by MSI which I don't have control over? Here is the log. I couldn't understand anything useful other than error code. ...Id start 13:48:25: CostFinalize.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.MSI (c) (4C:38) [13:48:25:747]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2205 2: 3: MsiAssembly MSI (c) (4C:38) [13:48:25:762]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property. Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'.MSI (c) (4C:38) [13:48:25:825]: PROPERTY CHANGE: Adding enUS property. Its value is '\\wmiscratch\scratch\davut\DaRT\en-us'.MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Patch MSI (c) (4C:38) [13:48:25:840]: Note: 1: 2205 2: 3: Condition MSI (c) (4C:38) [13:48:25:840]: PROPERTY CHANGE: Adding MSDARTShortCuts property. Its value is 'C:\Users\Davut\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Diagnostics and Recovery Toolset\'.MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1314 2: \\wmiscratch\scratch\davut\DaRT MSI (c) (4C:38) [13:48:25:903]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:31:637]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT. MSI (c) (4C:38) [13:48:31:652]: Note: 1: 1606 2: \\wmiscratch\scratch\davut\DaRT Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT.MSI (c) (4C:38) [13:48:32:909]: Product: Microsoft Diagnostics and Recovery Toolset 6.0 -- Error 1606. Could not access network location \\wmiscratch\scratch\davut\DaRT. Id ended 13:48:32: CostFinalize. Return value 3Thanks,Davut Date: Wed, 31 Oct 2007 11:35:43 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MSI returns 1606 Could not access location This happens if your MSI requires the original source media for some reason during uninstall. Usually, it's some coding error that causes this problem. Look in the verbose log file and see what is causing the source prompt. Davut Karabay wrote: Hi, I run my insaller (e.g. msiexec /i XYZ.msi). Select a network path to install (e.g. \\somecomputer\someshare\installdir). Product is installed with success. Now delete the network path. Run the installer again. It returns 1606 saying that could not access the network location. Installer is stuck. Can't uninstall or repair. Is this by design? Can I handle it differently? Thanks, Davut _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews - 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 _ Climb to the top of the charts! Play Star Shuffle: the word scramble challenge with star power. http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct- 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
Re: [WiX-users] How to prevent cached msi being invoked (not askingmsiexec /fv)
I generated a real GUID (package id) :). But that didn't work. It still invokes the cache. Do you think it shouldn't? Re: [WiX-users] How to prevent cached msi being invoked (not askingmsiexec /fv)From: Hugues Valois [EMAIL PROTECTED] - 2007-11-01 21:03Attachments: Message as HTML Did you forget to change the package id? Or use---- to have a package id generatedautomatically by Wix.=20From: [EMAIL PROTECTED]:[EMAIL PROTECTED] On Behalf Of DavutKarabaySent: Thursday, November 01, 2007 12:41 PMTo: [EMAIL PROTECTED]: [WiX-users] How to prevent cached msi being invoked (notaskingmsiexec /fv)=20Hi,=20When I run the new version of installer, it invokes the installed oldversion. I don't want that happen. I want the new version installedanyway. How can I break the link between the new and the old? I changedProduct ID GUID but it didn't help. Using Launch Conditions do not helpbecause old version is invoked. Here I am not asking msiexec /fv. Myusers will likely run the installer by double clicking.=20Thanks,Davut _ Peek-a-boo FREE Tricks Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHMloc=us- 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
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
That was the first thing I did, changing both product id and upgrade code. But still invokes the cached msi. I think I will give another try because everyone suggests it will work. By the way please bare with me on installers :). It is one of the things that I inherited recently. Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)Date: Thu, 1 Nov 2007 14:38:33 -0700From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Peter is suggesting you change your Product Id=”GUID”. I think you might want to also consider changing the UpgradeCode=”GUID” also for future ease of upgrading one product versus the other, but it really depends on what your ultimate goal is. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 2:31 PMTo: Peter Marcu; [EMAIL PROTECTED]: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Hi Peter - What do you mean by changing the product code? From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Thu, 1 Nov 2007 13:47:35 -0700Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 1:40 PMTo: [EMAIL PROTECTED]: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED],Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway.Why?-- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP--New version has launch conditions to install only on Vista--Try installing new version on XP (to test that it won't install)--New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now! Windows Live Hotmail and Microsoft Office Outlook – together at last. Get it now! _ Climb to the top of the charts! Play Star Shuffle: the word scramble challenge with star power. http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct- 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
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Rob, Peter, Blair and Chad - Thank you guys all for the help. Turns out I haven't changed Package/@Id. Now it is working as charm! Thanks a lot.Davut Date: Thu, 1 Nov 2007 15:49:24 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Can you share the before and after values for: Product/@Id Product/@UpgradeCode Package/@Id What version of the WiX toolset are you using? Davut Karabay wrote: Hi,When I run the new version of installer, it invokes the installed old version. I don't want that happen. I want the new version installed anyway. How can I break the link between the new and the old? I changed Product ID GUID but it didn't help. Using Launch Conditions do not help because old version is invoked. Here I am not asking msiexec /fv. My users will likely run the installer by double clicking.Thanks, Davut Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews - 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 _ Peek-a-boo FREE Tricks Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHMloc=us- 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
[WiX-users] MSI returns 1606 Could not access location
Hi, I run my insaller (e.g. msiexec /i XYZ.msi). Select a network path to install (e.g. \\somecomputer\someshare\installdir). Product is installed with success. Now delete the network path. Run the installer again. It returns 1606 saying that could not access the network location. Installer is stuck. Can't uninstall or repair. Is this by design? Can I handle it differently? Thanks, Davut _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews - 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
[WiX-users] How to prevent administrative (network) installation
Hi, How can I prevent a network installation (msiexec.exe /a XYZ.msi)? I pasted below the WIX content. Should I add a single dialog to AdminUISequence, to say that it is not supported, and give the option to finish? Is there a better way? (PS: I am not a WIX expert... Never understood why we had to list FatalError, UserExit, ExitDialog and PrepareDlg dialogs in AdminUISequence. I think this whole sequence thing is more complicated than it should be. Wondering if anyone feels the same way.) ... UI ... AdminUISequenceCustom Action=DIRCA_TARGETDIR Sequence=750TARGETDIR=/CustomShow Dialog=FatalError OnExit=error /Show Dialog=UserExit OnExit=cancel / Show Dialog=ExitDialog OnExit=success /Show Dialog=PrepareDlg Before=CostInitialize![CDATA[]]/ShowShow Dialog=AdminWelcomeDlg After=CostFinalize /Show Dialog=ProgressDlg After=AdminWelcomeDlg / /AdminUISequence... /UIAdminExecuteSequence Custom Action=DIRCA_TARGETDIR Sequence=750TARGETDIR=/Custom/AdminExecuteSequence... Thanks,Davut _ Help yourself to FREE treats served up daily at the Messenger Café. Stop by today. http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline- 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
[WiX-users] How to install msxm3 merge module
Hello, I need to install MSXML3 merge module. I have added following lines to my WIX, but the installer terminates prematurely (nothing useful in the MSI logs!!). Does anyone know how to do it? ... Directory Id=TARGETDIR Name=SourceDir ... Merge Id=msxml3 Language=1033 SourceFile=msxml3_wim32.msm DiskId=1 / .../Directory ...Feature Id=MyFeature Title=Title Description=Description Level=1 AllowAdvertise=no ... MergeRef Id=msxml3 / .../Feature ... Regards, Davut _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us- 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
Re: [WiX-users] How to install msxm3 merge module
Hi Raj, I am merging MSXML3 SP7. Did you have to install all three modules (msxml3_wim32.msm, msxml3inf_wim32.msm and wdstddll_wim32.msm)? I was only trying msxml3_wim32.msm.Thanks,Davut Subject: RE: [WiX-users] How to install msxm3 merge moduleDate: Mon, 27 Aug 2007 14:54:38 -0700From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Hello Davut, What version of MSXML are you merging in? I was having a similar difficult time with this last week, but what solved the issue was getting a more recent service pack of MSXML and replacing the files in my installation with those. http://community.installshield.com/showthread.php?p=281196mode=threaded offers an explanation. I hope it helps. Raj From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Monday, August 27, 2007 5:47 PMTo: [EMAIL PROTECTED]: [WiX-users] How to install msxm3 merge module Hello, I need to install MSXML3 merge module. I have added following lines to my WIX, but the installer terminates prematurely (nothing useful in the MSI logs!!). Does anyone know how to do it? ...Directory Id=TARGETDIR Name=SourceDir... Merge Id=msxml3 Language=1033 SourceFile=msxml3_wim32.msm DiskId=1 /.../Directory...Feature Id=MyFeature Title=Title Description=Description Level=1 AllowAdvertise=no... MergeRef Id=msxml3 /... /Feature...Regards,Davut Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! _ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE- 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
[WiX-users] How does WIX pop-up Vista Consent Dialog
Hi, I want my WIX generated MSI to pop-up Vista Consent Dialog. How can I do it? Interestingly the dialog pops up for un-install, but NOT for install. My WIX was originally written for XP and 2003. Thanks, Davut _ Make every IM count. Download Windows Live Messenger and join the i’m Initiative now. It’s free. http://im.live.com/messenger/im/home/?source=TAGWL_June07- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to launch MSI from MSI
I have a WIX based MSI. My product depends on a separate component, which installs with its own MSI. Is there a way that I can launch the other MSI from mine? Thanks, Davut _ Mortgage refinance is Hot. *Terms. Get a 5.375%* fix rate. Check savings https://www2.nextag.com/goto.jsp?product=10035url=%2fst.jsptm=ysearch=mortgage_text_links_88_h2bbbdisc=yvers=925s=4056p=5117 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Single WIX to install multiple versions
Hello, I have a WIX based installer which currently installs the product on down level XP and Win2K3. In the next version I want to support Vista, where product binaries will change cosiderably. How can I achieve installing on downlevel and Vista with a single WIX? Regards, Davut _ Interest Rates Fall Again! $430,000 Mortgage for $1,399/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-18679moid=7581 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
