为什么 perforce 显示“//depot<不包含文件或文件夹>”？
从昨天开始，我一直无法连接到我们的 Perforce 服务器。展开仓库会显示消息“//depot”。有趣的是，我上周连接得很好，坐在我旁边的人也可以毫无问题地连接。
IT 部门没有说设置没有改变，也没有报告任何错误。距离多个时区也无济于事！
我希望这里有人遇到过类似的问题，并且可以告诉我要翻转哪个开关。
已解决：使用 P4Win 或 P4V 没有错误。但使用命令行 p4.exe 我收到错误“受保护的命名空间 - 访问被拒绝”。将其传递给 IT 后，必然会再次神秘地工作。听起来好像我禁用了权限然后重新启用。没有人承认任何事情，但至少我又重新站起来并开始奔跑了！
有趣的是，在收到错误消息之前我必须进入命令行。
Starting yesterday I have been unable to connect to our Perforce server. Expanding the depot gives the message "//depot ". Funny because I connected just fine last week and the folks sitting next to me can connect without problems.
IT says nothing the settings have not changed and no errors are being reported. It doesn't help that IT is multiple time zones away!
I'm hoping someone here has seen a similar problem and can tell me which switch to flip.
SOLVED: Using P4Win or P4V there are no errors. BUT using the command line p4.exe I get the error "protected namespace - access denied". Passed this onto IT and perforce mysteriously works again. Sounds like I got my permissions disabled and then re-enabled. No-one has owned up to anything but at least I'm up and running again!
Funny that I had to go to the command line before I got an error message.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
“受保护的命名空间 - 访问被拒绝” - 表示您没有指定路径的权限。如果您启用了详细日志记录，您应该在 P4V 输出窗口中看到此消息。
一种可能性是管理员在编辑组或保护表时可能意外地在您的用户名中引入了拼写错误，或者将您从组中删除，实质上删除了您的访问权限（但很容易恢复）。规范库保留对 perforce 服务器控制文件的更改，以便管理员可以检查出了什么问题，但规范库不会告诉您哪个管理员更改了它。必须在活动之前创建规格库。
"protected namespace - access denied" - means you have no permissions for the specified path. You should see this message in P4V output window if you have the detailed logging enabled.
One possibility is an administrator may have accidentally introduced a typo in your username whilst editing a group or the protection table, or removed you from a group, essentially removing your access (but easy to restore). The spec depot keeps changes to perforce server control files so an administrator could check to see what went wrong, but the spec depot does not tell you which administrator changed it. The spec depot must be created before the event.