The WiX documentation itself has a page on logging: How To Guides\Others\Get a log of your installation for debugging
The online version of that page is here: http://wix.sourceforge.net/manual-wix3/get_a_log.htm It is instructive to read the logs sequentially as it allows you to see the flow that the engine takes and the timing of the setting of different values/properties. When I looked at your source code, here is the hierarchy I saw (shown as identifier\name of folder under parent): TARGETDIR\SourceDir - Required "root" of the hierarchy ProgramFilesFolder - Initial path is set by MSI - does not use its parent OneSpatial\1Spatial INSTALLDIR\dam ComDir\com ConfigDir\config ExeDir\exe AppDataFolder - Initial path is set by MSI - does not use its parent OneSpatialAppData\1Spatial GOTH_DATAROOT\data GOTH_DAM\dam GOTH_DAM_LOG\log GOTH_LIC\lic GOTH_ODBD_SORT\sort GOTH_OBDB_ROOT\odbd GOTH_ODBD_CONFIG\config GOTH_ODBD_DEFAULT\default GOTH_ODBD_HISTORY\history GOTH_ODBD_LOCK\lock GOTH_ODBD_OBJIDX\objidx GOTH_ODBD_OBJECT\reg Directory identifier values are session properties. If those properties exist before the CostFinalize, the corresponding values are used for those directories. Properties are then created for each directory to reflect each of their paths, so that they can be used in other tables or CAs and/or verified in CAs/logs. Assuming that NO properties are passed on either the installation command-line or via the build system, and assuming a 32-bit Windows 7 "standard" installation (AppDataFolder is in a different location on XP and downlevel), this is my quick determination of where I expect your MSI to place each of the above directories when the product was not previously installed and no properties are passed in via the command line nor changed by the UI: TARGETDIR = root folder of hard drive with the largest free space at time of installation ProgramFilesFolder = C:\Program Files\ OneSpatial = C:\Program Files\1Spatial\ INSTALLDIR = C:\Program Files\1Spatial\dam\ ComDir = C:\Program Files\1Spatial\dam\com\ ConfigDir = C:\Program Files\1Spatial\dam\config\ ExeDir = C:\Program Files\1Spatial\dam\exe\ AppDataFolder = C:\Users\<Installing-User-FolderName>\AppData\Roaming\ OneSpatialAppData = C:\Users\<Installing-User-FolderName>\AppData\Roaming\1Spatial\ GOTH_DATAROOT = $(env.SystemDrive)\1Spatial\data\ GOTH_DAM = $(env.SystemDrive)\1Spatial\data\dam\ GOTH_DAM_LOG = $(env.SystemDrive)\1Spatial\data\dam\log\ GOTH_LIC = $(env.SystemDrive)\1Spatial\data\lic\ GOTH_ODBD_SORT = $(env.SystemDrive)\1Spatial\data\sort\ GOTH_OBDB_ROOT = $(env.SystemDrive)\1Spatial\data\odbd\ GOTH_ODBD_CONFIG = $(env.SystemDrive)\1Spatial\data\odbd\config\ GOTH_ODBD_DEFAULT = $(env.SystemDrive)\1Spatial\data\odbd\default\ GOTH_ODBD_HISTORY = $(env.SystemDrive)\1Spatial\data\odbd\history\ GOTH_ODBD_LOCK = $(env.SystemDrive)\1Spatial\data\odbd\lock\ GOTH_ODBD_OBJIDX = $(env.SystemDrive)\1Spatial\data\odbd\objidx\ GOTH_ODBD_OBJECT = $(env.SystemDrive)\1Spatial\data\odbd\reg\ *NOTE: $(env.SystemDrive) is the root folder of the system drive of the system building the MSI file, NOT the system installing the MSI. While most Windows 7 installations use a system drive value of C:\, that is by no means universal and is NOT required on any version of Windows as far as I know. The corresponding MSI property would be [WindowsVolume], which already contains the backslash, if you need the corresponding path on the system you are installing on. Note that all identifier names that are in all CAPS can be placed anywhere by whomever installs your MSI, (parent/sibling relationships do not have to be honored), so if there are any required sibling relationships, the corresponding identifiers should not have been made public (all CAPS). Compare the above expected values with the values found in the verbose log, and investigate where/how those values are set. Also, check the action states of all components containing CreateFolder elements. Blair -----Original Message----- From: mat_macwilliam [mailto:marcus.macwill...@1spatial.com] Sent: Wednesday, November 30, 2011 2:18 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] CreateFolder is not creating required directory structure ... Blair, I am a complete novice to this. The person who originally wrote our XML is no longer at the company. How do I get complete logging information out of the MSI when it is run? Incidentally the directory structure is correct. The ProgramFiles folder is for the DAM itself which is a service. (DAM = Data Access Manager). The AppDatFolder in c:\1Spatial\data are the database files the DAM manages. The strange thing is that the dam, dam\log and lic sub-directories are created, but the sort, obdb and obdb sub-directories are not, yet they are in the same hierarchy. Cheers, Marcus. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-CreateFolde r-is-not-creating-required-directory-structure-tp7044160p7046289.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
