I use AdminStudio for Configmgr (a free edition) to create response transforms

Today packaging Dragon 11 and getting error installing the Visual C++ Runtime with a fairlyy standard msiexec /i msifile TRANSFORMS=mstfile /qr

Error applying transforms verify path is valid. I create the transform on my own PC which is windows 7 and I tested my package on a Windows 7 VM and it worked fine, but then got the above error message on an XP VM. I assume it has something to do with the different versions of windows installer but as a test I installed the adminstudio onto the XP VM and recreated the transform and then the command line worked ok on windows XP. Haven't yet got round to retesting on windows 7 but I suspect that will be ok as well

Does this mean I have to create all transforms within XP i.e. the lowest operating system ?

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Paths need to be pretty specific.

c:\windows\system32\msiexec.exe /i \\server\share\file.msi TRANSFORMS="\\server\share\file.mst" /qr

Also, that error message may be indicating that the MSI may not like something within the MST.

One other possibility is your MST is corrupted. I'm using AdminStudio/InstallShield 10 and periodically, I have to start over with my MST's because they don't build/save properly and become corrupted.
Answered 07/12/2011 by: jmaclaurin
Third Degree Blue Belt

Please log in to comment
0
Dragon was also very particular about the order you install its Visual C++ component and the Dragon app through version 10. I haven't worked with v11 yet but consider you may still have to install the Visual C++ component first, suppress any reboots and then continue with installing Dragon 11.
Answered 07/12/2011 by: Helpy
Senior Yellow Belt

Please log in to comment
0
So a transform created under windows 7 should work ok with and older XP system with the older version of msiexec ?

As I said I installed adminstudio on the XP VM and recreated the MST. Then tested in the package and it works fine under both XP and Windows 7

For the package I put the Visual C++ in a subdirectory under Dragon and cal from a VBscript - here's the line

IntReturnCode = oWSH.Run ("msiexec /i """ & MSIFile & """ TRANSFORMS=""" & MSTFile & """ /qr SKIP_PENDINGREBOOT_CHECK=1 REBOOT=ReallySuppress",1,True)

MSIfile and MSTfile are translating to a proper directory path i.e. \\unc\Visual Runtime\Visual C++ etc. etc.

I then run Dragon

intReturnCode = oWSH.Run ("msiexec /i ""Dragon NaturallySpeaking 11.msi"" SERIALNUMBER=" & strSerialNumber & " /qb /l* ""%temp%\Dragon11.log""",1,True)

I was going to log a separate thread for this because again I created a transform and was getting issetup type errors. I found that with /qb and no transform it works ok so I'll go with that !
Answered 07/12/2011 by: iburnell
Senior Yellow Belt

Please log in to comment
0
in my vbscripts, i stopped using double or triple " i noticed that this could lead to problems. now i use the character 34, like this:

strMsiToRun = Chr(34) & strCurrentDir & "Open Workbench.msi" & Chr(34)
strTrans = Chr(34) & strCurrentDir & "NikuCorporationOpenWorkbench122EN.mst" & Chr(34)
intErrCode = objShell.Run("msiexec.exe /i " & strMsiToRun & " TRANSFORMS=" & strTrans & " REBOOT=ReallySuppress /qn /l*v " & Chr(34) & strCurrentDir & "OWB_Install.log" & Chr(34), RUNHIDDEN, True)

i suggest you try it.
Answered 07/12/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
Nice tip - thanks - I'll give that a try
Answered 07/13/2011 by: iburnell
Senior Yellow Belt

Please log in to comment
0
Hi - sorry to raise this one again but every time I seem to create a response transform on my own PC (Windows 7) the packages run just fine on Windows 7 but not on Windows XP

Can I just check do you have to step down to an XP machine to create the transform in the first place or is it my bad scripting. Sorry I don't have the exact command line in front of me - I was packaging Safend client which is a security tool. The command was something like msiexec /i safend.msi TRANSFORMS=safend.mst /qr
Answered 08/28/2011 by: iburnell
Senior Yellow Belt

Please log in to comment
0
It has been an unwritten rule for some time that one packages for the lowest common denominator (in this case, XP) and add conditions for higher OSes. Build yourself an XP Pro VM and use that. You can copy your exclusion list etc. from your W7 packaging VM which, of course, you should retain for testing purposes.
Answered 08/29/2011 by: VBScab
Red Belt

Please log in to comment
0
ok - thanks for the confirmation
Answered 08/29/2011 by: iburnell
Senior Yellow Belt

Please log in to comment
0
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="?
Answered 12/22/2011 by: zzpack
Orange Senior Belt

Please log in to comment
4
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?
Answered 12/22/2011 by: VBScab
Red Belt

Please log in to comment
-4
Obv I care.
And a merry fuc*ing x-mas to you Scrooge.
Answered 12/23/2011 by: zzpack
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity