Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
这是(某种程度上)此问题的重复< /a> 这为我解决了这个问题。
来自该帖子:
IIS 7 还创建“IUSR”作为通过 IIS 访问文件的默认用户。因此,让用户 IUSR 具有文件/文件夹的读取权限。如何检查IUSR是否已读取Access?右键单击->文件夹->属性->安全选项卡查看 IUSR 是否在组或用户名列表中,如果否。点击编辑->添加->高级->立即查找 ->选择 IUSR 并单击“确定”四次
IIS 7 还创建“IUSR”作为通过 IIS 访问文件的默认用户。因此,让用户 IUSR 具有文件/文件夹的读取权限。
如何检查IUSR是否已读取Access?右键单击->文件夹->属性->安全选项卡查看 IUSR 是否在组或用户名列表中,如果否。
点击编辑->添加->高级->立即查找 ->选择 IUSR 并单击“确定”四次
This is (sort of) a duplicate of this question which fixed the issue for me.
From that post:
IIS 7 also creates "IUSR" as default user to access files via IIS. So make user IUSR has read access to files/folders.How to check if IUSR has read Access? Right Click -> Folder -> Properties -> Security Tab See if IUSR is in Group or user names list, If No.Click Edit -> Add -> Advanced -> Find Now -> Select IUSR and click OK four times
IIS 7 also creates "IUSR" as default user to access files via IIS. So make user IUSR has read access to files/folders.
How to check if IUSR has read Access? Right Click -> Folder -> Properties -> Security Tab See if IUSR is in Group or user names list, If No.
Click Edit -> Add -> Advanced -> Find Now -> Select IUSR and click OK four times
使用失败的请求跟踪和紧凑视图可查看导致 401.3 的原因。由于它使用 VS IDE 工作正常,这意味着它在登录用户帐户的上下文中工作。维韦克
Use Failed Request Tracing & Compact View to see what is causing 401.3. Since it is working fine using VS IDE that means it's working in context of login user account.Vivek
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
暂无简介
文章 0 评论 0
接受
发布评论
评论(2)
这是(某种程度上)此问题的重复< /a> 这为我解决了这个问题。
来自该帖子:
This is (sort of) a duplicate of this question which fixed the issue for me.
From that post:
使用失败的请求跟踪和紧凑视图可查看导致 401.3 的原因。由于它使用 VS IDE 工作正常,这意味着它在登录用户帐户的上下文中工作。
维韦克
Use Failed Request Tracing & Compact View to see what is causing 401.3. Since it is working fine using VS IDE that means it's working in context of login user account.
Vivek