I have a WPF installer which is created using WIX, WIX Custom Bootstrapper and Burn. I have used 3.9 version WIX to create and compile the WIX file. I tried to install that installer in my machine which have already installed AVG Antivirus and my installer properly installed in it. Then I have updated the WIX to 3.11 version and compiled the WIX source file then build the WPF installer. Now, I tried to install my installer in same machine which have AVG Antivirus already installed in it. Installer failed to install and exception occurs as follows,
Error 0x800700e8: Failed to wait for child to connect to pipe.
Error 0x800700e8: Failed to connect to elevated child process.
Error 0x800700e8: Failed to actually elevate.
Error 0x800700e8: Failed to elevate.
I have disable the AVG antivirus and tried to install Installer which is build with 3.11. WPF installer installed properly in that mahcine.
Anyone suggest me on how to resolve this and any help would be appreciated?
Related
These are the prompts i face whenever i try to install the msi file.I also tried installing it by unchecking mongodb compass but still facing the same error.
I also tried installing by zip file and version 4.4.12 but still facing some error
Firewall is Disable
Antivirus in off
temp Directory is clean
and windows installer service restarted
the windows installer service could not be accessed, this can occur if you are running windows in safe mode, or if the windows installer is not correctly installed contact your support personnel for assistance mongodb win 10
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
When trying to create a 64 bit MSIX package using the Publish command in a VS 2019 WPF packaging project,
we are getting the following error 'wappublish\win-x64\project.assets.json' not found... Run a NuGet package restore to generate this file'.
The packaging project itself builds fine and can be debugged. Running 'dotnet restore' from the package manager console does not help. We have noticed there is no win-x64 directory created under wappublish.
We are using VS 2019 16.7.4 Community Edition. Anyone any ideas what could cause this.
Thanks
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.
I have a build definition in TFS that compile my code, then using a post build event, I create a Setup.exe file using Installshield.
Using Release Management I am able to deploy the installer to a machine and start the installation process using the tool RunCommandLine, I add the required parameters to the setup.exe so it will install the application silently (using an answer file to avoid user interaction). This process works smoothly!!!
I want to go far, so I tried to launch a release from a gated check-in....change the build template, install the release management client in the build agent, configure my build definition......I performed a small change in my code, then a check-in.....it compiles in the server, and start the release process: deploy the installer and start the installation process using the tool RunCommandLine, I add the required parameters to the setup.exe so it will install the application silently.....but I got a timeout so the release was rejected. I check the machine and found that the setup.exe was still running 0% CPU usage.....very strange.
Checking the build log I found that the command line used by msbuild to launch the release process is something like this:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\ReleaseManagementBuild.exe -tfs "http://tfs:8080/tfs/Mycollection" -tp "Project1" -bd "Mybuild" -bn "Mybuild_20150623_15.1.0.9" -ts "QA" -nologo
I ran it, and the behavior was the same: the installer got stuck...0% CPU Usage.....Release rejected by timeout.....
So...I open Release Management Client look for the recently created release, and click in the option "Retry failed deployment"....It works!!!! the installer install!!! it does not hangs!!!
I was able to reproduce this behavior several times:
Release launched from Release Management Console......Works
Release launched from ReleaseManagementBuild.exe .......Does not works (Setup.exe hangs)
Any suggestion??