SSDT SSIS Extension installation failed with VS 2019 Enterprise - ssis

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

Related

build error: error building at STEP "RUN /usr/libexec/s2i/assemble"

I have faced this error with OpenShift:
error: build error: error building at STEP "RUN /usr/libexec/s2i/assemble": error while running runtime: exit status 1
This is the log:
Using SDK: 3.1.111
---> Restoring application dependencies...
Restore completed in 4.45 sec for /opt/app-root/src/PMCModel/PMCModel.csproj.
Restore completed in 13.92 sec for /opt/app-root/src/PMCBackEnd/PMCBackEnd.csproj.
---> Publishing application...
Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
/opt/rh/rh-dotnet31/root/usr/lib64/dotnet/sdk/3.1.111/Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.8 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [/opt/app-root/src/SharedModule/SharedModule.csproj]
/opt/rh/rh-dotnet31/root/usr/lib64/dotnet/sdk/3.1.111/Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.8 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [/opt/app-root/src/PMCModel/PMCModel.csproj]
error: build error: error building at STEP "RUN /usr/libexec/s2i/assemble": error while running runtime: exit status 1

SSIS .dtsx package error - Failed to start project

All, I'm using visual studio community 2019 - please see error message below. This error occurs when I try to run/execute a .dtsx package. I've registered regsvr32 dts.dll successfully, but to no avail:
Thanks for any help.

SSIS (SQL Server Integration Services) installation failed

installing the Microsoft.DataTools.IntegrationServices.exe
on a Windows 10 PC, with Visual Studio 2019 already installed,
I got this error:
Can anyone help me understand why this happens?
Thanks a lot in advance.
Luis
Here the last part of the log file:
[5CD0:13EC][2021-05-31T19:42:29]i319: Applied execute package: ISVsix,
result: 0x80131500, restart: None
[5CD0:13EC][2021-05-31T19:42:29]e000: Error 0x80131500: Failed to
execute EXE package. [0AEC:278C][2021-05-31T19:42:29]i329: Removed
package dependency provider: ISVsix, package: ISVsix
[0AEC:278C][2021-05-31T19:42:29]i351: Removing cached package: ISVsix,
from path: C:\ProgramData\Package
Cache\15160B731819F56D87A626F9A2777550340022D7
[0AEC:278C][2021-05-31T19:42:29]i326: Removed dependency:
{ab4889d7-79a3-40dc-9c9e-ccbeca99d453} on package provider:
ISVsixPreInstall, package ISVsixPreInstall
[5CD0:13EC][2021-05-31T19:42:29]i000: MainViewModel.OnPackageAction:
Install Started for package Microsoft SQL Server Integration Services
Projects Pre Install (id: ISVsixPreInstall)
[5CD0:13EC][2021-05-31T19:42:29]i000:
MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall
progress: 14 [0AEC:278C][2021-05-31T19:42:29]i301: Applying rollback
package: ISVsixPreInstall, action: Uninstall, path:
C:\ProgramData\Package
Cache\BB952DD82F1ADAE438C26E4EE6C94F84C07CB447\ISVsixPreInstall.exe,
arguments: '"C:\ProgramData\Package
Cache\BB952DD82F1ADAE438C26E4EE6C94F84C07CB447\ISVsixPreInstall.exe"
/instanceIds:"2904af6a,6f5e5ef0"
/log:"C:\Users\Luigi\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20210531194052_0_ISVsixPreInstall.log"
/u' [5CD0:13EC][2021-05-31T19:42:29]i000:
MainViewModel.OnPackageAction: Install Completed for package Microsoft
SQL Server Integration Services Projects Pre Install (id:
ISVsixPreInstall) [5CD0:13EC][2021-05-31T19:42:29]i319: Applied
rollback package: ISVsixPreInstall, result: 0x0, restart: None
[0AEC:278C][2021-05-31T19:42:29]i329: Removed package dependency
provider: ISVsixPreInstall, package: ISVsixPreInstall
[0AEC:278C][2021-05-31T19:42:29]i351: Removing cached package:
ISVsixPreInstall, from path: C:\ProgramData\Package
Cache\BB952DD82F1ADAE438C26E4EE6C94F84C07CB447
[5CD0:13EC][2021-05-31T19:42:29]i000:
MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall
progress: 100 [0AEC:278C][2021-05-31T19:42:29]i330: Removed bundle
dependency provider: {ab4889d7-79a3-40dc-9c9e-ccbeca99d453}
[0AEC:278C][2021-05-31T19:42:29]i352: Removing cached bundle:
{ab4889d7-79a3-40dc-9c9e-ccbeca99d453}, from path:
C:\ProgramData\Package Cache{ab4889d7-79a3-40dc-9c9e-ccbeca99d453}
[5CD0:13EC][2021-05-31T19:42:29]e000: MainViewModel.OnBundleAction:
Bundle action failed: Unknown error (0x80131500) (0x80131500)
[5CD0:13EC][2021-05-31T19:42:29]i399: Apply complete, result:
0x80131500, restart: None, ba requested restart: No
[5CD0:4D80][2021-05-31T19:48:12]i000: MainViewModel.OpenUrl: Opening
url:
C:\Users\Luigi\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20210531194052.log
[5CD0:4D80][2021-05-31T20:04:01]i000: MainViewModel.OpenUrl: Opening
url:
C:\Users\Luigi\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20210531194052.log
And here only the ERROR rows:
[0AEC:278C][2021-05-31T19:42:29]e000: Error 0x80131500: Process
returned error: 0x80131500 [0AEC:278C][2021-05-31T19:42:29]e000: Error
0x80131500: Failed to execute EXE package.
[5CD0:13EC][2021-05-31T19:42:29]e000: Error 0x80131500: Failed to
configure per-machine EXE package. ...
[5CD0:13EC][2021-05-31T19:42:29]e000: Error 0x80131500: Failed to
execute EXE package. ... [5CD0:13EC][2021-05-31T19:42:29]e000:
MainViewModel.OnBundleAction: Bundle action failed: Unknown error
(0x80131500) (0x80131500)
After hours trying to figure out why my installation was failing, I found a post where someone suggested to repair Visual Studio installations via VS Installer, I did it, of course this meant that the enviroment was going to be restored as new, but it solved my issue.
I hope this could help you friend, have a nice day!
For me, the reason of failure was my PC was missing some of the target packs. No need to Repair the installation.
I installed .NET 4, 4.5 and 4.7 targeting packs from VS installation media and the SSIS installation succeeded smoothly.
I solved this problem by following:
Installed all .Net Framework versions 4.X with
Visual Studio Installer
I also tried to install Microsoft.DataTools.IntegrationServices.exe on a Windows 10 PC, with Visual Studio 2019 already installed.
Try running the .exe file with "Administrator" privileges.
My error code was "Unknown error (0xffffffff) (0xFFFFFFFF)

