Space ” ” in environmental variable causing issue with some installers
We have an issue that affects the way some installers (EXE) use the TEMP or TMP
user environmental variable (EV). They seem to be stumbling on the fact
the variable has a space in it for the "Local Settings" part, when executing the msi command for an msi file that it has extracted to the %Temp% folder. 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 of altering the EV for TEMP and TMP, such as using quotes etc, but nothing will work. It usually results with the installer exclaming an "Internal Error" if I use quote marks. Changing the temp folder to something outside of "Local Settings" to get rid of the 'space' will work but this shouldn't have to be done. It works fine on our default local administrator 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, which is %USERPROFILE%Local SettingsTemp.
Any ideas folks as this is really baffling me.
Many thanks
Software/Hardware used:
Windows XP pro 32 bit
I have tried many different ways of altering the EV for TEMP and TMP, such as using quotes etc, but nothing will work. It usually results with the installer exclaming an "Internal Error" if I use quote marks. Changing the temp folder to something outside of "Local Settings" to get rid of the 'space' will work but this shouldn't have to be done. It works fine on our default local administrator 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, which is %USERPROFILE%Local SettingsTemp.
Any ideas folks as this is really baffling me.
Many thanks
Software/Hardware used:
Windows XP pro 32 bit
ASKED:
May 14, 2010 4:17 PM
UPDATED:
May 17, 2010 8:19 AM
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
All Answer Wiki Contributors:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
Have you tried using other paths including blank spaces ?
The problem could be related to access permissions (not likely, but possible).
Thanks for your reply. I have tried other variables with spaces and they don’t work either. I did originally try permissions (setting full control to everyone) but it didn’t make any difference. The fact that some installers can copy the files to the TEMP folder in Local Settings, but just not execute the MSI using the MSIexec command seems to imply that it is not a permissions issue.