msiexec \a tmp folders lizii <cronvek[ at ]gmail.com> 18.06.2007 13:12:48 am trying to build my own patches at the moment - which involves me decompressing my MSI with msiexec. i use this call in the command line: msiexec /a Navigator.msi /qb TARGETDIR="C:\Documents and Settings \estyles\Desktop\PatchTest\SecondRelease\uncompressed1" which is fine - and it decompresses the files into the specified folder...however it then goes and leave tmp folders on one of the network drives consistently - namely the J drive. been through my environment variables...and they are as such: %TMP% : %USERPROFILE%\Local Settings\Temp %TEMP%: %USERPROFILE%\Local Settings\Temp %USERPROFILE%: C:\Documents and Settings\estyles There is no reason why it is using a mapped drive instead of a solid drive...and i am running out of places to find this error! Any advice welcomed. thanks folks!

Re: msiexec \a tmp folders "Phil Wilson" <phil.wilson[ at ]wonderware.something.com> 18.06.2007 23:26:13 A MSI log might help you see what's going on. Anything odd like custom actions in the AdminUI/AdminExecute sequence tables? -- Phil Wilson [MVP Windows Installer] "lizii" <cronvek[ at ]gmail.com> wrote in message news:1182172368.874060.33940[ at ]w5g2000hsg.googlegroups.com... [Quoted Text] > am trying to build my own patches at the moment - which involves me > decompressing my MSI with msiexec. > > i use this call in the command line: > msiexec /a Navigator.msi /qb TARGETDIR="C:\Documents and Settings > \estyles\Desktop\PatchTest\SecondRelease\uncompressed1" > > which is fine - and it decompresses the files into the specified > folder...however it then goes and leave tmp folders on one of the > network drives consistently - namely the J drive. > > been through my environment variables...and they are as such: > > %TMP% : %USERPROFILE%\Local Settings\Temp > %TEMP%: %USERPROFILE%\Local Settings\Temp > %USERPROFILE%: C:\Documents and Settings\estyles > > There is no reason why it is using a mapped drive instead of a solid > drive...and i am running out of places to find this error! Any advice > welcomed. > > thanks folks! >

Re: msiexec \a tmp folders lizii <cronvek[ at ]gmail.com> 19.06.2007 07:35:29 the only "odd" thing i can find is this: SystemFolder.6CF3F7DF_6AED_451D_BF8F_AD216156BF2B which personally i have no clue...i have tried to avoid touching anything within the MSI at all. Interesting as well is if i disconnect this drive and rename as another letter "Y: etc" then the problem seems to vanish but then it does not place them within the Temp folder.. Now i have a full verbose log..but not sure if it would be appreciated if i post the whole thing...so i will post a snippet for now and if its all fine then i will post the whole thing: Action ended 08:29:31: SystemFolder. 6CF3F7DF_6AED_451D_BF8F_AD216156BF2B. Return value 1. MSI (s) (54:24) [08:29:31:193]: Machine policy value 'MaxPatchCacheSize' is 10 MSI (s) (54:24) [08:29:31:193]: Baseline: Sorting baselines for {E58A4653-7F62-4810-A6E1-8EF7247BACC4}. MSI (s) (54:24) [08:29:31:193]: Baseline: New baseline 2.3.7 from transaction. MSI (s) (54:24) [08:29:31:193]: Baseline: Sorted order Native: Order 0. MSI (s) (54:24) [08:29:31:193]: Baseline Data Table: MSI (s) (54:24) [08:29:31:193]: ProductCode: {E58A4653-7F62-4810- A6E1-8EF7247BACC4} Version: 2.3.7 Attributes: 0 PatchId: Native BaselineId: -2147483648 Order: 0 MSI (s) (54:24) [08:29:31:193]: Baseline File Table: Action start 08:29:31: CostInitialize. MSI (s) (54:24) [08:29:31:209]: Note: 1: 1321 2: J:\MSI7a82d.tmp\ MSI (s) (54:24) [08:29:31:209]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'L:\'. MSI (s) (54:24) [08:29:31:209]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'. MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Patch 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: PatchPackage 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: MsiPatchHeaders 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2205 2: 3: __MsiPatchFileList MSI (s) (54:24) [08:29:31:209]: Dumping __MsiPatchMedia table... MSI (s) (54:24) [08:29:31:209]: Delta compression fallback method for this product transaction is 'MSI 2.0 legacy obsolescence' MSI (s) (54:24) [08:29:31:209]: Doing action: FileCost Action ended 08:29:31: CostInitialize. Return value 1. MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Registry 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Class 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Extension 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: TypeLib 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: IniFile 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: MoveFile 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: DuplicateFile 3: -2147287038 MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: ReserveCost 3: -2147287038 Action start 08:29:31: FileCost. it even refers to J: there - but nowhere else in the file is there a reference to J: - and i cannot for the life of me understand why it thinks in cost initalize to use J - much less change the rootdrive to L:... The plot thickens. On 19 Jun, 00:26, "Phil Wilson" <phil.wil...[ at ]wonderware.something.com> wrote: [Quoted Text] > A MSI log might help you see what's going on. > > Anything odd like custom actions in the AdminUI/AdminExecute sequence > tables? > > -- > Phil Wilson > [MVP Windows Installer] > > "lizii" <cron...[ at ]gmail.com> wrote in message > > news:1182172368.874060.33940[ at ]w5g2000hsg.googlegroups.com... > > > am trying to build my own patches at the moment - which involves me > > decompressing my MSI with msiexec. > > > i use this call in the command line: > > msiexec /a Navigator.msi /qb TARGETDIR="C:\Documents and Settings > > \estyles\Desktop\PatchTest\SecondRelease\uncompressed1" > > > which is fine - and it decompresses the files into the specified > > folder...however it then goes and leave tmp folders on one of the > > network drives consistently - namely the J drive. > > > been through my environment variables...and they are as such: > > > %TMP% : %USERPROFILE%\Local Settings\Temp > > %TEMP%: %USERPROFILE%\Local Settings\Temp > > %USERPROFILE%: C:\Documents and Settings\estyles > > > There is no reason why it is using a mapped drive instead of a solid > > drive...and i am running out of places to find this error! Any advice > > welcomed. > > > thanks folks!

