HTTP 403 Forbidden SharePoint 2013

Today  I faced an Issue in SharePoint where I got the error :"HTTP 403 Forbidden" for any site collection under a Web Application and this problem existed on Central Admin.

Error : HTTP 403 Forbidden

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.



This problem occured after I tried configuring the SSL certificate for Central admin and the other Web Application. In this attempt I managed to Crash my SharePoint Farm.

  • I have tried accessing the site from IIS with no go.

  • Did Run the SharePoint Configuration Wizard successfully. Tried accessing the Central Administration Page with no go :(
Resolution:

After Trying the above options which did not work , finally I have deleted the Central Administration site from IIS.
Run the SharePoint Products Configuration Wizard again and the Central Administration site has  been recreated. Launched Central Admin and it is UP this time.

Now that I am done with fixing CA , tried accessing the site collections under a Web Application and the same issue occurred again.

Troubleshooting done : 

Checked the Web Config file and turned off the Custom Error Mode , but did not help.
Deleted the Content database from the web app and joined it back and retried with no go.
Deleted the Web Application on Port:80 and connected to the existing Content DB and retried , no success.
After all this analysed that the problem could be in the Web Config file , that could have been altered.

Hence to isolate the issue , I extended Web Application onto another Port: 30325 , to check if the problem is with IIS and after this I was able to access the web app and associated site collections normally by adding.
To bring things to normal , I stopped the IIS Site that was created on Port:80 and changed the Port of the extended web Application from 30325 to 80.






Comments

Post a Comment

Popular posts from this blog

Migrate Secure Store Service Application from SharePoint 2013 to SharePoint 2016

Image
Migrate Secure Store Service Application Whenever we migrate SharePoint from one version to the next version , we recreate most of the service applications. However, in few cases where we have dependencies  with service applications like secure store and Managed metadata service which may have several credentials and term stores. recreating all the service IDs may be a tedious job and can easily land us in to issues. Hence, it is recommended to upgrade the Secure store service application.  Title: Steps to Migrate Secure Store Service Application from SharePoint 2013 to 2016 In on of my SharePoint Migration Projects from SharePoint 2013 to SharePoint 2016  Secure Store Service Application was one of the critical services used by the customer due to its dependency with Data Refresh Jobs from SSAS.  This article is a step by step approach to migrate Secure Store from SP 2013 to SP2016. Steps: Identify the Secure store database used in the SharePoint 2013 Database and restore a copy to th
Read more

Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm.

Image
Unable to start Secure Store Service : Error : Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm. Solution : Delete the Secure Store Service Application. Close all the browsers and runt the sharePoint Configuration wizard and retry to configure the secure store service and the issue should be fixed. If the issue still persists , start the Secure Store Service Application using the following commands. $proxy = Get-SPServiceApplicationProxy | where {$_.TypeName -eq "Secure Store Service Application Proxy"} $proxy.Status = "Online" $proxy.Update() In few cases it may happen that the Proxy service may start and the secure store service still has an error.In this case please delete the Secure Store service  and recreate using PowerShell as below : $sa = New-SPSecureStoreServiceApplication -Name "Secure Store Service Applicatio
Read more