Custom Action Woes

G'Day All,

Working with Expression Web SP1 (updates extracted into the update folder and applying successfully)
Install copies the files locally to "C:\Temp\ExpressionWeb" where setup.exe is executed from here with a CA (210) calling the config.xml file in this location. All components are attrib 16 ( I'll clean this up at the end with another script).

My problem is the uninstall. I have a custom action type (50) after InstallFinalize in the EI sequence before RemoveExistingProducts.
My Property is set to:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\setup.exe" =UNINSTALLPATH command: /uninstall WEBDESIGNER /dll ESETUP.DLL

I'm getting Error 1721 (ProcMon showing that it was looking for the C:\Temp files). The log file isn't giving me much help either.
"MSI (s) (54:D8) [15:05:59:328]: Product: Microsoft Expression Web SP1_1.0_R1 -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: CA_UninstExpWeb, location: "C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\setup.exe", command: /uninstall WEBDESIGNER /dll ESETUP.DLL"

When I run the command manually I get the uninstall correctly.

We have to install this as an msi because of our GP environment. I've read that MS doesn't support the mass deployment of this product (before someone mentions it, so don't get me started on why MS is following this xml installation package path like my other favourite vendor).

Any help on the CA or any ideas on what to try, greatly appreciated.

Any advice

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 12 years ago
Red Belt

(ProcMon showing that it was looking for the C:\Temp files).
Hi, Wayne. My initial thoughts:
- Does ProcMon show you it *finding* the files it requires?
- It couldn't be something simple like spaces in filenames, requiring quote marks, could it?
- I'd monitor the manual uninstall with ProcMon to see exactly what activity takes place and compare that with what happens when the MSI attempts it.
Posted by: WayneB 12 years ago
Blue Belt
Thanks for replying VB,

Sorry I didn't get back to you earlier, I got dumped with extra stuff which has been a blast.[8|]

Thought I'd have something more substantial to report on this. You gave me an idea though, regarding the spaces.
So I created a type 18 CA which executes lsrunas.exe and an autoit script to handle the Yes/No prompt. This still doesn't uninstall completely when run through GP but the individual scripts run as desired.

I'm going to try mucking with the chaining of the individual apps (5 msi's and 3 update patches) by transforming each of the msi's. Currently on GP deployment, the msi finishes but the setup.exe called from my type 50 CA still continues until finished, allowing users to log in and can the installation which we all know some will. This will enable removal to be a little easier (hopefully).

This is looking like one of our Adobe CS3 installations on a minor scale, but still a pain in the....

I'll keep ya posted.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