如何强制注销VSS上的所有用户？
VSS 再次开始破坏我的存储库。 修复命令不允许我修复，锁定 VSS 似乎不会影响当前登录的用户——而且它不是用户，它声称唯一登录的人是管理员（通过 VSS 管理工具！）我已经关闭了 VSS 管理工具和客户端的所有实例。
VSS is resuming it's sabotage of my repository again. The repair command won't let me repair, the lock VSS doesn't seem to affect currently logged in users-- and it isn't a user, its claiming the only person logged in is admin (via the VSS admin tool!) and I have already closed all instances of the VSS admin tool and client.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
在计算机管理中，关闭所有会话并打开文件。 这很激烈，但这是我发现解决这个问题的唯一方法。 您可能还想暂时关闭共享。
In computer management, close all the sessions and open files. It's drastic, but that is the only way I found to fix it. You also might want to close the share temporarily.
我遇到了同样的问题，即使按照上面答案中的步骤操作，它也没有消失，直到我停止SQLWriter（Sql Server VSS Writer）和 >SSService（Visual SourceSafe LAN 服务）服务。
I had the same problem and even after following the steps in the answer above, it did not go away until I stopped the SQLWriter (Sql Server VSS Writer) and SSService (Visual SourceSafe LAN Service) services.
给每个人写一封邮件：
主题：VSS 紧急情况
正文：要求每个人立即断开与 VSS 的连接。 这不是演习。 我再说一遍：这不是演习。
Write a mail to everyone:
Subject: VSS Emergency
Body: Everyone is asked to disconnect immediately from VSS. This is not a drill. I repeat: this is not a drill.
重新启动机器并重试。
Reboot the machine and re-try.
还关闭所有 Visual Studio 实例，因为它们也是（或可以是）Visual Source Safe 的客户端。
Close also all Visual Studio instances since these are also (or can be) clients of Visual Source Safe.
停止 SSService（Visual SourceSafe LAN 服务）对我有用，谢谢。
它节省了很多时间和混乱......
stopping SSService (Visual SourceSafe LAN Service) worked for me, thanks.
it saved lot of time and confusions...
我每天凌晨 2:00 都会通过任务计划程序运行这个批处理文件，此时任何人都不应该登录，但他们确实登录了。 看来确实能达到目的。
我遇到的唯一问题是备份文件夹中可能有数据，这会导致分析器停止运行。 因此，如果我再次遇到该问题，我可能最终会添加一些命令将这些内容移出 data\backup 文件夹。 （在这种情况下，您必须将analyze.log 文件保留在备份文件夹中。不过，我对此还没有做足够的研究。）
我希望这会有所帮助！
I have this batch file running through the Task Scheduler 2:00 a.m. every day when no one should be logged in anyway, but they are. It seems to do the trick.
The only issue I have come across is the backup folder might have data in it, which stops analyzer in its tracks. So I might end up adding some commands to move the stuff out of the data\backup folder if I run into that issue again. (In that scenario, you have to keep the analyze.log file in the backup folder. I haven't done enough research into that, though.)
I hope this helps!