Forum Discussion
App installs with no errors, but does not fully install
MicrosoftI assume what you say about how you call regedit is about the Powershell script you use for installing the application?
After you create the MSIX package and install it, how are you launching Regedit to see the changes to the registry? The keys from HKLM\Software\ODBC should be present if you view the registry from inside the packaged app's container.
Chacon Dan Gough TIMOTHY_MANGAN
Tried using CommandInDesktopPackage from powershell. Error attached.
Installed MSIX Commander and ran. Error attached.
I assume my methodology is not working. I copy a folder called DB2 to the Desktop of my Hyper-V I use building packages. When I create the package, I launch Powershell ISE and run the commands below. Can you suggest a better way to accomplish what I'm trying to do?
Start-Process -FilePath "C:\Users\Dave\Desktop\DB2\setup.exe" # *Installs the App
Copy-Item -Path "\Users\Dave\Desktop\DB2\db2consv_zs.lic" -Destination "C:\Program Files\ibm\SQLLIB\BIN\db2consv_zs.lic" *Copies license file
Start-Process -FilePath "C:\Program Files\ibm\SQLLIB\BIN\db2licm.exe" -ArgumentList '-a db2consv_zs.lic' *Activates license
Start-Process -FilePath "C:\Windows\regedit.exe" -ArgumentList "/s C:\Users\Dave\Desktop\DB2\systemodbc.reg" # *Install System ODBC connections
Start-Process -FilePath "C:\Windows\regedit.exe" -ArgumentList "/s C:\Users\Dave\Desktop\DB2\userodbc.reg" # *Install User ODBC connections
David Hed Looking at your manifest, I see three things.
- Package includes a service. While you can package it up on an older OS, the runtime support for services inside the package exists only in new "2004" version of the OS. Please be sure that you are not testing on 1909.
- I see the FlexNet service is involved. I would suggest directly reaching out to Flexera as to how to handle apps including their service. While their experience with MSIX will be with their own packaging tool, concepts on how to handle their licensing service should be portable to any packaging tool.
- I see "Common AppData" mentioned. Packages with content under "C:\program data" will need the Psf FileRedirectionFixup, much like "AppData" and "LocalAppData".
Sorry.....I had been digging internally so much I didn't see the button for the manifest file right in front of my face. Attached is a docx with the contents.
Another possibility I did not consider. Are you building to deploy to older OSs using MSIX Core?
David Hed Well something has to generate an AppXManifest.xml file and it has to be at the root of the package or you don't have a MSIX file! It really isn't clear from the thread if you used the Microsoft MSIX Packaging Tool to generate the package, or if you are building your own using MakePri/MakeAppX.
The Packaging Tool will generate the AppXManifest.xml file for you, so if it did not then the tool should have generated an error in creating the package.
- Chacon
I couldn't see any attached logs. Could you double check?
The manifest file is inside the package. You can view it by unpacking your .msix, e.g. by using the Package editor in the MSIX Packaging Tool, or using any zip extraction utility. If you unpack the .msix, the file name will be AppxManifest.xml.
You can also find the manifest generated by the MSIX Packaging Tool in its logs folder. It will be a file with a .Manifest extension.
The way you are installing and packaging your application seems correct to me overall. I think to solve your problem we need to focus more on what happens after you install the .msix and run it.
Could you try Invoke-CommandInDesktopPackage or MSIX Commander again, if possible in a different machine?
Machine is in developer mode. App did not generate a Manifest file. Recreated package, again no Manifest file. Have attached log.
David Hed Perhaps do the following to help us understand:
- Confirm you have developer mode enabled (due to publisher name shown in attachment)
- Post the AppxManifest.xml file from the package.
