28
Hi all,
I want to install a MPOS extension package. When I run a deploy via the ModernPos project everything works. But when I try to install the extension manually via PowerShell using the ModernPos.Installer the installation runs without errors but the Modern POS says that the extension package cannot be loaded. Does anyone have a solution?
Thank you very much.
Hi,
i have same problem here, but with Store Commerce app
do you have any idea ? or solutions?
Hi, normally the certificate is automatically generated in the development environment during the build. If you don't have a certificate that matches the settings in your MPOS project, an error should occur during the build.
If you don't find the certificate and have the same problem as I had, you can try to install the ModernPos.cer. You can find it under PosSample\ModernPos\AppPackage\ModernPos_Test
Glad you are unblocked, just in case want to share the information on how to deal with that case is outlined under bullet #3 of the section Troubleshooting:
Hi all,
Thank you very much for your help. I was able to solve the problem.
I should have mentioned that the desktop tool 'Install or update Retail Modern POS' no longer worked after running the ModernPos.Installer.
The solution for me was to install the certificate (ModernPos/bld/x86/debug/<MPOS_Certificate>.pfx) under Certificates (Local Computer) > Trusted Root Certification Authorities.
After that I could run the 'Install or update Retail Modern POS' tool without any problems and the extension was recognized correctly.
>... the Modern POS says that the extension package cannot be loaded. ...
Which version of SDK you use?
>... When I run a deploy via the ModernPos project everything works. But when I try to install the extension manually via PowerShell using the ModernPos.Installer ...
What does this mean exactly - are you initiating the deployment from within PowerShell? If so - can you run the installer directly without PowerShell and see if you have the same issue?
Can re-run the deployment with --Verbosity Trace and see if there will be additional logs pointing to the failure?
>... also checked the suggestions from community.dynamics.com/.../introducing-sealed-installers. I could not see any incompatibility between Retail Server's part of the extension and MPOS. ...
Please share more details as it is not currently clear what exactly the differences are between your environment and that case outlined in the above link.
Hi chbtn did you get any solution from Microsoft that you can share?
I currently have the following issue when trying to launch the MPOS after installing the extensions. And I'm wondering if it is the same problem you had.
The package full name returned from the AppxManifest (Commerce_9.34.1.256_x86__ww0vcv2v6zyfe) does not match the name generated from the AppInstaller (Commerce_9.34.1.256_x86__d333bm6bd465r).
(The above issue I had was a result of a difference in repo.props Publisher value (CN=....) and the value of the publisher in the certificate. Basically there was a spelling error in the repo.props file)
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (