So, I wanted to view the Site Usage reports after reading a post by Joel Oleson.
I went to SharePoint Central Administration > Operations > Usage Analysis Processing. I enabled the logging there. Following the further instructions, I then enabled logging for MOSS. This is in SharePoint Central Administration > Shared Services > Usage reporting. (If you don’t do both in MOSS, it gives you an error message saying that it needs ‘Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing’ enabled. That’s why Joel mentioned it!)
I then went to view the usage for my site collection (Site Actions > Site Collection Usage Reports).
I was prompted for my username and password 3 times, which was puzzling. It looked like the HTTP Basic authentication dialog…
… and after that I got a page saying “Service Unavailable”. Worse, when I tried going back to my site, I got the same message. Checking IIS, I found the AppPool had stopped.
Examining the event log, I’ve got a bunch of errors from the .NET Runtime saying:
.NET Runtime version 2.0.50727.42 – Fatal Execution Engine Error (7A05E2B3) (80131506)
I’ve got no idea what’s going on, and can’t find any documentation. Great
More Info: Further info – I reverted my VM and tried again. I’m now getting a “401.1 Unauthorised” response on the page, but at least the AppPool isn’t dying.
I did get given a plausible answer, though I haven’t tried it yet
Comments from my old blog:
If I remember correctly this is caused by the Reporting Services components that it uses to render the pages. Somewhere there is a dependency on the service’s user profile, perhaps the Temp folder, but regardless usually there is no profile created since the service account has never been logged on interactively to the server so that the profile could be created. This results in a crash of the w3wp process which gives you the symptoms you have experienced.
I have been fixing this by logging on one time as the service onto the server which will be serving these pages.
Yup, that’s pretty much what the answer I was given was – log in once to create that profile.