Forum Discussion
MSIX Instal AppxManifest error 0x80070002
Hello,
i changed that info:
problem was at this place i found two registring items, is that correct? If only one item wich?
<com:TypeLib Id="00020802-0000-0000-c000-000000000046">
<com:Version VersionNumber="1.5" LocaleId="7" LibraryFlag="0" HelpDirectory="VFS\ProgramFilesX86\Microsoft Office\OFFICE11\" />
<com:Version VersionNumber="1.5" LocaleId="0" LibraryFlag="0" HelpDirectory="VFS\ProgramFilesX86\Microsoft Office\OFFICE11\">
<com:Win32Path Path="VFS\ProgramFilesX86\Microsoft Office\OFFICE11\GRAPH.EXE" /> </com:Version> </com:TypeLib>
1. If i let both after change first to version 1.5, i have the following error message: 0x80131500
2. if i delete the first item, i can create the MSIX, but if i try to instal:
Fehler bei der App-Installation. Fehlermeldung: AppxManifest.xml(2605,12): Fehler 0x80070003: Das Paket "Word2003MMV_1.0.0.0_x64__0axtw1mbg53sp" kann nicht registriert werden: Der Pfad "VFS\Users\KAS\AppData\Local\Temp\VBE" wurde nicht gefunden. (0x80070003)
Regards Karsten
The VBE issue in Manifest.xml
<com:TypeLib Id="0ed4565c-cf2a-41b8-a6f0-0bce0b5b90d5"> <com:Version VersionNumber="2.0" LocaleId="0" LibraryFlag="6" HelpDirectory="VFS\Users\KAS\AppData\Local\Temp\VBE"> <com:Win32Path Path="VFS\Users\KAS\AppData\Local\Temp\VBE\MSForms.exd" /> </com:Version> </com:TypeLib>
- James PikeJun 07, 2019Microsoft
Hi Michael,
I apologize for not noticing your thread sooner.
If my German translation is correct, the error you are seeing is related to the HelpDirectory attribute on your com interface.
Win32 COM entries are less stringent on their requirements and allow registration of help directories that do not exist. MSIX however requires that the path be valid.
This HelpDirectory attribute is probably not meaningful for your purposes, so I would just remove the entire attribute.
Let me know if that unblocks you! If not, please let me know how else I can be of assistance.
Thanks!
James
- Michael MüllerMay 07, 2019Copper Contributor
Hello with the actual MSIX Packaging Tool, we get error message again. What we can do with this extension? What we can edit in Package, that we can install it?
Fehler bei der App-Installation. Fehlermeldung: AppxManifest.xml(2663,12): Fehler 0x80070002: Das Paket "MSIXWord2003_1.0.1.0_x64__0axtw1mbg53sp" kann nicht registriert werden: Der Pfad "VFS\SystemX64" wurde nicht gefunden. (0x80070002)
<com:Interface Id="04598fc1-866c-11cf-ab7c-00aa00c08fcf" UseUniversalMarshaler="true"> <com:TypeLib Id="ac2de821-36a2-11cf-8053-00aa006009fa" VersionNumber="2.0" /> </com:Interface>
<com:TypeLib Id="ac2de821-36a2-11cf-8053-00aa006009fa"> <com:Version VersionNumber="2.0" LocaleId="0" LibraryFlag="2" HelpDirectory="VFS\SystemX64"> <com:Win32Path Path="VFS\SystemX86\FM20.DLL" ResourceId="2" /> </com:Version> </com:TypeLib>
<com:TypeLib Id="0d452ee1-e08f-101a-852e-02608c4d0bb4"> <com:Version VersionNumber="2.0" LocaleId="0" LibraryFlag="2" HelpDirectory="VFS\SystemX64"> <com:Win32Path Path="VFS\SystemX86\FM20.DLL" /> </com:Version> </com:TypeLib>
regards karsten
- Michael MüllerDec 13, 2018Copper Contributor
Hi Peyman,
i have publish the links to our package and logs in hub https://aka.ms/AA3afhr
please download there an let us know updated.
regards karsten
- Peyman ZanjaniNov 26, 2018Microsoft
The person doing the packaging needs to ensure the package is properly signed, not the end user. For information about why signing files is important, see Introduction to Code Signing.
Looking at the new error it looks like these paths do not exist in your package:
<com:TypeLib Id="0ed4565c-cf2a-41b8-a6f0-0bce0b5b90d5"> <com:Version VersionNumber="2.0" LocaleId="0" LibraryFlag="6" HelpDirectory="VFS\Users\KAS\AppData\Local\Temp\VBE"> <com:Win32Path Path="VFS\Users\KAS\AppData\Local\Temp\VBE\MSForms.exd" /> </com:Version> </com:TypeLib>
We need your full logs and your installer to investigate this further, looks like you filed a few feedback items about this, but I could not find the logs or installer attached to any of them. Let me know if you already attached them and I will follow up on why I can't see them on our end.
Can you please manually attach them to this feedback item https://aka.ms/AA3afhr?
You can find the logs at %localappdata%\packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\
Thanks,
Peyman
- Michael MüllerNov 21, 2018Copper Contributor
Hi,
Why is that depend at User?
regards Karsten
- Michael MüllerNov 21, 2018Copper Contributor
Why is that depend at User?