[WiX-users] SetTargetPath causes errors in remote installations. Is there an alternative?
Our installation needs to install SQLExpress under certain conditions, and unfortunately we don't know what those condtions are until the user has already gotten through the installation, so we can't run it ahead of time through the setup.exe. After much experimentation I got an ExeCommand custom action hooked up to the Finish button of the ExitDialog page which runs the SQLExpress installer's setup.exe after our own msi has finished. This worked perfectly until people started trying to run the installation remotely over a mapped network drive, at which point whenever they hit Finish with the Sql installation box checked they'd get Error 1315: Unable to write to the specified folder: E:\Install\SQLEXPRESS\. and when they hit okay instead of exiting it goes back to the final dialog page instead of exiting. Since when I try double-clicking the setup.exe file at the same location I get a Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. error I'm sure there's no way to get the SQLExpress installation to work under these conditions, but I'd like to be able to have it fail gracefully. Some research has indicated that the Publish Event SetTargetPath is the problem, and if I remove it then the error goes away, but the SQLExpress installation is no longer successfully run when the installer is run from a local location either. Is there anyway to get rid of the error with SetTargetPath or replace it with something else that will work locally but fail silently remotely? Here's the relevant bits of code: The custom action to actually run the setup.exe CustomAction Id=InstallSqlExpress Directory=SQLEXPRESSDIR ExeCommand='[SQLEXPRESSDIR]setup.exe -q /morebootchk /qb reboot=ReallySuppress addlocal=all instancename=OURNAMESPACE SCCCHECKLEVEL=IncompatibleComponents:1;MDAC25Version:0 ERRORREPORTING=1 SQLAUTOSTART=1 SAPWD=%1!s! DISABLENETWORKPROTOCOLS=0 /l*v %2!s!' Return=asyncNoWait / And the custom actions to set the location of the setup.exe (Using my own custom action was the only way I could find to reference a directory above the one which our own installer was running from.) CustomAction Id=SetSqlExpressDir Execute=immediate BinaryKey=mofc.dll DllEntry=SetSqlExpressDir / CustomAction Id=SetSqlExpressDir.SetProperty Return=check Property=SetSqlExpressDir Value=[SOURCEDIR] / In the InstallUISequence we schedule two of the above actions: Custom Action=SetSqlExpressDir.SetProperty Before=ExecuteActionNOT Installed/Custom Custom Action=SetSqlExpressDir After=SetSqlExpressDir.SetPropertyNOT Installed/Custom And in the ExitDialog we call the first CA when the Finish button is pressed: Control Id=Finish Type=PushButton X=246 Y=242 Width=56 Height=17 Default=yes Cancel=yes Text=[ButtonText_Finish] Publish Event=SetTargetPath Value=SQLEXPRESSDIR1/Publish Publish Event=DoAction Value=InstallSqlExpress![CDATA[(NOT Installed) AND InstallSqlExpressCheck AND (GROUP = 1) AND NOT OURNAMESPACELOCATION]]/Publish Publish Event=EndDialog Value=Return1/Publish /Control If the SetTargetPath event is removed then when we try to run it locally clicking Finish causes it to exit properly but the SQLExpress setup isn't run and the log shows: Action 6:50:30: ExitDialog. Dialog created MSI (c) (83:CD) [06:52:26:459]: Doing action: InstallSqlExpress Action 6:52:26: InstallSqlExpress. Action start 6:52:26: InstallSqlExpress. Action ended 6:52:26: ExitDialog. Return value 1. Action ended 6:52:26: INSTALL. Return value 1. Action ended 6:52:26: InstallSqlExpress. Return value 1631. Thanks! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Hit her G-spot every time
Have a 9 inch pecker and open doors and legs every night. http://www.ppcthemovers.com/ Add up to 3 inches today. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Force ACLs to child objects
Hi folks-
I'm having issues with setting perms with the util:PermissionEx and
Permission elements. The folder ACLs are being set correctly but they
are not being propagated down if there are child folders with different
permissions. Is there a way to force or reset the permission entries on
child objects?
This is my snippet..
Component Id=SomeWebFolderComp Guid={yadda yadda}
CreateFolder Directory=SomeWebFolder
Permission User=Administrators GenericAll=yes /
util:PermissionEx Domain=[ComputerName] User=ASPNET
GenericRead=yes Read=yes GenericExecute=yes /
util:PermissionEx Domain=[ComputerName]
User=IUSR_[ComputerName] GenericRead=yes Read=yes
GenericExecute=yes /
/CreateFolder
/Component
Thanks tons!
Chris
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Pyro and .mst File
Hey everyone, I was looking through the WiX Help (wix.chm) and found a nifty diagram called the WiX Toolset Interaction Diagram (under About WiX | Tools and Concepts). In the diagram it shows you can take a .mst transform file and convert it into a .msp patch installer using the Pyro utility. Can anyone tell me how this is done and what command line parameters you would use? To give some background, I have created an MSI installer using VS 2008 and now I need to patch the installation. So I updated the source and rebuilt another updated MSI installer. Then I used the MSIMSP.exe utility in the Windows SDK Toolkit to create an .msp patch installer. It is functional, but I would like to modify some UI elements of this automatically created .msp file. I found some neat Windows Installer db editor called appEditor from http://www.camwood.com/. I loaded up the auto-generated .msp file and it pulled out the .mst transform file. Then I it told me to select the base transform, so I assumed it meant the original version of the .msi installer. When it came up, I was able to look at the dialog screens and it looks like I will be able to edit some of the strings and other UI elements. So anyway, now I'm thinking I will be able to save the modified .mst file and somehow get it back into the .msp file. I will keep looking around the Camwood application for a way to reconstitute the .msp, but I am wondering if there is an alternate way using the Pyro utility. I have the .mst file (for some reason there is a targetToupgrade.mst and a #targetToupgrade.mst) and then there are 7 .cab files (with their filenames being a bunch of square characters for some reason). Will the Pyro utility work for me at all? Thank you in advance. Mike- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Pyro and .mst File
Can you elaborate a bit more on what UI elements you would like to change? Is that the purpose of creating your patch? Or is it to patch an existing product? To answer your question on how to use Pyro, Peter Marcu has some blog entries on how to build an MSP with WiX. You could start here: http://blogs.msdn.com/pmarcu/archive/2007/04/27/building-a-patch-using-wix-v3-0.aspx The two mst files you are seeing in the patch are transforms. One mst describes the changes that will be made to the targeted product and the other has information about how to install the patch. The cabs likely contain new files that will patch over the existing files on the targeted product. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Murray Sent: Friday, March 21, 2008 3:56 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Pyro and .mst File Hey everyone, I was looking through the WiX Help (wix.chm) and found a nifty diagram called the WiX Toolset Interaction Diagram (under About WiX | Tools and Concepts). In the diagram it shows you can take a .mst transform file and convert it into a .msp patch installer using the Pyro utility. Can anyone tell me how this is done and what command line parameters you would use? To give some background, I have created an MSI installer using VS 2008 and now I need to patch the installation. So I updated the source and rebuilt another updated MSI installer. Then I used the MSIMSP.exe utility in the Windows SDK Toolkit to create an .msp patch installer. It is functional, but I would like to modify some UI elements of this automatically created .msp file. I found some neat Windows Installer db editor called appEditor from http://www.camwood.com/. I loaded up the auto-generated .msp file and it pulled out the .mst transform file. Then I it told me to select the base transform, so I assumed it meant the original version of the .msi installer. When it came up, I was able to look at the dialog screens and it looks like I will be able to edit some of the strings and other UI elements. So anyway, now I'm thinking I will be able to save the modified .mst file and somehow get it back into the .msp file. I will keep looking around the Camwood application for a way to reconstitute the .msp, but I am wondering if there is an alternate way using the Pyro utility. I have the .mst file (for some reason there is a targetToupgrade.mst and a #targetToupgrade.mst) and then there are 7 .cab files (with their filenames being a bunch of square characters for some reason). Will the Pyro utility work for me at all? Thank you in advance. Mike - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Corresponding element of FileShare in Wix 3.0
Hi, I am upgrading from Wix 2.0 to Wix 3.0. Some source files use FileShare which I can not find in Wix 3.0 anymore. I am wondering what should be the right replacement? Thanks for help! Zhisheng _ How well do you know your celebrity gossip? http://originals.msn.com/thebigdebate?ocid=T002MSN03N0707A- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Pyro and .mst File
I want to change UI elements in the .msp patch installer itself. The whole patcher install is autogenerated by msimsp.exe, a command-line utility. I had no control over which dialog screens were present in the patch installer, nor the text or banner for that manner. Yes, this is a patch for an existing installed product, which was installed by an installer I wrote a few months back. Thank you for the link; however, it appears I have seen that page before. The problem with this example is the .msp patch installer is created solely from WiX source files, like .wixmst instead of a standard .mst. My .mst file wasn't created using WiX utilities like Candle and Light. So I guess my question still stands whether I can utilize the Pyro utility on a transform file that wasn't created using WiX (a standard .mst transform file, especially one decompiled from an exisitng .msp patch installer using the Camwood appEditor program)? Thank you again in advance for any further guidance you all can provide. From: Jordan Fitzgibbon Sent: Friday, March 21, 2008 5:33 PM To: Mike Murray ; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Pyro and .mst File Can you elaborate a bit more on what UI elements you would like to change? Is that the purpose of creating your patch? Or is it to patch an existing product? To answer your question on how to use Pyro, Peter Marcu has some blog entries on how to build an MSP with WiX. You could start here: http://blogs.msdn.com/pmarcu/archive/2007/04/27/building-a-patch-using-wix-v3-0.aspx The two mst files you are seeing in the patch are transforms. One mst describes the changes that will be made to the targeted product and the other has information about how to install the patch. The cabs likely contain new files that will patch over the existing files on the targeted product. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Murray Sent: Friday, March 21, 2008 3:56 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Pyro and .mst File Hey everyone, I was looking through the WiX Help (wix.chm) and found a nifty diagram called the WiX Toolset Interaction Diagram (under About WiX | Tools and Concepts). In the diagram it shows you can take a .mst transform file and convert it into a .msp patch installer using the Pyro utility. Can anyone tell me how this is done and what command line parameters you would use? To give some background, I have created an MSI installer using VS 2008 and now I need to patch the installation. So I updated the source and rebuilt another updated MSI installer. Then I used the MSIMSP.exe utility in the Windows SDK Toolkit to create an .msp patch installer. It is functional, but I would like to modify some UI elements of this automatically created .msp file. I found some neat Windows Installer db editor called appEditor from http://www.camwood.com/. I loaded up the auto-generated .msp file and it pulled out the .mst transform file. Then I it told me to select the base transform, so I assumed it meant the original version of the .msi installer. When it came up, I was able to look at the dialog screens and it looks like I will be able to edit some of the strings and other UI elements. So anyway, now I'm thinking I will be able to save the modified .mst file and somehow get it back into the .msp file. I will keep looking around the Camwood application for a way to reconstitute the .msp, but I am wondering if there is an alternate way using the Pyro utility. I have the .mst file (for some reason there is a targetToupgrade.mst and a #targetToupgrade.mst) and then there are 7 .cab files (with their filenames being a bunch of square characters for some reason). Will the Pyro utility work for me at all? Thank you in advance. Mike - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How well is blue pill working for you?
It's driller time!
http://ladmt.rustarena.com/?prod=zl{0xvhuvColvwv1vrxufhirujh1qhw
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