Can't install SSRS or SSIS package from SQL Server Data Tools package onto Visual Studio 2017

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.

Mercurial side-by-side configuration is incorrect

I'm trying to install and run x64 Mercurial 3.8.3, but I'm getting the following error:
D:\Program Files\Mercurial>hg.exe
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
Running sxstrace.exe gives the following log:
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = D:\Program Files\Mercurial\hg.exe
AssemblyDirectory = D:\Program Files\Mercurial\
Application Config File =
-----------------
INFO: Parsing Manifest File D:\Program Files\Mercurial\hg.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\WINDOWS\WinSxS\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9177_none_acd40623e1d81331.manifest
INFO: Begin assembly probing.
INFO: End assembly probing.
ERROR: Activation Context generation failed.
End Activation Context Generation.
It seems like it's looking for C:\WINDOWS\WinSxS\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9177_none_acd40623e1d81331.manifest, which doesn't exist on my computer. I think this file comes from the Microsoft Visual C++ 2008 Redistributable Package (x64), but when I installed/repaired it I still get the same error.
I've also come across this same package from chocolatey, but its version history seems to indicate that its latest version is 9.0.30729.6161, not the 9.0.30729.9177 I'm looking for. I'm not sure where to find this version of the package.
I've already looked at these questions which seem very similar to my situation:
Side by Side configuration is incorrect error
Visual Studio 2012 Side by side configuration is incorrect
Edit: I've just reinstalled with x86 Mercurial and it works. Not ideal, but at least it's a workaround.
Microsoft Visual C++ 2008 Redistributable Package 9.0.30729.9177 doesn't seem to be publicly available, so I ended up reinstalling Windows. Now I can run Mercurial after installing it.