Can't install MSIX package with powershell - wpf

The problem
I am trying to install a .net core 3.1 wpf app onto a windows 2019 server using msix as the method of deployment. The windows server is up to date and should support msix, but will not install any msix package I create using the powershell command Add-AppPackage.
The packages will install on windows 10 machines if you click on the .appinstaller file and use the gui, but they will not install on the same machine if you use powershell.
What I have tried
I've went through this troubleshooting page to no avail.
I have tried different msix packages
I have tried using a local file directory
I have tried running as administrator
Code
This is an example of what I am trying to install:
Running the .appinstaller file will correctly install this uwp app.
However, this will not work:
Add-AppPackage .\TestUwp.appinstaller
Error Message
This is the error message the powershell script outputs:
Add-AppPackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened.
error 0x8007000D: Opening the package from location TestUwp.appinstaller failed.
NOTE: For additional information, look for [ActivityId] 742e8080-11e2-0000-5f0b-3374e211d601 in the
Event Log or use the command line Get-AppPackageLog -ActivityID 742e8080-11e2-0000-5f0b-3374e211d601
At line:1 char:1
+ Add-AppPackage .\TestUwp.appinstaller
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (W:\...\.appinstaller:String) [Add-AppxPackage],
FileNotFoundException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPac
kageCommand
PS W:\[file location here]> Get-AppPackageLog -ActivityID 742e8080-11e2-0000-5f0b-3374e211d601
Time ID Message
---- -- -------
4/14/2020 9:17:50 AM 603 Started deployment Add operation on a package with main
parameter TestUwp.appinstaller and Options 0 and 0. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help
diagnosing app deployment issues.
4/14/2020 9:17:50 AM 465 error 0x8007000D: Opening the package from location
TestUwp.appinstaller failed.
4/14/2020 9:17:50 AM 403 error 0x8007000D: Failure to get staging session for:
file:///W:/[file location here]/TestUwp.appinstaller.
4/14/2020 9:17:50 AM 404 AppX Deployment operation failed for package with error
0x80073CF0. The specific error text for this failure is: error
0x8007000D: Opening the package from location
TestUwp.appinstaller failed.

When you use:
Add-AppxPackage .\TestUwp.appinstaller
The path will be mapped to the positional parameter -Path. This parameter is designed to specify the path to the app package. But you are not installing the app directly. You are using an app installer file. To install from that, use:
Add-AppxPackage -AppInstallerFile .\TestUwp.appinstaller
With this command, I was able to install your package successfully.

Related

Could not install IdentityServer3.AccessTokenValidation in .netframework 4.61 API

I have a .NetFramework4.61 WebAPI. I am trying install IdentityServer3.AccessTokenValidation & System.IdentityModel.Tokens.Jwt using Nuget but it is giving me the below error. I also try to install using package manager console that too also failed
>Install-Package IdentityServer3.AccessTokenValidation -Version 2.14.0
>Install-Package System.IdentityModel.Tokens.Jwt -Version 6.11.0
How to resolve this issue?
Severity Code Description Project File Line Suppression State
Error Exception 'System.AggregateException' thrown when trying to add source 'http://172.16.20.241:11688/codeengines/nuget/'. Please verify all your online package sources are available.
One or more errors occurred.
Unable to load the service index for source http://172.16.20.241:11688/codeengines/nuget/.
An error occurred while sending the request.
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.16.20.241:11688
This seems to be lack of nuget source issue and you need to add the nuget source for nuget.org and then try to install the package
Add a nuget source point to https://api.nuget.org/v3/index.json on visual studio
Install the package again. You can select the package source on package management console on visual studio or specify it in the command as bellow:
PS> Install-Package IdentityServer3.AccessTokenValidation -Version 2.14.0 -Source nuget.org

No selenium server jar found error while running protractor tests in Azure DevOps