Re: msiexec \a tmp folders "Adrian Accinelli" <hclnospamalias2[ at ]newsgroup.nospam> 19.06.2007 20:02:51 "lizii" <cronvek[ at ]gmail.com> wrote in message news:1182238529.493025.301840[ at ]n60g2000hse.googlegroups.com... [Quoted Text] > the only "odd" thing i can find is this: > SystemFolder.6CF3F7DF_6AED_451D_BF8F_AD216156BF2B > which personally i have no clue...i have tried to avoid touching > anything within the MSI at all. > > Interesting as well is if i disconnect this drive and rename as > another letter "Y: etc" then the problem seems to vanish but then it > does not place them within the Temp folder.. > > > Now i have a full verbose log..but not sure if it would be appreciated > if i post the whole thing...so i will post a snippet for now and if > its all fine then i will post the whole thing: > > Action ended 08:29:31: SystemFolder. > 6CF3F7DF_6AED_451D_BF8F_AD216156BF2B. Return value 1. > MSI (s) (54:24) [08:29:31:193]: Machine policy value > 'MaxPatchCacheSize' is 10 > MSI (s) (54:24) [08:29:31:193]: Baseline: Sorting baselines for > {E58A4653-7F62-4810-A6E1-8EF7247BACC4}. > MSI (s) (54:24) [08:29:31:193]: Baseline: New baseline 2.3.7 from > transaction. > MSI (s) (54:24) [08:29:31:193]: Baseline: Sorted order Native: Order > 0. > MSI (s) (54:24) [08:29:31:193]: Baseline Data Table: > MSI (s) (54:24) [08:29:31:193]: ProductCode: {E58A4653-7F62-4810- > A6E1-8EF7247BACC4} Version: 2.3.7 Attributes: 0 PatchId: Native > BaselineId: -2147483648 Order: 0 > MSI (s) (54:24) [08:29:31:193]: Baseline File Table: > Action start 08:29:31: CostInitialize. > MSI (s) (54:24) [08:29:31:209]: Note: 1: 1321 2: J:\MSI7a82d.tmp\ > MSI (s) (54:24) [08:29:31:209]: PROPERTY CHANGE: Adding ROOTDRIVE > property. Its value is 'L:\'. > MSI (s) (54:24) [08:29:31:209]: PROPERTY CHANGE: Adding > CostingComplete property. Its value is '0'. > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Patch 3: -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: PatchPackage 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: MsiPatchHeaders 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2205 2: 3: > __MsiPatchFileList > MSI (s) (54:24) [08:29:31:209]: Dumping __MsiPatchMedia table... > MSI (s) (54:24) [08:29:31:209]: Delta compression fallback method for > this product transaction is 'MSI 2.0 legacy obsolescence' > MSI (s) (54:24) [08:29:31:209]: Doing action: FileCost > Action ended 08:29:31: CostInitialize. Return value 1. > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Registry 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Class 3: -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: Extension 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: TypeLib 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: IniFile 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: MoveFile 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: DuplicateFile 3: > -2147287038 > MSI (s) (54:24) [08:29:31:209]: Note: 1: 2262 2: ReserveCost 3: > -2147287038 > Action start 08:29:31: FileCost. > > it even refers to J: there - but nowhere else in the file is there a > reference to J: - and i cannot for the life of me understand why it > thinks in cost initalize to use J - much less change the rootdrive to > L:... > > The plot thickens. > > On 19 Jun, 00:26, "Phil Wilson" <phil.wil...[ at ]wonderware.something.com> > wrote: >> A MSI log might help you see what's going on. >> >> Anything odd like custom actions in the AdminUI/AdminExecute sequence >> tables? >> >> -- >> Phil Wilson >> [MVP Windows Installer] >> >> "lizii" <cron...[ at ]gmail.com> wrote in message >> >> news:1182172368.874060.33940[ at ]w5g2000hsg.googlegroups.com... >> >> > am trying to build my own patches at the moment - which involves me >> > decompressing my MSI with msiexec. >> >> > i use this call in the command line: >> > msiexec /a Navigator.msi /qb TARGETDIR="C:\Documents and Settings >> > \estyles\Desktop\PatchTest\SecondRelease\uncompressed1" >> >> > which is fine - and it decompresses the files into the specified >> > folder...however it then goes and leave tmp folders on one of the >> > network drives consistently - namely the J drive. >> >> > been through my environment variables...and they are as such: >> >> > %TMP% : %USERPROFILE%\Local Settings\Temp >> > %TEMP%: %USERPROFILE%\Local Settings\Temp >> > %USERPROFILE%: C:\Documents and Settings\estyles >> >> > There is no reason why it is using a mapped drive instead of a solid >> > drive...and i am running out of places to find this error! Any advice >> > welcomed. >> >> > thanks folks! > I can't say that I've seen the same tmp files there myself - normally I see those in %windir%\Installer or in personal user profile temp. If neither TEMP nor TMP are defined it appears that %USERPROFILE% is used to hold non-privileged temp files. As for why the J: drive comes into play I think this is simply related to the standard ROOTDRIVE resolution in an admin install -- namely ROOTDRIVE becomes the first available writable network drive with available space (look it up in MSDN for complete details). This is likely why switching to y:\ seems to make it go away - since another earlier drive is used instead. You could try adding ROOTDRIVE=C:\ to your command line and see if the files end up there instead. I suggest trying this with someone else's MSI file (orca.msi is nice and small) and see if you get similar results. Sincerely, Adrian Accinelli

