Adobe Audition 3 Help

I was able to get this to install with no problem with my transform. When I attempt to uninstall, I get the following:

MSI (s) (80:F8) [13:37:09:315]: Note: 1: 1725
MSI (s) (80:F8) [13:37:09:315]: Product: Adobe Audition 3.0 -- Removal failed.

MSI (s) (80:F8) [13:37:09:315]: Attempting to delete file C:\WINDOWS\Installer\bb188.mst
MSI (s) (80:F8) [13:37:09:315]: Unable to delete the file. LastError = 32
MSI (s) (80:F8) [13:37:09:330]: Cleaning up uninstalled install packages, if any exist
MSI (s) (80:F8) [13:37:09:330]: MainEngineThread is returning 1603
MSI (s) (80:FC) [13:37:09:330]: Destroying RemoteAPI object.
MSI (s) (80:8C) [13:37:09:330]: Custom Action Manager thread ending.
=== Logging stopped: 3/18/2010 13:37:09 ===
MSI (c) (D0:94) [13:37:09:346]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D0:94) [13:37:09:346]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/18/2010 13:37:09 ===

I have 1 custom action which runs for the install with a condition:
If NOT REMOVE~="ALL" then...

However, the problem is not with the install, it's with the Uninstall. I'm uninstalling using the same user name as the install.

Any suggestions would be worth looking at.

0 Comments   [ + ] Show comments

Answers (7)

Posted by: cygan 13 years ago
Fifth Degree Brown Belt
what is your custom action doing and where is it sequenced
Posted by: Secondlaw 13 years ago
Third Degree Blue Belt
The custom action is a compiled .wse which simply installs a few registry keys (Execute Deferred, before InstallFinalize):

Windows Registry Editor Version 5.00


With these keys populated, we essentially bypass the logged in user from seeing the registration screen.

This exe is through active setup. Within the transform, I created a new component with the appropriate active setup keys.
Posted by: cygan 13 years ago
Fifth Degree Brown Belt
ORIGINAL: Secondlaw

The custom action is a compiled .wse which simply installs a few registry keys (Execute Deferred, before InstallFinalize):

just out of interest why are you using .wse

in your vendor msi you don't want to change you feature structure so all you need to do provided you have an advertised shortcut is

create a component and add all your hkcu keys
Posted by: Secondlaw 13 years ago
Third Degree Blue Belt
My initial solution was to do just as you said. So, I created a few advertised shortcuts and removed the ones provided within the msi via transform. I then created my HKCU keys and moved them along with my new shortcuts to the same component. This package didn't like that. It would not install the shortcuts when I added them manually in the transform. So, my next thing was to create the WSE (could have used anything but WSE was simple) and made it an active user setup. Maybe I should create the shortcuts in the WSE too but then I'll have to create a seperate uninstall for it too.
Posted by: anonymous_9363 13 years ago
Red Belt
Your log extract is taken too far down. Open it again and find theline which contains the text 'Return value 3.' Post the dozen or so lines above and below the line where that text occurs. Also, please use the CODE tag when posting logs, script or anything of length.

As for the registry stuff, you clearly made some sort of error with your shortcut creation. I've never yet come across a package which "didn't like" features added via the described method.
Posted by: Secondlaw 13 years ago
Third Degree Blue Belt
I've never had a problem with shortcuts either. This is the first time for me too. Can you make a mistake creating shortcuts? I've been packaging for a while and this is the first time this has happened to me.

(Adobe) Value: C:\Program Files\Adobe\Adobe Audition 3.0\
(Adobe) Requesting property: SIFPath
(Adobe) Value: Audition.sif
(Adobe) SIF full path: C:\Program Files\Adobe\Adobe Audition 3.0\Audition.sif
(Adobe) Requesting property: ProductCode
(Adobe) Value: {53C141BA-4F9E-43FB-B4F9-0C01BB716FA8}
(Adobe) Serial number from registry: 976587043075406739162005
(Adobe) GetSerialNumberInfo failed
(Adobe) END - RegisterForAUM40
MSI (s) (80:F8) [13:37:08:674]: Transforming table InstallExecuteSequence.

Action ended 13:37:08: UnRegisterForAUM40. Return value 3.
Action ended 13:37:08: INSTALL. Return value 3.
Property(S): Text = 0
Property(S): DiskPrompt = [1]
Property(S): Registration = No
Property(S): InstallMode = Complete
Property(S): UpgradeCode = {1AD0312E-D85C-4698-B9EA-C665591BFB0A}
Property(S): VersionNT = 501
Property(S): REMOVE = ALL
Property(S): Installed = 2007/10/10 14:56:38
Property(S): INSTALLDIR = C:\Program Files\Adobe\Adobe Audition 3.0\
Property(S): ACTIVATION = C:\Program Files\Adobe\Adobe Audition 3.0\Activation\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): ADOBE = C:\Program Files\Adobe\
Posted by: anonymous_9363 13 years ago
Red Belt
So the action causing the failure is 'UnRegisterForAUM40'. I suggest running the uninstall through a debugger and setting a break-point on that action. Then, kick off ProcMon - remember to filter out processes you're not interested in, like Explorer, your A/V and so on. Then, step the debugger so it executes that action. When it completes, return to ProcMon and see what you've got. I'm willing to bet that there's a file or registry entry missing/corrupt or a permission issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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