I am trying to run protractor test on Azure DevOps pipeline and getting the following error. Notice that jar file path is pointing to my local drive even when the tests are being run from Azure DevOps server. Any idea what I need to do?
Same test works when running from local machine but fails on Azure. I have the selenium-server-standalone-3.141.59.jar in my project's node_modules folder. What I don't understand is that why is it looking at my local machine (C:\Automation) when I am running test from Azure.
[13:33:31] I/launcher - Running 1 instances of WebDriver
[13:33:31] E/local - Error code: 135
[13:33:31] E/local - Error message: No selenium server jar found at
C:\Automation\my_app\node_modules\protractor\node_modules\webdriver
manager\selenium\selenium-server-standalone-3.141.59.jar. Run 'webdriver-manager
update' to download binaries.
This issue may be caused by:
selenium-server-standalone-3.141.59.jar does not exist in your project's node_modules\protractor\node_modules\webdriver-manager\selenium location.
selenium-server-standalone exists with different version.
Try to add a command line task to Update webdriver.
Useful resources:
Error: No selenium server jar found at "Location"
https://medium.com/#ganeshsirsi/protractor-end-to-end-tests-configure-on-ci-cd-tfs-vsts-azure-devops-publish-html-results-9143846f579f
https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/javascript?view=azure-devops&tabs=code#end-to-end-browser-testing

Cannot use chectl auth:login or server:shutdown

I am attempting to restart my local eclipse che server after editing some configuration. I attempted to run chectl server:stop, but got this error:
» Error: E_SHUTDOWN_CHE_SERVER_FAIL - Failed to shutdown Eclipse Che server. Login context is not set. Please login
» first.
So I attempted to login with chectl auth:login, but was again presented with an error:
Using https://che-che.169.254.109.208.nip.io/api server API URL to log in
Error: Command failed with exit code 1: oc status
error: you do not have rights to view project "default" specified in your config or the project doesn't exist
I've looked through the documentation, and couldn't find how to create a "default" project
I used chectl server:deploy --platform=docker-desktop to start my server.
I have tried other methods of deploying che, but it only worked when using Docker desktop without helm.
I am using Windows 10 home, and deploying it using Docker desktop (Engine v19.03.13) and kubernetes version v1.19.3.
Edit: I have filed a bug report on github: https://github.com/eclipse/che/issues/18355

How to install Crystal Reports for .Net 3.5 Winforms application

We have a VB.Net Winforms (x86) application that uses the freely redistributable version of Crystal Reports. Although the application works fine on my test machine, when installing on a client's machine and trying to print a report from the application, the error: The system cannot find the file specified. File name: 'CrystalDecisions.CrystalReports.Engine ... is displayed.
The inno-setup includes the CR redistributable "CRRedist2008_x86.msi" which was installed by the client during the installation. (We also tried running the "CRRedist2008_x64.msi" but received an "unsupported processor type" error).
I have read about Merge Modules that are prerequisites for .NET 1/2 (VS 2002/2005), but cannot find any useful information related to .NET 3.5 and am wondering if these files are still required and how to package and deploy them if they are in fact needed.
Any guidance on how to resolve this installation issue is much appreciated.
Edit
The Inno-Setup contains the following command that checks to see if CR is installed and if not the MSI is launched from the final setup form:
[Run]
Filename: "{app}\CRRedist2008_x86.msi"; Description: "Crystal Reports"; Flags: nowait postinstall skipifsilent; Check: EnsureCrystalReports105Installed();
The problem is that you are not actually executing the MSI file. You can see this by running your installer with /LOG and reviewing the resulting log file.
This is because MSI files cannot be directly executed -- they're data files, not programs.
To resolve this, you need to run msiexec instead, passing the MSI file as a parameter; eg.
[Run]
Filename: {sys}\msiexec.exe; Parameters: "/i ""{app}\CRRedist2008_x86.msi"""; ...
You should review the command line parameters accepted by msiexec and properties accepted by the MSI file to see if you want to do something different, eg. running the install silently instead of interactively.
Also, running it as postinstall is fine if this component is optional for your application and it can gracefully handle it not being installed. If this is not the case then you should treat it as a prerequisite instead and always install it via PrepareToInstall.

sublime text2 package control cannit find any package for installation

I am using sublime text2 on windows 7 64bit. And I installed package control successfully, then I use ctrl + alt + P and I entered :install package, then I got the error .
Package Control: Error downloading channel.
URL error [Errno 10060] A connection attempt failed
because the connected party did not properly respond after a period of time,
or established connection failed
because connected host has failed to respond downloading https://sublime.wbond.net/repositories.json.
error: Package Control: There are no packages available for installation.
it seems that I cannot access to the server, do I need to set proxy or make some network setting ?
Yes, just set the http_proxy and https_proxy variables in Package Control Settings. The stub is already given. The formats should be as follows,
http://username:password#proxyHost:proxyPort
and
https://username:password#proxyHost:proxyPort
The username:password bit is optional.

Resources