HELP NEEDED with MSIEXEC
Hello All,
For deploying our software we use MSIEXEC for the installation. The msiexec command is,
msiexec.exe /I “test.msi†transforms=â€Âtest.mst†/q
After the install is completed it adds the path of install source to the system PATH environment.
To explain better,
1. I am installing from D:\Image\install path(Where test.msi is present) and my binaries to be installed are under D:\image\install\program files\Test.
2. Software gets installed at "c:\program files\Test".
3. After the install is complete source path "D:\image\install\Test\program files\Test" is getting added to the PATH environment variable along with the install path("c:\program files\Test"). This is causing some problem.
I would like to know why is source path getting added to PATH environment variable and what could be the problem. If anyone has faced the similar problem and was able to fix it. Please help me.
Thanks in advance.
For deploying our software we use MSIEXEC for the installation. The msiexec command is,
msiexec.exe /I “test.msi†transforms=â€Âtest.mst†/q
After the install is completed it adds the path of install source to the system PATH environment.
To explain better,
1. I am installing from D:\Image\install path(Where test.msi is present) and my binaries to be installed are under D:\image\install\program files\Test.
2. Software gets installed at "c:\program files\Test".
3. After the install is complete source path "D:\image\install\Test\program files\Test" is getting added to the PATH environment variable along with the install path("c:\program files\Test"). This is causing some problem.
I would like to know why is source path getting added to PATH environment variable and what could be the problem. If anyone has faced the similar problem and was able to fix it. Please help me.
Thanks in advance.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
MSIPackager
14 years ago
Personally never had that happen to me..
What's in the environment table of the transformed MSI ?
Cheers,
Rob.
What's in the environment table of the transformed MSI ?
Cheers,
Rob.
Posted by:
smooochy
14 years ago
What are you using to package it?
In Windows Installer, the WriteEnvironment Strings standard action writes to your environment variables based on what is in your Environment Table.
If you want to remove this completely then remove the action from your sequence, and/or delete the entry in the Environment Table.
In Windows Installer, the WriteEnvironment Strings standard action writes to your environment variables based on what is in your Environment Table.
If you want to remove this completely then remove the action from your sequence, and/or delete the entry in the Environment Table.
Posted by:
smooochy
14 years ago
Well SMS is the deployment tool, for packaging you use Installshield, WISE, etc.
Just asking because if you use Installshield I could tell you where to look, but I'm not familiar with other packaging tools.
Just asking because if you use Installshield I could tell you where to look, but I'm not familiar with other packaging tools.
Posted by:
maker.rain1
14 years ago
Installshield is used for creating the install package. But for deployment SMS is used.
Posted by:
smooochy
14 years ago
Okay well then in the buttons on the left-hand side there should be a "Sequences and Custom Actions" selection, where the WriteEnvironmentStrings action should be listed.
Look for the Environment table in the Direct Editor.
Look for the Environment table in the Direct Editor.
Posted by:
maker.rain1
14 years ago
I checked the Environment table in the .mst file but i dont see anything that adds the additional path. Any other thing that could be causing the problem?
Thanks
Thanks
Posted by:
anonymous_9363
14 years ago
- A Custom Action?
- A direct addition to the registry? If it's a user-level variable, it'll be in HKCU\Environment. For machine-level, check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
- A direct addition to the registry? If it's a user-level variable, it'll be in HKCU\Environment. For machine-level, check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Posted by:
pjgeutjens
14 years ago
If it's a vendor MSI you might want to run through the custom actions, see if there's one that looks suspect.
I guess it could be injected straight into the registry too at [HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].
If this is a bust, combined with the tests already mentioned above, I think it's time to start looking to your SMS server as the possible culprit.
PJ
I guess it could be injected straight into the registry too at [HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].
If this is a bust, combined with the tests already mentioned above, I think it's time to start looking to your SMS server as the possible culprit.
PJ
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.