Comments (22)
  1. Anonymous says:

    Thanks! saved me from hours of binging 🙂

  2. Anonymous says:

    I can not get through to http-403–can not get into ddc to get free chips..i do not know how to fix it cause–I do not know how to fix it..if you could fix it for me…it worked yesterday but not today..i can not figure it out ..can you fix it for me –please..can
    not get into links..

  3. Fuady says:

    Hi Praveen,

    Thank you so much for your article. We experienced similar situation that sometimes the clients received 403 Forbidden. We will try to give Read permission to the Bin directory.

    My question is, how about the client is anonymous? In our SharePoint, we have enabled the Anonymous permission. Should we give read access to Everyone?

    Thank you in advance


  4. bhavik says:

    Hi Praveen,

    I am getting HTTP 403 Forbidden for /_vti_bin/client.svc and all. .svc files under /_vti_bin. Initially I was not able to browse the /_vti_bin folder itself, however I was able to resolve it by enabling Directory Browsing. But I am still unable to browse client.svc. I took Failed Request Tracing log and below is the error:


    ModuleName : ManagedPipelineHandler


    HttpStatus : 403

    HttpReason : Forbidden

    HttpSubStatus : 0

    ErrorCode : The operation completed successfully.


    Any suggestions on how to resolve this…

  5. Chris Adams says:

    Exactly what I needed.  Worked great, thanks!

  6. hi Fuady,

    Yes. By default, Everyone has Read access to the folder. But if its missing, then please grant the permissions.

    – Praveen

  7. hi Bhavik,

    Could you check if 'domainusers' is added to the ISAPI folder under 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15' ?

  8. Horst Wutscher says:

    Great Post, it helps me to fix my problem also!

  9. shohel Rana says:

    This is great. My problem is resolved.

  10. shohel Rana says:

    This is great. My problem is resolved.

  11. IgnacioR says:

    Found similar behavior post-deploy of SP1, and used this reference to guide on the troubleshooting. Effectively found the lack of ACLs in the bin directory and solved it… thanks Praveen!

  12. Tim says:

    That worked for me too.

  13. michal says:

    thanks mate. worked for me. one thing to keep in mind – it may not work if you add those permissions to folder which higher in the hierarchy.

  14. Chip Wolt says:

    [SOLVED] I had 403 on WFEs, but all worked fine from workstations. Solution: turn off the proxy on WFE.

  15. Neeraj says:

    HI All,

    we have similar experience on few of the links resulting in 403 error . we have 4 WFE servers in SP Farm and the functionality is working perfectly fine on one of the servers whereas we are having issue on rest of 3 WFE servers.

    we have tried the above recommendations but no luck yet.
    enabled request tracing logs and getting the below warning in ISAPI module.

    ModuleName IsapiModule
    Notification 128
    HttpStatus 403
    HttpReason Forbidden
    HttpSubStatus 0
    ErrorCode 0
    ErrorCode The operation completed successfully. (0x0)
    can you please recommend and share your viewpoints on priority.

  16. You, sir are a boss! Thanks for this solution.

  17. rodrigo says:

    Very useful! Helped me to solve my issue!

  18. John says:

    I was getting 403 error on custom SP 2010 login page.
    Gave "IUser" account Read access to FBA Virtual directory bin folder. It worked 🙂
    Thanks a lot.

  19. Manju says:

    I have tried in the above but it could not resolve the issue

  20. Livio Alves says:

    Worked for me!!!

  21. axman777 says:

    Thank you for this article! We were receiving this error only form the APP server in a three tier Test farm – WFE worked correctly without any issues. Checked permissions on the bin folder and Everyone with READ was missing on the APP server! Added back
    and everything is working as expected again. Thank you!

  22. Zaid says:

    hi Praveenh

    im getting the 403 error, I can use the mapped network folder ( I saved earlier on my laptop) to browse a document library but accessing the portal itself gives 403. central admin and mysites are working OK.

    I checked the bin folder which had everyone with read and I added authenticated users with the 3 permissions but still no luck 🙁 don’t know if you are monitoring this post or not I desperately need your help.

    I read through the comments you asked someone for isapi folder if it had the authenticed user or not, mine does not have authenticated users on the ISAPI folder. should I add n check.

    I don’t want to further mess it up on my own 🙁

Comments are closed.

Skip to main content