SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I can't tell exactly what's causing the 403 Forbidden error (that's literally all of the information I have in the browser regarding the error) but this is the scenario:

I navigate to my application page which creates a sub-site and applies a template.

It creates the sub-site fine (and the logs claim that the application of the template was fine).

It applies a web template - who's feature activated event receiver creates sub-directories in the new sub site's document library and applies custom content types to this document library.

Now, like I say the site is created fine - but the document library sub-directories are not there - and the content types are not applied to the doc library - so I'm assuming for some reason (relating to a 403!?) the event receiver is not being fired - or it's not getting that far.

What I've Tried/Looked Into

  • First I checked the ULS logs - there doesn't seem to be any exceptions that I can see that would cause this
  • Checked the content types actually exist in the new sub-site - they do
  • Tested again on dev machine - this is all working fine on my dev machine - so I know that it's not a case of features being deployed to the wrong level of site/site collection etc.
  • Tried removing any code from the featureactivated event receiver, still getting the 403.

Any help HUGELY appreciated.

Please note: I can access the sub site (all it's _layouts pages and the default WelcomePage) without any access problems.

share|improve this question
403's are authenticatation errors, are you the site collection owner? – Nicholas King Oct 8 '12 at 9:30
Yes, I am. I'm pretty sure it's not a permissions issue. I did consider that at first. Thanks a lot for your reply. – JᴀʏMᴇᴇ Oct 8 '12 at 9:35
A temporary workaround would be for me to include the code that creates these sub-directories and applies content types etc. in the code-behind of the application form mentioned in my OP - opinions on this approach also appreciated. – JᴀʏMᴇᴇ Oct 8 '12 at 9:49
up vote 2 down vote accepted

I had a similar problem. After I created my Web Application I received a strange error, But my Web Application was created, so I continued creating a Site Collection on it but received "403 forbidden" in the end.

These instructions helped me:

After I raised the timeout parameters in the IIS I recreated the WebApp and the Site Collection.

I hope it can be of some help for you or others.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.