Accessing Web Service through Application throws 403 error, accessing the web service in browser (by an admin) fixes the issue.


  • I have had this happen across a few different applications.  Most recently, on a SharePoint (WSS 3.0) instance integrated with ADFS.  Users were not reaching the Realm Selection Page when trying to load their SharePoint site.  I found a few errors in the logs (on our Resource Proxy Server) that connection attempts to our web service were getting 403 Forbidden errors.  I tried to access the web service in my browser and after a minute or two, the web service loaded.  Then I accessed the SharePoint application and it successfully loaded and the errors in the logs stopped.

    What causes this issue?  Why does it get resolved when an admin accesses the Web Service?


    Thursday, March 29, 2012 3:53 PM

All replies