Hey guys/gals,
Just wanted to pass on a solution to a problem that I ran into today in case anyone else runs into it. So today I had a customer who was simply trying to access their SharePoint Usage reports . Unfortunately when they were going into site settings and selecting the link they were receiving a 403 forbidden error.. So the first thing i checked was that the application pool account had the correct rights in SQL server (dbcreator and security admin) on the content databases in which I was accessing.
Everything looked fine and then it struck me. I wonder if the application pool account is running under the correct identity of the application pool that was running the web application that I was trying to access the usage reports through? Bingo I checked the application pool identity under IIS and it was running under Network Service (very bad because this service account does not have rights to access the content databases). So I quickly changed the application pool identity to the account which had the correct permissions above ran an IISRESET (just in case) and the usage reports were now accessible!
Another day another problem solved now if I could only keep all of the solutions I have written down on this blog in my brain that would be even better.
Cheers,
Jason Medero
WSS MVP
Need SharePoint Consulting?? Contact me