Software Deployment

Run the uninstall with a verbose log. That ought to show you whether or not the CA ran.

I am not that much familiar in analysing log files. I am including the portion of the uninstall log file that corresponds to the custom action I mentioned about.

MSI (s) (D4:B0) [15:23:22:316]: Executing op: FeatureUnpublish(Feature=Accessory_PowerPoint_ENU,Parent=CurrentUser,Absent=2,Component=UA1f2*$Up=I2GrAt4vT,)
MSI (s) (D4:B0) [15:23:22:316]: Note: 1: 1402 2: UNKNOWN\Installer\Features\BA7FB0ADBE885764F81A35E1DA398812 3: 2
MSI (s) (D4:B0) [15:23:22:316]: Executing op: ActionStart(Name=TSC_RemoveAddin_PP,Description=Removing PowerPoint Add-in...,)
MSI (s) (D4:B0) [15:23:22:316]: Executing op: CustomActionSchedule(Action=TSC_RemoveAddin_PP,ActionType=1062,Source=On Error Resume Next
Set appPPT = CreateObject("PowerPoint.Application")
appPPT.CommandBars("SnagIt ").Delete
appPPT.Quit
Set appPPT = Nothing,,)
MSI (s) (D4:6C) [15:23:22:316]: Entering MsiProvideComponentFromDescriptor. Descriptor: T%i&7oT-C?kaTW(0fqX8Toolbox>M5KDYSUnf(HA*L[xeX)y, PathBuf: FBF348, pcchPathBuf: FBF344, pcchArgsOffset: FBF2A4
MSI (s) (D4:6C) [15:23:22:316]: MsiProvideComponentFromDescriptor called for component {997FA962-E067-11D1-9396-00A0C90F27F9}: returning harcoded oleaut32.dll value
MSI (s) (D4:6C) [15:23:22:316]: MsiProvideComponentFromDescriptor is returning: 0

Help me out

Hi Veena,

I suggest that you check the properties of the corresponding CA that runs the Vbscript. Make sure whether that the CA is run in 'System Context' or 'User Context' and also try and analyze the placing of the CA. I suppose try running the CA is system context.

Also check the return value of the same CA from the verbose log that you have generated. This gives you an idea whether this CA has run or not.

Cheers [8|]

Rajit's comments are valid, although I'd nitpick a little and say that the return value tells you whether the CA returned a success or failure return code: if a CA doesn't get run, the log would explicitly say that.

To thos comments I would add the question, does the command bar "SnagIt " (WITH THE SPACES IN ITS CAPTION/TITLE!) exist? Could that be a simple typo on the vendor's part? Does that script snippet remove the add-in if you run it outside of the MSI as a stand-alone script? Also, my reading of the script - although I admit to knowing next to nothing about the PP Object Model - suggests that all it does is remove the toolbar, not the add-in.

If it was me, I'd record a macro in PP of the add-in removal. That'll be in VBA, of course, but it will show you the syntax required.

Rajit: I tried changing the CA context to 'System Context' (Earlier it was running under 'User Context'). Yet, the toolbar remains

VBScab: The script removes the add-in if I run it outside the MSI(only if the toolbar is specified with spaces as "SnagIt "). Could you suggest me some how to record a macro in PP for the add-in removal

Thanks for the replies

VBScab: Could you suggest me some how to record a macro in PP for the add-in removalAre you serious?!? All the Office apps are the same:

Tools/Macro/Record New Macro

then, when you've removed the add-in

Tools/Macro/Stop Recording

Alt+F11 will then take you into the VBA Editor, from where you can copy the code. Remember that it will be VBA code and its variables will (hopefully!) be 'typed' i.e. defined like 'Dim sAddIn As String' and so on. You'll need to remove the type definitions before you can use the code in VB Script.

VBScab : I can find only one line of code in the VBA Editor after following the procedure for recording a macro

Application.CommandBars("SnagIt ").Delete

This is same as the CA code

...then that proves me wrong, i.e. that the syntax you had is perfectly valid, although it *looks* like there are more spaces in the command bar name. I'd paste this part:

CommandBars("SnagIt ")

and replace the identical part in the CA, just be sure the name is right.

After that, I'd add some error-trapping into the CA that tests whether the add-in removal was successful or not.

There are no extra spaces in the VBA code

The toolbar remains only in the "Limited User Mode" after uninstallation (gets removed in "Admin mode")

The file PPT11.pcb is created in both the Admin and Limited User Mode when PowerPoint is lauched after installation in the location "C:\Documents and Settings\test\Application Data\Microsoft\PowerPoint"

The folder "C:\Documents and Settings\test\Application Data\Microsoft\PowerPoint" gets removed in admin mode after uninstallation, but remains in Limited User Mode.
The toolbar gets removed if I manually delete the file PPT11.pcb

Is it advisable to do this. Because, the file seems to store some configurations

ORIGINAL: veenarvg
The toolbar remains only in the "Limited User Mode" after uninstallation (gets removed in "Admin mode")So did you check yet whether the CA is running in User or System context (see post 4)?. To my mind, what you say here indicates that it's running in User context, whereas it ought to be in System context.

ORIGINAL: veenarvg
The file PPT11.pcb is created in both the Admin and Limited User Mode when PowerPoint is lauched after installation in the location "C:\Documents and Settings\test\Application Data\Microsoft\PowerPoint" From what I remember about MS's file naming, that PCB file contains the bitmap for the toolbar. It may contain configuration information, too. Therefore, deleting it will have unknown effects.

ORIGINAL: veenarvg
Is it advisable to do this.
To do what?

I have already checked changing the "User context" to "System Context". But, the toolbar remains