We're working on making the interactive link of SQL Server setup's pop-up message a bit more useful than it is today, and the more specific situation where our very own SSMS introduces the problem is under review. the following steps would reach the situation : install a first SQL Server 2017 instance (no error), install SSMS 17 from the Web (no error), install a 2nd instance (error 1638).Īnyway, the important thing is that situation is covered by KBĪnd as indicated in the KB, a simple Repair of 'Microsoft Visual C++ 2015 Redistributable (圆4)' followed by a server restart should clear the problem (please check the current KB content though, as it may be updated with further details after this post is published). Note that it could happen even after SQL Server 2017 setup was executed successfully once already. Running SQL Server on a development machine is a key part in automating database deployments.Typically, running SQL Server locally is accomplished by installing SQL Server Developer edition. VS Shell installation has failed with exit code 1638. Depending on which products were installed on the server beforehand, a SQL Server 2017 setup may fail with the following error :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |