"error apply transform" when running batch file
I have a series of batch files that I occasionally use for installing .msi packages. The file looks like:
@echo off
pause
msiexec.exe /i "\\installation_path\file.msi" TRANSFORMS=file.mst /qb
cls
exit
About 60% of the time, I get the message "error applying transform". In my troubleshooting, here are the characteristics I have noted:
- It is not OS specific.
- It is not tied to user rights.
- It happens on some machines, but not all.
- It happens only with a minority of the batch files and their respective packages/transforms, and it is always the same ones that fail.
- It happens (so far) only with transforms I created with WPS 5.1 or InstallTailor 6.0 - but not with every transform created by Wise products. It has not yet happened with any .mst's created by any version of ORK.
- It happens whether I specify the full UNC path to the transform, or whether I just name the transform as it exists at the root of the install directory.
I have scoured the internet but not come up with anything helpful.
Craig --<>.
@echo off
pause
msiexec.exe /i "\\installation_path\file.msi" TRANSFORMS=file.mst /qb
cls
exit
About 60% of the time, I get the message "error applying transform". In my troubleshooting, here are the characteristics I have noted:
- It is not OS specific.
- It is not tied to user rights.
- It happens on some machines, but not all.
- It happens only with a minority of the batch files and their respective packages/transforms, and it is always the same ones that fail.
- It happens (so far) only with transforms I created with WPS 5.1 or InstallTailor 6.0 - but not with every transform created by Wise products. It has not yet happened with any .mst's created by any version of ORK.
- It happens whether I specify the full UNC path to the transform, or whether I just name the transform as it exists at the root of the install directory.
I have scoured the internet but not come up with anything helpful.
Craig --<>.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
TomB
19 years ago
you can try to add "/l*v c:\temp\log\appname.log" to your command line to get a verbose log output to see if it gives you any more information.
Here is a BAT template I use for testing:
I just have to fill in the package name and packageId (filename). I name the Transform the same as the packageID. The Install.bat is in the same directory as the MSI.
Since i have started to use %~dp0 I have not had any issues.
Here is a BAT template I use for testing:
@echo off
Title = Application Installation
Set pkgid=
Set pkgName= ""
Set InstMST=YES
CLS
echo Installing %pkgName% ...
echo.
IF /I %InstMST% == NO GOTO :NOMST
IF /I %InstMST% == YES GOTO :MST
GOTO :END
:NOMST
REM **********************
REM No TransForm (default)
REM **********************
msiexec ALLUSERS=1 /i "%~dp0%pkgid%.msi" /qb+ /l*V %windir%\log\%pkgid%.log
GOTO :END
:MST
REM **********************
REM Transform
REM **********************
msiexec ALLUSERS=1 /i "%~dp0%pkgid%.msi" TRANSFORMS="%~dp0%pkgid%.MST" /qb+ /l*V %windir%\log\%pkgid%.log
GOTO :END
:END
I just have to fill in the package name and packageId (filename). I name the Transform the same as the packageID. The Install.bat is in the same directory as the MSI.
Since i have started to use %~dp0 I have not had any issues.
Posted by:
craig16229
19 years ago
Tom,
Thanks for the rapid response.
Reading your reply and looking at your batch file reminded me of some things I forgot about batch files. %~dp0 is definitely the better way to do this. I will do some testing and see if this resolves it.
Craig --<>.
Thanks for the rapid response.
Reading your reply and looking at your batch file reminded me of some things I forgot about batch files. %~dp0 is definitely the better way to do this. I will do some testing and see if this resolves it.
Craig --<>.
Posted by:
craig16229
19 years ago
No luck - same error. Will grab verbose logging and post it here.
Craig --<>.
Craig --<>.
Posted by:
craig16229
19 years ago
Verbose Windows Installer Logging indicates that the target workstations have too low of a version of the Windows Installer Runtime Environment. I will have to compare versions on the affected machines tomorrow.
Craig --<>.
Craig --<>.
Posted by:
craig16229
19 years ago
Update for those of you it may help:
Windows Installer Logging saves the day again. Updating the problem machines to Windows Installer 3.1 v2 resolved the issue.
Craig --<>.
Windows Installer Logging saves the day again. Updating the problem machines to Windows Installer 3.1 v2 resolved the issue.
Craig --<>.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.