EDIT: sorry I just found the Windows Installer errors forum [:)]

This may be a little OT, for which I apologise...

In the last few weeks I've had problems with Transforms, and today I discovered why. A logfile said:

UNKNOWN) DEBUG: Error 2759: Transform C:\DOCUME~1\REPACK~1\xplore\Temp\331bd03d.mst version 301 incompatible with engine; Min: 30, Max: 300.

I've figured it out to be that the version of MSIEXEC on my test machine is 3.0, whereas I'm on 3.1 on my PC. I upgraded to Adminstudio 6 - and I suspect that it's creating Transforms for installer 3.1.

I think I have 2 options:

- Upgrade the Windows Installer Engine across all 100+ PCs to 3.1 (this doesn't look easy as when I downloaded the redistributable from MS there is no MSI, and I don't fancy repackaging a system patch )

- Get Adminstudio to create Transforms compatible with MSIEXEC 3.0

Anyone any thoughts?


Ian E
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I assume that you solely use GP to deploy software.
Do u use any other software distribution tool?
If you are running WSUS for your windows environment you can assign this as a client update. Otherwise i think you may be abit stuck with the exe... and an install script.
Answered 09/13/2005 by: rahvintzu
Orange Senior Belt

Please log in to comment
The windows installer version on pc you create the msi / mst on, is the version created. I use 5.5 and had the same issue. in stall admin studio client on a PC with win installer 3.0, and then create the msi, or mst on that machine. As admin studio calls the current version of the client you are running it on.. i think..

Just happened to me this morning
Answered 09/15/2005 by: ancientcontra
Senior Yellow Belt

Please log in to comment

Thanks - that makes sense. I did have the Installer version 3.1 on my machine.

We've managed to fettle WSUS and it's working OK now so all the client machines have v3.1 on.
Answered 09/15/2005 by: IanE
Senior Yellow Belt

Please log in to comment