Re: msiexec \a tmp folders lizii <cronvek[ at ]gmail.com> 20.06.2007 09:54:57 -snip!- Interesting! Its definitely something with rootdrive. Ran the tests that you suggested there - and discovered that with the ROOTDRIVE = <something on c:\> - no folders are created, and the same goes for orca.msi - although i admit i cannot find the said folders in the location specified...i would assume since its trying to make those on a temporary basis that they would be deleted. However - both will dump the .tmp folders into the J: drive without the extra command. So it seems that i could add a custom action to my msi or just when building patches...just that extra command. I would like to know if it is actually making those folders in the location specified however...or if they are going somewhere else or just being deleted that quickly there is no chance of seeing them. Although looking at the log the RootDrive property just stays as what i specified...so logically i assume thats not going to change. Thanks for your help guys - that seems to have solved a problem i have been hunting for a while! One wall down...ever so many to go!

Re: msiexec \a tmp folders "Adrian Accinelli" <hclnospamalias2[ at ]newsgroup.nospam> 20.06.2007 16:29:09 "lizii" <cronvek[ at ]gmail.com> wrote in message news:1182333297.133232.6080[ at ]n60g2000hse.googlegroups.com... [Quoted Text] > -snip!- > > Interesting! Its definitely something with rootdrive. Ran the tests > that you suggested there - and discovered that with the ROOTDRIVE = > <something on c:\> - no folders are created, and the same goes for > orca.msi - although i admit i cannot find the said folders in the > location specified...i would assume since its trying to make those on > a temporary basis that they would be deleted. However - both will > dump the .tmp folders into the J: drive without the extra command. So > it seems that i could add a custom action to my msi or just when > building patches...just that extra command. > > I would like to know if it is actually making those folders in the > location specified however...or if they are going somewhere else or > just being deleted that quickly there is no chance of seeing them. > Although looking at the log the RootDrive property just stays as what > i specified...so logically i assume thats not going to change. > > > > Thanks for your help guys - that seems to have solved a problem i have > been hunting for a while! One wall down...ever so many to go! > > If you want more then run filemon or processmon during the admin install and you'll see all the file opens that take place. These are now Microsoft tools and you can get them at http://www.microsoft.com/technet/sysinternals/default.mspx. Sincerely, Adrian Accinelli

Re: msiexec \a tmp folders lizii <cronvek[ at ]gmail.com> 21.06.2007 12:48:07 ProcessMonitor worked a treat! Although a lot of information being thrown at you at once - i saw msiexec and indeed it used the c:\ when specified! Fantastic little tool! Thanks for your help!