Software Deployment Question

Error 2721 installing MSI with transform : Custom Action IsServerCore is not found in binary table stream

11/19/2012 13277 views

 When I am installing the msi with transform it is giving error 2721 custom action IsServerCore is not found. but the custom action is present in custom action table. how to resolve this please help.


0 Comments   [ + ] Show comments


Community Chosen Answer

  • yeah i have seen these sites.. but they doesn't work out for me

All Answers


If you look at your Custom Action in the CustomAction table, find the value in the 'Source' column and make sure that it exists in the first column of the 'Binary' table.

Answered 11/19/2012 by: captain_planet
Black Belt

  • the source value is there in the binary table but not installing giving same error
  • Does it install without the transform? What type of CA is it? Have you checked that, even though the entry is present in the Binary table, that the stream isn't corrupt? Try extracting the binary stream and check it looks ok and isn't 0kb or something daft.
  • No it's not installing without transform. it is giving a error 1920 serviceMCAfeeFrameork is not installed doesn't have privelliges to it
    that McAfeeFrameork CA is not there in CA table
    ( I have extracted the binary stream of IsServerCore CA unable read it but it's not any empty 0kb file)

>Try extracting the binary stream
Any packager worthy of the name will have downloaded the WI SDK which includes a bunch of scripts, one of which deals with MSI streams.

I think the WI SDK is now only available as part of the Platform SDK but that's worth having anyway.

Answered 11/21/2012 by: VBScab
Red Belt

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