MSIX Packaging Tool failure

%3CLINGO-SUB%20id%3D%22lingo-sub-375967%22%20slang%3D%22en-US%22%3EMSIX%20Packaging%20Tool%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-375967%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I'm%20trying%20to%20package%20%3CA%20href%3D%22https%3A%2F%2Fcloud.google.com%2Fchrome-enterprise%2Fbrowser%2Fdownload%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EChrome%20for%20Enterprise%3C%2FA%3E%26nbsp%3Bbut%20the%20packaging%20tool%20is%20failing%20with%20the%20attached%20log.%3C%2FP%3E%3CP%3EWhy%20would%20this%20happen%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377453%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377453%22%20slang%3D%22en-US%22%3E%3CP%3E%40Deleted%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Graham%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20just%20added%20the%20version%20to%20the%20TypeLib%20463ABECF-410D-407F-8AF5-0DF35A005CC8%20from%20the%20interface%20with%20the%20same%20GUID.%20The%20version%20is%201.0%20as%20in%20the%20COM%20TypeLib%20with%20the%20same%20GUID.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20!%3C%2FP%3E%3CP%3EVictor%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376987%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376987%22%20slang%3D%22en-US%22%3EHi%20Victor%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20also%20struggling%20with%20converting%20Google%20Chrome%20Enterprise%20to%20MSIX.%20I%20will%20try%20the%20workaround%20since%20it%20solved%20the%20issue%20for%20you.%20Quick%20question%20though...%20did%20you%20purge%20or%20correct%20the%20com%20registry%20keys%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EGraham%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376694%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376694%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F235896%22%20target%3D%22_blank%22%3E%40James%20Pike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20James%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20was%20indeed%20what%20you%20described%2C%20so%20I%20could%20work%20around%20it%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help%20!%3C%2FP%3E%3CP%3EVictor%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376365%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376365%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Victor%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat%20particular%20failure%20is%20a%20little%20tricky%20to%20identify%20purely%20from%20the%20output%20logs.%26nbsp%3B%20The%20components%20picked%20up%20during%20monitoring%20your%20installer%20caused%20a%20hard%20failure%20in%20MakePri.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20recently%20looked%20into%20a%20similar%20issue%20where%20underlying%20components%20of%20makepri%20were%20unable%20to%20handle%20a%20generated%20manifest%20having%20a%20com%20interace-%26gt%3Btypelib%20entry%20without%20a%20version%20and%20a%20matching%20(By%20Guid)%20com%20typelib%20entry%20with%20a%20version.%20The%20error%20surfaced%20in%20the%20same%20manner.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETry%20checking%20your%20partial%20manifest%20file%2C%20visible%20in%20the%20logs%20as%20file%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Evn5adl2j.gzy.Manifest%2C%20in%20your%20log%20output%20directory.%26nbsp%3B%20If%20you%20see%20this%20problem%2C%20unfortunately%20the%20easiest%20workaround%20today%20would%20be%20to%20purge%20or%20correct%20the%20invalid%20com%20registry%20keys%20in%20the%20registry%20while%20the%20monitoring%20process%20is%20still%20active.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EPlease%20let%20me%20know%20if%20this%20looks%20like%20your%20problem%20or%20feel%20free%20to%20share%20the%20rest%20of%20your%20log%20files%20with%20me%20privately%20for%20a%20closer%20look.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EWe%20intend%20to%20make%20identifying%20and%20resolving%20such%20issues%20easier%20in%20future%20updates%20to%20MSIX%20Packaging%20Tool.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EThanks!%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EJ%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Eames%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, I'm trying to package Chrome for Enterprise but the packaging tool is failing with the attached log.

Why would this happen ?

4 Replies

Hi Victor,

 

That particular failure is a little tricky to identify purely from the output logs.  The components picked up during monitoring your installer caused a hard failure in MakePri.

 

I recently looked into a similar issue where underlying components of makepri were unable to handle a generated manifest having a com interace->typelib entry without a version and a matching (By Guid) com typelib entry with a version. The error surfaced in the same manner.

 

Try checking your partial manifest file, visible in the logs as file vn5adl2j.gzy.Manifest, in your log output directory.  If you see this problem, unfortunately the easiest workaround today would be to purge or correct the invalid com registry keys in the registry while the monitoring process is still active.

 

Please let me know if this looks like your problem or feel free to share the rest of your log files with me privately for a closer look.

We intend to make identifying and resolving such issues easier in future updates to MSIX Packaging Tool.

 

Thanks!

James

@James Pike 

 

Hi James,

 

The problem was indeed what you described, so I could work around it :)

 

Thanks for your help !

Victor

Hi Victor,

I am also struggling with converting Google Chrome Enterprise to MSIX. I will try the workaround since it solved the issue for you. Quick question though... did you purge or correct the com registry keys?

Thanks,
Graham

@Deleted 

 

Hi Graham,

 

I've just added the version to the TypeLib 463ABECF-410D-407F-8AF5-0DF35A005CC8 from the interface with the same GUID. The version is 1.0 as in the COM TypeLib with the same GUID.

 

Hope this helps !

Victor