I have been struggling to install SSIS extension on Visual Studio 2019 Enterprise.
Error Details:
[0BBC:47D8][2021-10-29T20:18:09]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 11
[5288:4B60][2021-10-29T20:18:12]e000: Error 0xc0000005: Process returned error: 0xc0000005
[5288:4B60][2021-10-29T20:18:12]e000: Error 0xc0000005: Failed to execute EXE package.
[0BBC:47D8][2021-10-29T20:18:12]e000: Error 0xc0000005: Failed to configure per-machine EXE package.
It seems there are issues with my computer. Below is the screenshot that the tool is not able to repair the .NET Framework. Truly I believe this is a good starting point.
Try to install .NET Framework manually from the following URL:
https://support.microsoft.com/en-us/kb/3102436
If that does not work, try to run the following tool:
https://www.microsoft.com/en-us/download/details.aspx?id=30135&wa=wsignin1.0
SSDT was installed through the Visual Studio 2017 installer, but didn't include Analysis Services, Reporting Services or Integration Services tooling. I downloaded the latest SQL Server Data Tools installer and tried installing, but only Analysis Services installed. Both SSRS and SSIS fail. Both give:
"Unknown Error 0x80131509).
I've tried several times, rebooted, re-downloaded, nothing worked. If I uninstall SSDT, VS installer will remove many other components, so didn't want to do that without seeing if someone had a solution.
Help?!
Thanks!
End of the log file shows this:
Error 0x80131509: Process returned error: 0x80131509
Error 0x80131509: Failed to execute EXE package.
Error 0x80131509: Failed to configure per-machine EXE package.
MainViewModel.OnPackageAction: Install Completed for package SQL Server Reporting Services (id: Microsoft.DataTools.ReportingServices)
Applied execute package: Microsoft.DataTools.ReportingServices, result: 0x80131509, restart: None
Error 0x80131509: Failed to execute EXE package.
Removed package dependency provider: Microsoft.DataTools.ReportingServices, package: Microsoft.DataTools.ReportingServices
Removing cached package: Microsoft.DataTools.ReportingServices, from path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\
Removed dependency: {f55a890f-6c82-4455-9bb5-2a902cdb7d87} on package provider: Microsoft.DataTools.AnalysisServices, package Microsoft.DataTools.AnalysisServices
MainViewModel.OnPackageAction: Install Started for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 15
Applying rollback package: Microsoft.DataTools.AnalysisServices, action: Uninstall, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"18a2cbc4" /logFile:"C:\Users\sspotts\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20180522091154_000_Microsoft.DataTools.AnalysisServices.log" /u:04a86fc2-dbd5-4222-848e-911638e487fe'
Error 0x80070003: Failed to CreateProcess on path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe
Error 0x80070003: Failed to execute EXE package.
Error 0x80070003: Failed to configure per-machine EXE package.
MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
Applied rollback package: Microsoft.DataTools.AnalysisServices, result: 0x80070003, restart: None
Removed package dependency provider: Microsoft.DataTools.AnalysisServices, package: Microsoft.DataTools.AnalysisServices
Removing cached package: Microsoft.DataTools.AnalysisServices, from path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\
Unable to remove cached package: Microsoft.DataTools.AnalysisServices, from path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\, reason: 0x80070003. Continuing...
MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{f55a890f-6c82-4455-9bb5-2a902cdb7d87}, resume: None, restart: None, disable resume: No
Removed bundle dependency provider: {f55a890f-6c82-4455-9bb5-2a902cdb7d87}
Removing cached bundle: {f55a890f-6c82-4455-9bb5-2a902cdb7d87}, from path: C:\ProgramData\Package Cache\{f55a890f-6c82-4455-9bb5-2a902cdb7d87}\
Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{f55a890f-6c82-4455-9bb5-2a902cdb7d87}, resume: None, restart initiated: No, disable resume: No
MainViewModel.OnBundleAction: Bundle action failed: Unknown error (0x80131509) (0x80131509)
Apply complete, result: 0x80131509, restart: None, ba requested restart: No
MainViewModel.OpenUrl: Opening url: C:\Users\sspotts\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20180522091154.log
You need to install Download Data-Tier Application Framework (DacFx) 17.4.1
before installing the SSDT. This will fix the issue
More information will be needed to diagnose the issue. Please,
Download and run https://aka.ms/vscollect
Oen an issue on https://developercommunity.visualstudio.com
Attach %TEMP%\vslogs.zip from the first step
In a cmd window, browse to the folder with the downloaded setup exe.
Then run
SSDT-Setup-ENU.exe /layout
cd payload
Microsoft.DataTools.*.VSIX
Replace the asterisk in the last command with the modules you want to install and that are located in the payload folder.
e.g.
Microsoft.DataTools.AnalysisServices.VSIX
Microsoft.DataTools.IntegrationServices.VSIX
Microsoft.DataTools.ReportingServices.VSIX
This is my biggest pet-peeve with SSDT on VS2017 - I have been using it since it was in Preview. Uninstall SSDT completely and reinstall it. See the link below and look at the accepted answer. You will need to perform some manual intervention after the installer runs its uninstall - ignore the warning about putting your computer in an unusable state.
visual studio (SSDT) 2017 unable to start debugging
Note: Whenever an update for SSDT/VS2017 comes out, they install fine. But, for some reason (and I don't know why), SSAS and SSRS have their own separate updates. In order to install them, you have to first uninstall the existing SSAS/SSRS installations (Tools -> Extensions and Updates -> Tools). I failed to do this one time for SSAS and had the pleasure of reinstalling both SSDT and VS2017. It makes no sense.
I had the same problem installing SSDT 15.6.0 with Visual Studio 2017 (versions 15.7.2 and 15.7.3). I solved the problem downloading and installing SSDT 15.7.0 (download link here).
In SSDT 15.7.0 changelog is mentioned a problem with SSRS and SSIS installation, so probably there was an issue in the installer component of versions before 15.7.0.
Here is an excerpt from the changelog regarding an installer-related issue fixed in this release of SSDT:
Fix an issue that SSAS cannot be installed before SSRS and SSIS are installed in VS 15.7.2.
My app is already published in the Store, it was built on Windows 8.1 and it perfectly works on 8.1 (desktop and tablet). However it crashes on Windows 10 just after I navigate from page that has a WebView control (though this might not be the reason). I looked at windows logs (eventvwr.msc) and found out the crash has happened in a system library.
Has anybody faced problems with Windows 8.1 apps running on Windows 10?
UPDATE 1: information from system's event log
Faulting application name: ....
Faulting module name: twinapi.appcore.dll, version: 10.0.10240.16397, time stamp: 0x55af0938
Exception code: 0xc000027b
Fault offset: : 0x0001cab9
Faulting process id: 0xe30
Faulting application start time: 0x01d0daabb7ab6d89
Faulting application path: C:\Program Files\WindowsApps.....
Faulting module path: C:\Windows\System32\twinapi.appcore.dll
Faulting package full name: ....
Faulting package-relative application ID: App
UPDATE 2
With help of this article Debugging a Windows 8.1 Store App Crash Dump I've cracked crash dump and found out the problem method in my code. That method has code that captures a screenshot of a web page with webView.CapturePreviewToStreamAsync(memoryStream); and saves it to local file. I suspect webview causes the crash because its core should differ from one on windows 8.1 (is it based on MS Edge instead of IE?).
I'm opening the default project for Windows Phone 8 using VS 2012 Professional and WP8 SDK, and am trying to configure the Windows Phone 8 WVGA 512 (default) emulator.
Using build and deploy both work. Build and deploy are both checked in the build settings for all build types. The output gives me this:
Deploy started: Project: ABCD, Configuration: Debug x86
Deploying C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap...
Connecting to Emulator WVGA 512MB...
Installing the application...
Deployment of C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap succeeded.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
However if I try to open the Simulation Dashboard to change any settings (Lock Screen -> Unlocked or "Enable Network Simulation", Visual Studio returns the error:
Connection to Windows Phone device or emulator failed.
How do I fix this issue? I have no headway on this problem because there's nothing from Google or stackoverflow, and I've tried a ton of things related to this problem (mainly the fixes for the infamous Could Not Debug Application error.)
Thanks for the help.
I have very similar problem, but in my case the simulation does not work on actual device (it used to, but now suddenly it doesn't). It does work with emulator. Deploying and debugging works fine on both.
This would suggest that it might be more general problem. Not tied to target device type in particular.
Using MonoDroid 4.0.6 and MonoDevelop, any attempt to run in an emulator fails with this error listed below:
The minSdkVersion matches the emulator's SDK version. All AVDs were created by the MonoDroid isntaller.
Detecting package list location
Getting package list from device
Installing shared runtime package on device
1849 KB/s (25866362 bytes in 13.657s)
pkg: /data/local/tmp/Mono.Android.DebugRuntime-debug.apk
Success
Installing the platform framework
1565 KB/s (16530851 bytes in 10.310s)
pkg: /data/local/tmp/Mono.Android.Platform.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Failed to install the platform framework
I solved this in 2 ways.
1) In the manifest the minSdkVersion should match or be lower than the emulator
2) (what tripped me up) The Mono DLLs References of the project should be set to the Android version too.
Both are needed. I come from a Java Android background so never thought to change anything but the manifest.