SQL Server 2017安装被卡住

本文介绍了SQL Server 2017安装被卡住的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

由于某些原因，我无法在Windows 10计算机上安装SQL Server 2017.

For some reason I can't get SQL Server 2017 installed on my Windows 10 machine.

与此错误的安装程序有关的第一件事是，我必须卸载 VCRuntime 2017 才能使安装程序正常工作.

First thing to do with this buggy installer is that I had to uninstall VCRuntime 2017 in order for the installer to work.

现在，每次我尝试安装时，安装程​​序都会卡在此时:

And now, the installer is stuck at this point exactly every time I try to install it:

到目前为止我已经尝试过的:

What I've tried so far:

• 杀死msiexec进程

• 使用提及的其他参数运行安装程序完成

Setup.exe /SkipInstallerRunCheck

正在重新启动...正在重新安装...正在关闭防病毒软件...

Restarting ... reinstalling ... turning off anti-virus ...

[已解决]

该问题是由于后台下载特别是在互联网速度较低(例如python或R-support组件)的情况下永久占用的.

The problem was due to a background download that was taking forever especially on a low internet speed (i.e. python or R-support component).

[解决方案]

• 如果您确实需要 python或R-support ，只需等待下载完成
• 否则，从组件列表中取消选择 python和R-support .
• (或)从任务管理器中终止 python或R-support组件下载程序的子进程.

• If you really need python or R-support just wait until download is complete
• Else, deselect python and R-support from the component list.
• (or) kill the child process for python or R-support component downloader from task manager.

推荐答案

UPDATE :

UPDATE:

原来的实际问题是R-support组件在后台缓慢下载，从而锁定了安装GUI 没有向用户显示有关什么的通知或警告 实际发生的情况 .

The actual problem turned out to be the R-support component(s) slowly downloading in the background locking up the installation GUI with no notification or warning show to the user as to what is actually going on.

因此，看来此锁定安装问题"可能是由安装几个不同的组件引起的，至少是由 Python 或 R-support 引起的.如下所述，请检查任何可用的日志或事件日志以获取线索.

So it seems this "locked install problem" can be caused by installing several different components, at least by Python or R-support. As mentioned below, please check any available logs or event logs for clues.

总而言之，选项:

如果不需要，可以尝试取消选择要安装的组件.

如果需要组件，请完成设置，然后按照以下说明检查日志文件中的进度.验证Internet访问权限(代理吗?).

卡住了吗?

更新:"> 您看到此博客了吗 ?看起来该安装程序尝试下载并安装 Python运行时，而这可能要花很长时间. 您是代理人吗??没有直接连接到互联网?如果是这样，我想这也可能导致更多问题.可能不是原因，但值得一提.

Stuck Download?

UPDATE: Did you see this blog? Looks like the setup tries to download and install the Python runtime, and this can take forever. Are you behind a proxy btw? No direct connection to the Internet? If so I suppose this could also cause further problems. Probably not the cause, but worth a mention.

显然，您可以检查以下日志文​​件以了解安装进度:

Apparently you can check the following log file for progress for the installation:

%ProgramFiles%\Microsoft SQL Server\140\Setup Bootstrap\Log\DATE_TIME\RSetup.log

%ProgramFiles%\Microsoft SQL Server\140\Setup Bootstrap\Log\DATE_TIME\RSetup.log

必须将上述路径中的

DATE_TIME转换为您的有效值.例如: 20170804_162723 (日期部分和时间部分).

DATE_TIME in the above path must be converted to your valid values. For example: 20170804_162723 (date part and time part).

也请参见此答案: SQL Server 2016安装冻结 .您也可以尝试以下建议， 取消选择不需要的所有组件 ，以防止任何后台下载?

See this answer as well: SQL server 2016 installation freeze. You could also try the suggestion to deselect all components you do not need to prevent any background downloads?

保留以下通用调试建议.

Leaving in the general purpose debugging suggestions below.

通用建议 :根据经验，我会创建一个新的本地管理员用户，并尝试使用该帐户进行安装.这是为了避免在常规Windows使用过程中用户配置文件或注册表中发生任何不洁"或特殊情况.可能做的不多，但是有时可以轻松地完成工作.我认为值得尝试.

Generic Advice: From experience I would create a new local admin user and try to install using that account. This is to avoid any "unclean" or special conditions that have occurred in your user profile or registry during regular Windows use. Might not do much, but sometimes it gets the job done with surprising ease. Worth a try I think.

一些其他事情 :我写下了前不久的检查清单，我将其添加并查看它是否启发了一些可以帮助您的新想法.请参阅" 核心部署问题 ".从更长的首次书面记录-这些答案之一无意间变成了博客，也许很难阅读.

Some Further Things: I wrote up a little check list a while back, I'll add it and see if it inspires some new ideas that can help you. See under "Core Deployment Problems". That first "check list" was condensed from a longer and somewhat excessive first writeup - one of those answers that unintentionally turned into a blog and maybe a hard one to read.

记录 :您是否正确检查了日志文件和/或事件日志，以了解什么是线索?发生了什么?我找到了部署的最佳方法，以启用所有MSI安装的日志记录.与当您突然需要一个真实的日志文件时总是可以使用它的好处相比，它所触发的性能影响微乎其微. 您可以按照installsite上的说明启用所有MSI文件的日志记录. org (部分:" 计算机上所有设置的全局范围 ").安装后，MSI日志文件将仅位于您的 %TEMP% 文件夹中.它们有一个随机的十六进制名称，如果不需要它们，您可以定期将它们全部冲洗掉.您可以按修改日期/时间进行排序，以查找最新创建的日期/时间.

Logging: Did you check log files and / or event logs properly for clues as to what is happening? I find the best approach for deployment to enable logging for all MSI installations. The performance hit it triggers is minuscule compared to the benefit of having a real log-file always available when you suddenly need one. You can enable logging for all MSI files as explained on installsite (section: "Globally for all setups on a machine"). MSI log files will then just sit in your %TEMP% folder after installation. They have a random hex name, and you can flush them all regularly if you do not need them. You sort by modify date / time to find the latest one(s) created - obviously.

Jedi trick :如果未启用所有MSI文件的日志记录功能，您将需要回家并重新考虑生活.故事的寓意:MSI日志文件很棒.它们很冗长，但是很漂亮.有一些此处解释的提示(底部).

Jedi trick: You will want to go home and re-think your life if you don't enable logging for all MSI files. Moral of the story: MSI log files are cool. They are very verbose, but they are beautiful. There are some hints on interpreting them here (bottom).