Hello togheter,

I was just about to test the changes I've done to the QuickTime package but it failed with error code
2721 (Custom action not found in Binary table stream)

I'am pretty sure that this is encountered by deleting the two custom actions "Launch_QTTASK" and
"Install Packages" from the custom action table. Also i have deleted them from the InstallExecute and
InstallUISequence.

Is there anything further I need to delete regarding this custom actions to not get this error message?

Greetings
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
How about instead of deleting the CAs out of the tables you take the much less invasive option of giving them an impossible-to-meet condition (my personal favorite is 1=2), so they just don't execute?
Answered 10/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Ahh, thank you a lot...haven't thought at all about something like that.
I'll try it as soon as Im back to work.

Greetings
Answered 10/13/2010 by: Teitan
Senior Purple Belt

Please log in to comment
0
entering 0 (zero) in the installexecute and UI seqeunce should do the trick

quick question why are you deleting the CA's
Answered 10/13/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
The action Launch_QTTask is installing the quicktray icon which we don't need to keep the system clear and
the Install_Packages is trying to install the other msi's which are stored in the setup exe and I only want
the quicktime.msi to be installed.
Answered 10/14/2010 by: Teitan
Senior Purple Belt

Please log in to comment
0
I've had another issue with QuickTime. In fact it's solved but perhaps someone could explain me why it happened.

After adding a component with some company registry keys and testing it, I wondered why they have never appeared in the registry at all. After a lot of
testing I had the idea to put the registry keys in a component of QuickTime itself which also added some Registry keys and it worked. The QuickTime component
dont has any special Conditions but I found a CA which is named "CheckAndGrantAccessToRegistryKeys" perhaps it has something to do with that issue?

It would be nice to understand the problem that I can solve something like this faster if I'am facing it next time.

Greetings.
Answered 10/14/2010 by: Teitan
Senior Purple Belt

Please log in to comment
0
Teitan,

did you remember to associate your new component with a feature? and did this feature have a correct InstallLevel set?

PJ
Answered 10/14/2010 by: pjgeutjens
Red Belt

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