IIS 进程无法访问正在使用的文件
我们为服务器创建了 SSL 证书,当我们想要启动 IIS 时,我们收到此错误:
该进程无法访问该文件,因为该文件正在被另一个进程使用。
端口 443 似乎正在使用中。我该如何解决这个问题?或者我怎样才能知道为什么端口 443 被使用?
We created an SSL certificate for our server and when we want to start IIS we get this error:
The process cannot access the file because it is being used by another process.
Port 443 seems to be in use. How can I solve this? Or How can I learn why port 443 in being used?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
Marc B 的评论值得一个实际的答案,所以我将其粘贴在这里:
使用
netstat -b -a
在提升权限的 shell 中。它将显示所有活动端口以及连接到它们的进程。如果持有您端口的进程是 svc.exe 或其他多实例可执行文件,您可以添加-o
(感谢 Mike K 的评论)。我在我的开发机器上看到过这种情况,其中 Skype 实际上接管了端口 80 和/或 443。 要关闭和禁用 Skype 对端口 80 和端口 443 的使用和侦听,
Marc B's comment is deserving of an actual answer, so I will paste it here:
Use
netstat -b -a
in an elevated privilege shell. It'll show all active ports and the processes attached to them. You can add-o
if the process holding on to your port is svc.exe or another multi-instance executable (thanks to Mike K for the comment).I've seen this happen on my development box where Skype actually takes over port 80 and/or 443. To turn off and disable Skype usage of and listening on port 80 and port 443,
我刚刚关闭了 Skype,解决了问题。
I just closed the skype, resolved the issue.
netstat -aon 将显示哪个进程正在使用该文件。就我而言,它是 Skype,但也可以是使用它的任何进程。
在 Skype 中禁用“允许端口 80 进行传入连接”对我来说很有效。
netstat -aon will show which process is using the file. In my case it was Skype but it could be any process that uses it.
Disabling 'allow port 80 for incoming connections' in skype did the trick for me.
就我而言,我们没有 Skype,并且 netstat 没有使用端口 80 或 443 返回任何其他进程。从提升的命令提示符手动重新启动也无法解决问题。最终不得不重新启动盒子才能解决问题。
我将默认网站更改为端口 88,以防增加问题。
In my case -- we had no skype and the netstat didn't return ANY other processes using port 80 or 443. A manual restart from an elevated command prompt did not resolve the issue either. Ended up having to restart the box to clear up the issue.
I changed the default website to port 88 just in case that added to the issue.
可能是端口问题。以前我的端口是 80,现在我将其更改为 8080,然后一切正常。
it may port issue. previously my port was 80 now i change it with 8080 then everything works fine for me.