Error applying transforms?
Hi,
Having an odd issue here. I created a response mst using the Tuner in installshield and then direct edited the mst to add some registry keys.
When I attempt to install the msi with the mst I get:
"Error applying transforms. Verify that the specified transform paths are valid."
I use the command:
msiexec /i name.msi transforms=name.mst
I have done this many times in the past without any issues. Not sure what is wrong here.
Outa curiousity I tried applying the mst to the msi and it applied just fine. The new msi installs fine with all my changes in it. Thing is I do not want to apply the mst as I will have multiple different mst based on the different departments this packages is used in.
Anyone have any ideas?
Many Thanks
Having an odd issue here. I created a response mst using the Tuner in installshield and then direct edited the mst to add some registry keys.
When I attempt to install the msi with the mst I get:
"Error applying transforms. Verify that the specified transform paths are valid."
I use the command:
msiexec /i name.msi transforms=name.mst
I have done this many times in the past without any issues. Not sure what is wrong here.
Outa curiousity I tried applying the mst to the msi and it applied just fine. The new msi installs fine with all my changes in it. Thing is I do not want to apply the mst as I will have multiple different mst based on the different departments this packages is used in.
Anyone have any ideas?
Many Thanks
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
So, when does any problems arise for using "Transforms=" instead of "TRANSFORMS="?WHO CARES?!? Just make it all upper-case every time you use it. How hard is that?
Posted by:
craig16229
19 years ago
emuringer,
I am wondering if you are running into the same issue I did just a few weeks ago. The cause was the transform required a newer version of the Windows Installer environment. Installing Windows Installer 3.1 v2 resolved it for me.
To verify whether or not this is your issue, enable verbose Windows Installer logging, run the install again, and read the log.
Here is the thread from when I ran into this:
http://itninja.com/question/"error-apply-transform"-when-running-batch-file&mpage=1&key=❑
Craig --<>.
I am wondering if you are running into the same issue I did just a few weeks ago. The cause was the transform required a newer version of the Windows Installer environment. Installing Windows Installer 3.1 v2 resolved it for me.
To verify whether or not this is your issue, enable verbose Windows Installer logging, run the install again, and read the log.
Here is the thread from when I ran into this:
http://itninja.com/question/"error-apply-transform"-when-running-batch-file&mpage=1&key=❑
Craig --<>.
Posted by:
MSIPackager
19 years ago
msiexec /i name.msi transforms=name.mst
Doesn't is need to be TRANSFORMS= (upper case) ?
Posted by:
wiseapp
19 years ago
Hi Emu:
I think Craig is right installing the new windows installer service resolves most of the installshield problems. However I would still prefer that you should switch on the verbose to get this rectified.
I think Craig is right installing the new windows installer service resolves most of the installshield problems. However I would still prefer that you should switch on the verbose to get this rectified.
Posted by:
MSIMaker
19 years ago
ORIGINAL: MSIPackager
msiexec /i name.msi transforms=name.mst
Doesn't is need to be TRANSFORMS= (upper case) ?
Ummm...now thats a good question...I think is does doesnt it?
Posted by:
plangton
19 years ago
Yep, TRANSFORMS is a public property, which have to be in upper case (as far as I know), just like ALLUSERS. From MSDN:
"The property names in the list can be uppercase and lowercase letters (private properties), or all uppercase (public properties).
This property must never end with a semicolon."
Hope that helps
Rgds
Paul
"The property names in the list can be uppercase and lowercase letters (private properties), or all uppercase (public properties).
This property must never end with a semicolon."
Hope that helps
Rgds
Paul
Posted by:
emuringer
19 years ago
Thanks for the replies guys,
I was not aware that TRANSFORMS had to be uppercase. However we install all our packages from a vbscript and I was using our standard template which did have it in uppercase already.
However craig was correct. I thought we were using the latest version of the installer but it turns out we were not. Once updated the transform installed just fine.
Thanks for the help!
I was not aware that TRANSFORMS had to be uppercase. However we install all our packages from a vbscript and I was using our standard template which did have it in uppercase already.
However craig was correct. I thought we were using the latest version of the installer but it turns out we were not. Once updated the transform installed just fine.
Thanks for the help!
Posted by:
zzpack
13 years ago
Old thread, but still.
I know transforms is a public property. But there´s no problem installing a package with a command like e.g:
"msiexec.exe /i msiname.msi Transforms=mstname.mst /qb
on a Win XP or Win 7
So, when does any problems arise for using "Transforms=" instead of "TRANSFORMS="?
I know transforms is a public property. But there´s no problem installing a package with a command like e.g:
"msiexec.exe /i msiname.msi Transforms=mstname.mst /qb
on a Win XP or Win 7
So, when does any problems arise for using "Transforms=" instead of "TRANSFORMS="?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.