Transform error - upgrade to Installer 3.1?
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?
Cheers
Ian E
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?
Cheers
Ian E
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
wiseapp
18 years ago
Hi Iane:
As you said it's actually a problem with the windows installer service since from the log also it is very clear that it doesnt like MSIEXEC 3.0 however I think rolling out windows installer service 3.1 wont be that easy but still its cheaper atleast you dont need to buy license.
As you said it's actually a problem with the windows installer service since from the log also it is very clear that it doesnt like MSIEXEC 3.0 however I think rolling out windows installer service 3.1 wont be that easy but still its cheaper atleast you dont need to buy license.
Posted by:
IanE
18 years ago
Thanks for your replies.
No it's not a repackaged MSI - as far as I can remember I've seen this with 3 packages, 2 were native MSIs for which I was creating transforms, 1 was a repackaged setup.exe.
It appears that Installer 3.1 can be put out with WSUS but we're having problems with that at the moment.... [:@]
No it's not a repackaged MSI - as far as I can remember I've seen this with 3 packages, 2 were native MSIs for which I was creating transforms, 1 was a repackaged setup.exe.
It appears that Installer 3.1 can be put out with WSUS but we're having problems with that at the moment.... [:@]
Posted by:
dj_xest
18 years ago
Hi IanE,
Is it possible for you to include MS Installer 3.1 in your package that will run as a pre-install? I think you know what I am saying.. This will avoid deploying a separate patch to that 100+ pc's. What do you think? [;)]
Is it possible for you to include MS Installer 3.1 in your package that will run as a pre-install? I think you know what I am saying.. This will avoid deploying a separate patch to that 100+ pc's. What do you think? [;)]
Posted by:
IanE
18 years ago
ORIGINAL: dj_xest
Hi IanE,
Is it possible for you to include MS Installer 3.1 in your package that will run as a pre-install? I think you know what I am saying.. This will avoid deploying a separate patch to that 100+ pc's. What do you think? [;)]
I don't know this for certain, but I don't think this would work... Surely there wouldn't be a way for a package (MSI, installed by MSIEXEC.exe on the PC) would be able to UPGRADE the msiexec.exe on the PC, cos it would be in use....? That make sense...?
We've since got WSUS working properly, Windows Installer 3.1 is flying out to all clients, so software should deploy OK.
Incidentally, Installer 3.1 upgrade is also offered on SUS (as well as WSUS). The reason we weren't getting the patch to all clients to SUS was there was a problem with the permissions which were set on the AU services. So we hadn't been issuing patches for weeks. Oops [:)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.