VS Shell installation has failed with exit code 1638

-
When am try to installing SQL server 2017 on windows 64 Bit system, i am getting bellow error.
TITLE: Microsoft SQL Server 2017 Release Candidate 1 (RC1) Setup
------------------------------

The following error has occurred:

VS Shell installation has failed with exit code 1638.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.800.90&EvtType=0x5B39C8B9%25401434%25403

------------------------------

Solution
Try to download and install VC++ 2015 manually from bellow link

https://www.microsoft.com/en-us/download/details.aspx?id=48145

Comments

  1. Veera Blogspot28 December 2020 at 23:19

    Thank you for your valuable information,Keep doing your best.

    MSBI Online Training India

    ReplyDelete
  2. ram k1 October 2021 at 22:21

    I sincerely appreciate you taking the time to share these information

    ReplyDelete

Post a Comment

Popular posts from this blog

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer) Chec...
Read more

On-premises data gateway December release

-
We are happy to announce that we have just released the December update for the on-premises data gateway (version 3000.154.3). This update brings the on-premises data gateway up to date with the December release of Power BI Desktop. Download:  On-premises data gateway December release This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the December version of Power BI Desktop.
Read more