Local Settings Temp folder issue

Microsoft Windows xp professional w/serv...
May 7, 2010 at 07:19:21
Specs: Windows XP
I am currently baffled by the following issue;

OS - Win XP Pro 32bit SP3

Background;

When attempting to install certain packaged software it will fail or in some cases bring up the Windows Installer information window.

We have noticed that it appears to happen when an installer, EXE or MSI relies upon transforming a further extracted MSI with an MST file.

This only occurs if the files are attempted to be extracted to the root of the temp folder. The files are not created hence cannot be run. The Windows Installer information window will appear if you attempt to run msiexec pointing to a file that does not exist.

For example;

When it works, an example>
We run an EXE that is located on the desktop. This then extracts further EXE's (and subfolders) to a folder called, for example, "SFX18C.tmp". Another folder called, for example, "{8907BCE9-6673-4A9A-A24A-892C26294539}", is also created within the TEMP folder which contains various INI files, an MSI and MST file. The installer then runs/transforms this MSI which appears to be named via a selection of random numbers and letters such as "aaetc234.msi & aaetc234.mst" in the root of the TEMP folder. The file size of this msi is exactly the same as the msi located in the {8907BCE9-6673-4A9A-A24A-892C26294539} folder. The installation continues and these files are removed, along with the {8907BCE9-6673-4A9A-A24A-892C26294539} and "SFX18C.tmp" folder.

When it doesn't work, an example>
We run an EXE that is located on the desktop. This then extracts further EXE's (and subfolders) to a folder called, for example, "SFX18C.tmp". Another folder called, for example, "{8907BCE9-6673-4A9A-A24A-892C26294539}", is also created within the TEMP folder which contains various INI files, an MSI and MST file. No files are created in the root of the TEMP folder and the Windows Installer window opens. When this is closed the {8907BCE9-6673-4A9A-A24A-892C26294539} and "SFX18C.tmp" folder and files within are removed.

Information;

The issue does not occur if we are logged in as the original local administrator account. We have created further local administrator accounts and these suffer from the same issue. Domain accounts with administrator privileges also have the same issue as do users with Domain Admin rights.

I have tried changing permissions and ownership on the Local Settings and Temp folder, even adding in Everyone as full permissions but still the issue persists.

The following seems an important find for me as it must be related to something within the location of Local Settings;
If we change the environment variable for TEMP and TMP to something outside of %USERPROFILE%\Local Settings, such as C:\TEMP or %USERPROFILE%\TEMP then the extraction\transform works fine and the installation will complete.

We have uninstalled our AV product which has made no difference.

We have deleted the contents of the TEMP folder and tried again.

We use two manufacturers, HP and Lenovo. The issue is apparent on all our Lenovo's models which use the same image and was originally based on an XP build provided from Lenovo. We have looked back at a previous image (7 months old) that was created from that original XP build and that also suffers from this issue. Our HP build does not have this issue.

We have a packaged Citrix XenApp EXE which successfully extracts an MSI and tmp files to the root of the TEMP folder and installs successfully. Other temp files, such as from Adobe, are also apparent in the root of the TEMP folder.

Summary;

So it appears that there is an issue with certain packaged installers combined with the location of the TEMP folder when in its default location (%USERPROFILE%\Local Settings folder), and using any account that isn't the original administrators account.

Any ideas? Thank you for taking the time to read this long query!

Thanks!


See More: Local Settings Temp folder issue

Report •


#1
May 7, 2010 at 17:54:23
Maybe this info will help.

Windows Installer Cleanup Utility
http://windowsxp.mvps.org/MSICLEAN.htm
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/defaul...

How to resolve Common "Windows Installer" Problems
http://support.microsoft.com/kb/555175


Report •

#2
May 10, 2010 at 02:14:51
Thanks for your reply Johnw.

I have previously looked at some of those links, but it does appear that this problem isn't related with the Windows Installer, as that will run MSI files and install them fine when they aren't extracted out of a packaged installer. The issue here appears to be an issue with package extractor not being able to extract files to the TEMP folder if it is located in %USERPROFILE%\Local Settings\
Because the files don't exist the extractor then fails to run the extracted files, an MSI in our case.

If we change the environment variable for TEMP to something outside of %USERPROFILE%\Local Settings, such as C:\TEMP or %USERPROFILE%\TEMP then the extraction works fine and the installation will complete.

I am wondering what is not allowing these files to be extracted to only folders located in the usual TEMP location.


Report •

#3
May 11, 2010 at 01:26:19
DesktopTeam, SWAG, sounds to me like cache size might be the determinant here. That's something you can specify. Enlarge it?
HTH.
Ed in Texas.

Report •

Related Solutions

#4
May 11, 2010 at 03:19:11
Thanks for your input Ed. Tried enlarging the cache as you suggested, but still no joy.

Report •

#5
May 11, 2010 at 10:14:02
Ok, an update.

After much further investigation it looks like it is an issue with the way installers use the TEMP or TMP user environmental variable. They seem to be stumbling on the fact the variable has a space in it for the "Local Settings" part. When I tried a different location I used a variable that by co-incidence did not contain any spaces and it worked.

I have tried many different ways to encompass the EV for TEMP and TMP, such as using quotes etc, but nothing will work. Changing the temp folder to something outside of "Local Settings" will work but this shouldn't have to be done. It works fine on our default local admin user account, but not on any other domain or local account so there must be a global setting that isn't being carried over or is missing. The variables are set up the same way on our HP image, and I believe the default XP way. I will keep investigating. If anyone has any further thoughts then please share.

Thanks.


Report •

#6
May 12, 2010 at 02:47:16
Opened new post because of these further findings, post here;

http://www.computing.net/answers/wi...

Mods please feel free to close/lock this post.


Report •


Ask Question