I have an application, NetIQ, that has the initial installation, a Service Pack 1 upgrade, and a hotfix to apply to the Service Pack 1 upgrade. I built one exe that installs all three; now I need to build an exe for only the hotfix.

All three installations were vendor-provided exe's. I tried extracting files and doing silent installs from any MSI's inside the exe's, but had various troubles with that approach, so I took a lazy way out and used AdminStudio to run each of the exe's sequentially and build one big MSI. I've tested this and it works the way the users want it to.

Now I'm trying to build a package for just the hotfix, which will be applied to PCs in our environment (Office 2003, Windows XP SP2) that have had the initial app and the SP1 upgrade installed manually from the vendor-provided exe's.

I tried extracting the files from the hotfix exe and found a MSP, but trying to install that from the command line results in a failed install. I tried building a package using AdminStudio, which worked, and installed successfully, but the problem there is that when I look at Add/Remove Programs, the hotfix install is listed as a separate program instead of upgrading the version number of the original install.

I'm not sure what else to try. I've run the install (both the client's exe and my command line w/ the patch) while also running Process Monitor, but don't know exactly what I'm looking for. Nothing obvious jumps out at me that says "here's where/why it's breaking".

The command line looks like a pretty standard patch install command, plus the addition of the ISSETUPDRIVEN=1 property to get past the "...use setup.exe" dialog that initially appeared when I tried installing from the MSP.

Here's a chunk of the log file where I believe the install is failing (based on what I've read about searching the install log for "Return value 3" when the MSI error is 1603), but again, not exactly sure what I'm looking for:

MSI (s) (48:DC) [14:35:50:096]: Executing op: ActionStart(Name=OnFeaturesInstalling,,)
MSI (s) (48:DC) [14:35:50:111]: Executing op: ActionStart(Name=OnMoving,,)
MSI (s) (48:DC) [14:35:50:111]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (48:DC) [14:35:50:111]: Error in rollback skipped. Return: 5
MSI (s) (48:DC) [14:35:50:158]: No System Restore sequence number for this installation.
MSI (s) (48:DC) [14:35:50:158]: Unlocking Server
MSI (s) (48:DC) [14:35:50:158]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (48:DC) [14:35:50:174]: Transforming table InstallExecuteSequence.
MSI (s) (48:DC) [14:35:50:174]: Transforming table InstallExecuteSequence.
MSI (s) (48:DC) [14:35:50:174]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:DC) [14:35:50:174]: Doing action: ISCleanUpFatalExit
MSI (s) (48:DC) [14:35:50:174]: Transforming table CustomAction.
MSI (s) (48:DC) [14:35:50:174]: Transforming table CustomAction.
MSI (s) (48:DC) [14:35:50:174]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (48:DC) [14:35:50:190]: Transforming table Binary.
MSI (s) (48:DC) [14:35:50:190]: Transforming table Binary.
MSI (s) (48:DC) [14:35:50:190]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (48:E8) [14:35:50:252]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2EA.tmp, Entrypoint: CleanUp
Action start 14:35:50: ISCleanUpFatalExit.
1: Shutting down the PRC server...
1: RPC server shut down.
1: enter OnEnd
Action ended 14:35:50: ISCleanUpFatalExit. Return value 1.
Action ended 14:35:50: INSTALL. Return value 3.
1: Skip installation of module help files
1: enter myNetIQProdRegExistsCheck
1: AppManager NOT Found!
1: Analysis Center NOT Found!
1: enter myServicesStart
1: ext myServicesStart
1: exit OnEnd
1: ###--> *****************************************************************
1: ###--> Log File 0 Closed!
1: ###--> *****************************************************************
1: ###--> INFORMATION: Failed to close file handle=0 with return code=-501
1: MsiServerStartup ends
Action ended 14:35:56: ISMsiServerStartup. Return value 0.
Property(S): ALLUSERS = 1


My only other clue is from an email from the vendor that states the installation does a series of checks to see whether the exe is being installed on a variety of servers or not (we're installing to desktops). Don't know if this is why it's failing when I try installing from the MSP or not.

The vendor has communicated to us that doing anything other than a manual install of their exe isn't supported. However, this isn't feasible in our environment w/ a few hundred PCs to update. Any ideas of what I might try next are appreciated. I've posted, too, to the NetIQ QMunity forum, but no answers were forthcoming there except for the response that what we're trying to do isn't supported. Am I just out of luck, then?
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
It sounds like you've used Admin Studio to re-package MSIs which is probably the biggest no-no in packaging.

I'd suggest that you go back to making the silent installs of the MSIs work. Invariably, silent installs of MSIs fail because the original packager failed to ensure that Custom Actions in the UI sequence are, at best, marked to be always run or, at worst, copied to the Execute Immediate sequence. You can take care of that in your transform(s).

Lastly, try to avoid patching clients individually. It's much easier to patch an Administrative Installation Point and install from the patched MSI.
Answered 01/26/2010 by: VBScab
Red Belt

Please log in to comment
0
Not sure I follow you.

First, I agree about repackaging w/AdminStudio. But it was a last-ditch effort to make a deadline, and all my other attempts had failed. I know, that's still an excuse.

So right now what I have is a package that silently installs all three things: the original app, the Service Pack 1 upgrade, and the hotfix. That works, end users tested it, everybody's happy.

Now I need to create a silent install package for just the hotfix. When I extract files from the hotfix, I find, among other things, an MSP file. That's the part I can't get to work.

So are you saying I need to go back and repackage the first two things by applying transforms to the extracted MSI's? If so, I'm still not sure how that gets me to making a successful silent install package for the MSP.

Also agree w/ you about patching clients individually. There's no way we can do that given the number of PCs we're talking about.
Answered 01/26/2010 by: RonW
Green Belt

Please log in to comment
0
Yes, I would re-visit the MSIs but I completely understand about deadlines, etc. I could almost bet you have a salivating project manager driving things...

Anyway, if you have a package which installs the app, service pack and hotfix, why not simply edit that down to just the hotfix? Presumably the otfix is installed via a Custom Action? So, remove the features not involved with that, remove the CA which installs the SP and you're left with the hotfix installation, no? A bit Heath Robinson but, it seems to me, that's the fastest way to get to where you need to be.
Answered 01/26/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi Ron,

Apologies for late response but this AppDeploy posting has only just come up in our daily web scan.

I'm the manager of the NetIQ Qmunity and noted your comment about the AppManager forum. I have contacted two of the Qmunity's "Uber Geeks" to respond/re-investigate your original post within Qmunity.

In the meantime there is additional information here not in the original post - mind if I carry it over?

Regards
David
Answered 04/05/2010 by: Shephardd
Yellow Belt

Please log in to comment
0
Hi, Shephardd. That's fine. Let me know if there's any other info I can provide. Where we're at with the NetIQ packages is that I've been able to create a full package (the app, a Service Pack 1 update, and a hotfix), but unable to create a package just for the hotfix itself.
Answered 04/05/2010 by: RonW
Green Belt

Please log in to comment
1
Thanks Ron -
Our Uber Geek: Tim Sedlack, responded to your original post in the Qmunity AppManager Forum:
[blockquote]Are you planning on using Radius or SMS or some other tool to run this deployment? We see a common case for creating a response file for agents (as people generally have large numbers of these) - but it's very rare (in fact I haven't heard of a customer with so many Control Center UIs installed). I'll check with the team and see what I can find.[/blockquote]David
Answered 04/05/2010 by: Shephardd
Yellow Belt

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