We decided to change the url of our main Web App. Not a problem, I think. I change the bindings, pull back the header, re-extended it and….nothing. Now I get a ‘403 Forbidden error’ and it’s driving me crazy.
But I made the problem worse…
I thought, hey, nothing on that site, I’ll create a new one. Tried that, got an error, BUT it created that one anyway and now I can’t delete it.
I didn’t build this installation I took it over after the last person left, and yes, it’s been a while since I did back end SharePoint but oh man, what the actual H, sharepoint?
Did you change the Alternate Access Maps? And is your DNS configured correctly? You don’t really have to do the URL changes in IIS, especially if you aren’t putting in the bindings manually. Typically, all you need to do is change alternate access mappings, and maybe fix broken links. Of course it’s a different story if you are using host-named site collections.
Right, update. After opening up all the permissions and confirming it wasn’t sql, I did a trace log and I found it is throwing a 404 AND a 403. The error says SPRequestModule RESOLVE_REQUEST_CACHE. Does this help? Or rather does this help anyone who can help?