I recently encountered a strange problem accessing my SharePoint0 sites and the SharePoint Central Administration site after installing .NET Framework 3.5 SP1 on my Windows Server 2003 running SP2.
The error message I recieved was the HTTP 403 Forbidden error. This was showing up for all sharepoint sites.
At first I tried specifying the URL along with the .aspx page name, resetting IIS, checking IIS to see if Integrated Authentication was enabled in IIS, and a bunch of other troubleshooting steps, with no luck.
I then decided to uninstall the .NET Framework 3.5 SP1 using the Add/Remove Programs, but strangely the problem persisted.
Solution:
Finally after some googling around, this is the workaround I used to fix this problem. I'm not sure if this is the best way of going about solving the problem, but it worked for me.
1. Open IIS (click Start -> Run -> and type inetmgr)
2. Expand Application Pools
3. Right-click Application Pool of your web application and click Properties.
4. Click the Identity tab in the property page
5. Under Application Pool Identity, choose Local System instead of Network Service
6. Click Apply
7. Click OK
8. Reset IIS
Hi Sarith,
ReplyDeleteIt works great and it did the trick.
Thanks,
Vijay
Did you end up leaving the .NET SP1 update uninstalled?
ReplyDeleteThanks Vijay!
ReplyDeleteAnonymous User:
Sorry for my late response.
You can perform the above mentioned steps even with having the .NET Framework 3.5 SP1 installed. It works fine in either case.
Regards,
Sarith
Hi Sarith,
ReplyDeleteDoes this works with Central Administration site? I tried all the options available i.e. Network Service, Local Service and Local system, but no success...
Now I am trying to uninstall 3.5 SP1, let see what happen... I will update.
Sanjay
Hi Sanjay,
ReplyDeleteAny luck with the Central Admin site? You could try running the Config Wizard and then checking the app pool settings.
Sarith
You can also specify a specific account for your app pool to run under. We always use a domain admin account.
ReplyDeletePlease also see this MS KB article dealing with a security feature implementation that is included with 3.5 SP1. This will affect all SP web services.
http://support.microsoft.com/default.aspx/kb/896861
@Joe : Thanks for your valuable contribution.
ReplyDeleteI had basically the exact same problem, but had to reinstall .net framework, then was stuck for a while - but found this fix:
ReplyDeletehttps://www.hensongroup.com/blogs/archive/2009/05/11/moss-2007-403-forbidden-error-after-net-framework-updates-fail-to-install.aspx
This did not work for me, I tried changing it to Local service and system. It was set for configurable with a domain user account that had administrative rights.
ReplyDeletePlease go configurable and use administrator username and password instead of local system/network service. It will surely work. I have done it.
ReplyDelete